Request Data Format for Writing a Variable
Request Path Data
Request Service Data
Data Type USINT
AddInfo Length USINT
(AddInfo)
Num of Element (L)
(H)
Actual data*
Variable name specification
Data type of variable to write
Additional information: Field length in bytes
Additional information: CRC value of structure
UINT
Response Service Data
There is no response service data.
*1. Data to write: Store the data to write in little-endian format.
Data Type Code for data type of variable to write. Refer to 8-7 V
ariable Data Types on page 8-87.
AddInfoLength Specify the size of the AddInfo area only when accessing a structure variable.
Set 02 hex for a structure variable. Otherwise, set 00 hex.
AddInfo The CRC code of the structure definition is specified only when accessing a structure
variable.
In this case, the size of AddInfo will be 2 bytes.
NumOfElement Specify the number of elements in the array. Do not specify 0000 hex (an error will oc-
cur).
For variables other than arrays, set 0001 hex.
Actual data Specify the actual data in little-endian format.
If 0001 hex is specified for an array
, specify the actual data in the same format as when
you access a variable with the data type of the elements of the array.
Response Codes
CIP
status
Meaning
Add
status
Cause
00 SUCCESS --- The service ended normally.
02 RESOURCE_UNAVAILABLE --- The internal processing buffer is not availa-
ble.
04 PATH_SEGMENT_ERROR --- The request path specification is not cor-
rect.
05 PATH_DESTINATION_UNKNOWN --- The link was followed to the end, but the
variable was not found.
0C OBJECT_STATE_CONFLICT 8010 Downloading, starting up
8011 There is an error in tag memory.
13 NOT_ENOUGH_DATA --- The data length was too short for the speci-
fied service.
15 TOO_MUCH_DATA --- The data length was too long for the speci-
fied service.
8 CIP Message Communications
8-85
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
8-6 Read and Write Services for Variables
8
8-6-2 Write Service for Variables
To Next Page
Loading...
