There is a P to P fix in the latest 270 image , QF1306143 (920043)
This Quick Fix may be installed if the following launch conditions are met:
Windows XP with I/A Series versions 8.4 thru 8.7
Windows 2003 Server with I/A Series versions 8.4 thru 8.7
Windows 7 with I/A Series version 8.8 thru CCS 9.2
Windows 2008 Server with I/A Series version 8.8 thru CCS 9.2
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
Dirk Pauwels [dirk.pauwels@xxxxxxxxxx]
Sent: Thursday, January 26, 2017 4:59 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Peer To Peer Issue Causing Process Trip
Hi Terry,
We haven't got 280's, only 270's but we've had this sort of problem both on
CP60 and ZCP270. Some cases were harmless, some weren't. No cause was found. A
CP reboot always solved it, sometimes a delete-undelete + checkpoint of both
source and target also solved it.
Ie: We've had addition sequences which kept pumping product because the weight
indication didn't change etc...
Since no cause was identified there's still a risk this might happen so we try
to keep the important stuff in the same CP. Unfortunately this is not always
possible.
If the I/O's are very important, maybe you can implement a second layer of
interlocks? Or keep them in the same CP.
Rgds,
Dirk
-----Oorspronkelijk bericht-----
Van: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] Namens ;
terry.lloyd@xxxxxxxxxxxxxx
Verzonden: woensdag 25 januari 2017 17:18
Aan: foxboro@xxxxxxxxxxxxx
Onderwerp: [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
________________________________
Lawter Notice: The information (including any attachments) contained in this
communication is confidential, private and proprietary, may be privileged or
otherwise protected by applicable law or legal rule, and is intended only for
the use of the addressee(s). Unauthorized use, disclosure, distribution or
copying is strictly prohibited and may be unlawful. If you have received this
communication in error, please notify the sender immediately by reply e-mail,
or by calling the sender, and then delete it completely from your system.
_________________________________________________________________________
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 email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person.
_________________________________________________________________________
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
