Specifications

Allen-Bradley DF1 Driver Help

Error writing to address '<address>' on device '<device name>'

[Status=<STS>, Ext. Status=<EXT. STS>]

Error Type:

Serious

Possible Cause:

1. Node cannot be found.

2. Duplicate node detected.

3. The address requested in the block does not exist in the PLC.

4. Processor is in program mode.

Solution:

Check the status and extended status codes that are being returned by the PLC. 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 block of data the driver is asking for is not available in the PLC.

Error writing to address '<address>' on device '<device name>'. Framing

error

Error Type:

Serious

Possible Cause:

1. Unexpected frame received.

2. Frame size mismatch.

Solution:

The device is returning an invalid write response or one of unexpected size. If this error occurs frequently,

contact Technical Support.

Checksum error occurred writing to address '<address>' on device '<device

name>'

Error Type:

Serious

Possible Cause:

There is bad cabling connecting the devices causing noise and checksum errors.

Solution:

Inspect cabling between the Host PC and the device.

Error writing to address '<address>' on device '<device name>'. Slave

sink/source full

Error Type:

Serious

Possible Cause:

The slave device cannot accept any more requests from the master. The client may be requesting data too fast.

Solution:

The driver will automatically poll and re-poll the slave to empty its source and in turn make room for responses

from requests previously in the full sink. If this error occurs too often, decrease the update rate on suspected

tags, not necessarily the tag being written to.