Re: [foxboro] Emergency Shutdown testing
- From: "Jones, Charles R. (Chuck)" <Chuck.Jones@xxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 10 Mar 2006 12:57:11 -0500
One suggestion is to lock out all the motors from their power supplies
and set the ignore limit switch (IGNLM1 and/or IGNLM2) in the GDEV
blocks. The principle is that, once you've determined that the GDEVs
are in sole control of the motors, you can separate the blocks from the
motors and crash them all you want until your testing is complete then
hook them back up again.
Chuck Jones
Automation Technologist
Tate & Lyle -- Lafayette South Plant
765.477.5324 - Office | 765.586.5290 - Cell
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of brad.s.wilson@xxxxxxxxxxxxxx
Sent: Friday, March 10, 2006 12:29 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Emergency Shutdown testing
Although this doesn't directly relate to DCS, I'm curious how sites
handle
testing of their ESD systems. Since we have nothing considered
critical,
we do not have a standalone system like Triconex, but rather we've
written
sequence code that directly toggles motors & valves and safes control
loops, in addition to using EXC blocks to handle DEP block shutdowns.
Our
problem is that our reliability engineer wants to test those ESD
programs
by turning on ALL the motors and then verifying that they all stop when
the
code is run. I don't like to idea of having everything running dry &
deadheaded. If you test your ESD systems, how do you ensure that it
will
actually do everything that you want it to do?
Brad Wilson
Process Control Engineer
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
***************************************************************************=
**************************
This email and any files transmitted with it are confidential and intended =
solely for the=20
use of the individual or entity to whom they are addressed. If you are not =
the intended=20
recipient or the person responsible for delivering the email to the intende=
d recipient, be=20
advised that you have received this email in error that any use, disseminat=
ion,=20
forwarding, printing, or copying of this email is strictly prohibited. If =
you have received=20
this email in error please notify the sender immediately. Please note that =
we reserve=20
the right to monitor and read any emails sent and received by the Company i=
n=20
accordance with and to the extent permitted by applicable legal rules.
***************************************************************************=
**************************
_______________________________________________________________________
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:
