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 annunciation with ALH and other PC based systems
From: Elder Matias <[email protected]>
To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>
Date: Fri, 16 Jan 2015 18:25:13 +0000

Rod,

 

I was involved with a such a systems (and we needed to address that very concern that our regulator had). 

 

The two places where the alarm goes off Is in the field and in the control room. 

 

One could argue that the alarm going off in the field plays a safety role if it is purpose is to direct staff to leave the area.  Redundant and diverse solutions using both horns and lights would be a nice way of handling it.  There are some pretty nifty IEC 61508 certified monitors and horns on the market.   Personal preference I would try to do that one independently of EPICS as the hazard and risk analysis is simplified.

 

One could potentially argue the annunciation in the control room is not safety critical but safety related.  The safety issue is resolved if the local horn is going and staff have left the area.  Generally I would use a separate app with watchdogs etc.  I am aware of one lab with the regulator required that app to be running as a condition of operating the machine.

 

I think it comes down to how you do the Hazard and Risk Analysis and the mitigation you have in place. 

 

 

Elder Matias

Mighty Oaks

http://www.mightyoaks.com

 

 

----------------------

Subject:

RE: Alarm annunciation with ALH and other PC based systems

From:

"Munro Jr, John K." <[email protected]>

To:

Rod Nussbaumer <[email protected]>, epics Techtalk <[email protected]>

Date:

Wed, 14 Jan 2015 22:25:30 +0000

Hi Rod,

 

Background noises and alarm floods are also potential problems, so if alarms are really important, audio needs to be supplemented with visual alarms (i.e., a multi-factor approach needs to be considered).  Relying on audio alarms alone is probably not going to be satisfactory because someone is always going to be adjusting something to suit individual preferences.  Are you doing any alarm filtering?

 

John Munro

ORNL

 

 

-----Original Message-----

From: [email protected] [mailto:[email protected]] On Behalf Of Rod Nussbaumer

Sent: Wednesday, January 14, 2015 4:27 PM

To: epics Techtalk

Subject: Alarm annunciation with ALH and other PC based systems

 

Hi All:

 

Sorry that this isn't really an EPICS question, other than the tenuous

connection via Alarm Handler.

 

The question has been raised here about how to ensure that the audible

alarms from Alarm Handler are always audible. A number of places exist

where this can be disabled. The speakers can become faulty, the

wall-wart commonly used to power the speakers can become disconnected or

faulty, the volume control on the speakers can be turned down, the host

OS software controls can be turned down or muted either through accident

or software fault, audio cables can become faulty, and sound card

hardware can become faulty. Most of these will manifest only in silence.

 

Has anyone undertaken measures to monitor any of these components in

some way, or implemented hardware which is not subject to the common

frailties of commodity audio equipment used for control room alarms?

 

Any suggestions cheerfully accepted. Thanks.

 

Rod Nussbaumer

E-Linac Controls, TRIUMF

Vancouver, Canada.

 

 

Elder Matias, BSc,

CEO  T: 250.386.9398 x203 | [email protected]
MIGHTY OAKS  Business ~ IT ~ Community  27 Burnside Road West Victoria | TF: 866.386.9398 | www.mightyoaks.com

 




This e-mail is intended only for the person to whom it is addressed (the "addressee") and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use that a person other than the addressee makes of this communication is prohibited and any reliance or decisions made based on it, are the responsibility of such person. We accept no responsibility for any loss or damages suffered by any person other than the addressee as a result of decisions made or actions taken based on this communication or otherwise. If you received this in error, please contact the sender and destroy all copies of this e-mail.

Ce courrier est strictement reservé a l'usage de la personne a qui il est adressé (le destinataire). Il peut contenir de l'information privilégiée et confidentielle. L'examen, la réexpédition et la diffusion de ce message par une personne autre que son destinataire est interdite. Nous refusons toute responsabilité a l'égard des pertes ou des dommages subis par une personne autre que le destinataire par suite de decisions ou de mesures fondées sur le contenu de cette communication ou autrement. Si vous avez recu ce courrier par erreur, veuillez communiquer avec son expéditeur et en détruire toutes les copies.

Navigate by Date:
Prev: Re: How to access bigstring using channel access Ralph Lange
Next: seg fault in sseq record when using AfterN option Pearson, Matthew R.
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 annunciation with ALH and other PC based systems Maren Purves
Next: industrial barcode reader Pearson, Matthew R.
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 ·