Yes they were all updated.  This doesn't seem to be the problem, but we'll
keep checking.

Thanks for your assistance.

John

****************************************************************************
********************


I know all FBM's require EEPROM update for version 6.2.1. But you have done
that
I guess...

Ron Deen

Campbell John C wrote:

> We are currently upgrading one of our sites from a CP30FT to a CP60FT and
> are experiencing some difficulties.  The actual upgrade went relatively
> smoothly but after the AW was placed back on line with the new CP60's we
> started to receive numerous fieldbus failure alarms (PIOBUS A/B) that
would
> randomly come in and out.  Sometimes we would have no alarms for about 1/2
> hour and then continuous alarms for the next 20 minutes.  There was no
> pattern as to when the alarms would occur.  Occasionally when the alarms
> occurred we would lose communication to the fieldbus altogether (blue flu
on
> the operator screen).  Until we do some more detail investigations (with
Fox
> Mass.) we have gone back to the old CP30 system.
>
> Has anyone else experienced similar problems and what did you do to get
> around it.
>
> Some back ground information:  The switchover is being performed at the
same
> time as a revision upgrade from 6.1 to 6.2.1 on a AW/WP51B system.  All
> fieldbus modules are of the traditional rack mounted type (no din rail
> mounted modules).
>
> Much appreciation for any assistance.
>
> John Campbell
> Dofasco
> [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]


-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to