Re: [foxboro] .S file search

Peter,
        Thanks for taking time to explain what you know about the IACC
and IEE databases and the functionalities gained and lost.  It was quite
informative.  We welcome additional input from Foxboro folks that have
the inside scoop as well.
Cheers,
Tom VandeWater=20

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Bruley, Peter T
Sent: Tuesday, June 26, 2007 9:00 AM
To: Weiss, Andreas; Foxboro@Freelists. Org (E-mail)
Subject: Re: [foxboro] .S file search

Andreas:

Someone can pipe up and correct me if I am wrong but this is how I =3D
understand these processes:

IACC

IACC uses a proprietary database that is spread across about 6-7 ".icd"
=3D
files.=3D20
I have no idea what icd stands for but these files contain your entire =
=3D
system (all the CP's in your system)
These files are compressed (or padded with control characters) they are
=3D
basically unreadable when loaded into a text editor.
Along with all the workfile information the .S files are contained =3D
somewhere in those proprietary database files.
These files can grow to become very large (about 30MB per CP) as you add
=3D
more CP's
Usually kept in D:\opt\fox\IACC\Database
There is a way to split up your system into many IACC databases (i.e. =
=3D
have a database per CP)
IACC compiles the ".S" files and then sends the binaries to the Foxboro
=3D
System=3D20
(the AW does not do the compiling so it does not need the .S files)
Although the AW will not have the .S files it does have the "Workfiles"
=3D
and the "Checkpoint" files
IACC does not have to reside on a Foxboro I/A host. The IACC host just =
=3D
needs network access to a I/A AW.
IACC uses the AW's "foxapi" to communicate changes between the IACC =3D
database and Foxboro System (similar to FoxCAE)
(so there is a long waiting period as IACC creates all the IACC driver =
=3D
calls before communication actually occurs)
You can still make old style "savealls" to the hard drive =3D
(/opt/fox/ciocfg/api/save_all)=3D20
However you can not use "loadall" (/opt/fox/ciocfg/api/load_all) to put
=3D
these back into the system as this would by pass the IACC database.
So basically the "save_all" and "load_all" functionality is gone"
You can still use "icc print" and "icc driver task" but be careful not =
=3D
to create any new blocks as your IACC database will be out of sync as =
=3D
you can't upload new blocks into IACC.
IACC tried to incorporate System Definition however this functionality =
=3D
always lagged behind and was never really used.



IEE

IEE uses a proprietary database that is coupled to a SQL database called
=3D
"Galaxy Database".=3D20
The SQL database contains no block parameters and I believe it is used =
=3D
to organize all the visual objects/names as you draw your configuration
=3D
in loops called "Strategies".
Again the proprietary database files are basically unreadable when =3D
loaded into a text editor.
Like IACC, IEE does the compiling of all the ".S" files before =3D
communicating to the CP's (so there are no .S files on the AW)
Unlike IACC,  IEE actually has to run on an I/A host and IEE does NOT =
=3D
use "foxapi" calls to communicate to the I/A system (this is good)
However because IEE actually communicates directly to the CP's (via the
=3D
CP's host AW) not only are there no .S files on the AW but the workfiles
=3D
that where stored on the AW are no longer used.=3D20
Because there are no workfiles you can no longer use any of the =3D
"/opt/fox/ciocfg/api" tools=3D20
This means no more "icc print" or "icc driver task" scripts (and no you
=3D
can't use the "save_all" or the "load_all" calls either.)
Apparently there will be a new type of scripting language available with
=3D
IEE=3D20
However I have not seen a document or a script to prove this claim.
About the only legacy thing left over from the old ICC days is the "CSA"
=3D
database.
Currently (as of v8.2) the check point file is still being stored on the
=3D
AW that hosts the CP so at least "dbvu" still works.
However once v8.4 is released the check point file will be stored in the
=3D
CP270 flash memory and "dbvu" could be headed for the trash too.
Unlike IACC, You can only have one(1)IEE database. This Galaxy database
=3D
must contain every CP/Gateway on the system.
IEE also includes the System Definition functionality and you won't be =
=3D
able to use System Def on the side with IEE.
(it does have a one time SysDef import function for migrating)


thanks

Peter


-----Original Message-----
From: Weiss, Andreas [mailto:Andreas.Weiss@xxxxxxxxxxxx]
Sent: Tuesday, June 26, 2007 1:00 AM
To: Bruley, Peter T
Subject: FW: [foxboro] .S file search


>  If your new v8.x XP System uses IACC or IEE you are out of luck as
you =3D3D
can NOT access the .S files.

Hi Peter,

are you having any information about the kind of database and the
database structure of IACC or IEE?

Regards,
Andreas

=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
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: