Omron NJ Series User Manual page 352

8 CIP Message Communications
The following data format is used.
Data Format
USINT
USINT
UINT
*1. For STRING data, the output format differs from the format when accessing individual elements in the
following ways.
• There are no fields for the text string lengths. Only the text strings (including NULL) are given.
• The transferred data length is not the combined lengths of the text strings, but the memory
size that is allocated to the STRING variable.
• Upper and lower bytes are reversed.
Example: The outputs will be as follows for a STRING array named s that has two elements (with the data
quantity per element is set to 4 bytes)
when s[0]="ab", and s[1] is "d".
Individual [0]: D0 00 03 00 61 62 63 (hex)
Entire array: D0 00 62 61 ?? 00 00 64 ?? ?? (hex) (??: Invalid data.)
• Handling Multi-dimensional Array
Elements for a multi-dimensional array are given in order from the deepest elements.
For example, the data is read in the following format when Var is specified for a variable defined
with UINT Var[2][2].
Data Format
USINT
USINT
UINT
UINT
UINT
UINT
The following data format is used for a BOOL array (using BOOL b[2][3] as an example).
Data Format
USINT
USINT
(WORD)
• Exceptions When Specifying the Num of Element Field
8-90
Data Type
00 hex
Num of Elem (L)
(H)
Data
:
Data
C7 hex
00 hex
Value of Var[0][0] (L)
(H)
Value of Var[0][1] (L)
(H)
Value of Var[1][0] (L)
(H)
Value of Var[1][1] (L)
(H)
C1 hex (data type code for BOOL)
00 hex
rsv rsv b[1][2]
rsv rsv rsv
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User's Manual (W506)
Data type of array elements (A1 hex is not used.)
Gives the number of elements in the array.
The actual data for the elements of the array are
given in order in the same format as when the
elements are accessed individually.*
Data type code for UINT
b[1][1] b[1][0] b[0][2]
rsv rsv rsv
b[0][1] b[0][0]
rsv rsv