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 slave whose
process data communications are not possible, is detected for Sysmac errors. To display the
Sysmac errors, you need to change the state in which process data communications are pos-
sible for the slave. Therefore, if both the error that process data communications are not pos-
sible for the slave and Sysmac error occur at the same time, first remove the error that
process data communications are not possible for the slave and then make the suitable cor-
rection. Check the Sysmac error for the slave after the process data communications are re-
started with the slave. Then, remove the cause of the Sysmac error and reset the error again.
For details on the error that process data communications are not possible for the slave, refer
to
Errors in the EtherCAT Master Function Module
in the
NJ/NX-series Troubleshooting
Manual (Cat. No. W503)
. You can find it in the operation cell for each event.
• If you delete the assignment of the Sysmac error status from the processing data communi-
cations 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 communica-
tions errors only through the transmission of emergency messages or status information that
is mapped for other process data communications. Use emergency messages and other sta-
tus information for which PDOs are mapped to detect slave errors in this case. Transmission
of emergency messages is disabled by default for OMRON slaves.
Additional Information
• 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 the
NJ/NX-series Troubleshooting Manual (Cat. No. W503)
for details on checking
for errors and corrections.
Backing Up and Restoring Parameters
The Sysmac devices use an option in the version-1.0.1 ESI specifications to enable backing up and
restoring the backup parameters that are specified in the ESI files in non-volatile memory in the
slaves.
You can back up and restore the backup parameters that are stored from the Sysmac Studio.
This makes it easy to set slaves when they are replaced.
Additional Information
• If you use slaves from other manufacturers, obtain the slave information files that are compli-
ant with the version-1.0.1 ESI specifications from the slave manufacturers.
• Refer to
on page 9-28 in the for how to back up slave data from
the Sysmac Studio.
• Refer to
on page 9-30 in the for how to restore slave data from the
Sysmac Studio.
• Refer to
on page A-15 in the for details on ESI.
2 Part Names and Slave Settings
2-13
NJ/NX-series CPU Unit Built-in EtherCAT Port User's Manual (W505)
2-3
Features of Sysmac Devices
2
2-3-2
Sysmac Device Features
Summary of Contents for NJ101-10 Series
Page 10: ...Manual Structure 8 NJ NX series CPU Unit Built in EtherCAT Port User s Manual W505...
Page 80: ...3 EtherCAT Communications 3 12 NJ NX series CPU Unit Built in EtherCAT Port User s Manual W505...
Page 236: ...9 Troubleshooting 9 38 NJ NX series CPU Unit Built in EtherCAT Port User s Manual W505...
Page 274: ...Appendices A 38 NJ NX series CPU Unit Built in EtherCAT Port User s Manual W505...
Page 275: ...I Index I 1 NJ NX series CPU Unit Built in EtherCAT Port User s Manual W505 I...
Page 279: ......
