Filter
Top Products
387
CIP Message Communications Appendix D
Response Codes
General Status Code
The General Status Code is stored in the response data after execution of the CMND instruction has been
completed.
General Status
Code (hex)
Status Name Description of Status
00 Success Service was successfully performed by the object specified.
01 Connection failure A connection related service failed along the connection path.
02 Resource unavailable Resources needed for the object to perform the requested service were
unavailable.
03 Invalid parameter value See Status Code 20 hex, which is the preferred value to use for this condition.
04 Path segment error The path segment identifier or the segment syntax was not understood by the
processing node. Path processing shall stop when a path segment error is
encountered.
05 Path destination
unknown
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 shall
stop when a path destination unknown error is encountered.
06 Partial transfer Only part of the expected data was transferred.
07 Connection lost The messaging connection was lost.
08 Service not supported The requested service was not implemented or was not defined for this Object
Class/Instance.
09 Invalid attribute value Invalid attribute data detected.
0A Attribute list error An attribute in the Get_Attribute_List or Set_Attribute_List response has a
non-zero status.
0B Already in requested
mode/state
The object is already in the mode/state being requested by the service.
0C Object state conflict The object cannot perform the requested service in its current mode/state.
0D Object already exists The requested instance of object to be created already exists.
0E Attribute not settable A request to modify a non-modifiable attribute was received.
0F Privilege violation A permission/privilege check failed.
10 Device state conflict The device's current mode/state prohibits the execution of the requested ser-
vice.
11 Reply data too large The data to be transmitted in the response buffer is larger than the allocated
response buffer
12 Fragmentation of a
primitive value
The service specified an operation that is going to fragment a primitive data
value, i.e. half a REAL data type.
13 Not enough data The service did not supply enough data to perform the specified operation.
14 Attribute not supported The attribute specified in the request is not supported.
15 Too much data The service supplied more data than was expected.
16 Object does not exist The object specified does not exist in the device.
17 Service fragmentation
sequence not in
progress
The fragmentation sequence for this service is not currently active for this data.
18 No stored attribute data The attribute data of this object was not saved prior to the requested service.
19 Store operation failure The attribute data of this object was not saved due to a failure during the
attempt.
1A Routing failure (request
packet too large)
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.
1B Routing failure
(response packet too
large)
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 ser-
vice.
1C Missing attribute list
entry data
The service did not supply an attribute in a list of attributes that was needed by
the service to perform the requested behavior.