Re: [foxboro] FW: parameter state at CP boot
- From: steve.shimp@xxxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 30 Jan 2006 10:19:08 -0500
Dirk - Yours is the exact same situation that has me concerned.
Thanks to Con O'Brien for the suggestion of a simple scheme involving CIN
and SWCH blocks. I have already tested it and it does exactly what I need,
and is easy to reset and clear.
I am still trying to decide if I should assist the control room by doing
something to clear AUTDSR and MANDSR parameters on all of our GDEV blocks,
or forcing them to handle this manually.
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
"Pauwels, Dirk
- RSM"
<Dirk.Pauwels@ To
hexionchem.com <foxboro@xxxxxxxxxxxxx>
> cc
Sent by:
foxboro-bounce Subject
@freelists.org [foxboro] FW: parameter state at CP
boot
01/30/06 09:44
AM
Please respond
to
foxboro@freeli
sts.org
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
- References:
- [foxboro] FW: parameter state at CP boot
- From: Pauwels, Dirk - RSM
Other related posts:
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- [foxboro] FW: parameter state at CP boot
- From: Pauwels, Dirk - RSM