Who re-wrote the mbboDirectRecord between 3.13.2 and 3.13.4, and what was
the purpose of the changes to process() ?
There seems to be some very confusing behavior the first time you write to
VAL if the record has never been processed. Why does it reset VAL from the
B* fields, overwriting the value I wrote to it ?
I could return status=2 from init_mbboDirect() and leave UDF=True, which
will make it skip the "reset from B*" step, but that also bypasses the call
to convert() and RVAL won't be set properly when writeValue() is called.
The simplest solution I can see is to set SEVR=NO_ALARM in my device
support init_mbboDirect() routine, which seems very wrong.
Am I missing something obvious ?
Am I the only one who wants to use this to manipulate groups of bits,
rather than collecting a set of individual ones ? With the old version, you
could ignore the B* fields. Now you can't.
----
Brian McAllister Controls Programmer/Beam Physicist
[email protected] MIT-Bates Linear Accelerator
(617) 253-9537 Middleton, MA
- Navigate by Date:
- Prev:
Re: devNode, drvNode, drvSerial source? Peregrine M. McGehee
- Next:
Re: Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- 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: Problem talking CA across two CPUs in same crate??? Jeff Hill
- Next:
portable ca server john sinclair
- 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
|