Re: [foxboro] Was: Open loop alarm, now CP60 fieldbus musings

Corey,
        I'm interested to know a little bit more about your problem
because it may help me with mine.  Correct me if I am wrong in any of my
assumptions and please answer my questions.

Assumptions
1. You are having problems with intermittent fieldbus communication
errors
2. You are using CP-60's
3. Errors are on 200 Series FBM's

Questions
1. Are you running ladder logic in FBM's?
2. Are you using FCM10E's, (thinnet), or FCM10EF's ,(Fiber), to
communicate to FBM's?
3. What Version CP-60 image are you running?
4. What FCM EEprom Rev. are you running?  i.e. 1.14, 1.15...
3. Do your SYSMON errors look like the example shown below?

11-26-05 14:21:14      0  SYSMON =3D SYS18A  18CP01  Equip =3D 18B111

  SYSMON -00069 Single PIO Bus Access Error on B

11-26-05 14:21:40      0  SYSMON =3D SYS18A  18CP01  Equip =3D 18B111

  SYSMON -00071 Single PIO Bus Access Recovery on B

Thanks for any info you can provide!
Cheers,
Tom VandeWater

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Wednesday, November 30, 2005 10:25 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Was: Open loop alarm, now CP60 fieldbus musings

Yes, thin net, the bane of my existence.  I once thought I was rid of
that=20
stuff 10 years ago when the last of our VAX-hosted CAD terminals were=20
hauled off; silly me.  It also was the source of most of the=20
network-related problems I had with Honeywell TDC, though they had
decent=20
tools to figure out where the problem was.  I was nonplussed to see it
on=20
the CP60s.  But Foxboro is nothing if not retro ;-)

But it appears that my problems have been related to the baseplate side
of=20
things.  The last CP I brought up had intermittent cable problems across

several modules and baseplates, and finally went away when I swapped a=20
couple baseplates and one FBM.  The same thing is happening currently on

the CP I just brought up; B cable errors, intermittent, on several=20
FBMs/baseplates, one at a time.  I've ruled out fiber, coax, hubs, and=20
FCMs; now on to baseplates and FBMs....


Corey




stan <stanb@xxxxxxxxx>=20
Sent by: foxboro-bounce@xxxxxxxxxxxxx
11/30/2005 07:21 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
Corey R Clingo <clingoc@xxxxxxxxxxxxx>
cc
foxboro@xxxxxxxxxxxxx, brad.s.wilson@xxxxxxxxxxxxxx,=20
foxboro-bounce@xxxxxxxxxxxxx
Subject
Re: [foxboro] Open loop alarm






On Tue, Nov 29, 2005 at 05:17:05PM -0600, Corey R Clingo wrote:
> "...the end suer..."
>
> Well, I don't think it has come to that yet, but dealing with another
> 200-series fieldbus problem here over the last two days makes me want
to
> call my lawyer :)
>

That looks a lot like one of my typo's :-)


We've got the 200 serries fieldbuss situation pretty much under control,
here.

Mostly by following the recomendations about not taking the thin net out
of single cabinets.

--
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite=20
Vietcong Terror
- New York Times 9/3/1967




=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
 
 
_______________________________________________________________________
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: