Re: [foxboro] .S file search
- From: "Bruley, Peter T" <Peter.T.Bruley@xxxxxxxxxxxxxx>
- To: "Weiss, Andreas" <Andreas.Weiss@xxxxxxxxxxxx>, "Foxboro@Freelists. Org \(E-mail\)" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 26 Jun 2007 07:59:45 -0500
Andreas:
Someone can pipe up and correct me if I am wrong but this is how I =
understand these processes:
IACC
IACC uses a proprietary database that is spread across about 6-7 ".icd" =
files.=20
I have no idea what icd stands for but these files contain your entire =
system (all the CP's in your system)
These files are compressed (or padded with control characters) they are =
basically unreadable when loaded into a text editor.
Along with all the workfile information the .S files are contained =
somewhere in those proprietary database files.
These files can grow to become very large (about 30MB per CP) as you add =
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. =
have a database per CP)
IACC compiles the ".S" files and then sends the binaries to the Foxboro =
System=20
(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" =
and the "Checkpoint" files
IACC does not have to reside on a Foxboro I/A host. The IACC host just =
needs network access to a I/A AW.
IACC uses the AW's "foxapi" to communicate changes between the IACC =
database and Foxboro System (similar to FoxCAE)
(so there is a long waiting period as IACC creates all the IACC driver =
calls before communication actually occurs)
You can still make old style "savealls" to the hard drive =
(/opt/fox/ciocfg/api/save_all)=20
However you can not use "loadall" (/opt/fox/ciocfg/api/load_all) to put =
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 =
to create any new blocks as your IACC database will be out of sync as =
you can't upload new blocks into IACC.
IACC tried to incorporate System Definition however this functionality =
always lagged behind and was never really used.
IEE
IEE uses a proprietary database that is coupled to a SQL database called =
"Galaxy Database".=20
The SQL database contains no block parameters and I believe it is used =
to organize all the visual objects/names as you draw your configuration =
in loops called "Strategies".
Again the proprietary database files are basically unreadable when =
loaded into a text editor.
Like IACC, IEE does the compiling of all the ".S" files before =
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 =
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 =
CP's host AW) not only are there no .S files on the AW but the workfiles =
that where stored on the AW are no longer used.=20
Because there are no workfiles you can no longer use any of the =
"/opt/fox/ciocfg/api" tools=20
This means no more "icc print" or "icc driver task" scripts (and no you =
can't use the "save_all" or the "load_all" calls either.)
Apparently there will be a new type of scripting language available with =
IEE=20
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" =
database.
Currently (as of v8.2) the check point file is still being stored on the =
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 =
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 =
must contain every CP/Gateway on the system.
IEE also includes the System Definition functionality and you won't be =
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 =3D
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
_______________________________________________________________________
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
- Follow-Ups:
- Re: [foxboro] .S file search
- From: tom.vandewater
- Re: [foxboro] .S file search
- From: Doucet, Terrence
- Re: [foxboro] .S file search
- From: Johnson, Alex P \(IPS\)
Other related posts:
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- » Re: [foxboro] .S file search
- Re: [foxboro] .S file search
- From: tom.vandewater
- Re: [foxboro] .S file search
- From: Doucet, Terrence
- Re: [foxboro] .S file search
- From: Johnson, Alex P \(IPS\)