Re: [foxboro] CP60 giving errors in smon_log and "*" coming in SMDH

Kashif,

1. As Kevin points out, there are fixes to various CP60 fieldbus =
problems so you need to know everything about your hardware (firmware) =
in the CP (fault tolerant?)and the FBM's and the FCM's and in copper to =
fibre converters, etc. I believe that there were comments on this site =
about problems with the HART modules so you need to check that out too.  =
Document everything and then check with Foxboro Field Service and ensure =
that every module is at the latest eeprom for your IA version.


2. The copper Ethernet standard is a 1 Volt p-p signal. This is much =
lower than the 11 V p-p signal of the legacy fieldbus so stray noise has =
a greater chance to kill your Ethernet signals. Although not =
specifically prohibited in Foxboro documentation, copper Ethernet is not =
recommended to go outside an industrial enclosure. See ISA documents.  =
So if you have copper, outside your main enclosure, you likely need to =
re-think that and get fibre-optic cables. Verify that you do not violate =
the length of cable specifications.  Make certain that you're A and your =
B fieldbusses are identical. Verify that all copper connectors are =
tightly connected to the Ethernet cable shields. Inspect all copper =
cables to ensure that they are not coiled and that there are no bumps or =
dents in the insulation. (Sometimes cables can be pinched in a door and =
the insulation is destroyed. Coiled cables are noise traps!) If fibre =
optic cable is part of your buss, check all for broken connectors. =
Verify that any coiled fibre is greater than the minimum coil diameter =
(likely 15-20 cm). If the Black-Box copper to fibre converter is part of =
your bus, verify (check with a tool) that the copper shield is properly =
grounded.  Take a few minutes and watch the flashing led's to see if =
error led's or fault led's are flashing. Check that copper busses are =
terminated at each physical end and that the resistor is the correct =
value.=20

Some of this testing may require that you run Fieldbus A only, while you =
test Bus B, and vice-versa. So make sure that Bus A is correctly =
identified from start to end. Same check for Bus B since crossed cables =
can be a problem. Can you run a single fieldbus (only) without errors? =
If yes, let them run that way for a time when you can stay close by the =
system. Check the led's for errors and faults.

A lot of this testing may not be possible on a running process, so you =
need to be the judge of that. Schedule the testing at the next process =
shut-down.

3. The STATION display for the CP60 will give you the fieldbus load =
(scan). This should be less than 65 and you must not have CP overruns =
(LBUG_STA:STATION.CUMOVR). IF either of these is a problem, fix them by =
slowing down those ECB's that you can and make tough choices to get =
these two items in order.

There are some other parameters that can be read (omgets or put them on =
a display)  STATION.PIOE1R  STATION.PIOEFT  and  STATION.PIOEGB. Report =
these values while running Bus A, then switch to run Bus B and report =
the values. Compute the counts per hour here so that you know the rate =
of these counters for each fieldbus.

Terry Doucet



Objet=A0: Re: [foxboro] CP60 giving errors in smon_log and "*" coming in =
SMDH

Instead of attaching, why don't you put the smon_log files the email?

Also, what CP60 module revision, firmware and software image are you
running?  Do you have PLB blocks in use in the CP60s?

Regards,

Kevin FitzGerrell

On Wed, Feb 20, 2008 at 4:17 PM, Kashif Ijaz <kashifijaz93@xxxxxxxxxxx> =
wrote:
> The CP60 installed at our site are continuously giving erros in =
'smon_log' and there is '*' as unacknowledged faults in SMDH.  I have =
heard these are some inherent noise with CP60s. I have had similar =
problems at many sites and have troubleshooted on grounding and ferrite =
cores. Even if we fix all things still the errors are coming.  I am =
attaching the smon_log, If anyone can suggest any line of action, Please =
recommend. Regards, Kashif IjazINTECH Process Automation

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