/
ControlLogix Error Codes
ControlLogix Error Codes
- Michael Standal
Owned by Michael Standal
EtherNet/IP Encapsulation Error Codes
| Error Code (Hex) | Description | Notes |
|---|---|---|
| 0x0001 | Invalid or unsupported encapsulation command. | Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required. Additionally, verify the correct driver type has been selected for the device in question. Refer to the Protocol Selection Table. |
| 0x0002 | Insufficient memory to handle command. | Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required. |
| 0x0003 | Incorrect data found in data portion of encapsulated message. | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x0064 | Invalid session handle. | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x0065 | Invalid message length. | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x0069 | Unsupported encapsulation protocol revision. | This is unusual. Please contact AUTOSOL support if this persists. |
CIP Connection Error Codes
| Error Code (Hex) | Extended Code (Hex) | Description | Notes |
|---|---|---|---|
| 0x01 | 0x0100 | Connection in use or duplicate forward open | When the driver encounters this error it will attempt to close the connection and establish a new connection. |
| 0x01 | 0x0103 | A transport class and trigger combination has been specified which is not supported by the target | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x01 | 0x0106 | The connection cannot be established since another connection has exclusively allocated some of the resources required | Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0107 | Target connection for Forward Close not found | The device has removed this connection for whatever reason before the driver could close it. When the driver encounters this error it will attempt to generate a new connection serial number for future connections. |
| 0x01 | 0x0108 | Invalid network connection parameter | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x01 | 0x0109 | Invalid connection size | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x01 | 0x0110 | Target application for connection is not configured. Likely Cause: Incorrect Processor Slot Configuration | The driver was not able to establish a CIP Class 3 Explicit Connection on the Processor Slot configured for the device in ACM. Verify the correct zero-based number configured matches the processor slot in the device backplane. Additionally, verify the correct driver type has been selected for the device in question. Refer to the Protocol Selection Table. |
| 0x01 | 0x0111 | RPI not supported. Likely Cause: Incorrect Processor Slot Configuration | The driver was not able to establish a CIP Class 3 Explicit Connection on the Processor Slot configured for the device in ACM. Verify the correct zero-based number configured matches the processor slot in the device backplane. Additionally, verify the correct driver type has been selected for the device in question. Refer to the Protocol Selection Table. |
| 0x01 | 0x0112 | RPI values are not acceptable | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x01 | 0x0113 | Connection Manager has reached the max supported connections and cannot support any more connections | Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0117 | Invalid produced or consumed application path | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x01 | 0x0118 | Invalid or inconsistent configuration application path | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x01 | 0x0119 | Connection request failed because there are no non-listen only connection types currently open | Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x011A | The target object has reached the max supported connections and cannot support any more connections | Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0203 | Connected Message connection timed out | Refer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0204 | UCMM request timed out. This may be the result of congestion at the destination node | Refer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0301 | No connection buffer memory available in target or router nodes | Refer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0311 | Port not available. Likely Cause: Incorrect Processor Slot Configuration | The driver was not able to establish a CIP Class 3 Explicit Connection on the Processor Slot configured for the device in ACM. Verify the correct zero-based number configured matches the processor slot in the device backplane. Additionally, verify the correct driver type has been selected for the device in question. Refer to the Protocol Selection Table. |
| 0x01 | 0x0312 | Link address not available. Likely Cause: Incorrect Processor Slot Configuration | The driver was not able to establish a CIP Class 3 Explicit Connection on the Processor Slot configured for the device in ACM. Verify the correct zero-based number configured matches the processor slot in the device backplane. Additionally, verify the correct driver type has been selected for the device in question. Refer to the Protocol Selection Table. |
| 0x01 | 0x031E | No More User-Configurable link consumer resources available in the producing module | Refer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x031A | Connection already established | When the driver encounters this error it will attempt to continue the poll cycle with the current connection. |
| 0x01 | 0x031B | Direct Connection already established | When the driver encounters this error it will attempt to continue the poll cycle with the current connection. |
| 0x01 | 0x031F | No More User-Configurable link consumer resources available in the producing module | Refer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required. |
| 0x01 | 0x0810 | The target application does not have valid data to produce for the requested connection | Refer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required. |
| 0x02 | 0x0000 | Resource unavailable. Likely Cause: Incorrect Processor Slot Configuration | The driver was not able to establish a CIP Class 3 Explicit Connection on the Processor Slot configured for the device in ACM. Verify the correct zero-based number configured matches the processor slot in the device backplane. Additionally, verify the correct driver type has been selected for the device in question. Refer to the Protocol Selection Table. |
CIP Read/Write/Modify Services Error Codes
| Error Code (Hex) | Extended Code (Hex) | Description | Notes |
|---|---|---|---|
| 0x03 | 0x0000 | Bad parameter, size > 12 or size greater than size of element | This is unusual. Please contact AUTOSOL support if this persists. |
| 0x04 | 0x0000 | A syntax error was detected decoding the Request Path | Ensure tag was entered correctly. Tags are case-sensitive and must match a known tag from the discovery listing. See Tags. |
| 0x05 | 0x0000 | Request Path destination unknown | The tag was not present in the device as requested. Ensure tag was entered correctly. Tags are case-sensitive and must match a known tag from the discovery listing. See Tags. |
| 0x06 | 0x0000 | Insufficient Packet Space | Not enough room in the response buffer for all the data. This is unusual. Please contact AUTOSOL support if this persists. |
| 0x10 | 0x2101 | Device state conflict: keyswitch position: The requestor is attempting to change force information in HARD RUN mode. | Refer to device documentation to verify it is configured correctly to communicate with ACM and is not in a mode that prevents ACM from writing to it. |
| 0x10 | 0x2116 | Device state conflict: Redundancy IP Conflict. | Refer to device documentation to verify it is configured correctly to communicate with ACM and is not in a mode that prevents ACM from writing to it. |
| 0x10 | 0x2802 | Device state conflict: Safety Status: The controller is in a state in which Safety Memory cannot be modified | Refer to device documentation to verify it is configured correctly to communicate with ACM and is not in a mode that prevents ACM from writing to it. |
| 0x13 | 0x0000 | Insufficient Request Data | Data too short for expected parameters. This is unusual. Please contact AUTOSOL support if this persists. |
| 0x26 | 0x0000 | The Request Path Size received was shorter or longer than expected | This is unusual. Please contact AUTOSOL support if this persists. |
| 0xFF | 0x2105 | General Error | Access beyond end of the object. This is unusual. Please contact AUTOSOL support if this persists. |
| 0xFF | 0x2107 | General Error | Data type used in request does not match the target tag's data type. See Tags. |
Related pages
For assistance, please submit a ticket via our Support Portal, email autosol.support@autosoln.com or call 281.286.6017 to speak to a support team member.