Experimental Physics and Industrial Control System
In which case a possible solution for a bidirectional record
(without custom record types but with custom device support) is:
record A : input record with custom dev sup, scan PASSIVE
record B : periodically scanned record, with FLNK to A
within A's read_xxx device support function:
if PUTF true then
grab VAL and write to hardware
else
read from hardware and write to VAL
This writes on demand from the CA client and reads periodically.
- Peregrine
J. Frederick Bartlett wrote:
Marty,
I am somewhat confused by your answer to Peregrine. I had thought the PUTF
field of a record, which is described in the "Record Reference Manual" as
"Did dbPutField cause the current record processing", is exactly what
Peregrine is looking for.
--
Peregrine M. McGehee Sloan Digital Sky Survey
LANL/LANSCE-8 and NMSU/Department of Astronomy
(505) 667-3273; MS H820, LANL, Los Alamos, NM 87545
- Replies:
- Re: Record processing knowledge of dbAccess context Marty Kraimer
- Re: Record processing knowledge of dbAccess context Marty Kraimer
- References:
- RE: Record processing knowledge of dbAccess context J. Frederick Bartlett
- Navigate by Date:
- Prev:
RE: Record processing knowledge of dbAccess context J. Frederick Bartlett
- Next:
Re: Record processing knowledge of dbAccess context Marty Kraimer
- 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: Record processing knowledge of dbAccess context J. Frederick Bartlett
- Next:
Re: Record processing knowledge of dbAccess context Marty Kraimer
- 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