8 - 29
8 Pulse Output Units
NX-series Position Interface Units User’s Manual (W524)
8-7 I/O Refreshing Method Setting
8
8-7-4 Differences in I/O Refreshing Methods Based on the Controller
Precautions for Correct Use
• If you assign an NX Unit connected to an EtherCAT Coupler Unit as an I/O device for a MC
Function Module axis, the MC Function Module manages refreshing of the I/O data. In this
case, the MC Function Module manages refreshing of the I/O data for the entire Slave Termi-
nal, including the EtherCAT Coupler Unit.
If any of the operations or errors in the following table occur, the MC Function Module dis-
cards the Slave Terminal I/O data at that time. Refreshing of I/O data resumes when valid
data is obtained again.
From several milliseconds to several tens of milliseconds is required to resume refreshing of
I/O data, depending on the system configuration and the process data communications
cycle.
You can include an NX Unit that is not assigned to an axis in a Slave Terminal that is man-
aged by the MC Function Module, but keep in mind the above characteristics of the refresh-
ing of I/O data when you do so.
• If you want to avoid the effects of the refreshing of I/O data that is managed by the MC Func-
tion Module on NX Units that are not assigned to axes, place those NX Units on another
Slave Terminal. To use different Slave Terminals, use different EtherCAT Coupler Units and
configure the Slave Terminals so that one contains only NX Units that are assigned to axes
and one contains only NX Units that are not assigned to axes.
• To assign a Position Interface Unit to an axis in the MC Function Module, you must assign
NX Unit I/O Data Active Status in the EtherCAT Coupler Unit. Replace “” with 15,
31, 63, or 125 according to the highest NX Unit number of the EtherCAT Coupler Units.
Refer to the NX-series EtherCAT Coupler Unit User’s Manual (Cat. No. W519) for details.
Operation Using EtherCAT slaves only
Using an EtherCAT Coupler Unit +
NX Units
Intentional changes to
EtherCAT network con-
figuration elements
• Unintentional disconnection of an
EtherCAT slave or an EtherCAT
cable disconnection
• Unintentional connection of an
EtherCAT slave or an EtherCAT
cable connection
• EtherCAT slave power interrup-
tion
Same as at the left.
• Disconnection of an EtherCAT
slave due to a disconnect opera-
tion
• Connection of an EtherCAT slave
due to a connect operation
Same as at the left.
• Restarting of EtherCAT Slave Ter-
minal
• Restarting after parameters were
transferred to the Communica-
tions Coupler Unit
Unintentional changes to
EtherCAT network con-
figuration elements
None Performing an error reset when the
Slave Terminal is stopped due to an
error
To Next Page
Loading...
Need help?
General
