Specifications

Allen-Bradley ControlLogix Ethernet Driver Help
The address written to does not exist in the PLC.
Solution:
Check the status and extended status codes that are being returned by the PLC. Note that an extended status
code may not always be returned and the error information is contained within the status code. The codes are
displayed in hexadecimal.
Note:
Status code errors in the low nibble of the status code indicate errors found by the local node. Errors found by
the local node occur when the KF module cannot see the destination PLC on the network for some reason. Status
code errors in the high nibble of the status code indicate errors found by the PLC. These errors are generated
when the data location is not available in the PLC or not writeable.
See Also:
A-B documentation for STS and Ext. STS error code definitions.
Unable to write to address <address> on device <device name>. Frame
received contains errors.
Error Type:
Warning
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.
3. Incorrect frame size received.
4. TNS mismatch.
5. Invalid response command returned from device.
Solution:
The driver recovers 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>. Local node
responded with error [DF1 STS=<value>].
Error Type:
Warning
Possible Cause:
This error means that the PLC did not respond to the write request from the local node. A local node could be an
intermediate node like 1756-DHRIO, 1756-CNB, 1761-NET-ENI, and so forth.
Solution:
Refer to A-B documentation for STS error code definitions. For example, if the STS code '0x02'(hex) is returned,
verify the cabling between the remote node (PLC) and the local node.
Unable to write to function file <address> on device <device name>. Local
node responded with error [DF1 STS=<value>].
Error Type:
Warning
Possible Cause:
This error means that the PLC did not respond to the write request from the local node. A local node could be an
intermediate node like 1756-DHRIO, 1756-CNB, 1761-NET-ENI, and so forth.
Solution:
Refer to A-B documentation for STS error code definitions. For example, if the STS code '0x02'(hex) is returned,
verify the cabling between the remote node (PLC) and the local node.
www. kepware.com
114