Specifications

Allen-Bradley DF1 Driver Help

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

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

Error Type:

Serious

Possible Cause:

1. The function file 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 function file the driver is asking for is not

available in the PLC. The driver will not ask for this function file again after receiving this kind of error. This kind

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

Unable to read data starting at <start 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 read response or one of unexpected size. If this error occurs frequently,

contact Technical Support.

Unable to read function file <fun. file element> 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 function file read response or one of unexpected size. If this error occurs

frequently, contact Technical Support.

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

checksum error

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.

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

Checksum error

Error Type: