26 Rockwell Automation Publication 1756-PM020F-EN-P - January 2019
Reply Data C2 00 SINT Tag Type Value
nn nn nn…nn Data for Elements 980 through 1469
4th Message Request Field Bytes (in hex) Description - Symbol Instance Addressing
Request Service 52 Read Tag Fragmented Service (Request)
Request Path Size 03 Request Path is 3 words (6 bytes) long
Request Path 20 6B
25 00 1A E0
Logical Segment for Symbol Class ID
Logical Segment for Instance ID for the tag TotalCount
Request Data D6 06 Number of elements to read (1750)
Data Offset BE 05 00 00 Start at this element (1470) and return as much will fit
4th Message Reply Field Bytes (in hex) Description - Symbol Instance Addressing
Reply Service D2 Read Tag Fragmented Service (Reply)
Reserved 00
General Status 06 Reply Data Too Large
Extended Status Size 00 No extended status
Reply Data C2 00 SINT Tag Type Value
nn nn nn…nn Data for Elements 1490 through 1749
Each response, except the last one, shows the General Status of 06, Reply
Data Too Large, to indicate that more data is present than is in this particular
frame. The last response shows the General Status of 0 indicating that the
data read did not exceed the message size limit. This means that the entire
sequence of bytes has been read.
See also
CIP Services and User-created Tags on page 41
The Symbolic Segment Addressing and Symbol Instance Addressing may
return these errors.
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.
0x06 N/A Insufficient Packet Space: Not enough room in the response buffer for all the data.
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 or Byte Offset is beyond the end of the requested tag.
Read Tag Fragmented Service
Error Codes
To Next Page
Loading...
Need help?
General
