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  <20102011  2012  2013  2014  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  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Manipulating time in records
From: Marty Kraimer <[email protected]>
To: "[email protected]" <[email protected]>
Date: Thu, 21 Oct 2010 05:37:13 -0400
On 10/21/2010 04:46 AM, Di Maio Franck wrote:
Thanks all for the feedback

Clarification:
For ITER, we'll have a IEEE 1588-2008 network to provide time accuracy "below 1 micro-second", as per the norm, and below 50 ns with a properly configured network and maybe better as time goes.
(People interested in IEEE 1588-2008 can contact us, BTW)
Controllers will also be interfaced to fast communication network for feedback but that's another story.
The time expression won't be far in future (long pulses are still expressed in minutes) but they shall be precise.

To sum up the type aspect:
- A pair of integer is required&  signed integers are good enough for now ... provided that UINT32 support is completed within the next 68 years.
- Relative time (pulse time), with ns precision can fit in a FLOAT64 for 125 hours or something like that, which would be OK for us.
- A ns precision for a software interrupt is somehow excessive and microsecond precision would fit into a FLOAT64 mantissa but it's not very good to have many resolutions.

We are considering a waveform with 2 ints for time PVs and maybe FLOAT64 records for relative time (pulse time).

I also guess that pvData will/shall allow time struct with ns fractions in the API.

pvData defines a timeStamp that is similar to epics except that seconds after epoch is

1) An 64 bit signed integer rather than 32 bit signed integer. This prevents overflow for a really really long time.
2) epoch is posix epoch (Jan 1 1970 at 00:00:00 UTC) rather than epics epoch (Jan 1 1990 at 00:00:00 UTC)


The nanoseconds within the second is a signed 32 bit integer.
Replies:
RE: Manipulating time in records Dalesio, Leo
References:
Manipulating time in records Di Maio Franck
Re: Manipulating time in records Luedeke Andreas
RE: Manipulating time in records Di Maio Franck

Navigate by Date:
Prev: Re: Lookup table problem Maren Purves
Next: RE: Lookup table problem austen.rose
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Manipulating time in records Di Maio Franck
Next: RE: Manipulating time in records Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Oct 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·