Hi Mark,
> NUSE: The number of elements in the waveform to actually use. Must be <=NELM.
I think you intend this record to be something you can caput? If yes, maybe better to call it something other than NUSE since NUSE for a compressRecord is not modifiable (NUSE for a compress is the same concept as NORD for a waveform). Maybe "NINP" instead.
> Also, the record does not post monitors on the BUSY or NORD fields. Should this be the
> responsibility of device support, or does that code belong in the record?
I think the code belongs in the record. It would be very nice to have monitors on NORD!
Thank you!
Stephanie Allison
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Mark Rivers
> Sent: Friday, February 10, 2012 10:50 AM
> To: [email protected]
> Subject: Waveform record missing fields
>
> Folks,
>
> All versions of the EPICS Record Reference Manual from 3.13 to 3.14.12.2 document the
> following 2 fields in the waveform record:
>
> RATE Sampling Rate Some device support modules may find this useful.
> PTSS Pre-trigger Samples Some device support modules may find this useful.
>
> I really need to use these 2 fields in some new asyn device support I am writing. (This
> device support will allow me to remove the dependence of areaDetector on mca).
>
> But these fields do not actually exist in the waveform record, at least for any version of base
> from 3.14.8.2 to 3.14.12.2!
>
> I cannot find anything in the 3.13 or 3.14 release notes that mentions removing these fields.
>
> Questions:
>
> - Did these fields ever exist?
>
> - Should they be added?
>
> - If so, then while we are adding these fields are there others we should also add that would
> not break backward compatibility?
>
> Here are is one that I can think of:
>
> NUSE: The number of elements in the waveform to actually use. Must be <=NELM.
>
> Also, the record does not post monitors on the BUSY or NORD fields. Should this be the
> responsibility of device support, or does that code belong in the record?
>
> Thanks,
> Mark
>
>
>
- References:
- Waveform record missing fields Mark Rivers
- Navigate by Date:
- Prev:
Re: Waveform record missing fields Michael Davidsaver
- Next:
Re: Waveform record missing fields Andrew Johnson
- 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: Waveform record missing fields Michael Davidsaver
- Next:
Re: Waveform record missing fields Andrew Johnson
- 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
|