Re: [foxboro] Unique Alarm Sounds

Using a COUT tied to the horn.cfg file sounds like a great idea, only
one problem, my CP's/FBM's are 1000+ feet away.  I do have a 1X8 in the
control room where a CP could go but would be costly to purchase a
dedicated CP for only a couple of FBM channels tied to horns.=20

Dennis Stone
Process Control Engineer
Hunt Refining Company
dstone@xxxxxxxxxxxxxxxx
(205) 391-3345
(205) 391-3564 FAX
=20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin FitzGerrell
Sent: Tuesday, June 21, 2005 3:49 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Unique Alarm Sounds

Dennis,

External horns work well and are used in many of the control rooms I've
worked=20
with. =20

Consider also using the output to drive some type of light or other
indication=20
in addition to the horn.  I've worked with operators in several control
rooms=20
where in spite of the horn sounds being the same for several years,
operators=20
just didn't easily associate the horn sound with a particular unit (just
look=20
what happens in a room when a cell phone rings -- everyone checks their
phone=20
even if it's not their ring-tone).  This was particularly true when
operators=20
might be responsible for different units from one day to the next.  They
found=20
it much easier to hear the horn and then look to their console(s) to see
if=20
the alarm light was on over their area.  Associating alarm priorities
with=20
different lights on a stack in each area works well too.


Regards,

Kevin FitzGerrell
Sr Control Systems Engineer
Kinleith Pulp & Paper
Carter Holt Harvey Ltd.
+64 27 460 9994
Quoting "Lowell, Tim:" <Tim.C.Lowell@xxxxxxxxxxxxxxxxxx>:

> Dennis,
>=20
> The usual answer is to configure your horn.cfg file to output priority
> 1
> and 2 alarms, or whatever priority you wish, to a COUT block driving
an
> FBM10 (or the 200 series equivalent) 120V AC output which then drives
a
> standard annunciator horn. You can send different priorities to
> different horns, and have separate horns for each plant unit or area.
> We do that here, and it's very successful. If you want more info,
> contact me off-line.
>=20
> Tim Lowell
> Control Systems Engineer
> ConocoPhillips Trainer Refinery
> (610) 364-8362
> tim.c.lowell@xxxxxxxxxxxxxxxxxx
>=20
>=20
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Dennis Stone
> Sent: Tuesday, June 21, 2005 3:58 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] Unique Alarm Sounds=3D20
>=20
> Our facility will have an integrated control room, 3 separate units
> being operated by three separate operators from the same control room
> with six screens per operating unit. My problem is with alarming,
> currently only one operator is operating from this control room now
but
> will be joined by another in a couple of months. How can I
> differentiate alarms based on sound so that each operating area has a
> unique sound? I tinkered with the built-in alarm sounds and these are
> unacceptable due to lack of volume or tone. Does anyone have any ideas
> short of outputting the existing horn output to a distortion device
and
> then to an amp connected to a set of external speakers?
> =3D20
>=20
> Any help would be greatly appreciated.=3D20
>=20
> =3D20
>=20
> Dennis Stone
>=20
> Process Control Engineer
>=20
> Hunt Refining Company
>=20
> dstone@xxxxxxxxxxxxxxxx <mailto:dstone@xxxxxxxxxxxxxxxx>=3D20
>=20
> (205) 391-3345
>=20
> (205) 391-3564 FAX
>=20
> =3D20
>=20
>=20
> =3D20
> =3D20
> ______________________________________________
> _________________________
> This mailing list is neither sponsored nor endorsed by Invensys
Process
> Systems (formerly The Foxboro Company). Use the info you obtain here
at
> your own risks. Read
http://www.thecassandraproject.org/disclaimer.html
> =3D20
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> to unsubscribe: =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> =3D20
> =20
> =20
> ______________________________________________________________________
> _
> This mailing list is neither sponsored nor endorsed by Invensys
Process
> Systems (formerly The Foxboro Company). Use the info you obtain here
at
> your own risks. Read
http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
> =20

=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: