Re: [foxboro] PIDA block weirdness
- From: "BrianLong" <blong@xxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 24 Jan 2005 14:47:18 -0600
I've seen something similiar to this. It had to do with the CINHIB option
set in the compound vs. the priority of the alarm in the block.
Brian Long
AKD
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Lowell, Tim:
Sent: Monday, January 24, 2005 2:26 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] PIDA block weirdness
List,
We had a weird one today, and I was wondering if anybody had ever
witnessed similar behavior.
One of our console guys was trying to inhibit the alarms on a PIDA block
from a custom PIDA faceplate, and it wouldn't inhibit. Then he tried to
force the block into a MEASHI alarm by changing the MEASHI alarm
setting, and it would no longer go into alarm. We looked at it, and the
block really was inhibited, but the custom faceplate didn't show it, nor
did the standard PIDA detail display. Then we uninhibited it from the
engineering station in a cmdtool window using omgetimp on the .INHIB
parameter. We verified that the .INHIB parameter was FALSE, and that
the .CINHIB parameter for the compound was FALSE. We then tried to
force it into alarm again, and it still wouldn't go into alarm. So next
we tried to hit "enter" in ICC on some parameters and hit "DONE". No
change. Then we deleted/undeleted the block. Still nothing.
Finally, we completely deleted the block, checkpointed, and then rebuilt
the block from scratch. Now it works fine. Has anyone ever seen such a
thing? I'm a little concerned that we have other blocks in the same
state and don't even know it. The danger is that any blocks in this
state could go into an alarm condition, and no alarm would sound. The
last time anybody might have edited this block was maybe 2 years ago.
It's a fuel gas flow to a furnace, so it's not something that we would
want to modify very often under any circumstances. If you've ever seen
anything like this, please let me know.
Thanks,
Tim Lowell
Control Systems Engineer
ConocoPhillips Trainer Refinery
(610) 364-8362
tim.c.lowell@xxxxxxxxxxxxxxxxxx
_______________________________________________________________________
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
- References:
- [foxboro] PIDA block weirdness
- From: Lowell, Tim:
Other related posts:
- » Re: [foxboro] PIDA block weirdness
- » Re: [foxboro] PIDA block weirdness
- » Re: [foxboro] PIDA block weirdness
- » Re: [foxboro] PIDA block weirdness
- [foxboro] PIDA block weirdness
- From: Lowell, Tim: