> From [email protected] Thu Jan 22 11:10 CST 1998
> Subject: new record support
> To: [email protected]
> MIME-version: 1.0
> Content-transfer-encoding: 7BIT
>
> I would prefer to have a single record for the download. However,
> I'm not sure how this fits into epics. I would like the users to perform
> caputs for each of the parameters. After all of the parameters have been
> filled (each would have a field in the record), the user performs
> another caput to indicate that all of the parameters
> have been filled and the record can process by writing to the
> proper vme addresses. This is where I'm not sure how this fits into
> epics. I only want the record to process (write to port card) once, even
> while I am performing caputs -- which as I understand causes the record to
> process.
>
> I doubt that this is the first time a problem such as this has
> been encountered and I would appreciate any advise as to how to best
> approach this problem.
>
Just a thought: You'll have your own processing routine to go along with your
new record type anyway. Therefore, you can have your processing routine be smart
enough to only actually talk to the hardware when the "ready to go" field has
been filled in. Any other processing would just update the necessary fields in
the record.
-- Garrett Rinehart
Intense Pulsed Neutron Source
Argonne National Laboratory
- Navigate by Date:
- Prev:
new record support Jeffrey Mcdonald
- Next:
Re: about GPIB interface Bill Brown
- 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: new record support Carl Lionberger
- Next:
Re: new record support Ned Arnold
- 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
|