EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: alarm handler confusion (and solution)
From: Janet Anderson <[email protected]>
To: Maren Purves <[email protected]>
Cc: [email protected]
Date: Thu, 30 Aug 2001 16:13:26 -0500
Maren Purves wrote:

> What I had hoped is that we can start our alarm handlers from the
> command line (at reboot time of the workstation that they usually
> run on), silenced forever (works, thanks), and such that without
> ever opening an extra window or acknowledging an alarm the operator
> can find out by looking at this workstation (which isn't in front
> of the operator - the operator console has real estate problems
> as it is) whether an alarm that generated an email warning is still
> active - it is easier to go next door and look at the alarm handler
> than it is to look at the hardware that causes the alarm.
> We don't need the alarms to get acknowledged, but they have to be
> dealt with.
> 

If you don't want unacknowledged transient alarms to appear as alarms 
on the alh runtime window, you could execute alh in global mode after
setting the ACKT (acknowledge transients?) fields to NO (the default is
YES) in the .db files, or you could execute alh in local mode and set
the "Act/NoAck Transient Alarms" field in the alarm channel mask of
the alarm channels to T. 

Janet


References:
alarm handler confusion (and solution) Maren Purves
Re: alarm handler confusion (and solution) Ralph . Lange
Re: alarm handler confusion (and solution) Maren Purves
Re: alarm handler confusion (and solution) Ralph . Lange
Re: alarm handler confusion (and solution) Maren Purves
Re: alarm handler confusion (and solution) Janet Anderson
Re: alarm handler confusion (and solution) Maren Purves

Navigate by Date:
Prev: NI-1014 GPIB and RISC CPUs (PowerPC, SPARC etc). Andrew Johnson
Next: Re: Image capture Noboru Yamamoto
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  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: alarm handler confusion (and solution) Maren Purves
Next: Image capture Rolf Keitel
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·