Source time outside valid limits - Cause dp_fct is not running

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
2 posts • Page 1 of 1
SenthilMurugesan
Posts:15
Joined: Tue May 24, 2016 8:29 pm

Source time outside valid limits - Cause dp_fct is not running

Post by SenthilMurugesan »

Hi Team,

Time sync issue in the site(16hrs more), So we fixed the time issue after that we are facing the below log message.

When we looked into the WinccOA site, advice to use the below setting, we tried for past 24hrs and future 24hrs. still getting this warning message.
[event]
negativeSourceTimeDiff = 86400

[allsections]
valueChangeTimeDiff = 86400


WCCILevent (0), 2020.04.23 20:41:21.253, PARAM,WARNING, 20, Source time outside valid limits (resource: validTimeDiff), DP: System1:U1_V63WIM.ProcessValue.Display:_original.._value, MAN: (SYS: 1 Event -num 2 CONN: 1)

After investigating, we found the _dp_fct is used the in data point. Is using "DPE Connection" function to display the value.
p1=U1_V63WIM.ProcessValue.PLC.PV:_original.._value. Setting "Old/New compare" is selected.

When the value changes in "U1_V63WIM.ProcessValue.PLC.PV:_original.._value", we are getting that Waring message as mentioned above.

How to solve this issue, it happening in time syc, if past period. Looking for a solution. I don't know why "_dp_fct" inbuild WinccOA function does cause this error.

Thanks
Senthil M

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

Re: Source time outside valid limits - Cause dp_fct is not running

Post by leoknipp »

When looking at the log message you will find the information that it refers to a different resource: validTimeDiff.
Did you turn back the system time while the project was running?

Best Regards
Leopold Knipp
Senior Support Specialist

2 posts • Page 1 of 1