Specifications

www.kepware.com

Allen-Bradley DH+/DH-485 Device Driver Help

Possible Cause:

1. The connection between the device and the card is broken.

2. The connection between the host PC and the card is broken.

3. The card may have been loaded with incorrect module.

Solution:

1. Verify the cabling between the device and the card.

2. Verify that the card is inserted properly onto the right slot.

3. Verify that all the parameters (card, memory address, I/O port, etc) are correctly chosen while creating the project.

Failed to connect to device '<device name>'

Error Type:

Fatal

Possible Cause:

1. The card may not have been installed correctly.

2. An inappropriate "inf" file may have been loaded for this device.

Solution:

1. Verify that all the card pins are comfortably connected to the slot.

2. Go to Device Manager and make sure you do not have the wrong driver installed for this device.

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

[STS=<value>, EXT STS=<value>]. Tag deactivated

Error Type:

Warning

Possible Cause:

The address requested in the block 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 thus the error information is contained within the status code. The codes are displayed in

hexadecimal.

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.

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.

Note:

The block starting at address <address> may be deactivated in the process depending on the severity of the error. The

error message will state this as it does above.

Unable to write to address <address> on device '<device name>'. [STS=<value>, EXT

STS=<value>]

Error Type:

Warning

Possible Cause:

The address written to does not exist in the PLC.

Solution: