Source time outside valid limits

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
2 posts • Page 1 of 1
nedzad
Posts:32
Joined: Fri Feb 17, 2017 3:44 pm

Source time outside valid limits

Post by nedzad »

Hello,

Recently my server restarted and since its BIOS time was two hours in future in regard to a system time, some datapoint values were set with source time that corresponds to BIOS time. After that, server could not read any values from PLCs for the next two hours and I was getting this error message in log. I am wondering if there is any way to overwrite this source time, so that server can continue to read values normally?

I read this article: https://portal.etm.at/index.php?view=it ... &Itemid=54 , but this is different kind of problem.

I tried to set the .._original.._stime parameter manually, but it is read-only. Any suggestions?

Best regards,
Nedžad

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Source time outside valid limits

Post by leoknipp »

In WinCC OA the time information for a dp element must be in ascending order. Writing an original value with a time stamp older then the currently saved is not possible.

One possibility to set back the time stamps for the original value is to make an initialization of the "lastval" database, see link to FAQ section:
https://portal.etm.at/index.php?view=it ... &Itemid=54

Please be aware that even if the original values are corrected you will have entries in the history (alarms, events) and alarm information with the wrong time information.
Probably you will get log messages after the correction of the original values which refer to inconsistent time information, especially for alerts.

Best Regards
Leopold Knipp
Senior Support Specialist

2 posts • Page 1 of 1