Syncronize ServerTimestamp #1376
Replies: 3 comments 4 replies
-
|
Sorry i just realized the pictures where cut off |
Beta Was this translation helpful? Give feedback.
-
|
Are you using I can't see why the server timestamps would get replaced or be out of order except if they are later modified outside your loop, which happens here if you use SubscriptionModel: in |
Beta Was this translation helpful? Give feedback.
-
|
ServerTimestamp is always supposed to be "fresh" - at the time a value is read or polled, so it's not expected that you would be updating yourself underneath this naive subscription mechanism. |
Beta Was this translation helpful? Give feedback.
-
|
Hi we are using SubscriptionModel, so can you explain to me the meaning of servertimestamp because my understandig was i write a value and ServerTiemstamp shows that the value is accurate. So what we we want is to set the DataPublishTrigger Value when all the other Data is accurate. We have investigated this case further and we think we have the following Problem:
|
Beta Was this translation helpful? Give feedback.
-
|
SourceTimestamp vs ServerTimestamp are explained here: The key thing to take away is that the ServerTimestamp is expected to continually change; you set the value and it locks in the SourceTimestamp, and then even if the value does not further change, and a Client subsequently reads that value every second, the ServerTimestamp will update each time a value is returned in response, because the server "knew it to be accurate" at that point still. The SourceTimestamp would remain the same. You have no control over how/when queued data change notifications are sent to the client. If you need to ensure multiple datapoints are published atomically then consider packing them into a structure. It might also be possible to get the behavior you seek if you control the Client, by using the SetTriggering service, along with ensuring on the Server side you update the other items before the trigger item. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Kevin, Greetings Johann |
Beta Was this translation helpful? Give feedback.
-
|
One thing that might help is to introduce a lock to prevent sampling from occurring at the same time as you're updating Nodes. Something like: private final ReadWriteLock readWriteLock = new ReentrantReadWriteLock(true);
@Override
public List<DataValue> read(
ReadContext context,
Double maxAge,
TimestampsToReturn timestamps,
List<ReadValueId> readValueIds) {
try {
readWriteLock.readLock().lock();
return super.read(context, maxAge, timestamps, readValueIds);
} finally {
readWriteLock.readLock().unlock();
}
}and then in your code that updates the Nodes you would acquire This only solves one race, though. The Subscription will still be evaluating at its publishing interval independently from the sampling, and I think there's still some small chance a Subscription runs through its items to determine if they have anything queued or have been triggered at the same time that the sampling logic is looping through and setting values. That publishing and sampling are decoupled is by design in OPC UA. None of this would resolve your ServerTimestamp problem, either. You could force your way around that by doing sampling yourself instead of using the SubscriptionModel class. And again, if you have multiple data points that should update and be delivered atomically, then put them into a structure and publish the structure value. This is the only way to guarantee that a client receives them atomically. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
is there a possibilty to syncronize the servertimestamp ? I have the following Problem i write a linkedlist of Values directly to server within a loop
and the sourceTimestamps are in syncronous Order(values with sorted sourceTimestamp):
now the server Timestamp comes in an different Order(values sorted by serverTimestamp):
So the DatapublishTrigger Value which i want to be set as the last value comes somwhere inbetween. Is there a config or suggestion to archive the same order of server Timestamps like the sourceTimestamps ?
Beta Was this translation helpful? Give feedback.
All reactions