Specifications

Allen-Bradley ControlLogix Ethernet Driver Help
Warning
Possible Cause:
1. The packets are misaligned due to connection and/or disconnection between the PC and device.
2. There is bad cabling connecting the devices that is causing noise.
3. The wrong frame size was received.
4. There is a TNS mismatch.
5. An invalid response command was returned from the device.
6. The device is not Ethernet/IP enabled.
Solution:
1. The driver recovers from this error without intervention. If this error occurs frequently, there may be an
issue with the cabling, the network, or the device itself.
2. Verify that the device being communicated with is a Rockwell Ethernet/IP-enabled device.
ControlLogix-Specific Error Messages
The following sections pertain to messaging from the ControlLogix driver level source.
ControlLogix Specific Error Messages
Read Errors (Non-Blocking)
Read Errors (Blocking)
Write Errors
Project Synchronization Errors
Read Errors (Non-Blocking)
The following error/warning messages may be generated. Click on the link for a description of the message.
Read Errors (Non-Blocking) Error Messages
Read request for tag <tag address> on device <device name> failed due to a framing error. Tag
deactivated.
Unable to read <tag address> on device <device name>. Tag deactivated.
Unable to read tag <tag address> on device <device name>. [CIP error=<code>, Ext.
error=<code>].
Unable to read tag <tag address> on device <device name>. Controller tag data type <type>
unknown. Tag deactivated.
Unable to read tag <tag address> on device <device name>. Data type <type> is illegal for this
tag. Tag deactivated.
Unable to read tag <tag address> on device <device name>. Data type <type> not supported. Tag
deactivated.
Unable to read tag <tag address> on device <device name>. Tag does not support multi-element
arrays. Tag deactivated.
Read request for tag <tag address> on device <device name> failed due to a
framing error. Tag deactivated.
Error Type:
Warning
Possible Cause:
A read request for the specified tag failed due to one of the following reasons:
1. Incorrect request service code.
2. Received more or less bytes than expected.
Solution:
www. kepware.com
103