Allen-Bradley EtherNet/IP Client Tag-Based (ABMicro800) Error Codes

Connection Manager: Connection in Use or Duplicate Forward Open.

Connection Manager: Transport Class and Trigger combination not supported.

Connection Manager: Ownership Conflict.

Connection Manager: Connection not found at target application.

Connection Manager: Invalid connection type (problem with type or priority).

Connection Manager: Invalid connection size.

Connection Manager: RPI not supported. Could also be problem with inactivity timeout.

Connection Manager: Connection Manager cannot support any more connections.

Connection Manager: Either the vendor ID or the Product Code in the key segment did not match the device.

Connection Manager: Product Type in the key segment did not match the device.

Connection Manager: Major or minor revision information in the key segment did not match the device.

Connection Manager: Invalid connection point.

Connection Manager: Invalid configuration format.

Connection Manager: Connection request fails since there is no controlling connection currently open.

Connection Manager: Target application cannot support any more connections.

Connection Manager: RPI is smaller than the Production Inhibit Time.

Connection Manager: Connection cannot be closed since the connection has timed out.

Connection Manager: Unconnected Send timed out waiting for a response.

Connection Manager: Parameter error in Unconnected send service.

Connection Manager: Message too large for Unconnected Message service.

Connection Manager: Unconnected acknowledge without reply.

Connection Manager: No buffer memory available.

Connection Manager: Network Bandwidth not available for data.

Connection Manager: No Tag filters available.

Connection Manager: Not configured to send real-time data.

Connection Manager: Port specified in Port segment not available.

Connection Manager: Link address specified in port segment not available.

Connection Manager: invalid segment type or segment value in path.

Connection Manager: Path and Connection not equal in close.

Connection Manager: Ether Segment not present or Encoded value in Network Segment is invalid.

Connection Manager: Link address to self invalid.

Connection Manager: Resources on Secondary unavailable.

Connection Manager: Connection already established.

Connection Manager: Direct connection already established.

Connection Manager: Miscellaneous.

Connection Manager: Redundant connection mismatch.

Connection Manager: No more consumer resources available in the producing module.

Connection Manager: No connection resources exist for target path.

Connection Manager: Vendor specific.

Resource unavailable: Connection Manager resources are unavailable to handle service request.

Invalid parameter value.

Path segment error: The path segment identifier or the segment syntax was not understood by the processing node.

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.

Partial transfer: Only part of the expected Data was transferred.

Connection lost: The messaging connection was lost.

Service not supported: The requested service was not implemented or was not defined for this Object Class/Instance.

Invalid attribute value: Invalid attribute Data detected.

Attribute list error: An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero status.

Already in requested mode/state: The object is already in the mode/state being requested by the service.

Object state conflict: The object cannot perform the requested service in its current mode/state.

Object already exists: The requested instance of object to be created already exists.

Attribute not settable: A request to modify non-modifiable attribute was received.

Privilege violation: A permission/privilege check failed.

Device state conflict: The device's current mode/state prohibits the execution of the requested service.

Reply Data too large: The Data to be transmitted in the response buffer is larger than the allocated response buffer.

Fragmentation of a primitive value: The service specified an operation that is going to fragment a primitive Data value. For example, trying to send a 2 byte value to a REAL Data type (4 byte).

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

Attribute not supported: The attribute specified in the request is not supported.

Too much data: The service supplied more Data than was expected.

Object does not exist: The object specified does not exist in the device.

Service fragmentation sequence not in progress: The fragmentation sequence for this service is not currently active for this data.

No stored attribute data: The attribute Data of this object was no saved prior to the requested service.

Store operation failure: The attribute Data of this object was not saved due to a failure during the attempt.

Routing failure, request packet too large: The service request packet was too large for transmission on a network in the path to the destination.

Routing failure, response packet too large: The service response packet was too large for transmission on a network in the path from the destination.

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.

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

Embedded service error: See Service Packet error list (PLC-498 Error codes) below:

Vendor specific error: A vendor specific error has been encountered. This occurs when none of the specified errors relate to the error in the device.

Invalid parameter: A parameter associated with the request was invalid. This code is used when a parameter does meet the requirements defined in an Application Object specification.

Write-once value or medium already written: An attempt was made to write to a write-once-medium that has already been written or to modify a value that cannot be change once established.

Invalid Reply Received: An invalid reply is received (example: service code sent doesn't match service code received.).

Reserved by CIP for future extensions.

Reserved by CIP for future extensions.

Key failure in path: The key segment 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.

Path Size Invalid: 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.

Unexpected attribute in list: An attempt was made to set an attribute that is not able to be set at this time.

Invalid Member ID: The Member ID specified in the request does not exist in the specified Class/Instance/Attribute.

Member not settable: A request to modify a non-modifiable member was received.

Group 2 only server general failure: 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.

Reserved by CIP for future extensions.