Table of Contents
Advertisement
Appendix A
CIP Objects
Table 314 - Generic CIP Status Codes (continued)
0x1E (30)
Embedded service error
0x1F (31)
Vendor-specific error
0x20 (32)
Invalid parameter
0x21 (33)
Write-once value or
medium already written
0x22 (34)
Invalid reply received
0x23 (35)
Buffer overflow
0x24 (36)
Message-format error
0x25 (37)
Key failure in path
0x26 (38)
Path size invalid
0x27 (39)
Unexpected attribute in list
0x28 (40)
Invalid member ID
0x29 (41)
Member not able to be set
0x2A (42)
Group 2 only server general
failure
0x2B (43)
Unknown Modbus error
0x2C (44)
Attribute not attainable
0x2D (45)...
Reserved
0xCF (207)
0xD0 (208)...
Reserved for Object Class and service errors
0xFF (255)
General Code
Extended
Code
0x02
0x0201
0x0F
0x0F01
0x0F02
0x0F03
0x0F04
0x10
0x1001
0x01002
0x1003
542
A vendor-specific error has been encountered. The Additional Code Field of the Error Response
defines the particular error encountered. Use of this General Error Code only needs performed when
none of the Error Codes that are presented in this table or within an Object Class definition accurately
reflect the error.
A vendor-specific error has been encountered. The Additional Code Field of the Error Response
defines the particular error encountered. Use of this General Error Code only needs performed when
none of the Error Codes that are presented in this table or within an Object Class definition accurately
reflect the error.
A parameter that is associated with the request was invalid. This code is used when a parameter does
not meet the requirements of this specification and/or the requirements defined in an Application
Object Specification.
An attempt was made to write to a write-once medium (For example, WORM drive, PROM) that has
already been written, or to modify a value that cannot be changed once established.
An invalid reply is received (For example, reply Service Code does not match the request Service
Code, or reply message is shorter than the minimum expected reply size). This status code can serve
for other causes of invalid replies.
The message received is larger than the receiving buffer can handle. The entire message was
discarded.
The server does not support the format of the received message.
The Key Segment that was included as the first segment in the path does not match the destination
module. The object-specific status indicates which part of the key check failed.
The size of the path that was sent with the Service Request is either not large enough to allow the
Request to be routed to an object or too much routing data was included.
An attempt was made to set an attribute that is not able to be set currently.
The Member ID specified in the request does not exist in the specified Class/Instance/Attribute.
A request to modify a non-modifiable member was received.
This error code can only be reported by DeviceNet Group 2 Only servers with 4K or less code space
and only in place of Service not supported, Attribute not supported, and Attribute not able to be set.
A CIP to Modbus translator received an unknown Modbus Exception Code.
A request to read a non-readable attribute was received.
Reserved
This range of error codes is used to indicate Object Class specific errors. Use of this range is only
performed when none of the Error Codes that are presented in this table accurately reflect the error
that was encountered.
Description
The maximum number of class 3 connections are already in use
Intrusive services are not allowed for unconnected messages
A Set Attribute Single service is only allowed when there is an active class 3 connection that belongs to the module owner determined
by the Vendor ID and the Device Serial Number
User attempted to access a service that is limited to Class 1 access only
User attempted to access a service that is only accessible if alarm inhibit is active
An attempt to reconfigure the module was made while the module was already in program mode or in starting mode
A Set Attribute service on the Configuration Manager object was attempted while the module was in Program Mode or in Starting
Mode
Intrusive services are not allowed on the Non-Volatile Storage Object (0xA1) unless the module is in an Out of Box state without an
active class 1 connection
Rockwell Automation Publication 1444-UM001D-EN-P - June 2018
Hide quick links:
Advertisement
Table of Contents
