>>> "CL" == Carl Lionberger <[email protected]> writes:
CL> For some time there were fields for specifying the one severity, zero
CL> severity, and change-of-state severity for each bit (yes, 48 fields)
CL> in mbbiDirectRecord.dbd; as far as I know there was never any code
CL> for dealing with these fields in mbbiDirectRecord.c and now in 3.13.3
CL> they have been removed from the dbd file.
The problem with trying to use these would be that the alarm status and
severity are global properties of the record. There is no way for a client
to know which bit(s) actually caused the record to go into alarm.
Without that, the utility of these alarms seems quite limited.
----
Brian McAllister Controls Programmer/Beam Physicist
[email protected] MIT-Bates Linear Accelerator
(617) 253-9537 Middleton, MA
- Navigate by Date:
- Prev:
Re: bitwise severities on mbbiDirect Benjamin Franksen
- Next:
Re: Support for HP8656B Andrew Johnson
- 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: bitwise severities on mbbiDirect Benjamin Franksen
- Next:
Support for HP8656B Vitaliy Vziskin
- 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
|