> 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'd do this with a subroutine record. The input parameters would go to ao
records, which would hold the paramenters until the subroutine record
processed, but _not_ be out-linked or forward-linked to the subroutine record.
The subroutine record would reference the ao's through the inpa through inpl
fields. The subroutine record could be made to process by a caput to the PROC
field. The subroutine code would download the chips based on the input
parameters which would appear in the a-i fields.
Carl
//
// Carl Lionberger [email protected]
// Computer Systems Engineer Voice (510) 486-7503
// Engineering Division Fax (510) 495-2957
// Berkeley National Laboratory (LBNL)
//
- References:
- new record support Jeffrey Mcdonald
- Navigate by Date:
- Prev:
Re: about GPIB interface Bill Brown
- 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
- Navigate by Thread:
- Prev:
new record support Jeffrey Mcdonald
- Next:
Re: new record support Garrett D. Rinehart
- 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
|