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: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime
From: Mark Rivers <[email protected]>
To: "'Pearson, Matthew R.'" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Tue, 17 Sep 2013 14:29:16 +0000
Hi Matt,

> In the future plans section at the end, you mentioned that all plugins will call setTimeStamp to set the plugin timestamp. 
> Will this be required, even if TSE!=-2? Or, if it is required, would it done automatically in the plugin base class?

It is required even if TSE!=-2, because the plugin has no way of knowing what TSE is.

However, it is automatically handled by the plugin base class.

I have now finished the areaDetector task I discussed under the Future Plans section in the original document.  I have also changed the asyn implementation by adding two new asyn shell commands.

I have attached the revised document for asyn, and the new document for areaDetector.

I would appreciate any comments before I release these in the next versions of asyn and areaDetector.

Thanks,
Mark

-----Original Message-----
From: Pearson, Matthew R. [mailto:[email protected]] 
Sent: Tuesday, September 17, 2013 8:25 AM
To: Mark Rivers
Subject: Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime


Hi Mark,

I read your document, and it seems like a useful addition.

In the future plans section at the end, you mentioned that all plugins will call setTimeStamp to set the plugin timestamp. Will this be required, even if TSE!=-2? Or, if it is required, would it done automatically in the plugin base class? 

Cheers,
Matt

On Sep 11, 2013, at 4:46 PM, Mark Rivers <[email protected]> wrote:

> <AsynTimeStampSupport.pdf>

Attachment: AsynTimeStampSupport.pdf
Description: AsynTimeStampSupport.pdf

Attachment: areaDetectorTimeStampSupport.pdf
Description: areaDetectorTimeStampSupport.pdf


Replies:
Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Pearson, Matthew R.
References:
asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Mark Rivers

Navigate by Date:
Prev: Re: RDB archive engine warning messages Kasemir, Kay
Next: Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Pearson, Matthew R.
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: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Mark Rivers
Next: Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Pearson, Matthew R.
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 ·