The diagnosis history file “DiagHistory.csv” collects diagnosis information. It is stored in the root directory of the user disk and provides a maximum of 2.000 entries. When 2.000 entries are reached, the oldest entry is overwritten. The maximum size of extended data is 32 bytes.
The diagnosis history can be accessed with the Automation Builder or with the IEC application.
The diagnosis history file must be interpreted according to the device and/or the fieldbus. A demonstration of how to read out and receive diagnosis history messages with the IEC application is given in an ⮫ application example.
Example entry - Diagnosis history file
An entry consists of following data:
Name |
Type |
Comment |
Example |
---|---|---|---|
timestamp |
ARRAYDT OF BYTE |
RTC time of event in milliseconds consists of diTimestamp in DT format and uiMs milliseconds. See ⮫ “Structure DIAG_VAL_TYPE” STRUCT. |
1603371910177 |
event |
BYTE |
Event type (1=comes, 2=gone). |
1 |
class |
BYTE |
Severity of error event. |
4 |
compID |
UDINT |
Component ID |
270540802 |
conn |
UDINT |
Connector |
0xb17777ac |
connIdx |
UDINT |
Connector index |
0 |
sub |
DWORD |
SubsystemID: Any number describing detail/location within device, device specific |
369098752 |
addl |
DWORD |
AdditionalID: Additional number describing detail/location within device, optional, device specific |
0 |
error |
DWORD |
Error code |
9 |
extended data |
ARRAYDT OF BYTE |
Extended diagnosis data, max. 32 bytes |
With the entries compID, conn and connID, the device generating the event is clearly identified in the device tree.
If the PLC configuration is changed, the values of this entries may be changed also.
Therefore, the diagnosis history will be deleted during each download.