EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: time drift in camonitor timestamps
From: inari badillo <[email protected]>
To: Maren Purves <[email protected]>
Cc: [email protected]
Date: Tue, 8 Jan 2013 16:16:34 +0100
Thank you for your replies,

The magnitude of the error is about 700 microsecond (average), no matter the SCAN value is. So, it takes about 24min to have a 1s error.
Answering Michael Davidsaver´s question, I mean precessing relative to the start time. The different does not increase every cycle. Sorry if it wasn´t clear.
And finally yes, it seems reasonable to be caused by processing time. But in this case, wouldn´t it lead to malfunction?
Thanks again,

Inari Badillo

2013/1/4 Maren Purves <[email protected]>
If there's a genuine drift I'd expect that to be something like
the SCAN value + the processing time.

Maren


Michael Davidsaver wrote:
I mean, the difference between two
consecutive samples is always higher than the SCAN value, accumulating an
error.

Just to make certain I understand you.  Do you mean that the difference
increases with each iteration?  Or that the scan start time is moving
(precessing) relative to start of the system clock's second?

In case you have not seen it, the code in question is periodicTask().

http://bazaar.launchpad.net/~epics-core/epics-base/3.15/view/head:/src/ioc/db/dbScan.c#L561





On 1/3/2013 4:36 PM, Mark Rivers wrote:
What is the magnitude of the error?  How long does it take before the
error is 1 second, for example?

-----Original Message-----
From: [email protected]
[mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of
[email protected]
Sent: Thursday, January 03, 2013 3:09 PM
To: [email protected]
Subject: time drift in camonitor timestamps

Hi,

We have realized that when monitoring periodic PVs, provided by soft
IOCs in
standard machines under Windows/Linux/MacOS, it is observed a drift in
the
timestamps (server time) . I mean, the difference between two
consecutive samples is always higher than the SCAN value, accumulating an
error.

It seems that  this issue does not occur in RT systems such as VxWorks
(as
expected).

We are wondering if this is a known issue. In our opinion, this fact
could
lead to
malfunction problems, especially if it is not taken into account.

Does anyone in the list experienced this problem?

thank you







Replies:
Re: time drift in camonitor timestamps Ralph Lange
Re: time drift in camonitor timestamps Andrew Johnson
References:
time drift in camonitor timestamps ibadillo
RE: time drift in camonitor timestamps Mark Rivers
Re: time drift in camonitor timestamps Michael Davidsaver

Navigate by Date:
Prev: RE: motor cable assembly questions tom.cobb
Next: Re: time drift in camonitor timestamps Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: time drift in camonitor timestamps Michael Davidsaver
Next: Re: time drift in camonitor timestamps Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·