Sometimes, the 1784 u2dhp produces error descriptions that are needed for determining the source of the error and the corrective actions that need to be taken. Fortunately, the corrective action is relatively simple in most cases.

Missing Address

This can result from the address not being added properly to the client application. This problem can be solved by re-entering the address. You should also re-enter the address if the error message states that there is a syntax error in the device address.

Address Is Out Of Range For The Specified Device Or Register

The device has a range of addresses that are supported by it. If the address entered is outside this range, this error message will be returned. Double-check the address to make sure that it is correct. You may also receive a "address is not supported by device model" error message. 

Data Type Is Not Valid For Device Address

In this case, the tag address does not have a valid data type. You will need to modify the data type using the client application. For example, you may need to change the data type to an integer when it is currently a string.

Device Address Is Read-Only

You are trying to access the device address in a dynamic way, but you are only allowed to access it as a read-only file. This is corrected by changing the access mode with the client application. 

Array Support Is Not Available For The Specified Address

The address has an array reference for an address type that doesn't allow for arrays. The array reference will need to be removed as the address is reentered. 

Array Size Is Out Of Range For Address

The address is much larger than what is allowed by the device. It is possible that you might have added the address incorrectly. This is corrected by modifying the address to make it smaller. 

When To Contact Support

These are among the most common error descriptions. However, if you notice an error description that is not listed, contact the manufacturer for an explanation of what the specific error message means. There are also two fatal error types that may occur and are an indication of a serious problem. These are:

  • File Corruption
  • Interrupt not configured

If a file corruption error message is generated, one of the binary files may have been corrupted. If an interrupt is not configured, you may need to contact technical support to have them assist you in configuring the interrupt.