Experimental Physics and
Industrial Control System

Marty Kraimer <[email protected]> · Wed, 11 Jun 1997 09:15:24 -0500

Jeff is correct.
This will be fixed in next 3.13 release.
The affected record types are bi, bo, mbbi, mbbo.

Marty

Jeff Hill wrote:
> 
> > HOWEVER,
> >
> > The biRecord.c support code is not incorrect because there get_enum_str,
> > put_enum_str, get_enum_strs will ONLY get called if the field type
> > in question is DBF_ENUM. The only such field in the biRecord is VAL.
> > Many record support modules in base make this assumption.
> >
> 
> Yes, but PV values in the CA server monitor queue will be ignored in favor
> of the current value in the record if we leave the code as it is today.
> Therefore, clients that monitor the .VAl field of a bo record as a
> string will see the sequence of events "on off on" converted
> to "on on on" if the events are spaced closely together in time.
> 
> Explanation:
> This is because, when dbGetField() is called, the dbAddr structure
> is pointing at the value on the CA monitor queue and not at the
> .VAL field. The bo record's get_enum_str() routine ignores the
> dbAddr structure passed in and always converts  the VAL field
> to a string (returning the current and not the historic value of
> the .VAL field).
> 
> Jeff

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System