Peregrine M. McGehee wrote:
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.
This should work but if anyone ever uses A in a different way, e.g. an
output link is directed to it then it will fail.
Marty
- Replies:
- Re: Record processing knowledge of dbAccess context Peregrine M. McGehee
- References:
- RE: Record processing knowledge of dbAccess context J. Frederick Bartlett
- Re: Record processing knowledge of dbAccess context Peregrine M. McGehee
- Navigate by Date:
- Prev:
Re: Record processing knowledge of dbAccess context Marty Kraimer
- Next:
Re: Record processing knowledge of dbAccess context Peregrine M. McGehee
- 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 Peregrine M. McGehee
- Next:
Re: Record processing knowledge of dbAccess context Peregrine M. McGehee
- 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
|