Rockwell Automation Publication 1756-PM020F-EN-P - January 2019 33
4th Message Reply Field Bytes (in hex) Description - Symbol Instance Addressing
Reply Service D3 Write Tag Fragmented Service (Reply)
Reserved 00
General Status 00 Success
Extended Status Size 00 No extended status
The response to each request shows a General Status value of 00, Success
status indication, to indicate that the write operation was successful. No other
Reply Data is returned for this service.
See also
Write Tag Fragmented Service on page 28
Symbolic Segment Addressing and Symbol Instance Addressing return 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: 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: Unable to modify Safety Memory in the current controller state.
0x13 N/A Insufficient Request Data: Data is too small for expected parameters.
0x26 N/A The Request Path Size received was shorter or longer than expected.
0xFF 0x2104 General Error: Offset is beyond end of the requested tag.
0xFF 0x2105 General Error: Offset plus Number of Elements extends beyond the end of the requested tag.
0xFF 0x2107 General Error: Data type used in request does not match the data type of the target tag.
See also
Write Tag Fragmented Service on page 28
The Read Modify Write Tag Service modifies Tag data with individual bit
resolution. ControlLogix controllers read the Tag data, applies the logical or
modification masks or both, and writes the data the Tag. Also use the Read
Modify Write Tag Service to modify a single bit in a Tag without disturbing
other data.
See also
PCCC Commands on page 81
These are the Service Request Parameters.
Write Tag Fragmented Service Error
Codes
Read Modify Write Tag Service
Service Request Parameters