Beckhoff EPP3504-0023 Short Manual page 220

Appendix
Support for commissioning
The DiagMessages system is to be used above all during the commissioning of the plant. The
diagnostic values e.g. in the StatusWord of the device (if available) are helpful for online diagnosis
during the subsequent continuous operation.
TwinCAT System Manager implementation
From TwinCAT 2.11 DiagMessages, if available, are displayed in the device's own interface. Operation
(collection, confirmation) also takes place via this interface.
Fig. 166: Implementation of the DiagMessage system in the TwinCAT System Manager
The operating buttons (B) and the history read out (C) can be seen on the Diag History tab (A). The
components of the message:
• Info/Warning/Error
• Acknowledge flag (N = unconfirmed, Q = confirmed)
• Time stamp
• Text ID
• Plain text message according to ESI/XML data
The meanings of the buttons are self-explanatory.
DiagMessages within the ADS Logger/Eventlogger
Since TwinCAT 3.1 build 4022 DiagMessages send by the terminal are shown by the TwinCAT ADS Logger.
Given that DiagMessages are represented IO- comprehensive at one place, commissioning will be
simplified. In addition, the logger output could be stored into a data file – hence DiagMessages are available
long-term for analysis.
DiagMessages are actually only available locally in CoE 0x10F3 in the terminal and can be read out
manually if required, e.g. via the DiagHistory mentioned above.
In the latest developments, the EtherCAT Terminals are set by default to report the presence of a
DiagMessage as emergency via EtherCAT; the event logger can then retrieve the DiagMessage. The
function is activated in the terminal via 0x10F3:05, so such terminals have the following entry in the StartUp
list by default:
Fig. 167: Startup List
220 Version: 1.2 EPP3504-0023