Re: [foxboro] CP Error protocol

Probably only due to a fault in the micro

We retested our fault and found we can cause the error on our gateway by
requesting one read from it the OM load starts climbing and then it
smurfs

I have no experience on micro IA but "craptacular" comes to mind
Shaun=20

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Daniele Tocco
Sent: Wednesday, 18 October 2006 01:06
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CP Error protocol

Dear Shaum,
Our connection between PLC and DCS is done by a MICRO I/O not by a
FBM224.=20
Do you think this can be the cause of the problem?
----- Original Message -----
From: "Goldie, Shaun S" <Shaun.Goldie@xxxxxxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Monday, October 16, 2006 10:07 PM
Subject: Re: [foxboro] CP Error protocol


> Daniele
> This may not be of much help but we get
> K0MG03 Error Protocol FTXSS 000080 Memory violation occured
00006C09A05F
> On an intergrator 30 for Modbus Pluss, it happens when another device
on
> the MB+ network sends a command to the Gateway. (eg network device
> discovery scan)
> It looks like you are having the problem with a CP60 but you mention a
> PLC so there must be a ?FBM224.
> In our case the gateway memory dumps and takes 10 minutes to come back
> online
> Shaun
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Daniele Tocco
> Sent: Tuesday, 17 October 2006 05:57
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] CP Error protocol
>
> Hi all it is already 3 time that I got problems with one CP of the
> plant.
> It seems that the CP looses the comunication with the I/O interfaces.
> The syslog error is the following:
>
> CP6002 Error protocol FTXSS 00080 Memory violation occurred
00006C17130F
> CP6002 Error protocol FTXSS 00080 Memory violation occurred
00006C171B68
> CP6002 Error protocol FTXSS 00080 Memory violation occurred
00006C17130F
> CP6002 Error protocol FTXSS 00080 Memory violation occurred
00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> CP6002 Error protocol 1     1 No Msg found 00006C171B68
> AW7001 Process=3D3DNFD000001 NF8023-00001 NB Cable test to WP7002 OK. N=
o
> response from CP6002
>
> There is also a MC I/O error that has been logged 13 minutes before
> this. It trasduces the PLC signals in DCS signals. Could be this
device
> too to create the out of service of CP6002?
>
> Somebody can give me some hints?
>
> Thank you very much
>
> Daniele
>
>
> =3D20
> =3D20
>
_______________________________________________________________________
> 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
> =3D20
> foxboro mailing list:
http://www.freelists.org/list/foxboro
> to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> =3D20
>
>
> =3D0A=3D0ANOTICE - This message and any attached files may contain
informatio=3D
> n that is confidential and intended only for use by the intended
recipien=3D
> t. If you are not the intended recipient or the person responsible for
de=3D
> livering the message to the intended recipient, be advised that you
have =3D
> received this message in error and that any dissemination, copying or
use=3D
> of this message or attachment is strictly forbidden, as is the
disclosur=3D
> e of the information therein. If you have received this message in
error =3D
> please notify the sender immediately and delete the message.
>
>
>
_______________________________________________________________________
> 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:
http://www.freelists.org/list/foxboro
> to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>
>=20


=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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20


=0A=0ANOTICE - This message and any attached files may contain informatio=
n that is confidential and intended only for use by the intended recipien=
t. If you are not the intended recipient or the person responsible for de=
livering the message to the intended recipient, be advised that you have =
received this message in error and that any dissemination, copying or use=
 of this message or attachment is strictly forbidden, as is the disclosur=
e of the information therein. If you have received this message in error =
please notify the sender immediately and delete the message.
 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: