Re: [foxboro] PIDE Alarming
- From: "Douglas G. Lloyd" <doug@xxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 23 Apr 2009 14:23:13 -0400
Gonzalo,
You need to set up INHOPT correctly...
INHOPT
Inhibit Option specifies the following actions applying to all block alarms:
0 = When an alarm is inhibited, disable alarm messages but do not disable
alarm detection.
1 = When an alarm is inhibited, disable both alarm messages and alarm
detection. If an alarm condition already exists at the time the alarm
transitions into the inhibited state, clear the alarm indicator.
2 = Same as 0 for all inhibited alarms. For all uninhibited alarms,
automatically acknowledge "return-to-normal" messages. "Into alarm" messages
may be acknowledged by explicitly setting UNACK false.
3 = Same as 1 for all inhibited alarms. For all uninhibited alarms,
automatically acknowledge "return-to-normal" messages. "Into alarm" messages
may be acknowledged by explicitly setting UNACK false.
Regards,
Doug Lloyd
DGL Controls
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Gonzalo Díaz
Sent: Thursday, April 23, 2009 1:42 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] PIDE Alarming
I want to set an alarm for a PIDE output which controls a fan's motor, to be
enabled only when another fan's motor is stopped. To do so, I've programmed
a CIN block which reads the secondary motor status and its output is
connected to the PIDE INHIB parameter. It didn't work, so I changed the IVO
parameter of the CIN block but the result was the same. Is there any other
parameter I should take into consideration to do this successfully?
Thanks in advance,
Gonzalo Diaz
Mantenimiento Planta LPG
Servicios Buproneu S.A. (Capex S.A.)
Yacimiento "Agua del Cajón"
TE: ++54 299 493 1200 int 260
Gonzalo.Diaz@xxxxxxxxxxxxxxxxx<mailto:Gonzalo.Diaz@xxxxxxxxxxxxxxxxx>
_______________________________________________________________________
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: