Re: mbboDirect problems

[Eric Norum <wenorum@lbl.gov>]

Thanks for the quick analysis.  I’m not 100% sure that that meets the “principle of least surprise”, but it does explain what I’m seeing.  For now I’ve taken Ned Arnold’s suggest to set PINI=YES.  In the long run I’ll get rid of all word-writes and have nice screens with individual bit controls.

On Sep 8, 2014, at 3:01 PM, Mark Rivers <rivers@cars.uchicago.edu> wrote:

I think that is the way the mbboRecord works.  This is from the process() function:

 

        if(prec->nsev < INVALID_ALARM

        && prec->sevr == INVALID_ALARM

        && prec->omsl == menuOmslsupervisory) {

            /* reload value field with B0 - B15 */

            int offset = 1, i;

            unsigned char *bit = &(prec->b0);

            for (i=0; i<NUM_BITS; i++, offset = offset << 1, bit++) {

                if (*bit)

                    prec->val |= offset;

                else

                    prec->val &= ~offset;

            }

        }

        /* convert val to rval */

        convert(prec);

 

If I read this correctly then the first time the record processes sevr==INVALID_ALARM so it will overwrite the VAL field with the Bn fields.

 

Mark

-- 
Eric Norum
wenorum@lbl.gov