Allen-Bradley EtherNet/IP & ENI Adapter Error Codes

Topic: CM401

The PLC-496, PLC-497 and PLC-498 Error Codes are used to show any Errors that are generated by the connected PLC. These Error Messages include an eight digit hexadecimal value displayed embedded in the message. This value can be looked up in the specific PLC Error Tables to determine the cause of the Error. The possible PLC generated Error Codes for the Allen-Bradley EtherNet/IP communication protocol is represented by a hexadecimal value.

There are three basic application levels of messaging with the Tag-Based EtherNet/IP protocol that C-more does.

  1. EIP (sometimes called Encapsulation Header) - (Error Code PLC-496)
  2. CIP - (Error Code PLC-497)
  3. Service Packet - (Error Code PLC-498)

Errors may come back in any of these levels, depending upon the situation. The following tables show the Errors and which levels they may come back in. These Error Code tables cover possible Errors that are detected by the panel from Allen-Bradley PLC using the EtherNet/IP protocol for the ENI Adapter.

PLC-496 Error Codes

 

Note: The following errors are generated from the designated PLC, are monitored by the C-more Panel, and displayed on the Panel screen as a hexadecimal value in Panel Error Code PLC-496 message, if active. Refer to the PLC manufacturer’s documentation for additional information.

PLC Errors for Allen-Bradley EtherNet/IP Protocol — Encapsulation Errors — (Error Code 0xaaaaaaaa returned from the PLC)
Panel Error Code PLC-496 Hex value Description
0x00000001 The sender issued an invalid or unsupported encapsulation command.
0x00000002 Insufficient memory resources in the receiver to handle the command. You can get this error if the 1761-NET-ENI cannot connect to the PLC serially.
0x00000003 Poorly formed or incorrect Data in the Data portion of the encapsulation message.
0x00000004 -0x00000063 Reserved for legacy (Rockwell Automation).
0x00000064 An originator used an invalid session handle when sending an encapsulation Message to the target.
0x00000065 The target received a Message of invalid length.
0x00000066 -0x00000068 Reserved for legacy (Rockwell Automation).
0x00000069 Unsupported encapsulation protocol revision.
0x0000006a -0x000ffff Reserved for future expansion.

PLC-497 Error Codes

 

Note: The following errors are generated from the designated PLC, are monitored by the C-more Panel, and displayed on the Panel screen as a hexadecimal value in Panel Error Code PLC-497 message, if active. Refer to the PLC manufacturer’s documentation for additional information.

PLC Errors for Allen-Bradley EtherNet/IP Protocol — CIP Errors — (Error Code 0xaabbbb returned from the PLC)
Panel Error Code PLC-497 Hex value Description
0x010100 Connection Manager: Connection in Use or Duplicate Forward Open.
0x010103 Connection Manager: Transport Class and Trigger combination not supported.
0x010106 Connection Manager: Ownership Conflict.
0x010107 Connection Manager: Connection not found at target application.
0x010108 Connection Manager: Invalid connection type (problem with type or priority).
0x010109 Connection Manager: Invalid connection size.
0x010110 Connection Manager: Device not configured.
0x010111 Connection Manager: RPI not supported. Could also be problem with inactivity timeout.
0x010113 Connection Manager: Connection Manager cannot support any more connections.
0x010114 Connection Manager: Either the vendor ID or the Product Code in the key segment did not match the device.
0x010115 Connection Manager: Product Type in the key segment did not match the device.
0x010116 Connection Manager: Major or minor revision information in the key segment did not match the device.
0x010117 Connection Manager: Invalid connection point.
0x010118 Connection Manager: Invalid configuration format.
0x010119 Connection Manager: Connection request fails since there is no controlling connection currently open.
0x01011a Connection Manager: Target application cannot support any more connections.
0x01011b Connection Manager: RPI is smaller than the Production Inhibit Time.
0x010203 Connection Manager: Connection cannot be closed since the connection has timed out.
0x010204 Connection Manager: Unconnected Send timed out waiting for a response.
0x010205 Connection Manager: Parameter error in Unconnected send service.
0x010206 Connection Manager: Message too large for Unconnected Message service.
0x010207 Connection Manager: Unconnected acknowledge without reply.
0x010301 Connection Manager: No buffer memory available.
0x010302 Connection Manager: Network Bandwidth not available for data.
0x010303 Connection Manager: No Tag filters available.
0x010304 Connection Manager: Not configured to send real-time data.
0x010311 Connection Manager: Port specified in Port segment not available.
0x010312 Connection Manager: Link address specified in port segment not available.
0x010315 Connection Manager: invalid segment type or segment value in path.
0x010316 Connection Manager: Path and Connection not equal in close.
0x010317 Connection Manager: Ether Segment not present or Encoded value in Network Segment is invalid.
0x010318 Connection Manager: Link address to self invalid.
0x010319 Connection Manager: Resources on Secondary unavailable.
0x01031a Connection Manager: Connection already established.
0x01031b Connection Manager: Direct connection already established.
0x01031c Connection Manager: Miscellaneous.
0x01031d Connection Manager: Redundant connection mismatch.
0x01031e Connection Manager: No more consumer resources available in the producing module.
0x01031f Connection Manager: No connection resources exist for target path.
0x010320 -0x0107ff Connection Manager: Vendor specific.
0x020000 Resource unavailable: Connection Manager resources are unavailable to handle service request.
0x030000 Invalid parameter value.
0x040000 Path segment error: The path segment identifier or the segment syntax was not understood by the processing node.
0x050000 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.
0x060000 Partial transfer: Only part of the expected Data was transferred.
0x070000 Connection lost: The messaging connection was lost.
0x080000 Service not supported: The requested service was not implemented or was not defined for this Object Class/Instance.
0x090000 Invalid attribute value: Invalid attribute Data detected.
0x0a0000 Attribute list error: An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero status.
0x0b0000 Already in requested mode/state: The object is already in the mode/state being requested by the service.
0x0c0000 Object state conflict: The object cannot perform the requested service in its current mode/state.
0x0d0000 Object already exists: The requested instance of object to be created already exists.
0x0e0000 Attribute not settable: A request to modify non-modifiable attribute was received.
0x0f0000 Privilege violation: A permission/privilege check failed.
0x100000 Device state conflict: The device's current mode/state prohibits the execution of the requested service.
0x110000 Reply Data too large: The Data to be transmitted in the response buffer is larger than the allocated response buffer.
0x120000 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).
0x130000 Not enough data: The service did not supply enough Data to perform the specified operation.
0x140000 Attribute not supported: The attribute specified in the request is not supported.
0x150000 Too much data: The service supplied more Data than was expected.
0x160000 Object does not exist: The object specified does not exist in the device.
0x170000 Service fragmentation sequence not in progress: The fragmentation sequence for this service is not currently active for this data.
0x180000 No stored attribute data: The attribute Data of this object was no saved prior to the requested service.
0x190000 Store operation failure: The attribute Data of this object was not saved due to a failure during the attempt.
0x1a0000 Routing failure, request packet too large: The service request packet was too large for transmission on a network in the path to the destination.
0x1b0000 Routing failure, response packet too large: The service response packet was too large for transmission on a network in the path from the destination.
0x1c0000 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.
0x1d0000 Invalid attribute value list: The service is returning the list of attributes supplied with status information for those attributes that were invalid.
0x1e0000 Embedded service error: See Service Packet error list (PLC-498 Error codes) below:
0x1f0000 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.
0x200000 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.
0x210000 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.
0x220000 Invalid Reply Received: An invalid reply is received (example: service code sent doesn't match service code received.).
0x230000 Reserved by CIP for future extensions.
0x240000 Reserved by CIP for future extensions.
0x250000 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.
0x260000 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.
0x270000 Unexpected attribute in list: An attempt was made to set an attribute that is not able to be set at this time.
0x280000 Invalid Member ID: The Member ID specified in the request does not exist in the specified Class/Instance/Attribute.
0x290000 Member not settable: A request to modify a non-modifiable member was received.
0x2a0000 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.
0x2b0000 -0xcf0000 Reserved by CIP for future extensions.
0xd00000 -0xff0000 Reserved for Object Class and service errors: This range of error codes is to be used to indicate Object Class specific errors. Use of this range should only be used when errors in this table don't accurately reflect the error encountered.

PLC-498 Error Codes

 

Note: The following errors are generated from the designated PLC, are monitored by the C-more Panel, and displayed on the Panel screen as a hexadecimal value in Panel Error Code PLC-498 message, if active. Refer to the PLC manufacturer’s documentation for additional information.

PLC Errors for Allen-Bradley EtherNet/IP Protocol — Service Packet Errors — (Error Code 0xaabbbb returned from the PLC)
Panel Error Code PLC-498 Hex value Description
0x010000 DST Node is out of buffer space.
0x020000 Cannot guarantee delivery; link layer (The remote node specified does not ACK command).
0x030000 Duplicate token holder detected.
0x040000 Local port is disconnected.
0x050000 Application layer timed out waiting for response.
0x060000 Duplicate node detected.
0x070000 Station is offline.
0x080000 Hardware fault.
0x100000 Illegal command or format. Typical error received from PLC when addressed requested to the PLC does not exist. Usually occurs if memory map has not been expanded in PLC to the range requested from panel.
0x200000 Host has a problem and will not communicate.
0x300000 Remote node host is missing, disconnected, or shut down.
0x040000 Host could not complete function due to hardware fault
0x050000 Addressing problem or memory protected rungs.
0x060000 Function not allowed due to command protection selection.
0x700000 Processor is in Program Mode.
0x800000 Compatibility mode file missing or communication zone problem.
0x900000 Remote node cannot buffer command.
0xA00000 Wait ACK (1775 KA buffer full).
0xB00000 Remote node problem due to download.
0xC00000 Wait ACK (1775 KA buffer full).
0xD00000 Not used.
0xE00000 Not used.
0xF00100 Error code in the EXT STS byte. See the error code table below.
0xF00200 Fewer levels specified in address than minimum for any address
0xF00300 More levels specified in address than system supports.
0xF00400 Symbol not found.
0xF00500 Symbol is of improper format.
0xF00600 Address does not point to something usable.
0xF00700 File is wrong size.
0xF00800 Cannot complete request, situation has changed since start of the command.
0xF00900 Data or file size is too large.
0xF00A00 Transaction size plus word address is too large.
0xF00B00 Access denied; improper privilege. This will occur if Data file is set to constant or protected.
0xF00C00 Condition cannot be generated; resource is not available.
0xF00D00 Condition already exists; resource is readily available.
0xF00E00 Command cannot be executed.
0xF00F00 Histogram overflow.
0xF01000 No access.
0xF01100 Illegal Data type.
0xF01200 Invalid parameter or invalid data.
0xF01300 Address reference exists to deleted area.
0xF01400 Command execution failure for unknown reason; possible histogram overflow.
0xF01500 Data conversion error.
0xF01600 Scanner not able to communicate with 1771 rack adapter.
0xF01700 Type mismatch.
0xF01800 1771 module response was not valid.
0xF01900 Duplicated label.
0xF02200 Remote rack fault.
0xF02300 Timeout.
0xF02400 Unknown error.
0xF01A00 File is open; another node owns it.
0xF01B00 Another node is the program owner.
0xF01C00 Reserved.
0xF01D00 Reserved.
0xF01E00 Data table element protection violation.
0xF01F00 Temporary internal problem.