When the driver starts, it sets the computer’s TimeStamp for each read value, instead of the remote unit’s TimeStamp. How can I fix this issue, or at least discard the data?
Solution:
This happens because there are no events when the application starts. So, to make sure the tag’s value is not null until an event actually occurs, the driver performs an initial integrity (Class 0), retrieving the current values from all points. However, this message lacks the TimeStamp, and thus the point assumes the current value of the computer’s TimeStamp, and its quality is 216 (override).
When an event actually occurs at the point, it will be accepted even if its value is the same as the current one; its TimeStamp will be updated to what was sent by the remote unit, and its quality will be 192.
Thus, all data from the table whose quality is 216 can be discarded.
