Re: [foxboro] horn.cfg and System alarms


Two quick thoughts. 

Problem #1 We have the same problem but we can clear the system alarm (after
acknowledging it in the SMDH) by clicking on the process button.  We only
have system alarms tied to Extsys, all the rest are for Process Alarms.  I
don't think system alarms have 1-5 priorities.  We also have 1's in the
fields for AnnunKeyboard1&2 for Sys and Process Alarm priorites.  I realize
this sounds weird - clicking on the process alarm to clear system alarms but
it works.  See the CAR response below.

Problem #2 We have had a similar problems with alarms not presenting at a
station.  For one situation it worked initially than later quit working. We
tracked it to the Device Monitor incorrectly failing the station.  We also
have forgotten to add the logic name to the compound parameters block and
that caused a similar problem as Gaylon pointed out.

To be honest, I'm not sure how all this comes together and works. 

Gary Anderson
Arizona Public Service

CAR Response
********************************************************************

      Gary:

        Below please find response(s) to Customer Action Request(s) on which
you have been named as Submitter and/or Foxboro Contact.  Please ensure all
responses are communicated to the Customer Contact at your earliest possible
convenience.
        Regards,
        Pat Brandao
THE FOXBORO COMPANY CUSTOMER ACTION REQUEST

CUSTOMER   : Arizona Public Service       CAR          : 991199
ADDRESS    : POB 52034                    STATUS       : RESOLVED
CITY       : Phoenix
STATE/PROV : AZ                           DATE OCCURRED: 9/03/99
POST CODE  : 85072-2034                   LOGIN        : 9/07/99
SITE       :                              INTERIM DATE : 10/07/99
IR Number# :                              LOGOUT       : 2/17/2000
CUST REF # :
CUST. CONT : Gary T. Anderson             PRODUCT      : I/A
TELE #     : 602-393-5742                 VERSION      : 6.1.1
CUST E-MAIL: gtanders@xxxxxxxx <mailto:gtanders@xxxxxxxx>             SOURCE
: CUSTOMER SITE
CUST FAX   : 602-393-5467                 HARDWARE     : 50
SUBMITTER  : G. Anderson                  REPORT TYPE  : ENHANCEMENT
SUB E-MAIL : gtanders@xxxxxxxx <mailto:gtanders@xxxxxxxx>
PLATFORM     :
SUB FAX    : 602-393-5467                 IMPACT       : MINOR
FOX CONT   :                              REPRODUCIBLE : ALWAYS
FOX E-MAIL :                              FOX FAX      :
PROD TYPE  : FoxView
PROD CAT   : DISPLAY                      REGION       : D06
ATTACHMENTS:
CONFIGURATION: 1FTCP40, 1AW51B, 2WP51B
DESCRIPTION OF DIFFICULTY:
10/07/99 - Sent to (CP) as enhancement request.
This CAR is to request an improvement into the way the FoxView "System"
alarm button interface to COUT block works for the resetting of the contact
output, presently you have to click on the FoxView "Process"  alarm button
to allow this block to reset. At our site, we use seperate COUT blocks for
the Process and System alarms.  With the existing situatuation, if a
Foxboro "System" alarm comes in and is presented by our Plant Annunicator
System, the only way available to reset the Plant Annunicator System is to
click on the Foxboro "Process" alarm button.  Basically, if the "System"
alarm button interface worked the same as the "Process" alarm button for
resetting the COUT block our needs would be met.  We've been informed by
Foxboro CSC that this resetting of "System" and "Process" alarms works this
way because the typical interface is by the Foxboro Annunciator Keypad
which has only one reset button that services either alarm.  We believe our
request has some merit as it seems logical that each button should reset
similarly.  We are in this situation because our site only use CRT displays
with a trackball for our operator interface.   I speculate that if a touch
screen only interface were used, that this same situation would be present.
FOX ANALYST: M. LeBlanc       DATE QUAL: 2/17/2000 SC: E    SENT TO: MKT
COMMENTS: Reviewed by M. LeBlanc        CS PRIOR:           PT #:
                                                            SDE ENG:
CAR : 991199    LAST RESPONSE DATE: 2/17/2000    DUPs: 1 *    DUP OF:
2/17/2000 - Response from TAC (NL):
Your request for an improvement into the way that FoxView System alarm
button interfaces to a COUT block has been reviewed by Marketing. At this
time, The Foxboro Company has no plans to incorporate any modifications
into an upcoming release.  This CAR is now closed, but will remain active
in the engineering log for future consideration.
This CAR is now Resolved.
TARGET DATE:  2/10/00                TARGET VERSION:
   QF DATE :                                  QF # :
<<END>> of CAR Response ****************************************************

-----Original Message-----
From: Hicks, Gaylon F. [mailto:gfhicks@xxxxxxx]
Sent: Wednesday, April 24, 2002 9:03 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] horn.cfg and System alarms



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:             http://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:             http://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:             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: