Manual

EDS94AYCCA EN 5.0 - 06/2012 L 91
E94AYCCA communication manual (CANopen®)
Error messages
Possible causes and remedies
12.2 Possible causes and remedies
This chapter includes a list of all error messages of the communication module in
numerically ascending order of the error number. Possible causes and remedies as well as
responses to error messages are described in detail.
Short overview of the CANopen error messages
( 89)
MXI1: CAN module is missing or is incompatible [0x008c0017]
MXI2: CAN module is missing or is incompatible [0x008c0018]
CAN module (MXI1): bus-off [0x009d0000]
CAN module (MXI1): invalid node address 0 [0x009d0001]
Response (Lenze setting printed in bold) Setting: not possible
 None  System fault : Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information
Cause Remedy
The CANopen communication module in module slot
MXI1 is incompatible with the application.
Use a communication module supported by the
application.
Response (Lenze setting printed in bold) Setting: not possible
 None  System fault : Fault  Trouble  Quick stop by trouble  Warning locked  Warning  Information
Cause Remedy
The CANopen communication module in module slot
MXI2 is incompatible with the application.
Use a communication module supported by the
application.
Response (Lenze setting printed in bold) Setting: C13595 (; Adjustable response)
; None  System fault ; Fault ; Trouble ; Quick stop by trouble ; Warning locked ; Warning : Information
Cause Remedy
CANopen communication module in MXI1: "bus-off"
status
• Cable defect (e. g. loose contact)
• Too many faulty telegrams received.
• Two CAN nodes have the same node address.
• Eliminate fault in the ambience (e. g. EMC).
• Eliminate loose contact, tighten adapter.
• Assign different node addresses.
Setting the node address
( 33)
Response (Lenze setting printed in bold) Setting: not possible
 None  System fault  Fault  Trouble  Quick stop by trouble  Warning locked : Warning  Information
Cause Remedy
CANopen communication module in MXI1: initialisation
error
• The hardware allocation of the node address was
selected via DIP switches and the DIP switches of the
node address are all set to "0".
• Instead of the impermissible node address 0, node
address 1 is used.
• Set a different node address than "0" and carry out
mains switching.
Setting the node address
( 33)