EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: alarm severity set by other channel values
From: "J. Lewis Muir" <[email protected]>
To: [email protected]
Date: Thu, 24 Sep 2015 12:37:24 -0500
On 9/24/15 12:12 PM, Andrew Johnson wrote:
> The use of MS/MSS/MSI flags on input links is the other way to
> manipulate alarm severities; you might be able to insert ai records
> in the path to your other channels and use their HIHI/HIGH/LOW/LOLO
> fields to do what you need, but beyond this you're probably limited to
> coding your own behaviour in either sub/aSub or custom record types.

I second this; I've done something similar before.  It's a hack, but I'm
unaware of a nicer way to do it purely in the database.

Another variant of this that I've used is, when I don't need to be able
to disable the target record, I have a separate mbbi record to control
the severity, and then I specify it with "MS" in the SDIS field of the
target record with a DISV value that will never occur such that it will
never disable the target record, but it will propagate the severity:

--8<--
record(stringin, "$(P)$(D):Ap$(A)AutoTuneStat") {
  field(SDIS, "$(P)$(D):Ap$(A)AutoTnStatSev.VAL NPP MS")
  field(DISV, "-1") # Will never disable, but will propagate severity
  field(VAL, "Idle")
  field(PINI, "YES")
}

record(mbbi, "$(P)$(D):Ap$(A)AutoTnStatSev") {
  field(VAL, "0")
  field(ZRVL, "0")
  field(ZRST, "NO_ALARM")
  field(ONVL, "1")
  field(ONST, "MINOR")
  field(ONSV, "MINOR")
  field(TWVL, "2")
  field(TWST, "MAJOR")
  field(TWSV, "MAJOR")
  field(THVL, "2")
  field(THST, "INVALID")
  field(THSV, "INVALID")
  field(PINI, "YES")
}
-->8--

Regards,

Lewis

References:
alarm severity set by other channel values Patrick Thomas
Re: alarm severity set by other channel values Andrew Johnson

Navigate by Date:
Prev: Re: alarm severity set by other channel values Andrew Johnson
Next: Re: Unable to build support modules on Windows, with base 3.15.2 Kevin Peterson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: alarm severity set by other channel values Andrew Johnson
Next: Oerlikon leybold MAG.DRIVE iS peter.leicester
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·