IEC 104 driver setting wrong timestamp even if data should use server time

[adaneau]

Hi,

I am trying to connect to an IEC 104 slave device and figured out that the source timestamp are not in the same timezone than my server. Thus I wanted to ignore them by setting my addresses to a type not containing timestamp (from type 36 to type 9). My server is in UTC time.

This doesnt seems to work as the driver always send data with wrong timestamp:

WCCOAiec1:[2021.03.12;12:22:53:198 (7.314) V3111] DP_MSG_COMPLEX_VC Src: (SYS: 2 Driver -num 1 CONN: 1) Dst: (SYS: 2 Event -num 0 CONN: 1) Peer: (SYS: 2 Event -num 0 CONN: 1) originTime: 2021.03.12;12:22:53:198 realTime: 0 peerMsgId: 127 msgId: 200 origMsgId: 200 origUser: 0 wantAnswer: 0 answerId: 0 useServerTime: 0
WCCOAiec1: Group: 0 Src: (SYS: 2 Driver -num 1 CONN: 1) User: 0 Time: 2021.03.12;11:22:44:677
WCCOAiec1: Item: 0 ((Type: 313 Sys: 2 Dp: 1111741 El: 2 : _original.._value) Value: 0)
WCCOAiec1: Item: 1 ((Type: 313 Sys: 2 Dp: 1111741 El: 2 : _original.._aut_inv) Value: 0)
WCCOAiec1: Item: 2 ((Type: 313 Sys: 2 Dp: 1111741 El: 2 : _original..0) Value: 1)

Is there any specific configuration for forcing server timestamp for IEC data?

Configuration:
3,17 P007
Windows server 2012

Best regards
Alexandre Daneau

[kilianvp]

you can try "utcTimestamps = 1"

[adaneau]

Hi Killian,

I should have mentioned it, I tried this and also the syncTime configuration, none of them seems to have effect...

But anyway if I use local server time, that shouldnt even play a role as supposedly the WinCC OA server time should be used as it is no?

BR
Alex

[kilianvp]

Yes the internal time is always stored in UTC and converted to the local time zone for display. However, there are drivers that use the local time instead of UTC.