Re: [foxboro] Horn silencing
- From: "Grace, Kathy" <kathy.grace@xxxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 1 Feb 2010 10:02:54 -0500
The workstations in a CAG can be made to silence the horn for all workstations.
The issue with the alarm panel / table files needing to be the same has to do
with recovering alarms from a backup workstation not silencing the horns. This
can be confusing because both CAGs and backup workstations are configured in
the commgrp.cfg file.
Kathy
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Terry Doucet
Sent: Wednesday, January 27, 2010 4:37 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Horn silencing
Jack,
I think that when you put AW's and WP's into a common alarm group they must
have the same alarm panel and table and when you reboot one station in that
group, it will go to look at the current alarms in the "other" station and make
his alarms match. I don't think this will work for Priority and non-Priority
stations (receiving different alarms).
But it has been a while since I worked on the commgrp.cfg.
Terry
> Subject: Re: [foxboro] Horn silencing
> Date: Wed, 27 Jan 2010 09:43:12 -0600
> From: Jack.Easley@xxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
>
> Check into configuring /usr/fox/alarms/commgrp.cfg. Search for details on
> configuration commgrp.cfg in E-doc or CSC site.
>
> Jack Easley
> Sr. I&C Technician
> Luminant Power, Martin Lake Plant
> Phone 903.836.6273
> jack.easley@xxxxxxxxxxxx
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Jeff Hurt
> Sent: Wednesday, January 27, 2010 8:43 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] Horn silencing
>
> We have our nonpriority alarms going to one WP and our priority alarms going
> to a different WP. The priority alarms pick up a contact out from the
> horn.cfg file and drive siren. The contact out does not drop out until the
> alarm is silenced. I can silence the alarm from the WP where the priority
> alarm is directed to but I cannot silence the alarm from the WP where the
> nonpriority alarms are sent. Any thoughts on how what I can do to silence
> the alarm from the nonpriority WP?
> Thanks,
> Jeff
>
>
>
> _______________________________________________________________________
> 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: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
>
> _______________________________________________________________________
> 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: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
_________________________________________________________________
Say Happy New Year with Messenger for Mobile.
http://go.microsoft.com/?linkid-06117
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at Portland House, Bressenden Place, London,
SW1E 5BF (Registered number 166023). For a list of European legal entities
within the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto may be
subject to the terms of any agreements 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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
