Common Codes And Structures - Allen-Bradley 1444-TSCX02-02RB User Manual

Common Codes and
Structures
Table 314 - Generic CIP Status Codes
Code Name
0x00 (0) Success
0x01 (1) Connection failure
0x02 (2) Resource unavailable
0x03 (3) Invalid parameter value
0x04 (4) Path segment error
0x05 (5) Path destination unknown
0x06 (6) Partial transfer
0x07 (7) Connection lost
0x08 (8) Service not supported
0x09 (9) Invalid attribute value
0x0A (10) Attribute list error
0x0B (11) Already in requested
mode/state
0x0C (12) Object state conflict
0x0D (13) Object already exists
0x0E (14) Attribute not settable
0x0F (15) Privilege violation
0x10 (16) Device state conflict
0x11 (17) Reply data too large
0x12 (18) Fragmentation of a primitive
value
0x13 (19) Not enough data
0x14 (20) Attribute not supported
0x15 (21) Too much data
0x16 (22) Object does not exist
0x17 (23) Service fragmentation sequence not in progress
0x18 (24) No stored attribute data
0x19 (25) Store operation failure
0x1A (26) Routing failure, request packet too large
0x1B (27) Routing failure, response packet too large
0x1C (28) Missing attribute list entry data
0x1D (29) Invalid attribute value list
Description
Service was successfully performed by the object specified.
A connection-related service failed along the connection path.
Resources are needed for the object to perform the requested service were unavailable.
See Status Code 0x20, which is the preferred value to use for this condition.
The path segment identifier or the segment syntax was not understood by the processing node. Path
processing stops when a path segment error is encountered.
The path is referencing an object class, instance, or structure element that is not known or is not
contained in the processing node. Path processing stops when a path destination unknown error is
encountered.
Only part of the expected data was transferred.
The messaging connection was lost.
The requested service was not implemented or was not defined for this Object Class/Instance.
Invalid attribute data detected.
An attribute in the Get Attribute List or Set Attribute List response has a nonzero status.
The object is already in the mode/state requested by the service.
The object cannot perform the requested service in its current mode/state
The requested instance of object to be created already exists.
A request to modify a non-modifiable attribute was received.
A permission/privilege check failed.
The current mode/state of the device prohibits the execution of the requested service.
The data to be transmitted in the response buffer is larger than the allocated response buffer.
The service specified an operation that is going to fragment a primitive data value, such as half a
REAL data type.
The service did not supply enough data to perform the specified operation.
The attribute that is specified in the request is not supported.
The service supplied more data than was expected.
The object that is specified does not exist in the device.
The fragmentation sequence for this service is not currently active for this data.
The attribute data of this object was not saved before the requested service.
The attribute data of this object was not saved due to a failure during the attempt.
The service request packet was too large for transmission on a network in the path to the
destination. The routing device was forced to abort the service.
The service response packet was too large for transmission on a network in the path from the
destination. The routing device was forced to abort the service.
The service did not supply an attribute in a list of attributes that the service needed to perform the
requested behavior.
The service is returning the list of attributes that are supplied with status information for those
attributes that were invalid.
Rockwell Automation Publication 1444-UM001D-EN-P - June 2018
CIP Objects Appendix A
541