IEC 104 TimeStamp Problem

[jonred]

Hi,

I have encountered an strange behaviour of the timestamp of the IEC 104 Driver, it began to act as a counter.

I was teswting the clockSync in a IEC connection using this script in a button (only one connection):

Code: Select all

main(mapping event)
{

  dyn_string remotas;    
  dpGet("_Iec_1.Control.GQ",remotas);
  dpSet("_Iec_1.Control.GQ",remotas);
  dpQueryConnectSingle("syncronizar",true,"sync","SELECT '_original.._value' FROM '*.State'");
}

void syncronizar(string sync, dyn_dyn_anytype val) 
{ 
   int i;
   string dp;   
   for (i = 2; i

[Schoetzke]

When the Time only changed for one millisecond, then the time you want to set, is in the past. (older then the last Timestamp)


What is the Time when you DebugTN(GetCurrentTime())


Maybe it is a Summe/Wintertime Problem


Look if you have select in Windows "Automatically change summer winter time"

[Piterskiy]

Hi Jon,
check the time on IEC104 source, it looks like the time was behind there.
Value that comes before “NegativeSourceTimeDiff” will be written with EV time +1ms and the invalid flag _stime_inv would set (look at the invalid info bits on the screen).
Another computer could have a similar time synchronization as on the IEC104 source.

[jonred]

Ok, i will check that.

What i can see too is that the tymeSync is "stuck", i try to change the value but is always the same (the default, 1970/01/01)

[Gertjan van Schijndel]

The following config entries for the IEC driver might help 'timeSync' and 'utcTimestamps'.
To send the current time to the PLC you can write the value '0' to datapoint element '.Control.ClockSync'.

At which datapoint element do you see that the time sync is stuck? Or with which address config?
Did you configure something in the datapoint element '_Iec_.Control.ClockSync'?