On Wednesday 23 February 2005 14:40, Marty Kraimer wrote:
> Benjamin Franksen wrote:
> >On Wednesday 16 February 2005 20:42, Marty Kraimer wrote:
> >>If all that is desired to to make the record not be in alarm after
> >>initialization then just set
> >>
> >> field(SEVR,"NO_ALARM")
> >> field(STAT,"NO_ALARM")
> >> field(UDF,"0")
> >>
> >>In the record instance definition.
> >
> >Note that you can leave out SEVR and STAT as these are the default
> >values anyway.
> >
> >However, at least with 3.13.9 this doesn't work. The record (a bo) is
> >still UDF/INVALID after booting.
> >
> >Ben
>
> In both 3.13 and 3.14 dbCommon.dbd has the definitions:
>
> field(STAT,DBF_MENU) {
> prompt("Alarm Status")
> special(SPC_NOMOD)
> menu(menuAlarmStat)
> initial("UDF")
> }
> field(SEVR,DBF_MENU) {
> prompt("Alarm Severity")
> special(SPC_NOMOD)
> menu(menuAlarmSevr)
> initial("INVALID")
> }
>
>
>
> Thus the defaults are STAT=UDF and SEVR=INVALID.
Oops. I inferred what I said about the defaults from the output of dbst, which
threw your STAT/SEVR definitions out of my db file.
Ben
- Replies:
- Re: Initial STAT and SEVR for soft ai and ao records Benjamin Franksen
- References:
- RE: Initial STAT and SEVR for soft ai and ao records Mark Rivers
- Re: Initial STAT and SEVR for soft ai and ao records Benjamin Franksen
- Re: Initial STAT and SEVR for soft ai and ao records Marty Kraimer
- Navigate by Date:
- Prev:
RE: Flavors of Linux Tang, Johnny Y.
- Next:
Next EPICS Meeting (SLAC, April 27-29, 2005) Chestnut, Ronald P.
- 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: Initial STAT and SEVR for soft ai and ao records Marty Kraimer
- Next:
Re: Initial STAT and SEVR for soft ai and ao records Benjamin Franksen
- 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
|