Re: [foxboro] FW: parameter state at CP boot

For the GDEV block there is .HLDDSR parameter which can be used to drive all
gdevs to a safe or hold state.
When HLDDSR=0 OPEN device
     HLDDSR=1 CLOSE device
     HLDDSR=2 Leave device as-is. Do not change its state.
     and 
     HLD = 1
Then the DGEVs will drive the output to the state defined in HLDDSR.
All Gdev can be bulk driven via the .HLD input fro a CALC or SEQ block 
The .HLD input can be maintained high or pulsed.
You have to make sure that the logic that is driving the HLDs is executed
first of boot up.
IF the HLDDSR is already used for other purposes, then you have to explore
on how the USERL1 and USERl2 parameters can be used to provide you with this
new functionality.
These parameters are GDEV user parameters, you can store in there whatever
you like.
Regards

Leonardo Moramarco
Instructor, Lifetime Learning Center
Invensys Systems Canada Inc.
Foxboro Division
Phone: 514.421.8301
Fax:514.421.8301
Cell:514.942.4342
 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Pauwels, Dirk - RSM
Sent: Monday, January 30, 2006 9:45 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FW: parameter state at CP boot




We have the same problem. Not for controlled shutdowns, in which we take
a checkpoint with all vlves/pumps in safe position, but for crash,
uncontrolled, shutdown... Most of our valves are fail to close, so
shutdown is not so much of a problem, it's the startup we're worried
about....Because there is such a thing as a checkpoint file I asked
Foxboro if it was possible to create a default checkpoint reboot file,
which would contain safe valve/pump autdsr. This file only has to be
executed during reboot ,not during regular checkpoint. I was told it was
not possible to handle it this way. I'm sure other sites have the same
problem, so I'm also interested in knowing how they handle it. Creating
calc blocks to switch all of these vlvs to "safe" position would mean we
would have to create a large number of blocks.

Rgds,

Dirk Pauwels - DCS/MOC coordinator=20
Engineering dept.
Hexion Specialty Chemicals
E mail: dirk.pauwels@xxxxxxxxxxxxxx
T.  +32.(0)3.570.95.97
F.  +32.(0)3.570.16.09
Mob. +32.(0)497.428.300


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of steve.shimp@xxxxxxxxxxxxxx
Sent: vrijdag 27 januari 2006 16:43
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 =3D 0 and INITMA =3D 1.  However, the checkpoint =
file
has
the AUTDSR =3D 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

=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
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: