Yes, that is correct. asynManager initializes the timestamp to 0, so if a driver calls pasynManager->getTimeStamp() when pasynManager->updateTimeStamp() has never been called then it will get a timestamp of 0. If the record has a 0 timestamp, which will happen with TSE=-2 under these circumstances, then this is displayed as <undefined> by camonitor, etc.
Mark
-----Original Message-----
From: Pearson, Matthew R. [mailto:[email protected]]
Sent: Tuesday, September 17, 2013 11:30 AM
To: Mark Rivers
Cc: [email protected]
Subject: Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime
Hi Mark,
Thanks. I was trying to figure out if the areaDetector API is backwards compatible (regardless of what TSE is set to). But it does seem to be from reading your document. If a detector driver doesn't call updateTimeStamp(&pImage->epicsTS), then it will just be a zero timestamp presumably (and the record timestamp will be set to zero if TSE=-2). So, it would be harmless, but probably not something that people will do.
Cheers,
Matt
On Sep 17, 2013, at 10:29 AM, Mark Rivers <[email protected]> wrote:
> 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>
>
> <AsynTimeStampSupport.pdf><areaDetectorTimeStampSupport.pdf>
- References:
- asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Mark Rivers
- RE: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Mark Rivers
- Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Pearson, Matthew R.
- Navigate by Date:
- Prev:
Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Pearson, Matthew R.
- Next:
Newport 8742 motor controller driver tim.hayton
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: asyn support for EPICS timestamps and records with TSE=epicsTimeEventDeviceTime Pearson, Matthew R.
- Next:
BiRa Ethernet Power Supply Controllers Rod Nussbaumer
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|