Specifications

Allen-Bradley ControlLogix Ethernet Driver Help
Solution:
Refer to A-B documentation for STS error code definitions. For example, if STS code '0x02'(hex) is returned,
verify the cabling between the remote node (PLC) and the local node.
Unable to read <block size> element(s) starting at <address> on device
<device name>. [DF1 STS=<value>, EXT STS=<value>]. Tag(s) deactivated.
Error Type:
Warning
Possible Cause:
The address requested in the block does not exist in the PLC.
Solution:
Check the status and extended status codes that are being returned by the PLC. An extended status code may not
always be returned; therefore, the error information is contained within the status code. The codes are displayed
in hexadecimal.
Status code errors in the low nibble of the status code indicate errors found by the local node. The driver will
continue to retry reading these blocks of data periodically. Errors found by the local node occur when the KF
module cannot see the destination PLC on the network.
Status code errors in the high nibble of the status code indicate errors found by the PLC. These errors are
generated when either the block of data the driver is asking for is not available in the PLC or the address does not
exist in the PLC. The driver will not ask for these blocks again after receiving this kind of error.
Note:
The block starting at address <address> may be deactivated in the process depending on the severity of the
error.
See Also:
A-B documentation for STS and Ext. STS error code definitions.
Unable to read <block size> element(s) starting at <address> on device
<device name>. Frame received contains errors.
Error Type:
Warning
The error could be:
1. Incorrect frame size received.
2. TNS mismatch.
3. Invalid response command returned from device.
Possible Cause:
1. Misalignment of packets due to connection/disconnection between PC and device.
2. There is bad cabling connecting the devices that is causing noise.
Solution:
The driver will recover from this error without intervention. If this error occurs frequently, there may be an issue
with the cabling or the device itself.
Unable to write to address <address> on device <device name>. [DF1
STS=<value>, EXT STS=<value>].
Error Type:
Warning
Possible Cause:
www. kepware.com
113