5 Troubleshooting
5 - 16
CJ-series EtherCAT Slave Units Operation Manual (W541)
5-4 Troubleshooting with Emergency
Messages
EtherCAT Slave Units are able to report emergency messages to the EtherCAT master by using the
SDO communications if they detect errors.
When the power supply is turned ON, the EtherCAT Slave Unit always starts with the Notification set-
ting.
Emergency messages cannot be sent while there is an EtherCAT communications error.
Refer to 5-4-2 Emergency Error Codes on page 5-16 for the meanings of the emergency messages.
The following table lists the emergency error codes that are used with EtherCAT Slave Units and the
meaning of each error.
5-4-1 Emergency Message Notification
Byte 0 1 2 3 4 5 6 7
Contents Emergency error code Reserved 0000 hex
5-4-2 Emergency Error Codes
Error
code
(hex)
Error type Error name Description
Notification to
EtherCAT
master
Corrective action
5530 Memory access
error
Special Unit
Memory Error
An error occurred while
reading or writing the error
log.
All error log records cannot
be used during initialization
or registering an error log
record.
Yes Restart the EtherCAT
Slave Unit.
Replace the EtherCAT
Slave Unit if the error
recurs.
6140 SII Unit Verifi-
cation Error
An error occurred in the
slave information stored in
SII when the power supply
was turned ON.
No
6120 Unit error Special Unit
Error
An error occurred in the
EtherCAT Slave Unit.
Restart the CPU Unit.
Replace the EtherCAT
Slave Unit if the error
recurs.
7030 ESC Error An error occurred in the
ESC.
Replace the EtherCAT
Slave Unit if the same error
recurs when the Unit is
mounted to another CPU
Unit.
To Next Page
Loading...
Need help?
General
