Log In
Home
11/18/2020
Offline
I am currently collecting data from an OPCUA connection to a Wonderware Historian. The Historian is storing the timestamp from the OPCUA server and this timestamp is not accurate to my server time stamp. With 90+ machines and 5 different machine vendors it is becoming extremely difficult to manage this time sync. I have tried to work with Wonderware to create a driver that does not include the timestamp from the OPCUA server but they refused to update their driver to exclude the timestamp.
Is there any way to write the server time to the OPC UA server?
05/30/2017
Offline
I am not sure what the issue is.
Are you writing a client that pushes data to the historian?
11/18/2020
Offline
I will explain more: The Wondeware Historian has a driver that assists with the connection to the OPCUA server. Once the connection is established tags are configured to collect the data that is updated from the server. The driver in Wonderware does not allow for the tag data to have a time stamp other than the one coming from the OPCUA server. Because these servers reside on different machines and the time clock on each machine is not synced up with anything the Historian collects the tags with an incorrect time stamp. If I set the clock on the machine it alters the OPCUA time stamp throwing off the time stamp. Since there is continual drift with these clocks when I try to look at the historized data it does not trend accurately.
05/30/2017
Offline
OPC UA servers may support writing of the SourceTimestamp with a DataValue but you cannot count on this support.
Historians are a supposed use the SourceTimestamp because it ensure a continuous clock even if different devices are out of sync. If you introduce discontinuities by artificially changing the clocks then this creates issues for any historian. Trying override the data timestamp seems like a hack.
If there any reason you can't rely on a a network timeserver to keep your clocks in sync?
1 Guest(s)
Usage Policy