Specifications
59
www.kepware.com
Allen-Bradley DH+/DH-485 Device Driver Help
1. 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.
2. Status code errors in the low nibble of the status code indicate errors found by the local node. Errors found by the
local node occur when the card cannot see the destination PLC on the network for some reason.
3. Status code errors in the high nibble of the status code indicate errors found by the PLC. These errors are generated
when the data location is not available in the PLC or not write able.
Unable to write to address <address> on device '<device name>'. Frame received
contains errors
Error Type:
Warning
The Error Could Be:
1. Incorrect frame size received.
2. TNS mismatch.
3. Invalid response command returned from device.
Possible Cause:
1. Misalignment of packets due to connection/disconnection between PC and device.
2. There is bad cabling connecting the devices causing noise.
Solution:
The driver will recover from this error without intervention. If this error occurs frequently, there may be an issue with
the cabling or the device itself.
Failed RAM, CTC or SIO Test
Error Type:
Fatal
Possible Cause:
1. Memory Conflict.
2. Temporary network problem.
3. Bad memory address selected.
4. The parameters selected for Channel setup may be incorrect.
5. Card Corrupted.
Solution:
1. Some other device may be using the same memory address. Configure the device with a different memory address.
2. Restart the driver.
3. The memory address selected is not within the range: try a different memory address.
4. Modify the channel properties with appropriate values.
5. Replace the card.
Failed to complete diagnosis while performing M16 Diagnosis
Error Type:
Fatal
Possible Cause:
You should only see this error when one of the following error occurs. Click on the errors to review the possible
solutions.
Failed to perform M16 Diagnostic for base address <memory address>'
Failed to perform M16 Key write for device, <Device Name>
Failed to complete loading protocol file while performing M16 diagnosis for device <Device name>