Specifications
Allen-Bradley DH+ Driver Help
Solution:
1. Enable the interrupt by setting the correct jumper/DIP switch combination.
2. Set the interrupt parameter on the Channel Properties matching the one set up on the card.
Device Status Messages
The following error/warning messages may be generated. Click on the link for a description of the message.
Device Status Messages
Device '<device name>' is not responding
Unable to write to '<address>' on device '<device name>'
Failed to Connect to device '<device name>'
Device '<device name>' is not responding
Error Type:
Warning
Possible Cause:
1. The connection between the card and the device may be broken.
2. The connection between the PC and the card may be broken.
3. The card may have been loaded with an incorrect protocol.
4. The named device may have been assigned an incorrect memory address.
5. The channel may have been set up incorrectly.
6. The response from the device took longer to receive than the amount of time specified in the "Request Timeout"
device setting.
Solution:
1. Verify that the card is inserted correctly onto the right slot.
2. Verify the Device ID given to the named device matches that of the actual device.
3. Make sure the channel settings (such as baud rate, card type and so forth) match that of the card and device
settings.
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:
Warning
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 and so forth) 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 the Device Manager and make sure that the right driver is installed for this device.
Note:
www. kepware.com
60