[foxboro] horn.cfg and System alarms
- From: <Robert.Brennen@xxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 25 Apr 2002 09:29:33 -0600
Greetings,
We do something similar with our horn.cfg and the System alarm. Foxboro has
told us that there is no way to clear the "IN_1" other than to do what you have
done.... manually. The horn.cfg acts as a one shot and latches the I/O point.
...regards
Rob Brennen
Shell Canada
Scotford Refinery
> 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.
>
_______________________________________________________________________
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
- References:
- [foxboro] horn.cfg and System alarms
- From: Loupe, Rory (RJ)
Other related posts:
- » [foxboro] horn.cfg and System alarms
- » [foxboro] horn.cfg and System alarms
- [foxboro] horn.cfg and System alarms
- From: Loupe, Rory (RJ)