I suggest you limit the size of your strategy. At least in V4.03, they do
not yet have the blocks names showing in the left hand tree, so when, and I
when you open the strategy window on the right side, it will have hard to
find your block . If there are too many blocks, you will have to pan
around using the sliders.
At least in V4.03, you can not see the block names without first opening
the strategy, thus it can be quite hard to know which strategy to open to
find the block you are interested in, if you have a lot of interconnected
blocks. I suggest you group the blocks in the strategies by similar tag
name, even though that will likely result in the blocks being connected to
blocks in other strategies. There is a search function, but it is much
easier if you can tell from the strategy name, which strategy most likely
will contain the block you are looking for.
At least in V4.03, the expected way to configure block links between blocks
in different strategies is probably to: first, create Declaration Flags
in both strategies to represent the C:B.P that will be inter connected,
and then use that Strategy Declaration which uses a suggested Syntax of
something like Compound_Strategy_Block_Parameter. When you import the
blocks from SAVEALL, it should build the Strategy Declarations
automatically. At our site, we hate the Strategy Declaration concept that
causes extra work, so we just type in the full Compound:Block.Parameter
name, but you have to know and remember the full name because there is no
browse function for a connection between strategies that is not using
Strategy Declarations. I also delete the Strategy Declarations that were
previously created when I have a chance, after I have typed in the C:B.P
directly.
Control Editor has nice edit capabilities for CALC blocks (edit, cut and
paste) and some other nice features. However, if you are an ICC user and
don't plan to use templates or bulk building, you will most likely find
Control Editor to be much slower for you to work with. That said, I
believe they have some plans to implement some changes that will help speed
configuration for those used to ICC, by reducing the required steps (or
work flow).
Neil Martin, P.E.
Huntsman Performance Chemicals
Conroe & Dayton , TX.
Conroe ph) 936-760-6205
Dayton ph) 936-257-4212
pager) 936-522-0052
From: BLAKE COVERDALE <coverdale_blake_t@xxxxxxxxx>
To: "<foxboro@xxxxxxxxxxxxx>" <foxboro@xxxxxxxxxxxxx>,
Date: 03/02/2016 10:29 AM
Subject: [foxboro] Migrating from ICC to Control Editor
Sent by: foxboro-bounce@xxxxxxxxxxxxx
Dear List
I am looking at migrating a 20 FCP control system from ICC to Control
Editor
We recently upgraded the system from P91s @ v8.4 to H90s @ v9.1 and this is
'Part 2' of the upgrade to get us concurrent with the preferred Schneider
configurator.
Just wondering if other folk have gone through this and if there are any
pitfalls or 'gotchas'. Also have any folk undertaken the conversion
themselves or have they had Schneider do the work for them?
Thanks in advance for any advice offered
Regards,
Blake Coverdale
Eli Lilly
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_list_foxboro&d=CwIDAg&c=XEmjTyjfAPcP2RtAp-6FGA&r=ZpVrK9MXCB5d4f6Q6LS1uy4XvhiDwVPsKathhACqB_w&m=ZOS2hg9PZcjiNKojqRQRu2bQXAXv3P7A62N4YIBrOZo&s=VVxXlqDhKp9KDJBtaEIcr02_d9TLDQlFg1MTRIxlfkQ&e=
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 Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
