Address Name / seng range / [default seng] Info
0x2006:028 Error history buer: Message 22
•
Read only
Error history buer entry 23
0x2006:029 Error history buer: Message 23
•
Read only
Error history buer entry 24
0x2006:030 Error history buer: Message 24
•
Read only
Error history buer entry 25
0x2006:031 Error history buer: Message 25
•
Read only
Error history buer entry 26
0x2006:032 Error history buer: Message 26
•
Read only
Error history buer entry 27
0x2006:033 Error history buer: Message 27
•
Read only
Error history buer entry 28
0x2006:034 Error history buer: Message 28
•
Read only
Error history buer entry 29
0x2006:035 Error history buer: Message 29
•
Read only
Error history buer entry 30
0x2006:036 Error history buer: Message 30
•
Read only
Error history buer entry 31
0x2006:037 Error history buer: Message 31
•
Read only
Error history buer entry 32
Structure of the messages
The following example shows the detailed structure of one of the following messages (param-
eter 0x2006:006 ... 0x2006:037):
Message:
00E010431201 00520B0473FC010005009900 01
Meaning: Diag code Message type Text ID Time stamp in [ns] Flag param. 1 Parameter 1
Data type: U32 U16 U16 U64 U16 U8
Hex value: 0x4310 E000 0x0112 0x0099 0x0001 FC73 040B 5200 0x0005 0x01
Notes:
•
The upper 16 bits of the "Diag Code" contain the error code (in the example "0x4310").
•
Bit 0 ... 3 of the message type contain the error type (0: Info, 1: Warning, 2: Trouble,
3: Fault).
•
Convert me stamp: 0x0001 FC73 040B 5200 = 559045896000000 ns = 6 days, 11 hours,
17 minutes, 25 seconds
•
The ag for parameter 1 has no meaning for decoding the message.
•
The parameter 1 contains the counter for successive, idencal events.
17.3.1 Read out error history buer
There are two dierent opons to read individual messages of the "error history memory" (in
the logbook) from an external control or visualizaon system:
a)
Via the standard path dened by "ETG 1020" (EtherCat Technology Group)
b)
Via simple parameter access to messages in the "error history memory"
Opon (b) is described here.
You read diagnosc messages via simple parameter access to the "error history memory".
Diagnoscs and fault eliminaon
Error history buer
Read out error history buer
597