Re: [foxboro] CALCA / Foxdraw / BAD I/O Graphic Question
- From: "Riccardi, Joseph" <Joseph.Riccardi@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2011 10:19:31 -0500
RE: Note: using the GDEV is good but when we have a command to the valve, also
using CALCA is mandatory to consider the delay for travelling time.
The GDEV has a delay for travel time = TOC.
Time to Open or Close is the delay, in minutes, before the comparison for
mismatch is made. Configure a delay at least as great as the maximum time
required for the valve to go from one state to the other. To avoid truncation,
set TOC equal to an integral multiple of the PERIOD. TOC is changed only by
reconfiguring the block.
Joseph M. Riccardi
Senior I&C Engineer
Bechtel Parsons Blue Grass Team
Richmond, KY
859-626-4368
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Leonardo Mercado
Sent: Tuesday, October 04, 2011 11:03 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CALCA / Foxdraw / BAD I/O Graphic Question
Jason,
Seems you need to animate a Manual valve equiped with two limit switches; I
have done it with the below CALCA:
BI01: Opem Limit Switch "*.CIN"
BI02: Close Limit Switch "*.CIN"
IN RI01; this will be a settable travelling time based on your valve size
OUT M24
AND BI01 BI02; both LS active
OUT M01; Immediate Discrepancy Alarm
AND ~BI01 ~BI02; both not active
OUT BO02; can be used for animation "Blinking"
DON M24; wait travelling time
OUT M02; Discrepancy
OR M01 M02
AND ~BI09; If you have Maintenance Inhibition facility "valve in Maintenance
and no limit switches available so no need for alarm"
OUT BO01; Discrepancy ALARM "use for Animation also"
IN BI01; Set "Open"
IN BI02; Reset "Close"
MRS
OUT BO03; valve position for Animation; 1=open; 0= close
you can add also the part for BAD signal by using the CIN Block .BAD parameter
and use it for animation as well in the same CALCA block.
If you animate directly with the CALCA block you will need a multy layer Symbol
but you can still use ome extra MCOUT and you the bit state to animate the
different modes.
hope this can help you
Note: using the GDEV is good but when we have a command to the valve, also
using CALCA is mandatory to consider the delay for travelling time.
regards,
Leo.
________________________________
From: Russ Kaiser <russ@xxxxxxxxxxxxxxxxxx>
To: foxboro@xxxxxxxxxxxxx
Sent: Tuesday, October 4, 2011 3:29 PM
Subject: Re: [foxboro] CALCA / Foxdraw / BAD I/O Graphic Question
Wade,
I don't know if you are getting your individual limits via an integrator or
if they are native to your Foxbor system, but
we do this type of status indication for every valve in the plant using the
bitmap option for fill color within FoxView. It also works within DM too.
No layering is involved and if the connection is bad, the valve shows up
cyan all by itself.
With multiple thousands of valves setting up a calc block for each sucks up
a lot of horsepower.
Russ
>-----Original Message-----
>From: foxboro-bounce@xxxxxxxxxxxxx
>[mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of SLADE Jason
>-NANTICOKE
>Sent: Tuesday, October 04, 2011 9:52 AM
>To: foxboro@xxxxxxxxxxxxx
>Subject: [foxboro] CALCA / Foxdraw / BAD I/O Graphic Question
>
>All knowing list,
>
>Personal experience indicates that a field device with two
>limit switches requires 5 states to provide the operator with
>clear and accurate position indication at all times.
>
>These 5 states include:
>- open
>- closed
>- neither (midstroke/travelling)
>- both (oops!)
>- "I wish I could tell you, but I haven't got a flippin' clue"
>(FBM / FCM / PIO bus communication errors = CYAN)
>
>Using a CALCA block to convert the Boolean INs to mapped bits
>in Long Integer 1 (LO01) to drive a single bit-mapped graphic
>element (because layered graphics will lie like a rug), I'm
>having a problem coming up with a solution to the last state.
>For some unknown reason, steps 10 and beyond of the following
>logic example (or the graphic config) misses the mark. Either
>way, the graphic element won't turn cyan:
>
>BI01 = :NSO.CIN
>BI02 = :NSC.CIN
>
>STEP 1 - IN BI01
>STEP 2 - OUT O01 ; BIT 1 OF LO01 ENABLES OPEN INDICATION
>COLOUR STEP 3 - ; STEP 4 - IN BI02 STEP 5 - OUT O02 ; BIT 2 OF
>LO01 ENABLES CLOSED INDICATION COLOUR STEP 6 - ; STEP 7 - AND
>2 STEP 8 - OUT O03 ; BIT 3 OF LO01 ENABLES LIMIT FAULT
>INDICATION COLOUR AND FLASHING
>STEP 9 - ; WITH ALL 3 OF THESE BITS SET TO 0, THE GRAPHIC
>ELEMENT IS SET TO MID-STROKE COLOUR
>STEP 10- RBD BI01
>STEP 11- RBD BI02
>STEP 12- OR 2
>STEP 13- BIF 16 ; NEITHER INPUT BAD, CLEAR BAD FLAG
>STEP 14- SBD LO01 ; INPUT(S) BAD, SET BAD FLAG STEP 15- GTO 17
>STEP 16- CBD LO01 STEP 17- ; STEP 18- END
>
>What am I missing here?
>
>In advance, thanks.
>
>Jason Slade
>
>Control Technologist
>Protection & Control Systems Support
>OPG / Nanticoke GS
>
>
>-----------------------------------------
>THIS MESSAGE IS ONLY INTENDED FOR THE USE OF THE INTENDED
>RECIPIENT(S) AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
>PROPRIETARY AND/OR CONFIDENTIAL. If you are not the intended
>recipient, you are hereby notified that any review, retransmission,
>dissemination, distribution, copying, conversion to hard copy or
>other use of this communication is strictly prohibited. If you are
>not the intended recipient and have received this message in error,
>please notify me by return e-mail and delete this message from your
>system. Ontario Power Generation Inc.
>
>
>_______________________________________________________________________
>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
_______________________________________________________________________
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:
