CIP Error Codes

Service was successfully performed by the object specified.

A connection related service failed along the connection path.

Resources needed for the object to perform the requested behavior were unavailable. Further object specific information should be supplied in the object specific status field of the response.

A portion of the data supplied as an object specific data parameter of a service was invalid. The verification of the data is specified in the object definition of the object reporting the error.

The IOI segment identifier or the segment syntax was not understood by the processing node. The word offset to the first segment of the IOI that is not understood should be supplied in the first word of the object specific status field of the response. The offset is zero based and calculated from the first word following the IOI Size in the message IOI processing stops when an IOI segment error is encountered.

The IOI is referencing an object class, instance or structure element that is not known or is not contained in the processing node. The word offset to the first segment component that references something that is unknown or not present in the processing node should be supplied in the first word of the object specific status field of the response. The offset is zero based and calculated from the first word following the IOI Size in the message. IOI processing stops when an IOI destination unknown error is encountered.

Only part of the expected data was transferred.

The messaging connectionErrpr was lost.

The service requested was not implemented or defined for this class or instance object.

The value of an attribute of the object or class is invalid. The object specific status should report the attribute number and the status code of the first attribute refusing data.

An attribute in the Get_Attribute_List or Set_Attribute_List response has a non–zero status.

The object is already in the mode/state being requested by the service. The object specific status should report the object's current status.

The object cannot perform the requested service in its current mode/state. The object specific status should report the object's current status. For example, this error would be returned if a Transfer Service request was sent to the NVS Object before a Update Service request was received since the Update Service is required before data can be sent using the Transfer Service.

The requested instance of object to be created already exists.

The object attribute is not a settable attribute. The object specific status should report the number of the attribute refusing data.

The access permissions do not allow the object to perform the service. The access permissions available to the object should be reported in the extended status.

The device containing the object does not allow the object to perform the service in the device's current mode/state. The object specific status should report the device's current status. For example, a controller may have a key switch which when set to the 'hard run' state causes Service Requests to several different objects to fail, for example, program edits. This error code would then be returned.

The data to be transmitted in the response buffer is larger than the allocated response buffer, therefore, no data was transferred.

The service specified an operation that is going to fragment a primitive data value, for example, halve a REAL data type.

The service did not supply enough data to perform the specified operation.

The attribute specified is not defined for the class or object.

The service supplied more data than was expected (depending on the service and the object, the service may still be processed).

The object 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 prior to the requested service.

The attribute data of this object was not saved due to some failure during the attempt.

The service request packet was too large for transmission on a network in the path to the destination. The bridge 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 bridge device was forced to abort the service.

The service did not supply an attribute in a list of attributes that was needed by the service to perform the requested behavior.

The service is returning the list of attributes supplied with status information for those attributes that were invalid.

An embedded service resulted in an error.

A service failed because of an error condition related to the processing of a connection related service. This can occur during connected and unconnected messaging. The same extended status codes used for General Status Error Code 01 are returned for this error's extended status.

Obsolete.

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 error code can serve for other causes of invalid replies.

The Coordinated System Time (CST) value is not yet within the tolerance where it can accept an update. Try again.

Obsolete.

The Key Segment which was included as the first segment in the IOI does not match the destination module. The object specific status will indicate which part of the key check failed.

The Size of the IOI 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.

An attempt was made to set an attribute that cannot be set at this time.

See DeviceNet specification for details: http://www.odva.org/.

See DeviceNet specification for details: http://www.odva.org/.

This extended status code is returned when a request is rejected due to failure to match an ingress rule.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

This extended status code is returned when a request is rejected due to matching an ingress rule with action DENY.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

This extended status code is returned when a request is rejected due to matching an ingress rule with action ALLOW_INGRESS_SECURE, but the request was through a non CIP Security port.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

This extended status code is returned when a request is rejected due to failure to match an egress rule.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

This extended status code is returned when a request is rejected due to matching an egress rule with action DENY.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

This extended status code is returned when a request is rejected due to matching an egress rule with action ALLOW, but the CIPHER_LIST does not include an allowed cipher suite.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

One side of the (D)TLS connection has requested that the connection be closed.

Check that the model matches the actual communications flow.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Check that the model matches the actual communications flow.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Check the configuration.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Check the model to see if it matches actual comms flow. If so, contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Check that the model matches the actual communication flow.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Check that the module matches actual communication flow.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

For the cipher suites configured in the module, check that every target for an originator has a matching cipher suite allowed.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Please contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Check that the module matches actual communication flow. If so, contact technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

Verify that the correct device is addressed and that the project configuration includes devices supported by the CIP Security Policy. If this error persists, contact the security administrator or technical support.

This range of error codes has been reserved for future system use.

This range of error codes has been reserved for use by object and class specific services, or for development before registration.