Appendices
A - 48
NX-series EtherNet/IP Coupler Unit User’s Manual (W536)
4 Write the values to the NX object
in the NX Unit with unit number 2.
0x74
NX Configuration
object
0x01 0x34
Write NX object
0x02
: : ::::
5 Write the values to the NX object
in the NX Unit with unit number
63.
0x74
NX Configuration
object
0x01 0x34
Write NX object
0x3F
6 Save the set values in the Ether-
Net/IP Coupler Unit.
0x74
NX Configuration
object
0x01 0x36
Save parameter
0x00
7 Save the set values in the NX Unit
with unit number 1.
0x74
NX Configuration
object
0x01 0x36
Save parameter
0x01
8 Save the set values in the NX Unit
with unit number 2.
0x74
NX Configuration
object
0x01 0x36
Save parameter
0x02
: : ::::
9 Save the set values in the NX Unit
with unit number 63.
0x74
NX Configuration
object
0x01 0x36
Save parameter
0x3F
10 Restart the Slave Terminal. 0x01
Identity object
0x01 0x05
Reset
Setting
not
required.
11
*1
If tag data link communications
are set in the EtherNet/IP master,
the tag data links will recover auto-
matically.
*2
--- --- --- ---
11
*3
Write the initial values of the out-
put data to the Units in the Ether-
Net/IP Slave Terminal.
*4
0x04
Assembly object
0x94 0x10
Set_Attribute
_Single
Setting
not
required.
12
*3
Change the Units in the Ether-
Net/IP Slave Terminal to the Oper-
ational state.
0x74
NX Configuration
object
0x01 0x39
Change NX state
0x00
*1. This process occurs when you use an EtherNet/IP master that supports explicit messages.
*2. If tag data link communications are not set in the EtherNet/IP master, refer to A-3-6 Reading and Writing I/O
Data for EtherNet/IP Slave Terminals A-49 on page A-1 for the method to restart I/O communications.
*3. This process is not necessary when you use an EtherNet/IP master that supports explicit messages.
*4. This is necessary to prevent invalid data from being output as soon as the Units in the EtherNet/IP Slave Ter-
minal enter the Operational state.
Step Description
CIP objects to use
Class ID Instance ID Service code
Unit
number