Re: [foxboro] I/A Batch Unix to I/A Batch Windows

We're facing an upgrade from 8.0 on solaris to windows also, but not in 
the near future.....
Regarding the conversion tool: our invensys contacts assured us there was 
a tool available to convert the recipes, we have 400+ recipes so this is 
an important issue. Could be the tool is officially released in the 
meantime.
Right now we have some issues with the redundant version of BS 8.0 on 
solaris, one AW51(E) is updating the transition values ok, the backup AW51 
seems to use a delta of 1, which is not very useable if your transition 
statements are waiting for pressure values in BAR....

Any one have an idea where these delta's are configured? It does not seem 
to be in BS, Foxapi and backup BS settings for both stations are 
identical. 

Rgds,

Dirk


wrote:

David and all I/A Batch users,
Last february we migrated from rel.8.0 under Solaris to rel.8.1 under 
Windows.
We prepared the migration in detail, with many checkpoints as we manage 
>600 recipes, under a "large" IABatch licence.

Briefly, this is our experience:

1) ModelDB, IALinkDB and RecipeDB (still Raima based) need to be 
converted. 
A recipe conversion tool is not offered by Invensys (it is for internal 
use only): so we paid the conversion as a consultant activity.
2) If you have developed some "C" programs based on Raima ToolKit, you 
need to rewrite as new "COM" libraries are different, based on ActiveX. No 
conversion is possible. Even with NutCracker. 
3) Some tuning done on EnvDisplay parameters (and on FoxAPI too) due to 
read/write tags timing issue. 
Our case: when a recipe writes a tag (CP linked), you can read it updated 
only after 1-2s; otherwise you must insert some "wait" transitions in the 
recipe.
In december 2008 we moved from CP40(FT)/AW51E on nodebus to 
CP270Z(FT)/P90/P92 on the Mesh, leaving IABatch on a Solaris AW51E 
(Nodebus side with ATS): with this intermediate configuration, no 
read/write problems occurred.
4)IALink: it was impossible to configure a bit >9 for a CP tag, now there 
is a QF to solve it.
5)BatchDisplay: great flexibility now offered by zoomable SFC elements and 
3 recipe layers on full sizeable windows!
Jump functionality is still available and working well, but it is less 
flexible than before.
6)apart the usual care when you modify the code of a sequence in held 
state (restart it after CP checkpoint is completed), I noted that 
BatchManager crashed when operator started a new batch, where the first 
phase/sequence in the recipe was changed and CP checkpoint not yet 
finished. 
Ugly, as it required a stop/restart of the whole Runtime tasks. 
Luckily, hot restart feature works fine as in rel.8.0.

All the remaining features are kept: the feel & look is based on Windows, 
but the speed is significantly better.
We don?t have yet a development platform to play with IABatch in more 
detail; we played enough on the real platform in the second half of 2008, 
when still off-line. There are some feature we don't use as we don't know 
in deep...

Regards,

Alessandro Ghiglione
Senior Application Engineer

Infineum Italia s.r.l.
Strada di Scorrimento,2
17047 Vado Ligure (SV) - Italia
*   +39.019.2150.277 
mob. +39.3484535196 
*    +39.019.2150.326
* mailto:alessandro.ghiglione@xxxxxxxxxxxx







 
 

 


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