Rockwell Automation Publication 1756-PM020F-EN-P - January 2019 35
Error Code (Hex)
Extended Error
(Hex)
Description of Error
0x05 0x0000 Request Path destination unknown: Probably instance number is not present.
0x10 0x2101 Device state conflict: keyswitch position: The requestor is attempting to change 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.
See also
Read Modify Write Tag Service on page 33
The Multiple Service Packet Service conducts more than one CIP request in
a single CIP explicit-message frame. Use this service to optimize CIP reads
and writes by grouping service requests together for faster request
processing.
For details on this service, see the CIP Networks Library, Volume 1,
Appendix A.
See also
Read Modify Write Tag Service on page 33
CIP services on page 13
This is an example for Multiple Service Packets.
Message Request Field Bytes (in hex) Description
Request Service 0A Multiple Service Packet Service (Request)
Request Path Size 02 Request Path is 2 words (4 bytes) long
Request Path 20 02 24 01 Logical Segment: CLass 0x02, Instance 01 (Message Router)
Request Data 02 00 Number of Services contained in this request
06 00
12 00
Offsets for each Service; from the start of the Request Data
4C
73 00
01 00
First Request: Read Tag Service
Tag name: parts
Read 1 element
4C
07 91 0B 43 6F 6E 74 72 6F 6C 57
6F 72 64 00
01 00
Second Request: Read Tag Service
Tag name: ControlWord
Read 1 element
The Multiple Service Packet Request Path contains the Message Router
object (Class 2, Instance 1). This is the destination of the Multiple Service
Packet’s Request Path. The Request Data field contains the Number of
Multiple Service Packet Service
To Next Page
Loading...
Need help?
General
