
Chapter 1
CIP services
28
Rockwell Automation Publication 1756-PM020F-EN-P - January 2019
Message Request Field
Bytes (in hex)
Description - Symbol Instance Addressing
Request Path
20 6B
25 00 36 71
Logical Segment for Symbol Class ID
Logical Segment for Instance ID for the tag
CartonSize
Request Data
C4 00
DINT Tag Type Value
01 00
Number of elements to write (1)
0E 00 00 00
Data 0000000E=14 decimal
Message Reply Field
Bytes (in hex)
Description - Symbol Instance Addressing
Reply Service
CD
Write Tag Service (Reply)
Reserved
00
General Status
00
Success
Extended Status Size
00
No extended status
See also
CIP Services and User-created Tags
The Symbolic Segment Addressing and Symbol Instance Addressing may
returns these error codes.
Error Code (Hex)
Extended Error (Hex)
Description of Error
0x04
0x0000
A syntax error was detected decoding the Request Path.
0x05
0x0000
Request Path destination unknown: Probably instance number is not present.
0x10
0x2101
Device state conflict: keyswitch position: The requestor is changing force information in
HARD RUN mode.
0x10
0x2802
Device state conflict: Safety Status: The controller is in a state in which Safety Memory
cannot be modified.
0x13
N/A
Insufficient Request Data: Data too short for expected parameters.
0x26
N/A
The Request Path Size received was shorter or longer than expected.
0xFF
0x2105
General Error: Number of Elements extends beyond the end of the requested tag.
0xFF
0x2107
General Error: Tag type used n request does not match the target tag’s data type.
See also
The Write Tag Fragmented Service enables client applications to write to a
tag in the controller whose data will not fit into a single packet
(approximately 500 bytes). The client must issue a series of requests to the
controller to write all data using this service.
The Request Service, Request Path Size, Request Path, and Number of
Elements fields remain the same for each request. The client must change the
Write Tag Service Error Codes
Write Tag Fragmented Service