ControlLogix Error Codes

Owned by Michael Standal
Last updated: May 16, 2023
5 min read

EtherNet/IP Encapsulation Error Codes

Error Code (Hex)DescriptionNotes
0x0001Invalid 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.
0x0002Insufficient memory to handle command.Refer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required.
0x0003Incorrect data found in data portion of encapsulated message.This is unusual. Please contact AUTOSOL support if this persists.
0x0064Invalid session handle.This is unusual. Please contact AUTOSOL support if this persists.
0x0065Invalid message length.This is unusual. Please contact AUTOSOL support if this persists.
0x0069Unsupported encapsulation protocol revision.This is unusual. Please contact AUTOSOL support if this persists.

CIP Connection Error Codes

Error Code (Hex)Extended Code (Hex)DescriptionNotes
0x010x0100Connection in use or duplicate forward openWhen the driver encounters this error it will attempt to close the connection and establish a new connection.
0x010x0103A transport class and trigger combination has been specified which is not supported by the targetThis is unusual. Please contact AUTOSOL support if this persists.
0x010x0106The connection cannot be established since another connection has exclusively allocated some of the resources requiredRefer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required.
0x010x0107Target connection for Forward Close not foundThe 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.
0x010x0108Invalid network connection parameterThis is unusual. Please contact AUTOSOL support if this persists.
0x010x0109Invalid connection sizeThis is unusual. Please contact AUTOSOL support if this persists.
0x010x0110Target application for connection is not configured. Likely Cause: Incorrect Processor Slot ConfigurationThe 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.
0x010x0111RPI not supported. Likely Cause: Incorrect Processor Slot ConfigurationThe 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.
0x010x0112RPI values are not acceptableThis is unusual. Please contact AUTOSOL support if this persists.
0x010x0113Connection Manager has reached the max supported connections and cannot support any more connectionsRefer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required.
0x010x0117Invalid produced or consumed application pathThis is unusual. Please contact AUTOSOL support if this persists.
0x010x0118Invalid or inconsistent configuration application pathThis is unusual. Please contact AUTOSOL support if this persists.
0x010x0119Connection request failed because there are no non-listen only connection types currently openRefer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required.
0x010x011AThe target object has reached the max supported connections and cannot support any more connectionsRefer to device documentation to verify it is configured correctly to communicate with ACM at the performance level required.
0x010x0203Connected Message connection timed outRefer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required.
0x010x0204UCMM request timed out. This may be the result of congestion at the destination nodeRefer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required.
0x010x0301No connection buffer memory available in target or router nodesRefer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required.
0x010x0311Port not available. Likely Cause: Incorrect Processor Slot ConfigurationThe 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.
0x010x0312Link address not available. Likely Cause: Incorrect Processor Slot ConfigurationThe 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.
0x010x031ENo More User-Configurable link consumer resources available in the producing moduleRefer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required.
0x010x031AConnection already establishedWhen the driver encounters this error it will attempt to continue the poll cycle with the current connection.
0x010x031BDirect Connection already establishedWhen the driver encounters this error it will attempt to continue the poll cycle with the current connection.
0x010x031FNo More User-Configurable link consumer resources available in the producing moduleRefer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required.
0x010x0810The target application does not have valid data to produce for the requested connectionRefer to device and network documentation to verify they are configured correctly to communicate with ACM at the performance level required.
0x020x0000Resource unavailable. Likely Cause: Incorrect Processor Slot ConfigurationThe 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)DescriptionNotes
0x030x0000Bad parameter, size > 12 or size greater than size of elementThis is unusual. Please contact AUTOSOL support if this persists.
0x040x0000A syntax error was detected decoding the Request PathEnsure tag was entered correctly. Tags are case-sensitive and must match a known tag from the discovery listing. See Tags.
0x050x0000Request Path destination unknownThe 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.
0x060x0000Insufficient Packet SpaceNot enough room in the response buffer for all the data. This is unusual. Please contact AUTOSOL support if this persists.
0x100x2101Device 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.
0x100x2116Device 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.
0x100x2802Device state conflict: Safety Status: The controller is in a state in which Safety Memory cannot be modifiedRefer 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.
0x130x0000Insufficient Request DataData too short for expected parameters. This is unusual. Please contact AUTOSOL support if this persists.
0x260x0000The Request Path Size received was shorter or longer than expectedThis is unusual. Please contact AUTOSOL support if this persists.
0xFF0x2105General ErrorAccess beyond end of the object. This is unusual. Please contact AUTOSOL support if this persists.
0xFF0x2107General ErrorData type used in request does not match the target tag's data type. See Tags.

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.