

10:30, EET

December 21, 2011

10:52, EET

March 14, 2014

Sorry I didn’t understand how it can be used in these program code
name:=TPsString.Create(nil);
name.Value:= Info.softSettings.linkSettings.name ;
idx:= OPCserver.AddressSpace.AddVariable(ctrlIdx, name, ‘Name’);
and
var
arr: TPsFloatArray ;
HistoryData : array[0..POINT_COUNT-1] of double;
…
HistoryData:= ….
arr.AssignArray(HistoryData) ;
14:42, EET

December 21, 2011

8:37, EET

December 21, 2011

And what does our Prosys OPC Client show? The TimeBias parameter is the problematic one, which is not always interpreted or used correctly. If you check the LocalTimeBias option in Prosys OPC Client, the server will convert to the local time. This will make the client use NULL for the parameter. If the server is not supposed to convert, the client should use 0 for the TimeBias.
It feels like the client is requesting local time, but still converting the timestamps itself, too.
Most Users Ever Online: 1919
Currently Online:
44 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 793
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1538
Posts: 6493
Newest Members:
sophiadavis, Waynegalse, Phillipbus, Oscarsat, WilliamJer, WilliamTunse, mvsjonah79, RaymondSmutt, Merlin AI pap, patlawrence98Moderators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0
Administrators: admin: 1