Re: [foxboro] parameter state at CP boot

The BII command in a CALC block is a useful way of detecting block,
compound or CP intitialisation. You could use this to generate a
one-cycle pulse to force a GDEV block into INTLCK, for example, and set
the INTDSR to your desired reboot state. Be careful though, because this
state will then be forced whenever you hit DONE on the CALC block.

A couple of other intitialistion favourites...

SWCH blocks - to force a value of toggle on a CP reboot, connect TOGGLE
to the .MA parameter of a separate CIN block (say). Configure your
display to toggle the CIN.MA parameter to move the switch in normal
operation, and set the CIN.INITMA to force a certain state on
initialisation.

CALC blocks with flip-flops - use the BII statement to detect
initialisation, and then use external feedback to set or reset the
flip-flop for one cycle.

Regards,
Con

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of steve.shimp@xxxxxxxxxxxxxx
Sent: Saturday, 28 January 2006 1:43 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] parameter state at CP boot

I am looking for tips/feedback regarding setting parameters to a known,
safe state when a CP reboots.  For instance, we have a valve configured
via ICC such that AUTDSR = 0 and INITMA = 1.  However, the checkpoint
file has the AUTDSR = 1, which happened to be the desired valve state
when the checkpoint occurred.  When the CP reboots, the valve will be in
auto and open, which is undesirable.  I need a way to override this when
the CP reboots.

Is there any way that I can definitively tell when a CP is first
initializing/booting and explicitly override any undesirable parameters
that may be in the checkpoint file?


Steve Shimp
Maintenance & Systems Engineer
ExxonMobil Paulsboro Lube Plant
phone: 856.224.5059      cell: 609.820.8501      fax: 856.224.5030
email:  steve.shimp@xxxxxxxxxxxxxx

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