TYPE ERROR :
CIP Errors (0-255) and library specific errors (256-x)
InOut:
|
Name |
Initial |
Comment |
|
0 |
Service was successfully performed by the object specified. |
|
|
16#1 |
A connection related service failed along the connection path. |
|
|
16#2 |
Resources needed for the object to perform the requested service were unavailable |
|
|
16#3 |
See Status Code 0x20, which is the preferred value to use for this condition. |
|
|
16#4 |
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. |
|
|
16#5 |
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. |
|
|
16#6 |
Only part of the expected data was transferred. |
|
|
16#7 |
The messaging connection was lost. |
|
|
16#8 |
The requested service was not implemented or was not defined for this Object Class/Instance. |
|
|
16#9 |
Invalid attribute data detected. |
|
|
16#A |
An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero status. |
|
|
16#B |
The object is already in the mode/state being requested by the service |
|
|
16#C |
The object cannot perform the requested service in its current mode/state. |
|
|
16#D |
The requested instance of object to be created already exists. |
|
|
16#E |
A request to modify a nonmodifiable attribute was received. |
|
|
16#F |
A permission/privilege check failed |
|
|
16#10 |
The device’s current mode/state prohibits the execution of the requested service. |
|
|
16#11 |
The data to be transmitted in the response buffer is larger than the allocated response buffer |
|
|
16#12 |
The service specified an operation that is going to fragment a primitive data value, i.e. half a REAL data type. |
|
|
16#13 |
The service did not supply enough data to perform the specified operation. |
|
|
16#14 |
The attribute specified in the request is not supported. |
|
|
16#15 |
The service supplied more data than was expected. |
|
|
16#16 |
The object specified does not exist in the device. |
|
|
16#17 |
The fragmentation sequence for this service is not currently active for this data. |
|
|
16#18 |
The attribute data of this object was not saved prior to the requested service. |
|
|
16#19 |
The attribute data of this object was not saved due to a failure during the attempt. |
|
|
16#1A |
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. |
|
|
16#1B |
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. |
|
|
16#1C |
The service did not supply an attribute in a list of attributes that was needed by the service to perform the requested behavior. |
|
|
16#1D |
The service is returning the list of attributes supplied with status information for those attributes that were invalid. |
|
|
16#1E |
An embedded service resulted in an error. |
|
|
16#1F |
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 should only be performed when none of the Error Codes presented in this table or within an Object Class definition accurately reflect the error. |
|
|
16#20 |
A parameter 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. |
|
|
16#21 |
An attempt was made to write to a write-once medium (e.g. WORM drive, PROM) that has already been written, or to modify a value that cannot be changed once established. |
|
|
16#22 |
An invalid reply is received (e.g. 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. |
|
|
16#23 |
The message received is larger than the receiving buffer can handle. The entire message was discarded. |
|
|
16#24 |
The format of the received message is not supported by the server. |
|
|
16#25 |
The Key Segment that was included as the first segment in the path does not match the destination module. The object specific status shall indicate which part of the key check failed. |
|
|
16#26 |
The size of the path which 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. |
|
|
16#27 |
An attempt was made to set an attribute that is not able to be set at this time. |
|
|
16#28 |
The Member ID specified in the request does not exist in the specified Class/Instance/Attribute |
|
|
16#29 |
A request to modify a non-modifiable member was received |
|
|
16#2A |
This error code may 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 settable. |
|
|
16#2B |
A CIP to Modbus translator received an unknown Modbus Exception Code. |
|
|
16#2C |
A request to read a non-readable attribute was received |
|
|
16#2D |
The requested object instance cannot be deleted |
|
|
16#2E |
The object supports the service, but not for the designated application path (e.g. attribute). NOTE: Not to be used for any set service (use General Status Code 0x0E or 0x29 instead) |
|
|
16#100 |
Request timed out. |
|
|
IEtherNetIPService is not implemented. |
||
|
No physical connection. |
||
|
Wrong input value NULL. |
||
|
Size of data unacceptable. |
||
|
Version missmatch. Device implements not the same version of interface for the called method. |
||
|
Not enough memory |
||
|
An unknown error occured. |
||
|
Service was aborted |
