Specifications

Allen-Bradley DH+ Driver Help

The driver supplied by the OPC server for the card being used must be installed. For more information, refer to

Channel Setup.

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 address '<address>' on device '<device name>'. Frame received

contains errors

Unable to read data starting at address '<address>' on device '<device name>'. [STS=<value>, EXT

STS=<value>]. Tag deactivated

Unable to write to address '<address>' on device '<device name>'. Frame received contains errors

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

STS=<value>]

Unable to read data starting at 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.

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.