Log In
Register
Forum
Topic RSS
15:44, EET
August 9, 2016
Offline
Prosys OPC client sdk 3.1.8-580
I have a test setup with 2 opc ua servers that run follow line on the onStatusChange(UaClient uaClient, ServerStatusDataType status)
System.out.println(“>>>>” + deviceId + ” now=” + DateTime.currentTime() + ” Status getCurrentTime=” + status.getCurrentTime() + ” client=” + uaClient.getServerStatus().getCurrentTime() + ” getServerTimeDifference=” + client.getServerTimeDifference() + ” calc diff= ” + (DateTime.currentTime().getTimeInMillis() – status.getCurrentTime().getTimeInMillis()) + ” getStartTime=” + status.getStartTime());
BND cvcn is based on Unified Automation toolkit
DkFTUA2 is using the Rockwell FT Gateway OPC UA server
Example output:
>>>>BNDcvcn now=2018-11-27 13:25:14.1600000 Status getCurrentTime=2018-11-27 13:25:14.1586923 client=2018-11-27 13:25:14.1586923 getServerTimeDifference=-2 calc diff= 3 getStartTime=2018-11-22 10:46:00.4127100
>>>>DkFTUA2 now=2018-11-27 13:25:14.9890000 Status getCurrentTime=2018-11-13 12:24:48.8214507 client=2018-11-13 12:24:48.8214507 getServerTimeDifference=-1213226168 calc diff= 1213226168 getStartTime=2018-11-13 12:24:48.8214507
As you can see for DkFTUA2 the getServerTimeDifference is very big and the getCurrentTime is same as getStartTime!
But when I look to DkFTUA2 via OPCClients nodeid i=2258 (status current time) the value is matching current time.
Any idea what could case of these different value that are returned by onStatusChange event?
16:39, EET
April 3, 2012
Offline
Hi,
There are two possible sources for that value. The the server implementation must keep them in sync.
A) The ServerStatus node’s (i=2256) directly. The value is a ServerStatusDataType Structure which contains all the data in the subnodes of that node (a lot’s of Structure nodes behave like this).
B) CurrentTime node (i=2258) that is directly below the ServerStatus node.
The UaClient prefers A, if it cannot read that it will read the individual components instead, which includes B.
I recommend reporting this bug to the server vendor.
1 Guest(s)
