Appendices
A - 14
NX-series EtherNet/IP Coupler Unit User’s Manual (W536)
Format for Normal Response
Format for Error Response
CIP error code
Precautions for Correct Use
• If you do not use tag data link communications but want to input and output data with an NX
Unit, use this service and set the NX Unit to Operational state in advance.
• NX-series Safety Units do not support Change NX state.
• If you execute Change NX Unit state when tag data link communications are established, a
Device state conflict error occurs and the state of the NX Unit does not change. Restart the
EtherNet/IP Unit to enable any changes made with Change NX state.
• You cannot establish tag data link communications during execution of Change NX state.
• To confirm from the user program that I/O data communications for an NX Unit are possible,
use NX Unit Message Enabled Status in the I/O data. To check the Slave Terminal status,
use Slave Terminal Status in the I/O data. For details, refer to Details of I/O Data in the Eth-
erNet/IP Coupler Unit on page 9-15.
*2. The address is set in increments of 10 ms. If you set 0000000A hex (10 decimal), the time will be 10 ms. If
you set 0036EE80 hex (3,600,000 decimal), the time will be 1 hour.
Parameter name Description
Data
type
Value
(hex)
Reply Service Reply to Change NX state service USINT B9
Reserved Reserved USINT 00
General Status Code that indicates normal USINT 00
Size of Additional Status Size of Additional status USINT 00
Parameter name Description
Data
type
Value (hex)
Reply Service Reply to Change NX state service USINT B9
Reserved Reserved USINT 00
General Status Current error code defined by CIP USINT Current error code
Size of Additional Status Size of Additional status USINT
00
*1
*1. If the general status code in the response code is 0x1F (Vendor specific error), the value is 0x01.
Additional status Additional status UINT
Additional status
*2
*2. This is stored only when the value of Size of Additional Status is 0x01.
General status code (hex)
Error code
*1
*1. Refer to General Status Code on page A-30 for error descriptions.
02 Resource unavailable
10
Device state conflict
*2*3
*2. A drive state conflict error will occur if you execute this service when tag data link com-
munications are established.
*3. A device state conflict error will occur if you execute this service for an NX Unit for
which writing is enabled by an execution of the Switch parameter write mode object.
13 Not enough data
15 Too much data
20 Invalid parameter