Specifications

Allen-Bradley DF1 Driver Help
Possible Cause:
1. The serial connection between the device and the Host PC is broken.
2. The communications parameters for the serial connection are incorrect.
3. The named device may have been assigned an incorrect Network ID.
4. The response from the device took longer to receive than the amount of time specified in the "Request Timeout"
device setting.
Solution:
1. Verify the cabling between the PC and the device.
2. Verify that the specified communication parameters match those of the device.
3. Verify that the Network ID given to the named device matches that of the actual device.
4. Increase the Request Timeout setting so that the entire response can be handled.
Unable to write to '<address>' on device '<device name>'
Error Type:
Serious
Possible Cause:
1. The serial connection between the device and the Host PC is broken.
2. The communication parameters for the serial connection are incorrect.
3. The named device may have been assigned an incorrect Network ID.
Solution:
1. Verify the cabling between the PC and the device.
2. Verify that the specified communication parameters match those of the device.
3. Verify that the Network ID given to the named device matches that of the actual device.
Device Specific Messages
The following error/warning messages may be generated. Click on the link for a description of the message.
Device Specific Messages
Unable to read data starting at <start address> on device '<device name>' [Status=<STS>, Ext.
Status=<EXT. STS>]
Unable to read data starting at <start address> on device '<device name>' [Status=<STS>, Ext.
Status=<EXT. STS>]. Block deactivated
Unable to read function file <fun. file address> on device '<device name>' [Status=<STS>, Ext.
Status=<EXT. STS>]
Unable to read function file <fun. file element> on device '<device name>' [Status=<STS>, Ext.
Status=<EXT. STS>]. Block deactivated
Unable to read data starting at <start address> on device '<device name>'. Framing error
Unable to read function file <fun. file element> on device '<device name>'. Framing error
Unable to read data starting at <start address> on device '<device name>'. checksum error
Unable to read function file <fun. file element> on device '<device name>'. checksum error
Unable to read data starting at <start address> on device '<device name>'. Slave sink/source full
Unable to read function file <fun. file element> on device '<device name>'. Slave sink/source full
Unable to read data starting at <start address> on device '<device name>'. Slave source empty
Unable to read function file <fun. file element> on device '<device name>'. Slave source empty
Error writing to address '<address>' on device '<device name>' [Status=<STS>, Ext. Status=<EXT.
STS>]
Error writing to address '<address>' on device '<device name>'. Framing error
Checksum error occurred writing to address '<address>' on device '<device name>'
Error writing to address '<address>' on device '<device name>'. Slave sink/source full
Error writing to address '<address>' on device '<device name>'. Slave source empty
Device '<device name>' timed out writing to address '<address>'
Unable to read data starting at <start address> on device '<device name>'. Device replied with a
NAK
Unable to read function file <fun. file element> on device '<device name>'. Device replied with a
NAK
Unable to read data starting at <start address> on device '<device name>'. Memory map error
Unable to read function file <fun. file element> on device '<device name>'. Memory map error
Unable to read data starting at '<start address>' on device '<device name>'. Device replied with an
unexpected NAK. Check device link protocol
www. kepware.com
46