Diagnostics
6.2 Parameterization of the diagnostics
ASM 456 interface module
46
Operating Instructions, 07/2015, J31069-D0162-U001-A6-7618
Parameter assignment options
●
None
No other diagnostics data are reported, apart from standard diagnostics.
●
Hard errors
Extended diagnostics messages are generated in the case of the following events.
–
Hardware fault (memory test)
–
Firmware problem (checksum)
–
Reader connection interrupted
–
Short-circuit/break, if supported by hardware
–
Firmware update (message at start/end)
In the case of this diagnostics information, the Ext_Diag bit is set, that is, it is treated as
high-priority diagnostics information in the PLC (SF LED is ON)
●
Hard/soft errors low priority
In contrast to the hard errors, in this case, errors are also reported that arise during
command processing.
The diagnostics information is treated like status information, the Ext_Diag bit is not set.
●
Hard/soft errors high priority
Correspond to the hard/soft errors but the Ext_Diag bit is set.
With the diagnostics messages, a distinction is made between incoming and outgoing
diagnostics.
Incoming diagnostics
An event occurs and triggers a diagnostics message. The Ext_Diag bit is set, depending on
parameterization.
Outgoing diagnostics
The event is no longer current, a diagnostics message is output without a set Ext_Diag bit.
For events that only exist momentarily, the reset is delayed by 3 seconds.
The hard errors are supported by text messages stored in the GSD file.
