Experimental Physics and
Industrial Control System

"Brian McAllister" <[email protected]> · Fri, 24 Aug 2001 17:45:04 -0400

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

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System