|
Status (Hex)
|
Description
|
|---|---|
|
01
|
Connection-related service failed along the connection path. See Also: 0x01 Extended Error Codes
|
|
02
|
Resources needed for the object to perform the requested service were unavailable.
|
|
03
|
Invalid parameter value.
|
|
04
|
Path segment error. Tag does not exist in the device.
|
|
05
|
Path destination unknown. Structure member does not exist or array element is out of range.
|
|
06
|
Partial transfer; only part of the expected data was transferred.
|
|
07
|
Loss of connection.
|
|
08
|
Service not supported. The requested service was not implemented or was not defined for this class or instance.
|
|
09
|
Invalid attribute value.
|
|
0A
|
Attribute list error.
|
|
0B
|
Object is already in the mode/state requested by the service.
|
|
0C
|
Object cannot perform the requested service in its current mode/state. Project change may be in progress. See Also: 0x0C Extended Error Codes
|
|
0D
|
Requested instance of object to be created already exists.
|
|
0E
|
A request to modify a non-editable attribute was received.
|
|
0F
|
A permission / privilege check failed.
|
|
10
|
The device’s current mode/state prohibits the execution of the requested service.
|
|
11
|
Reply data too large. The data to be transmitted in the response buffer is larger than the allocated response buffer.
|
|
12
|
The service specified an operation that would fragment a primitive data value.
|
|
13
|
Not enough data. The service did not supply enough data to perform the specified operation.
|
|
14
|
Attribute not supported.
|
|
15
|
Too much data. The service supplied more data than expected.
|
|
16
|
The object specified does not exist in the device.
|
|
17
|
The fragmentation sequence for this service is not currently active for this data.
|
|
18
|
The attribute data of this object was not saved prior to the requested service.
|
|
19
|
The attribute data of this object was not saved due to a failure during the attempt.
|
|
1A
|
Routing failure; request packet too large.
|
|
1B
|
Routing failure; response packet too large.
|
|
1C
|
Missing attribute in list entry data.
|
|
1D
|
Invalid attribute value list.
|
|
1E
|
Embedded service error. One or more services returned an error within a multiple-service packet service.
|
|
1F
|
Vendor-specific error. Consult vendor documentation. See Also: 0x1F Extended Error Codes
|
|
20
|
Invalid parameter. Parameter does not meet the requirements of the CIP specification or Omron specification. See Also: 0x20 Extended Error Codes
|
|
21
|
An attempt was made to write to a write-once medium that has already been written.
|
|
22
|
Invalid reply received. Reply service code does not match the request service code or reply message is shorter than the minimum expected reply size.
|
|
23
|
The message received is larger than the receiving buffer can handle.
|
|
24
|
The format of the received message is not supported by the server.
|
|
25
|
The key segment included as the first segment in the path does not match the destination module.
|
|
26
|
The size of the path sent with the service request is not large enough to allow the request to be routed to an object or too much routing data was included.
|
|
27
|
Unexpected attribute in list.
|
|
28
|
The member ID specified in the request does not exist in the specified class, instance, or attribute.
|
|
29
|
A request to modify a non-modifiable member was received.
|
|
2A
|
DeviceNet-specific error.
|
|
2B
|
A CIP to Modbus translator received an unknown Modbus exception code.
|
|
2C
|
A request to read a non-readable attribute was received.
|
|
2D
|
A requested object instance cannot be deleted.
|
|
2E
|
The object supports the service, but not for the designated application path (for example, attribute).
|
|
2F - CF
|
Reserved by CIP.
|
|
D0 - FF
|
Object class specific errors.
|