Specifications

ManualsBrandsBack to Basics ManualsBlenderSCL5

Allen-Bradley DF1 Driver Help

Unable to read function file '<fun. file element>' on device '<device name>'. Device replied with

an unexpected NAK. Check device link protocol

Unable to read data starting at <start 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.

Solution:

Check the status and extended status codes that are being returned by the PLC. The codes are displayed in

hexadecimal.

Note:

This error message applies to local node errors. 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 for some

reason.

Unable to read data starting at <start address> on device '<device name>'

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

Error Type:

Serious

Possible Cause:

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

2. 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:

This error message applies to remote node errors. 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. The driver will not ask for these blocks again after receiving this kind of error. This kind of

error can be generated if the address does not exist in the PLC.

Unable to read function file <fun. file element> on device '<device name>'

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

Error Type:

Serious

Possible Cause:

1. Node cannot be found.

2. Duplicate node detected.

Solution:

Check the status and extended status codes that are being returned by the PLC. The codes are displayed in

hexadecimal.

Note:

This error message applies to local node errors. 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 this function file periodically. Errors

found by the local node occur when the KF module cannot see the destination PLC on the network for some

reason.