Re: [foxboro] INVALM issue on a CIN block -- solved

I'd say that is mostly the end result of what we do, but I'm thinking of 
going completely in that direction like you -- if for no other reason than 
that you cannot see the "raw" input value on a CIN on the faceplate or the 
detail.  That could probably be done in a graphic, using a combination of 
the IN and IV0 parameters, but Foxboro has not seen fit to do so, and 
we've been somewhat reluctant to build our own details and faceplates. But 
since the default displays repeatedly leave me wanting,I'm reconsidering 
that position as well.  In my copious spare time...

Corey Clingo
BASF Corporation






"Badura, Tom" <tbadura@xxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
08/22/2008 07:53 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] INVALM issue on a CIN block -- solved






It sounds like you already have your question answered.  But for what it
is worth we also have a convention with CIN blocks for discrete devices
where the block always reflects the actual state of the device (IVO = 0)
and then use the INVALM option as necessary to generate an alarm in the
proper state.  As such SCTXT0 always describes the Off state, SCTXT1
always describes the On state, and NM1 is the In Alarm message and NM0
is the Return to Normal message.  Many discrete devices such as level,
pressure, flow switches are configured for failsafe operation and we
used to use the IVO option; however, our techs and electricians were
used to seeing these being On as normal.  Having the CIN block reflect
this actual state and just using INVALM to generate an alarm in the Off
state has eliminated much confusion. 

Tom Badura
Plastics Engineering Company
920-458-2121 x3366
tbadura@xxxxxxxxxx








 
 
_______________________________________________________________________
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: