Marty Kraimer wrote:
>
> Breakpoint table alarm problem when reaching end of table.
> Benjamin suggested adding a field BRSV.
> Instead of adding yet another field why not just change
> recGblSetSevr(pai,SOFT_ALARM,INVALID_ALARM)
> to
> recGblSetSevr(pai,SOFT_ALARM,MAJOR_ALARM)
> when cvtRawToEngBpt or cvtEngToRawBpt returns an error.
Because a field would give a lot more flexibility (what if I want e.g.
NO_ALARM?) at almost no cost (two bytes per analog record).
In principle, I agree that uncontrolled inflation of fields should be
avoided. But if additional fields bring a real advantage they should be
added. (Speaking economically, an inflation target of zero is definitely
*not* a good idea).
Only weakly related: Since alarm status is a menu (menuAlarmStat) but
has more than 16 entries, monitoring the STAT field of a record in
string representation gives incorrect results with the current CA
version (all values over 15 will be represented by an empty string). I
dearly hope this will be solved with the upcoming next version of CA!
Ben
- Replies:
- Re: Apropos making fields configurable Ralph . Lange
- References:
- RE: Apropos making fields configurable Redman, Russell O.
- Re: Apropos making fields configurable Benjamin Franksen
- Re: Apropos making fields configurable Marty Kraimer
- Navigate by Date:
- Prev:
Re: Apropos making fields configurable Marty Kraimer
- Next:
Re: Apropos making fields configurable Ralph . Lange
- 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: Apropos making fields configurable Marty Kraimer
- Next:
Re: Apropos making fields configurable Ralph . Lange
- 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
|