Lenze I/O system 1000 - Alarms

6 PROFIBUS communication
6.11 Diagnostics
321
Lenze · I/O system 1000 · Reference Manual · DMS 5.0 EN · 09/2016 · TD17
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
6.11.5 Alarms
The alarm part of the slave diagnostic message informs about the alarm type and the cause that has
triggered an alarm. The alarm part consists of maximally 24 bytes. Maximally 1 alarm can be
reported per slave diagnostic message. The alarm part is always added as last part to the diagnostic
message if it is activated in the parameterisation.
Alarm status
If there is a diagnostic event for channel/channel group of a module, a module error may exist in
addition to a channel error. In this case, an entry is made even you have not enabled the diagnostics
for channel/channel group 0 of the module.
Structure of the alarm part, depending on the alarm type
Byte Function
x ... x + 3 Alarm status
Contains information on the alarm type.
x + 4
... x + 20
Diagnosealarm
The 20 bytes correspond to the data set 1 of the CPU diagnostics.
x + 4
... x + 7
Process alarm
The 4 bytes are module-specific and are described in the respective module chapters.
Structure of alarm status – byte x ... x + 3
Byte Function
x Bit 5 ... 0:
• 0b010100: Length of the alarm part incl. byte x
Bit 7 ... 6:
• 0b00 (fix): Code for device-related diagnostics
x + 1 Bit 6 ... 0: Alarm type
• 0b0000001: Diagnostic alarm
• 0b0000010: Process alarm
Bit 7: Code for alarm
x + 2 Bit 7 ... 0:
• 0b00000000 ... 0b00111111: ID number of the module that provides the alarm
• PROFIBUS slot 1 has the ID number ’0’
...
• PROFIBUS slot 64 has the ID number ’63’
x + 3 Bit 1, 0: Alarm type
• 0b00: Process alarm
• 0b01: Diagnostic alarm incoming
• 0b10: Diagnostic alarm outgoing
• 0b11: Reserved
Bit 2:
•0 (fixed)
Bit 7 ... 3: Alarm sequence number 0 ... 31
• 0b00000 ... 0b11111