Re: [foxboro] Silence Horn functionality without Annunciator Keyboard

All,

Just a point of clarification:

1) Silencing a horn does not acknowledge the alarm.
2) Acknowledging an alarm will silence the horn.

I agree that the I/A Series presumes that someone will be watching the
operator console and that the horn is intended to draw attention to that
console.

The mechanisms that I know to silence a horn remotely are:

Option 1 - External horns

1) Use external horns exclusively
2) Monitor a signal in a sequence block and use the sequence block to
reset the external horn contact.



Option 2 - Internal and/or external horns

1) Use console and/or external horns
2) Monitor a signal to silence the horn in a sequence block
3) Have the sequence block issue a command to a WP to silence the horn
using the appropriate DM command.

I don't really like the second approach because it requires more
sophisticated error handling - incase the WP is down or the network is
busy.




Regards,
 =

Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (voice)
713 329 1600 (switchboard)
713 329 1944 (fax)
alex.johnson@xxxxxxxxxxxxxxxx
http://ips.invensys.com =


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Doucet, Terrence
Sent: Tuesday, May 20, 2008 1:09 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Silence Horn functionality without Annunciator
Keyboard


Ron,

I think what is missing is to be able to ACK alarms when you are not in
=3D
front of a workstation. Perhaps there is only one operator who is in the
=3D
field working when an alarm comes in. It would be nice to cut off the =3D
klaxon before he has to go all the way to the screen. Perhaps he was =3D
doing something that he knew was going to fire the klaxon, so he already
=3D
knows what caused the alarm.

Not an easy solution in IA where the alarm system is based on the =3D
premise that you need to see what caused the alarm (be in front of a =3D
workstation) in order to ACK it. This is not necessarily a bad idea.

He could probably take a contact input to an IND block where the IND =3D
will force a display manager command in a station where the alarm is =3D
active and that station is in a common alarm group with the other =3D
stations receiving the alarm.

Terry


Object=3DA0: Re: [foxboro] Silence Horn functionality without Annunciator
=3D
Keyboard

Did you know F12 on the regular keyboard will also do it? Maybe you can
turn on the On-Screen Keyboard and use the F12 there? That is if you
have a workstation.
Also, I would think that you could use a discrete input (button) and
have it trigger in a seq block to do a silence horn silence command.
Anyone else have ideas?

Ronald G. Schafer
Distributed Controls System Administrator
White Birch Paper Company
Bear Island L.L.C. Division
Ashland VA, 23005
Phone 804-227-4034
Fax 804-227-4052

-- No attachments (even text) are allowed --
-- Type: text/x-vcard
-- File: rschafer@xxxxxxxxxxxxxxxxxxxxxxxxxx
-- Desc: rschafer@xxxxxxxxxxxxxxxxxxxxxxxxxx


=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
 =

 =

_______________________________________________________________________
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=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
 =



* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual=
 or entity to whom they are addressed. Please do not copy it or use it for =
any purposes, or disclose its contents to any other person. Further, this e=
-mail and any associated files may be confidential and further may be legal=
ly privileged. This email is from the Invensys Process Systems business uni=
t of Invensys plc which is a company registered in England and Wales with i=
ts registered office at Portland House, Bressenden Place, London, SW1E 5BF =
(Registered number 166023).  For a list of European legal entities within t=
he Invensys Process Systems business group, please click here http://www.in=
vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77.

If you have received this e-mail in error, you are on notice of its status.=
 Please notify us immediately by reply e-mail and then delete this message =
from your system. Thank you for your co-operation. You may contact our Help=
desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx T=
his e-mail and any attachments thereto may be subject to the terms of any a=
greements between Invensys (and/or its subsidiaries and affiliates) and the=
 recipient (and/or its subsidiaries and affiliates).


 
 
_______________________________________________________________________
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: