Re: [foxboro] horn.cfg and System alarms

Problem #1 I'm not sure about.  Sending System alarms to a horn is something
we've never tried, so I can't really give you a good answer. I read in a CAR
on the CSC web site that the way to silence a Sys alarm that is configured
in horn.cfg is to hit the horn silence button on the Annunciator Keyboard or
the "Process" button if you have FoxView.  I think hitting any Annunciator
Keyboard key silences the horn, as well.  I don't think silencing the horn
has anything to do with the Sys key being solid or flashing or red or green.
It's kind of analogous to getting a process alarm.  It doesn't matter what
state the process block is in, the horn will go off and stay sounding until
you hit the button, regardless of whether the block returns from alarm or is
acknowledged, at least by default.  You can change the horn silencing
properties in init.user in the section HRN_OPT.

Problem #2 I agree, try the WP logical name of the AW.  Device Monitor
doesn't know from AW names, only WP logical names.  I'm pretty sure you have
to configure each AW with a WP logical name that is different than the AW
name in SysDef.  Click on SHOW...Available WP's in ICC to find the AW
logical name from the list.

Tim Lowell
Control Systems Engineer
Phillips Petroleum Company, Trainer Refinery
Phone:  610-364-8362
Fax:    610-364-8211
tlowell@xxxxxxxx


        -----Original Message-----
        From:   Loupe, Rory (RJ) [SMTP:RJLoupe@xxxxxxx]
        Sent:   Wednesday, April 24, 2002 11: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

Other related posts: