Re: [foxboro] Unique Alarm Sounds

Dennis,

While I was teaching myself socket programming I a wrote a talking alarm
manager program.  Every alarm was unique.  Although the practicality of
such software was very low, it scored high on the funnality scale.  It
also became very annoying surprisingly quickly .  Basically I had a
alarm destination c program, like alarm line available on the cassandra
project, which took alarms, and placed them in a tcp socket that a Linux
box took formatted and passed to a human voice simulator. =20

Might not be the approach you are looking for, but a C program as an
alarm destination which plays sound files can do it.

Sean
Disclaimer
Current and future employers please note, I do do real work most of the
time, it was training really it was.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Dennis Stone
Sent: Wednesday, 22 June 2005 7:58 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Unique Alarm Sounds=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?
=20

Any help would be greatly appreciated.=20

=20

Dennis Stone

Process Control Engineer

Hunt Refining Company

dstone@xxxxxxxxxxxxxxxx <mailto:dstone@xxxxxxxxxxxxxxxx>=20

(205) 391-3345

(205) 391-3564 FAX

=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


EOM=0A=0ANOTICE - This message and any attached files may contain informa=
tion that is confidential and/or subject of legal privilege intended only=
 for use by the intended recipient. If you are not the intended recipient=
 or the person responsible for delivering the message to the intended rec=
ipient, be advised that you have received this message in error and that =
any dissemination, copying or use of this message or attachment is strict=
ly forbidden, as is the disclosure of the information therein. If you hav=
e received this message in error please notify the sender immediately and=
 delete the message.
 
 
_______________________________________________________________________
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: