Terry,
I believe some of your friends at another Dow site in Carrollton, KY
USA have experienced similar issues as indicated in the email linked below
which can be found in the Foxboro mail list archive. We experienced a few CP
peer-to-peer communication issues while I was working for Dow Corning at the
Carrollton site many years ago, prior to FCP270's or FCP280's. Although they
were written up and presented to Foxboro, they were never officially resolved,
and we couldn't replicate the problem at will. Because of events leading up
to the issue, we believe that the problem started when existing peer-to-peer
connections were modified within the sink and source CP's simultaneously and
without checkpointing the CP's until both were modified using ICC. We used the
Foxboro Station Object Manager utility called "RSOM" to look at the status of
each CP's connections, (and they showed correctly connected and healthy), we
found out that the Object Manager Table was messed up, which caused the wrong
variables to be passed from the source table to the sink table. It was very
insidious and eventually required a reboot, I believe of the sink CP.
//www.freelists.org/post/foxboro/foxboro-PeertoPeer-Connection-Problem-in-CP270-CP280,4
Cheers,
Tom VandeWater
Control Conversions, Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of terry.lloyd@xxxxxxxxxxxxxx
Sent: Wednesday, January 25, 2017 6:18 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Peer To Peer Issue Causing Process Trip
Yesterday we had a CP Peer-to-Peer issue that caused some valves to trip
closed, which in turn tripped our plant.
On closer investigation we found a number of BAD (cyan) connections, some of
these had also changed state from FALSE (healthy) to TRUE (trip), even though
the source block was healthy. The sink end of the connection is an FCP280, the
source end of the bad connections came from two FCP270's.
The event was triggered by adding new blocks to the FCP280 that were totally
unrelated to the trip logic. Exiting the ICC runs a checkpoint, and that
created the bad peer to peer connections.
The only way to resolve the bad connections was to checkpoint the source CP
then checkpoint the sink CP.
The images were updated to the latest available at the time, after last June's
advisory regarding Loss of Peer to Peer Connections with CP270 or CP280.
We realised that this also happened here last October on the same CP, but the
resolution was different, i.e. delete one bad connection, checkpoint sink CP,
all bad connections cleared, then rebuild connection, checkpoint , all ok.
A case has been raised with Schneider UK, they are looking in to this now.
Has anyone else had similar problems with FCP280?
Regards
Terry
Terry Lloyd, Systems Engineer
-------------------------------------------------------------
Building W601, Mail BA111C Voice: +44 (0)1446 723501
Dow Corning Ltd Fax: +44 (0)1446 723674
Cardiff Road E-Mail:
terry.lloyd@xxxxxxxxxxxxxx<mailto:terry.lloyd@xxxxxxxxxxxxxx>
Barry
Vale of Glamorgan, CF63 2YL
-------------------------------------------------------------
Dow Corning Limited is a limited liability company registered in England and
Wales, registered number: 00486170, registered office address: Cardiff Road,
Barry CF63 2YL, UK
This e-mail transmission and any files that accompany it may contain sensitive
information belonging to the sender. The information is intended only for the
use of the individual or entity named. If you are not the intended recipient,
you are hereby notified that any disclosure, copying, distribution, or the
taking of any action in reliance on the contents of this information is
strictly prohibited. Dow Corning's practice statement for digitally signed
messages may be found at
www.dowcorning.com/dcps<http://www.dowcorning.com/dcps>. If you have received
this e-mail transmission in error, please immediately notify the Security
Administrator.
[cid:image001.jpg@01D27723.F3757E90]
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
