Re: [foxboro] PIDA block weirdness
- From: Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 25 Jan 2005 10:49:08 +1300 (NZDT)
Below is a copy of what a PIDA block looks like in your checkpoint file. Makes
it easy to see configured alarms, and inhibit status as seen in the CP. Look at
ALMOPT to see what's configured for alarming, and INHIB and INHALM for inhibits.
Regards,
Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel: +64 (9) 573 7690
Fax: +64 (9) 573 7691
COMPOUND-BLOCK-PARAMETER REPORT
@ LEGEND FOR CONNECTION TYPE:
@
@ i= input parameter
@ o= output parameter
@ |= non-connectable parameter
@ == non-settable parameter
<trimmed>
NAME = BOILER:TC00001 (4:10) TYPE=123 PERIOD=2 PHASE=0
DESCRP='VESSEL TEMPERATURE'
TYPE == 'PIDA'
DESCRP == 'VESSEL TEMPERATURE'
PERIOD == 2
PHASE == 0
ALMOPT == 0x00020010
AUTSW i= F
BATCHO == F
BBIAS |= 0.0
BCALCI i= 83.0284 l=local BOILER:TCV00001.BCALCO
BIAS i= 0.0
BTRKOP == F
CEOPT == 1
DALOPT == 0
DEFINE == T
DELTI1 == 0.2
DELTI2 == 1.0
DELTO1 == 0.5
DERIV i= 0.0
DEVADB |= 0.0
DEVGRP |= 1
DEVPRI i= 5
DEVTIM == 0
DTIME i= 0.0
EI1 == 'C'
EI2 == '% '
EIN == '% '
EO1 == '% '
ERCODE == 0
FBK i= 83.0284 l=local BOILER:TCV00001.BCALCO
FBTBLK i= 0
FFTBLK i= 0
FILTER i= 0.0
FLBOPT == 0
HDALIM i= 100.0
HDATXT == ' '
HHAGRP |= 1
HHALIM i= 100.0
HHAOPT == 0
HHAPRI i= 5
HHATXT == ' '
HOALIM i= 100.0
HOATXT == ' '
HOLD i= F
HOLIM i= 105.0
HSCI1 == 100.0
HSCI2 == 100.0
HSCIN == 100.0
HSCO1 == 100.0
HZONE i= 100.0
INCOPT == T
INHALM i= 0x0000
INHIB i= F
INHOPT == 3
INITI i= 0 l=local BOILER:TCV00001.INITO
INITLR == 2
INITMA == 1
INITSE == 0
INT i= 0.1
KBIAS |= 1.0
KD i= 10.0
KZONE i= 1.0
LDALIM i= -100.0
LDATXT == ' '
LIMOPT == 2
LLALIM i= 0.0
LLATXT == ' '
LOALIM i= 0.0
LOATXT == ' '
LOCKID == ' '
LOCKRQ |= F
LOCSP == F
LOCSW i= F
LOLIM i= -5.0
LOOPID |= '12800001'
LR i= T
LSCI1 == 0.0
LSCI2 == 0.0
LSCIN == 0.0
LSCO1 == 0.0
LZONE i= 100.0
MA i= T
MALOPT == 2
MANALM == 1
MANFS == F
MANSW i= F
MBADOP == F
MCLOPT == F
MEAS i= 40.127 l=local BOILER:TT00001.PNT
MEASDB |= 2.0
MEASGR |= 4
MEASHL i= 75.0
MEASHT == ' '
MEASLL i= 0.0
MEASLT == ' '
MEASNM == ' '
MEASPR i= 2
MODOPT == 4
MULTIN i= 100.0
NLNBLK i= 0
NONLOP == F
OALOPT == 0
OSV == 5.0
OUT2 i= 83.0284
OUTADB |= 0.0
OUTGRP |= 1
OUTNM == ' '
OUTPRI i= 5
OWNER |= ' '
PBAND i= 400.0
PERTIM == 60.0
PRIBLK == F
PRLOAD i= 0.0
PROPT == T
PRSCAS == 4
PRSCON == 3
REMSW i= F
RI1 == 100.0 0.0 0.2
RI2 == 100.0 0.0 1.0
RIN == 100.0 0.0 0.0
RO1 == 100.0 0.0 0.5
RSP i= 40.0 l=local BOILER:TC00001.SPT
SE |= F
SPCLMP == F
SPHLIM i= 100.0
SPLCOP == F
SPLLAG i= 1.0
SPLLIM i= 0.0
SPLRDY i= F
SPRAMP i= F
SPRATE i= 0.0
SPROPT == 0
SPTARG i= 0.0
STATEB i= -2
STATEF i= -2
STRKOP == F
SUPGRP == 1
SUPOPT == 0
TRACK i= 0.0
TRKENL i= F
TSAMPL i= 0.0
Quoting Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>:
> Tim,
>
> Did you check the .INHSTA and .INHALM values?
>
> Do you still have a copy of the checkpoint file from before you fixed
> the
> problem (maybe the BBlbug.UC)? I find it helpful to use dbvu to look at
> the
> block parameters as stored in the CP for troubleshooting problems like
> this.
>
> Regards,
>
> Kevin FitzGerrell
> Systems Engineer
> Foxboro New Zealand
> ------------------------------------
> Tel: +64 (9) 573 7690
> Fax: +64 (9) 573 7691
>
> Quoting "Lowell, Tim:" <Tim.C.Lowell@xxxxxxxxxxxxxxxxxx>:
>
> > 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: //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: //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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
