CLICK EtherNet/IP Error Codes

General Status Error (SD104, SD110)

Extended Status Error (SD105, SD111)

Name

Description

0x00

0x0000

Success

Success

0x01

0x0100

Connection In Use/Duplicate Forward Open

A connection is already established from the target device sending a Forward Open request or the target device has sent multiple forward open request. This could be caused by poor network traffic. Check the cabling, switches and connections.

0x01

0x0103

Transport Class/Trigger Combination not supported

The Transport class and trigger combination is not supported. The CLICK CPU only supports Class 1 and Class 3 transports and triggers: Change of State and Cyclic.

0x01

0x0106

Owner Conflict

An existing exclusive owner has already configured a connection to this Connection Point. Check to see if other Scanner devices are connected to this adapter or verify that Multicast is supported by adapter device if Multicast is selected for Forward Open. This could be caused by poor network traffic. Check the cabling, switches and connections.

0x01

0x0107

Target Connection Not Found

This occurs if a device sends a Forward Close on a connection and the device can't find this connection. This could occur if one of these devices has powered down or if the connection timed out on a bad connection. This could be caused by poor network traffic. Check the cabling, switches and connections.

0x01

0x0111

RPI Not Supported

This error occurs if the Originator is specifying an RPI that is not supported. The CLICK CPU will accept a minimum value of 10ms on a CIP Forward Open request. However, the CPU will produce at the specified rate up to the scan time of the installed project. The CPU cannot product any faster than the scan time of the running project.

0x01

0x0114

Vendor ID or Product Code Mismatch

The compatibility bit was set in the Forward Open message but the Vendor ID or Product Code did not match.

0x01

0x0115

Device Type Mismatch

The compatibility bit was set in the Forward Open message but the Device Type did not match.

0x01

0x0116

Revision Mismatch

The compatibility bit was set in the Forward Open message but the major and minor revision numbers were not a valid revision.

0x01

0x011A

Target Object Out of Connections

The maximum number of connections supported by this instance of the object has been exceeded.

0x01

0x0123

Invalid Originator to Target Network Connection Type

The Originator to Target Network Connection Type specified in the Forward Open is not supported. Only Unicast is supported for O -> T (Output) data in the CLICK CPU.

0x01

0x0124

Invalid Target to Originator Network Connection Type

The Target to Originator Network Connection Type specified in the Forward Open is not supported. Multicast and Unicast is supported in the CLICK CPU. Some devices may not support one or the other so if this error is encountered try the other method.

0x01

0x0127

Invalid Originator to Target Size

This error is returned when the Originator to Target (Output data) size specified in the Forward Open does not match what is in the Target. Consult the documentation of the Adapter device to verify the required size. Note that if the Run/Idle header is requested, it will add 4 additional bytes and must be accounted for in the Forward Open calculation. The CLICK CPU always requires the Run/Idle header so if the option doesn't exist in the Scanner device, you must add an additional 4 bytes to the O -> T (Output) setup. Some devices may publish the size that they are looking for as an additional attribute (Unsigned Integer 16 value) of the Extended Error Code. An array can be defined for this field in order to view the extended error code attributes.

0x01

0x0128

Invalid Target to Originator Size

This error is returned when the Target to Originator (Input data) size specified in the Forward Open does not match what is in Target. Consult the documentation of the Adapter device to verify the required size. Note that if the Run/Idle header is requested, it will add 4 additional bytes and must be accounted for in the Forward Open calculation. The CLICK CPU does not support a Run/Idle header for the T -> O (Input) data. Some devices may publish the size that they are looking for as an additional attribute (Unsigned Integer 16 value) of the Extended Error Code. An array can be defined for this field in order to view the extended error code attributes.

Note: This error may also be generated when a Connection Point value that is invalid for IO Messaging (but valid for other cases such as Explicit Messaging) is specified, such as 0. Please verify if the Connection Point value is valid for IO Messaging in the target device.

0x01

0x012A

Invalid Consuming Application Path

This error will be returned by the CLICK CPU if the Consuming (O -> T) Application Path is not present in the Forward Open message coming from the Scanner device or if the specified Connection Point is incorrect.

0x01

0x012B

Invalid Producing Application Path

This error will be returned by the CLICK CPU if the Producing (T -> O) Application Path is not present in the Forward Open message coming from the Scanner device or if the specified Connection Point is incorrect.

0x01

0x012F

Inconsistent Application Path Combination

The combination of Configuration, Consuming and Producing application paths specified are inconsistent.

0x01

0x0132

Null Forward Open function not supported

The target device does not support the function requested in the NULL Forward Open request. The request could be such items as "Ping device", "Configure device application", etc.

0x01

0x0315

Invalid Segment in Connection Path

This error occurs when the target device cannot understand the segment type or segment value in the Connection Path. Consult the documentation of the device to verify the correct segment type and value. If a Connection Point greater than 255 is specified this error could occur.

0x01

0x0813

Not Configurable for Off-subnet Multicast

The producer has been requested to support a Multicast connection for a consumer on a different subnet and does not support this functionality.

0x04

N/A

Path Segment Error

The path segment identifier or the segment syntax was not understood by the target device.

0x05

N/A

Path Destination Error

The Class, Instance or Attribute value specified in the Unconnected Explicit Message request is incorrect or not supported in the Target device. Check the manufacturer's documentation for the correct codes to use.

0x08

N/A

Service not supported

The requested service was not implemented or was not defined for this Object.

0x09

Index to Error

Error in Data Segment

This error code is returned when an error is encountered in the Data segment portion of a Forward Open message. The Extended Status value is the offset in the Data segment where the error was encountered.

0x0E

N/A

Attribute not settable

A request to modify a non-modifiable attribute was received.

0x0F

N/A

Privilege violation

A permission/privilege check failed

0x13

N/A

Not Enough Data

Not enough data was supplied in the service request specified.

0x14

N/A

Attribute not supported

The attribute specified in the request is not supported

0x15

N/A

Too Much Data

Too much data was supplied in the service request specified.

0x16

N/A

Object does not exist

The object specified does not exist in the device.

0x20

N/A

Invalid parameter

A parameter associated with the request was invalid. This code is used when a parameter does not meet the requirements of this specification and/or the requirements defined in an Application Object Specification.

0x26

N/A

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.