At V8.8SE IA and V4.03 Galaxy, we went with Off-Mesh so that 1) we could
run multi-core on the Galaxy, and 2) at the time, it seemed like it was the
best for easier future IA upgrades. With newer V9.X IA running multicore,
the better option is most likely to run it ON-MESH for both performance and
ease of future IA upgrades, as long as the Galaxy AW does not host any IA
CPs or other IA devices.
At V8.8SE IA and V4.03 Galaxy, we originally had a couple of AWs that were
setup to be able run IDE client for control configuration, but it proved to
be excruciatingly slow, so we moved licenses and setup so that we only
accessed the Galaxy IDE configurator via RDP to the Server. I don't know
if, or how the performance of running IDE clients from other IA stations
may have improved with newer releases. Note, we run V1.1 On Mesh Galaxy on
a V8.4.2 AW at another site that we RDP/Remote FowView into and it runs
well, except that V1.1 Galaxy greatly lacks functionality and leaves a
whole lot to be desired.
Neil Martin, P.E.
Huntsman Performance Chemicals
From: BLAKE COVERDALE <coverdale_blake_t@xxxxxxxxx>
To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>,
Date: 03/03/2016 09:39 AM
Subject: Re: [foxboro] Migrating from ICC to Control Editor
Sent by: foxboro-bounce@xxxxxxxxxxxxx
Thanks a million for this Gordon & also thanks to the others for your input
Another question, any thoughts on whether the Galaxy server is best on or
off the MESH and is anybody running it virtualised?
Regards,
Blake Coverdale
Eli Lilly
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Buchner, Gord
Sent: Wednesday, March 02, 2016 10:40 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Migrating from ICC to Control Editor
Hi,
We did 24 FCP270's from ICC to FCS. They were done on the run and overall
it went very well. We did all the work ourselves. Here is my procedure:
1) We used bulk generate, using loopid to sort the blocks. So
spend the time out front getting your loopid's set in ICC to group the
blocks into strategies. Then follow this format throughout all your CP's.
2) We used PAS Integrity to query each CP (saved query to excel)
to get loopid before the bulk generate to check that the blocks were sorted
correctly and that you didn't have duplicate strategies.
3) You can't modify the default compound or block templates that
come with FCS so we made our own set of block templates and one compound
template ie, AIN > AIN_Pgp
4) Do the procedure below for each CP.
5) Use dbvu to get your remote connections on the system.
6) Fresh database and do a fresh saveall.
7) Create a bulkdata object.
8) Import Saveall into bulkdata object.
9) Generate ECB’s including FBM232 ECB’s.
10) Pick compound under control and change template to your
template. You can select all the compounds on the left and then right click
and select fill down with template selected. I left the STA and ECB
compound templates default.
11) Now pick Blocks under control and you will get the list of all
the blocks in the CP.
12) Pick type at the top and sort by block type. Under type select
your template on the first of that block type. Now select the rest of the
blocks of that type and use fill down to change them to your template. To
re-sort now use Base then repeat with each block type until all your block
templates are being used.
13) Now generate your strategies.
14) Your controller with compounds will show up in the unassigned
host under deployment.
15) Carefully look at the warnings and errors in the output
section to see if they are important. If there are big issues then delete
the controller with compounds and blocks in FCS, fix in ICC on system and
repeat until clean.
*Now what allowed me to feel good about doing this without initializing the
actual controllers was the I had an offline FCP270 with host station.
16) Set compound order in FCS. It will be alphabetical by default.
17) Export from FCS as a saveall and load into offline CP. (Faster
than object export and reloading into another FCS and deploying)
18) I actually compared compound by compound using a FV session
from the simulator and the actual system. (quick look, not detail of each
block)
19) Run dbvu on simulator CP and check against one from the actual
system.
20) Check that sequence code is there for each sequence block.
21) Once you are satisfied that the CP on the simulator matches
you real CP then continue in FCS.
22) Modify IDE_CP (safe guard file) in FCS to allow access for FCS
and disables ICC.
23) Go to deploy utilities.
24) Synchronize DB
25) This changes the deploy status of FCS to match controller.
(Will show deployed)
26) Upload runtime of CP this changes to get the current values
from the CP into FCS.
27) To compile all your sequence code in FCS you can pick the
controller and go to deploy it. Select all and at the top there is a
compile blocks selection. Pick next and then when it completes cancel the
deploy operation.
28) Not a bad idea to open each calc block sometimes FCS will
change a comment into a step if it was entered incorrectly in ICC. It shows
you what it wants to change when you open the calc block. Only a couple of
percent of blocks indicated changes and most were OK.
29) Try an undeploy and deploy of something to test FCS.
30) Open and save all Strategies.
Important Checklist:
Compound order.
Sequence code is there and compiles.
Blocks are all there.
DBVU remote connections are made.
