Omron NX701-17 Series User Manual page 55

Troubleshooting
OMRON defines component error status as Sysmac errors for the entire Sysmac Series.
You can use Sysmac errors to display errors that occur in slaves on the Sysmac Studio together with
corrections for the errors.
This allows you to detect slave errors and isolate the causes of the errors.
If a Sysmac error occurs in a slave, the values of the _EC_SlavErr system-defined variable and the ele-
ment of the _EC_SlavErrTbl system-defined variable that corresponds to the slave node address
change.
Refer to 9-1-1 How to Check for Errors for details on the values.
Additional Information
• This feature is not supported for OMRON slaves that are not Sysmac devices and slaves that
are manufactured by other companies. Check the error detection methods for each slave.
• Before you reset an error from the NJ/NX-series EtherCAT master, make sure you confirm the
cause of the error in the slave.
• Sysmac errors are not displayed on the Troubleshooting Dialog Box when the slaves are in Init
state. When a slave in Init state where a Sysmac error was detected is connected, you cannot
confirm the Sysmac error that was detected by the slave until communications are restarted
with that slave. Therefore, if an error that results in a slave going to Init state and a slave Sys-
mac error are detected at the same time, first reset the slave Init state, restart communications
with the slave, and then check the Sysmac error. Then, eliminate the cause of the error and
reset the error. Refer to 9-2-2 Error Descriptions for the errors that result in the Slave entering
Init state.
• If you delete the assignment of the Sysmac error status from the processing data communica-
tions data, e.g., to reduce the load on the EtherCAT communications line, you will not be able
to use the Sysmac error status in troubleshooting. (To delete the assignment, edit the PDO
map settings in the EtherCAT master settings on the Sysmac Studio so that the map object
that is mapped to object 2002 hex is not selected.) If you do so, you can detect errors that
occur in the slave applications other than communications errors only through the transmis-
sion of emergency messages or status information that is mapped for other process data com-
munications. Use emergency messages and other status information for which PDOs are
mapped to detect slave errors in this case. Transmission of emergency messages is disabled
by default for OMRON slaves.
• When the EtherCAT master detects an emergency message from a slave, the _EC_SlavEmergErr
system-defined variable changes to TRUE. Check the contents of the emergency message from
the slave on the Troubleshooting Dialog Box.
• Refer to Section 9 Troubleshooting for details on checking for errors and corrections.
NJ/NX-series CPU Unit Built-in EtherCAT Port User's Manual (W505)
2 Part Names and Slave Settings
2
2-13