Dear list,
Here's the final solution to my problem:
Because it wasn't possible to identify with full certainty which peer to
peer connections were frozen, the solution had to be a all-or-nothing
approach.
Rebooting the CP would fix the problem but that is taboo with a running
plant. Doing an Online Image Update with warm start (olug) rebuilt the OM
tables and fixed all my frozen p2p.
If you ever need to do an olug, please read the manual as it may not be as
bump-less as you expect, depending on your configuration.
Thanks again for all the suggestions,
Maks Wilde
On Tue, Sep 22, 2015 at 5:40 AM, McQuaid, Paul <
paul.mcquaid@xxxxxxxxxxxxxxxxxxxxxx> wrote:
FoxRay? FoxRay...... ? Ohhhh you mean "System Auditor" :-)
Best Regards
Paul McQuaid
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Joseph M. Riccardi
Sent: 21 September 2015 19:48
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Peer to Peer connection good but not updating
Foxray will identify all of the connections. Still plugging it, without
any guilt feelings, since it is all one big happy family now... :-)
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Maks Wilde
Sent: Monday, September 21, 2015 2:36 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Peer to Peer connection good but not updating
Thanks for all the replies. I am slowly making progress. I have found that
the block I was sourcing was used in multiple different block sinks. Once
all of those were deleted, checkpoint the CP, re-connect, and it's working.
What I'd like to know is, how do I determine all of my bad connections?
Thanks,
Maks Wilde
On Mon, Sep 21, 2015 at 1:27 PM, <Martin.Theobald@xxxxxxxxxxxxxx> wrote:
Maks,using the 'omlist'
We had something similar recently where the Sinks were the RI03 on a
number of CALCs in one FCP and Source was the .MEAS on a number of
RINs all in another FCP. After our workaround (rebooting the Source
FCP, after trying a similar list to yours), field service suggested
utility. Contact Field service for the utility and instructions.A.
Also suggested by field service (after the event), take a look on the
detail display for both the sink and source control stations and see
what the Peer to Peer statistics are.
Regards,
Martin Theobald
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Maks Wilde
Sent: 21 September 2015 17:31
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Peer to Peer connection good but not updating
Joe,
If I understand your question, in FoxView, I can click on RI0003
(showing 84%), click source, shows me the correct source path, click
on the "source path" button which takes me to that block, and when I
get there, the .PNT is reading 27%.
Maks Wilde
On Mon, Sep 21, 2015 at 12:24 PM, Joseph M. Riccardi
<Joe@xxxxxxxxxxxxx>
wrote:
Maks,
Sink = IND.RI0003, Source = AIN.PNT - You can see this in the
Select, Source view?
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be bought
or measured with money; and that is sincerity and integrity." - Donald
then.Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Maks Wilde
Sent: Monday, September 21, 2015 12:18 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Peer to Peer connection good but not updating
Dear List,
I'm reviving this thread as I've run into a similar issue.
During a turnaround, CPs were rebooted. It's been noticed that some
real input peer to peer values are frozen (not updating and not cyan).
I've tried:
A) Delete source block, checkpoint, rebuild source block, checkpoint
B) Delete and undelete sink block, checkpoint
C) Delete connection in sink block, checkpoint, re-connect
sink-source, checkpoint
D) Delete replace connection in sink block with other p2p,
checkpoint (updates ok), re-connect sink-source, checkpoint (back to
frozen
value)
None of the combinations stated above have corrected my peer to peer
problem.
Sink = IND.RI0003, Source = AIN.PNT . This is one block, but I have
a feeling there are many more as problems seem to be affecting other
areas also.
CP Soft Version is at 860050
Any ideas other than rebooting the CPs (which caused this issue in
the first
place) would be much appreciated.
Thanks,
Maks Wilde
On Tue, Aug 28, 2012 at 4:42 AM, Dirk Pauwels
<dirk.pauwels@xxxxxxxxxx>
wrote:
Hi all,
We've had this in the past multiple times. It also happened with
Reals BTW, not only with Booleans.
Alex's procedure usually solved it, but one time we had to call
the service guys in to solve it. I think we had to reboot the CPs
system.coincidence.Rebooting CP's is the last resort off course, nobody in his right
mind would reboot CP's during production....
We've also had PLB blocks that stopped working, but a delete/
undelete always solves that, reason again unknown.....
I was told the P2P problem can occur if you create and delete
tags in the same session, so now I usually checkpoint in between
deleting and creating tags and we haven't had it since, but this
could be
//www.freelists.org/list/foxborohelp much.
It's not a very comforting idea to run a chemical plant with lots
of automation, exotherm's in several reactors... and unreliable
P2P connections. It can get very scary and messy.....
I try to avoid P2P connections as much as possible, but sometimes
it's necessary.
I use Ain's which check for P2P errors, (station.PP_DEL, PP_DSC,
PP_NFD) with an alarm threshold of 1, if there are any, I'm
notified by mail and with a notification alarm, but I seem to
recall the frozen P2P connections were not reported as P2P errors,
because the connection was not broken, it was simply not updating,
so this doesn't
Running Rsom on a very regular base might help some, but even then
we can have problems caused by stale tags in a matter of minutes,
so it's not a solution....
Maybe someone could develop something like a constantly running
Rsom, with reporting and notification capability that doesn't take
much server processor capability?
Rgds,
Dirk
__________________________________________________________________
__ __ _ 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:
?subject=jointo subscribe: mailto:foxboro-request@xxxxxxxxxxxxx
?subject=leaveto unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx
system.
--
Confidentiality Warning: This message and any attachments are
intended only for the use of the intended recipient(s), are
confidential, and may be privileged. If you are not the intended
recipient, you are hereby notified that any review,
retransmission, conversion to hard copy, copying, circulation or
other use of this message and any attachments is strictly
prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, and delete this message
and any attachments from your
//www.freelists.org/list/foxboro
____________________________________________________________________
__ ___ 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:
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
//www.freelists.org/list/foxboro
____________________________________________________________________
__ ___ 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:
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
--
Confidentiality Warning: This message and any attachments are
intended only for the use of the intended recipient(s), are
confidential, and may be privileged. If you are not the intended
recipient, you are hereby notified that any review, retransmission,
conversion to hard copy, copying, circulation or other use of this
message and any attachments is strictly prohibited. If you are not
the intended recipient, please notify the sender immediately by
return e-mail, and delete this message and any attachments from your
//www.freelists.org/list/foxboro
______________________________________________________________________
___ 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:
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
**********************************************************************
******* This e-mail is sent on behalf of the De La Rue group of
companies (ââ¬ÅDe La Rueâ⬠). The e-mail and any attached files are
strictly confidential and are intended solely for the addressee. If
you have received this email in error, please notify the sender and
then delete the e-mail and any attachments. Where the content of this
email is personal or otherwise unconnected with De La Rueââ¬â¢s or its
customers' business, De La Rue accepts no responsibility or liability
for such content. You are advised to ensure that you have adequate
virus protection as De La Rue does not accept liability for any
viruses. De La Rue plc (company No.3834125), De La Rue Holdings
Limited (company No 58025) and De La Rue International Limited
(company No 720284) are all registered in England with their
registered office at: De La Rue House, Jays Close, Viables,
Basingstoke, Hampshire
RG22 4BS.
**********************************************************************
*******
--
Confidentiality Warning: This message and any attachments are intended
only for the use of the intended recipient(s), are confidential, and
may be privileged. If you are not the intended recipient, you are
hereby notified that any review, retransmission, conversion to hard
copy, copying, circulation or other use of this message and any
attachments is strictly prohibited. If you are not the intended
recipient, please notify the sender immediately by return e-mail, and
delete this message and any attachments 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 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
--
Confidentiality Warning: This message and any attachments are intended
only for the use of the intended recipient(s), are confidential, and may be
privileged. If you are not the intended recipient, you are hereby notified
that any review, retransmission, conversion to hard copy, copying,
circulation or other use of this message and any attachments is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately by return e-mail, and delete this message and any attachments
from your system.
