Omron NJ Series User Manual page 347

Request Data Format for Writing a Variable
Request Path Data
Variable name specification
Request Service Data
Data Type
AddInfo Length
(AddInfo)
Num of Element
Actual data*
Response Service Data
There is no response service data.
*1. Data to write: Store the data to write in little-endian format.
Data Type
AddInfoLength
AddInfo
NumOfElement
Actual data
Response Codes
CIP
status
00 SUCCESS
02 RESOURCE_UNAVAILABLE
04 PATH_SEGMENT_ERROR
05 PATH_DESTINATION_UNKNOWN
0C OBJECT_STATE_CONFLICT
13 NOT_ENOUGH_DATA
15 TOO_MUCH_DATA
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User's Manual (W506)
Data type of variable to write
USINT
Additional information: Field length in bytes
USINT
Additional information: CRC value of structure
(L) UINT
(H)
Code for data type of variable to write. Refer to 8-7 Variable Data Types on page 8-87.
Specify the size of the AddInfo area only when accessing a structure variable.
Set 02 hex for a structure variable. Otherwise, set 00 hex.
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.
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.
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.
Meaning
8 CIP Message Communications
Add
status
--- The service ended normally.
--- The internal processing buffer is not availa-
ble.
--- The request path specification is not cor-
rect.
--- The link was followed to the end, but the
variable was not found.
8010 Downloading, starting up
8011 There is an error in tag memory.
--- The data length was too short for the speci-
fied service.
--- The data length was too long for the speci-
fied service.
Cause
8-85
8