
L Firmware 1.37 - 09/2006 483
9400 HighLine | Parameter setting & configuration
Diagnostics & error analysis
Error messages of the operating system
CAN on board: Heartbeat error index 28 [0x0084001b]
CAN on board: Heartbeat error index 29 [0x0084001c]
CAN on board: Heartbeat error index 30 [0x0084001d]
CAN on board: Heartbeat error index 31 [0x0084001e]
CAN on board: Heartbeat error index 32 [0x0084001f]
CAN on board: Life guarding error [0x00840020]
Response (Lenze setting printed in bold) Setting: C00613/28 (; Adjustable response)
: None System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning ; Information
Cause Remedy
CAN on board: No heartbeat telegram received from
node 28.
See remedy for "Heartbeat error index 1".
Response (Lenze setting printed in bold) Setting: C00613/29 (; Adjustable response)
: None System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning ; Information
Cause Remedy
CAN on board: No heartbeat telegram received from
node 29.
See remedy for "Heartbeat error index 1".
Response (Lenze setting printed in bold) Setting: C00613/30 (; Adjustable response)
: None System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning ; Information
Cause Remedy
CAN on board: No heartbeat telegram received from
node 30.
See remedy for "Heartbeat error index 1".
Response (Lenze setting printed in bold) Setting: C00613/31 (; Adjustable response)
: None System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning ; Information
Cause Remedy
CAN on board: No heartbeat telegram received from
node 31.
See remedy for "Heartbeat error index 1".
Response (Lenze setting printed in bold) Setting: C00613/32 (; Adjustable response)
: None System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning ; Information
Cause Remedy
CAN on board: No heartbeat telegram received from
node 32.
See remedy for "Heartbeat error index 1".
Response (Lenze setting printed in bold) Setting: C00614 (; Adjustable response)
: None System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning ; Information
Cause Remedy
CAN on board: Cyclic node monitoring
• Slave response: Maximum time between two node
guarding telegrams (remote transmission request
telegram) from the master has been exceeded.
Select a different life guarding monitoring time or switch
off monitoring.
Komentarze do niniejszej Instrukcji