Re: [foxboro] upgrade path

  • From: "Joseph M. Riccardi" <Joe@xxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 11 Feb 2014 13:57:04 -0800

Frits,

Whoa!  I have been waiting to chime in with my experience but just assumed
you were upgrading to the FoxView (no Galaxy) V8.X, not the InFusion/FCS/Evo
(Galaxy) version 8.X.  Please clarify.  They are 2 different worlds...


Joseph M. Riccardi
386-441-0250 Office
386-451-7607 Cell
 
Joe@xxxxxxxxxxxxx
 
"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A. Adams



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Putman, Robert
Sent: Tuesday, February 11, 2014 1:46 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] upgrade path

Frits,

I might upgrade your less critical process first and learn everything you
can about the galaxy, windows boxes, etc. before upgrading your more
critical process.  I can't imagine that the CP270s would have an issue with
the high accuracy position control but you better ask Foxboro to be sure.
Good idea to get rid of 100 series I/O and your CP30 although we still use
some 100 series I/O and have not seen any issues.  We had to change some FBM
designations (letterbugs) during a recent upgrade so you may want to ask
about that.  You may want to ask about some of the newer offerings like thin
clients (could be significant cost savings but not for every application or
all stations).

You will also need to learn about the secure offering.

Thanks,
Bob

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Schouten, Frits JF
Sent: Tuesday, February 11, 2014 3:22 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] upgrade path

Hello all,
Is there a right way or an absolute wrong way to do an upgrade from Version
7.x with a mix of 100 and 200 series I/O to Version 8.x with only 200 series
I/O?
We have pretty much only one 24hr stop every two months and perhaps one
4-6hr stop a week, so it will be a live upgrade.

Currently I have two Version 7.x systems of which one still has a CP30 in
the mix of CP60s with both 100 and 200 series I/O.
The other Version 7.x system has only CP60s with a mix of 100 and 200 series
I/O.
Those two systems are linked at NodeBus level.

The CP60s talks 10Mbps to the FBMs. Replacing the CP60 first with a CP270
will put the fieldbus back to 268Kbps for the 100 series I/O. Is this an
issue?
There are two CP60s at 0.1BPC, one for high accuracy position control of
sample lances and one for high density data collection.
Can a CP270 comfortably run at 0.1BPC?

The CP30 can be engineered out with its I/O moved to a CP270 so, that
shouldn't be an issue.


Any thoughts or ideas on how to skin this cat?


Regards,

Frits Schouten | Principal engineer Process Computing department New Zealand
Steel & Pacific Islands Private Bag 92121 Auckland New Zealand
* Mob +64 21 963894
* Ph   +64 9 375 8111 ext 5261
* Fax  +64 9 375 8845
*
Frits.Schouten@xxxxxxxxxxxxxxxxxx<mailto:Frits.Schouten@xxxxxxxxxxxxxxxxxx>



________________________________
NOTICE - This message and any attached files may contain information that is
confidential, legally privileged or proprietary. It is intended only for use
by the intended recipient. If you are not the intended recipient or the
person responsible for delivering the message to the intended recipient,be
advised that you have received this message in error. Any dissemination,
copying, use or re-transmission of this message or attachment, or the
disclosure of any information therein, is strictly forbidden. BlueScope
Steel Limited does not represent or guarantee that this message or
attachment is free of errors, virus or interference.

If you have received this message in error please notify the sender
immediately and delete the message. Any views expressed in this email are
not necessarily the views of BlueScope Steel Limited



_______________________________________________________________________
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


________________________________

The information contained in this message and any attached files may be
privileged and/or confidential and protected from disclosure. If you are not
the intended recipient, any disclosure, copying, distribution or use of any
of the information contained in or attached to this transmission is strictly
prohibited. If you have received this transmission in error, please so
notify the sender immediately without reading it. Also, please promptly
destroy the original transmission and its attachments. Any views or opinions
presented in this message or attachments are those of the author and do not
necessarily represent those of KapStone Paper and Packaging Corporation or
its subsidiaries.
 
 
_______________________________________________________________________
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

Other related posts:

  1. Home
  2. foxboro
  3. Archive
  4. 02-2014