Re: [foxboro] IEE - CP Initialize/download time way too long

 Hi Corey

 The slow process is definitely the IEE application itself. It has nothing =
to do with the network or the FCP270's.

 As for the scripting API (Direct Access) it is a work in progress and all =
the sales people can do is tell you what you want to here. However working =
with IEE & Direct Access I can see that it is not a 1:1 replacement as IEE =
introduces another layer called "Contained Name" that can be different than=
 the "Compound Name". This effectively makes things twice as complicated as=
 you can't get nice dumps of your block parameters as external links show t=
his "Contained Name" then some "Flag Name" which is just a pointer to the r=
eal C:B.P (instead of the true C:B.P like we are used to using icc_prt.) So=
 you don't really know where your connections are going unless you can pars=
e this information with some sort of relational database. It's not all bad =
though as I  think it has been useful for changing some parameters in bulk =
or for creating new blocks.

Peter



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On=
 Behalf Of Corey R Clingo
Sent: Wednesday, June 25, 2008 6:14 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IEE - CP Initialize/download time way too long

I wonder how much of that time is the CP and how much is the IEE tool parsi=
ng/sending the data?  CP30s are not this slow with ICC, so I'm leaning towa=
rds the tool as the culprit.

Interesting info here, and I hope you find a resolution to this.  We just s=
aw an Invensys presentation that included IEE amongst other things.  It loo=
ked better than IACC, though the GUI definitely is not conducive to rapid b=
anging in of blocks by experienced I/A pilots.  We got told that one soluti=
on to that was the scripting API, which was "ICC driver task on steroids". =
 Oh well, we all know what too many 'roids will do to you :)


Corey Clingo
BASF Corporation

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