Re: [foxboro] Peer to Peer connection good but not updating
- From: Pedro Ramos <pedro.ramos@xxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 27 Aug 2012 17:34:46 +0000
You must do a checkpoint on both processors, preferably. Also, after doing a
reboot to a CP, you must also checkpoint it, or else it might not (will not)
re-sync, so rebooting it is not the answer.
We have several inter-processor connections and are used to that procedure if
we have to physically turn of the CP's. On CP60's, a newly created connection
only works after a checkpoint.
Greetings,
Pedro Ramos
-----Mensagem original-----
De: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] Em nome
de Terry Doucet
Enviada: segunda-feira, 27 de Agosto de 2012 17:58
Para: foxboro@xxxxxxxxxxxxx
Assunto: Re: [foxboro] Peer to Peer connection good but not updating
MK,
Remember that peer connections are not made during delete / undelete or even
during their creation but rather peer connections are made at the end of a
CHECKPOINT function in the SINK CP.
I saw a few times when I was able to go to the SINK block and make another
connection to the SOURCE block (connect the SOURCE.MA to a Boolean In). After
the CHECKPOINT, the original point started to update. Not sure why it worked
but it did.
If this does not fix your problem I would recommend looking at the SOURCE
resources with rsom or other tools to see if perhaps you have reached one of
the many limits of the CP station. The CP270 has such big limits that this is
unlikely but it might be worth checking before rebooting because if you are at
a limit, the reboot may not fix the problem.
Failing that, usually a reboot can fix this problem but not many plants can
tolerate a reboot of a CP.
Terry
> From: mkessler@xxxxxxxxxxxxx
> Date: Mon, 27 Aug 2012 12:46:10 -0400
> Subject: [foxboro] Peer to Peer connection good but not updating
> To: foxboro@xxxxxxxxxxxxx
>
> I have some peer to peer connections between calcA blocks in ZCP's
> that are not updating. (XXX.BO01 > YYY.BI01) I've deleted/undeleted
> the blocks, with no success. Deleting the source block does not turn
> the sink point Cyan which should normally be the case.
> I am able to see the status of the source using omget.
> I suspect corrupt OM lists. Will a re-boot clear these up or is a CP
> initialize/loadall required?
>
> Anyone experienced this type of problem?
>
> mk
>
>
>
>
> ______________________________________________________________________
> _ 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
>
_______________________________________________________________________
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
________________________________
Aviso: Este e-mail e quaisquer ficheiros inform?ticos com ele transmitidos s?o
confidenciais e podem conter informa??o legalmente privilegiada. Caso tenha
recebido este e-mail indevidamente ou julgue n?o ser o destinat?rio do mesmo,
queira informar de imediato o remetente e proceder ? elimina??o desta mensagem.
? estritamente proibido o uso, reencaminhamento ou reprodu??o n?o autorizada
desta mensagem e de quaisquer ficheiros nela contidos. Qualquer opini?o
expressa na presente mensagem ? imput?vel somente ? pessoa que a enviou, a n?o
ser que o contr?rio resulte expressamente do seu texto. Como o correio
electr?nico pode ser afectado por dificuldades t?cnicas ou operacionais, n?o se
garante a sua recep??o de forma adequada e atempada. A mensagem foi filtrada
por um detector de v?rus pelo que o remetente n?o se responsabiliza por danos
provocados por terceiros no sistema inform?tico do destinat?rio.
Warning: This e-mail and any files transmitted are confidential and may well
also be legally privileged. If you are not the intended recipient or have
received it in error or if you believe that you received a misaddressed e-mail
transmission, please notify us immediately by reply e-mail and then delete this
message from your system. Any unauthorized use, copying, disclosure or
distribution of contents of this e-mail is strictly prohibited and may be
unlawful. Unless otherwise stated, all views and opinion herein contained are
solely the expression of the sender. As e-mail can be subject to operational or
technical difficulties, the quality of reception may be affected and may be
subjected to time delays. A virus checker sweeps outgoing e-mail. Therefore the
sender doesn't accept any responsibility or liability whatsoever for any
adverse effects on your systems or data arising from intercepted, corrupted or
virus infected e-mail.
__CUFdisclaimer2011__
_______________________________________________________________________
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:
