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  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: Proposed change in asyn - request for comments
From: Michael Davidsaver <mdavidsaver@bnl.gov>
To: tech-talk@aps.anl.gov
Date: Wed, 30 May 2012 11:44:26 -0400
Hi Mark,

Would this be usable with the asyn "interrupt" mechanism? Also, have you considered adding a field for alarm severity as well?

I would like to be able to push data to records via I/O Intr with a valid/invalid flag and a timestamp.

Michael


On 5/28/2012 12:40 PM, Mark Rivers wrote:
Folks,

Eric Norum and I are proposing a change to asyn to enable standard asyn device support to set record timestamps based on time stamp information from an asyn driver.  The change is backwards compatible.  Here is the proposal:

- Add a timeStamp field to the asynUser structure

- Drivers can optionally set the timestamp field in the asynUser that is passed in interface read() operations and in callbacks to device support for input records.

- asyn device support sets the record timestamps based on pasynUser->timeStamp if the following are both true:
   - The record TSE field is set to epicsTimeEventDeviceTime (-2)
   - pasynUser->timeStamp is non-zero

The idea is that the asyn driver can determine the time stamp very close to the time that the I/O operation completed.  The record timestamp can thus be set much closer to the "true" time than if the time is determined with recGblGetTimeStamp later on when the record processes.

Before we commit this change I'd like to hear if this would be useful to others.  I'm particularly interested if this would help the LCLS and other FEL folks who want to timestamp areaDetector and other asyn driver records with the pulse identification.  Are there changes to the proposal that would make it more useful, but still general?

Cheers,
Mark




Replies:
Re: Proposed change in asyn - request for comments Eric Norum
RE: Proposed change in asyn - request for comments Mark Rivers
References:
Proposed change in asyn - request for comments Mark Rivers

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