RE: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime

[Mark Rivers <rivers@cars.uchicago.edu>]

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:pearsonmr@ornl.gov] 
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 <rivers@cars.uchicago.edu> wrote:

> <AsynTimeStampSupport.pdf>

Attachment: AsynTimeStampSupport.pdf
Description: AsynTimeStampSupport.pdf

Attachment: areaDetectorTimeStampSupport.pdf
Description: areaDetectorTimeStampSupport.pdf