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  <20122013  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  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Proposed change in asyn - request for comments
From: Eric Norum <[email protected]>
To: "Allison, Stephanie" <[email protected]>
Cc: EPICS Techtalk <[email protected]>
Date: Wed, 30 May 2012 12:06:38 -0700
On May 30, 2012, at 11:54 AM, Allison, Stephanie wrote:

Hi,

Wouldn't it be useful to have the TSE be accurate for such PVs even if they
don't finish processing until 1 or more events later?

Sure, this would be useful (not for LCLS BSA, which has already marked the old pulse as missing, but perhaps for other tools and other kinds of BSAs).

So the idea is that the TSE field of the record is set to -2 so that when the record is processed, normal record processing won't override what asyn set.  But the event code then has to be input to asyn in an alternate way and it has to be changeable on the fly.  And the data acquisition end of things does the epicsTimeGetEvent if a non-zero event code is available and then gives that timestamp to asyn device support later on.  Would be nice to let TSE be the event code but tell record processing not to use it (ie, by something unique in TSEL that doesn't resolve to a PV).    

That feels to me a little excessive in the overloading of the TSEL and TSE fields.
Perhaps once we have experience with the data acquisition layer providing the time stamps we'll be better able to determine the best way to handle this in a general fashion.


Thanks for thinking about timing,
Stephanie


-- 
Eric Norum
[email protected]


References:
Proposed change in asyn - request for comments Mark Rivers
Re: Proposed change in asyn - request for comments Ernest L. Williams Jr.
Re: Proposed change in asyn - request for comments Eric Norum
RE: Proposed change in asyn - request for comments Mark Rivers
RE: Proposed change in asyn - request for comments Allison, Stephanie
RE: Proposed change in asyn - request for comments Mark Rivers
RE: Proposed change in asyn - request for comments Allison, Stephanie

Navigate by Date:
Prev: RE: Proposed change in asyn - request for comments Allison, Stephanie
Next: Re: calc VAL field not updating from bi VAL field Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Proposed change in asyn - request for comments Allison, Stephanie
Next: Re: Proposed change in asyn - request for comments Bruce Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·