Re: [foxboro] horn.cfg and System alarms
- From: "Hicks, Gaylon F." <gfhicks@xxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 24 Apr 2002 12:02:44 -0400
As for problem #1, we have had this problem at our site from initial
installation in 1996, but I had thought (and was told by Foxboro) that it
was due to our running our system monitors on PWs. The elegant (not) fix
that we came up with is the script that I sent out earlier. The drawback of
this approach is that the contact output is cleared after a set time even if
the condition is not cleared. The advantage of this is that one failure
will not mask any subsequent failure. I've attached the script at the end
of this message.
Problem #2 - You need to put the WP logical name associated with the AW in
the compound parameters, and that should work. If you have already tried
that and it doesn't work, I have no clue.
Good Luck,
==================================================
Gaylon Hicks
Tennessee Valley Authority, Browns Ferry Nuclear Plant
Mail Stop PEC-2C
PO Box 2000
Decatur, AL 35609
Phone: (256) 729-7804 Fax: (256) 729-2047
email: gfhicks@xxxxxxx
FedEx Address: Shaw Road, Athens, AL 35611
==================================================
**********************************************************
#!/bin/sh
# -- This program will check the RFWCS trouble alarm output and, when TRUE
# -- (in alarm) automatically reset the alarm 240 seconds later.
# -- The AlmReset process id (PID) is written to the file AlmReset.PID
#
# Written by Gaylon Hicks, 09/30/97
#
echo $$ > /usr/applic/AlmReset.PID
while test "TRUE"
do
if test "`/usr/fox/bin/tools/omget RXLVL:1CO012.IN_8 | grep TRUE`"
then
sleep 240
/usr/fox/bin/tools/omset -b F RXLVL:1CO012.IN_8
echo ">>>> RFWCS Trouble Alarm Auto Reset - `date` <<<<" | lp -dLP01
echo ">>>> RFWCS Trouble Alarm Auto Reset - `date`" >>
/usr/applic/AlmReset.log
fi
sleep 60
done
*****************************************************************
-----Original Message-----
From: Loupe, Rory (RJ) [mailto:RJLoupe@xxxxxxx]
Sent: Wednesday, April 24, 2002 10:40 AM
To: 'Foxboro - Cassandra'
Subject: [foxboro] horn.cfg and System alarms
Below is the horn.cfg from an AW51B running 6.1. The SYSMON1 is a BLNALM
block with nothing connected to IN_1. SYSMON1.IN_1 is connected to IN_8 of
an MCOUT block which is configured to a FBM and wired to an external
Panalarm/Ronan.
Problem #1 : The alarm activates for a System alarm but does not clear
SYSMON1.IN_1 when the system alarms have been acknowledged. I have to go in
and manually toggle SYSMON1.IN_1.
Problem #2 : The alarm does not activate when any process alarm becomes
active. The AW is not used as an operator workstation so no compounds have
the AW letter bug in the group device for any compounds. I suspected that
could be the problem, so I configured an alarm to be sent to the AW with a
priority of 1 and the external alarm did not sound nor did SYSMON1.IN_1
become true.
Does anyone have a solution to these problems? Any help would be much
appreciated!
Rory Loupe
Dow Chemical
#
# Alarm Alert Horn Configuration File
# ===================================
# Process Alarm
# Priorities
# SYS 1 2 3 4 5
# --- -- -- -- -- --
1 LID BAW001
2 AnnunKeyboard1 0 0 0 0 0 0
3 AnnunKeyboard2 0 0 0 0 0 0
4 Console 0 0 0 0 0 0
5 Extsys SYS_ALARM:SYSMON1.IN_1
6 Extpri1 SYS_ALARM:SYSMON1.IN_1
7 Extpri2 SYS_ALARM:SYSMON1.IN_1
8 Extpri3 SYS_ALARM:SYSMON1.IN_1
9 Extpri4 SYS_ALARM:SYSMON1.IN_1
10 Extpri5 SYS_ALARM:SYSMON1.IN_1
#
# Support of multihead workstation additional horns:
# 2nd console horn and annunciator keyboards 3 and 4.
#
11 Console2 0 0 0 0 0 0
12 AnnunKeyboard3 0 1 1 0 0 0
13 AnnunKeyboard4 0 1 1 0 0 0
Rory Loupe
The Dow Chemical Company
LHC-3
P.O. Box 150, Building 6801 21255 highway 1,
Building 6801
Plaquemine, LA 70765-0150 USA Plaquemine, LA 70764 USA
Phone: 225.353-6409 Fax: 225.353.6968
E-mail: RJLoupe@xxxxxxx
_______________________________________________________________________
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
Other related posts:
