1. RECORD IDs DO NOT MATCH

When there is a read or write to a tag, a sanity check is made to ensure that the tag is known. In this test, the point address encoded in the tag is used as a database key to identify information about that point. If this information is not consistent, this error is reported by the driver.

The most likely reason for the data not being consistent is due to the point not being initialised correctly at startup, perhaps due to a configuration error. If this is the case, then ample syslog traces and error box warnings will have been produced to warn of such. It is recommended that full tracing be anabled, and that all reported errors at start up be examined.

2. TAG NOT RESOLVED

This error is reported to the driver by dedicated APACS software, the driver simply relays the error on to Citect. The error indicates that the requested tag is not recognised.

This is a very similar scenario to RECORD IDS DONT MATCH, and is most likely a consequence of the same.

3. DATA UNINITIALIZED

This error is also reported to the driver by dedicated APACS software, the driver simply relays the error on to Citect. The error indicates that the value of the requested tag is unknown. This most likely indicates that the dedicated APACS software has not yet received any values from the actual device for this point.

If it the problem only occurs at start-up, then it would be due to the lag of the system; if it always occurs, then the point does not exist or perhaps is disconnected/BadQuality.