Re: [foxboro] I/A Batch Unix to I/A Batch Windows
- From: dirk.pauwels@xxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 9 Jul 2009 17:54:47 +0200
We already have 8.4.2 with 2003 server as boothost running ICC. We haven't
had sequence problems like described in the customer advisory, even though
we use single quote references to strings and defines. Guess we were lucky
this time....
nice to hear the tool works, at least something less to worry about....
Dirk
"Moffatt, Daren" <daren.moffatt@xxxxxxxxxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
09/07/2009 16:02
Please respond to
foxboro@xxxxxxxxxxxxx
To
<foxboro@xxxxxxxxxxxxx>
cc
Subject
Re: [foxboro] I/A Batch Unix to I/A Batch Windows
My apologies for the previous email. Now I know not to send attachments.
With regards to the conversion tool, IPS decided to not "officially"
release the conversion tool, but the tool does exist, has been used in the
past, and will convert an I/A Series Batch Unix configuration to I/A
Series Batch Windows. Due to the number of conversion possibilities with
the different versions and the different hardware required, it is easier
to have the required Unix and Windows workstations staged in IPS and
perform the conversion internally. All that is required is a backup of the
current batch configuration directory. I would suggest working with your
local account manager if a conversion is required. He/She can contact me
to complete the process. The databases converted by the tool include
model, link, TIM, material, recipe, and security.
The following table documents several conversion paths:
1. FoxBatch to IA Batch Windows - internal conversion tool available
2. IA Batch Unix to IA Batch Windows - internal conversion tool available
3. IA Batch Windows (versions prior to 8.1) to IA Batch Windows v8.1 -
conversion tool provided with software
One other area of potential impact is possible recompiling of the sequence
code when migrating to and above I/A Series v8.2. This is not a
requirement from the batch software, but has an impact on batch systems
given the heavy reliance on sequence code in a batch application. There
was a customer advisory issued in February on this topic.
The Document B0700RW REV A "I/A Series® System V8.4.2 Release Notes and
Installation Procedures for Windows XP and Solaris Operating Systems"
Chapter 10.6 Integrated Control Block Software and Utilities, provides
overviews and detailed tips on "what to expect" and "how to resolve" the
specific issues.
Regards,
Daren Moffatt
Invensys Process Systems
daren.moffatt@xxxxxxxxxxxxxxxx
Office: 717-285-9477
Mobile: 717-319-1902
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Ghiglione, Alessandro
Sent: Thursday, July 09, 2009 7:23 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] I/A Batch Unix to I/A Batch Windows
Dirk,
I forgot 2 aspects:
A) we move from one redundant BS (rel.8.0) to two separate BS for
different plant area.
It was possible as the 2 area are independent.
The redundancy in the past gave us more trouble than benefits!
Repeated master/backup switchover were intolerable.
B) in rel.8.0 we used the same value read delta=write delta=1.0
Now in rel.8.1 , actual values are 0.001 (read delta) and 0.49 (write
delta).
When modifying a set point (write to CP) now the behaviour is consistent
with the delta value, while in rel.8.0 you read back the changed value
even if below the delta, as write delta were uninfluent....
BS EnvDisplay read/write delta values are written to FoxAPI.
I hope this help.
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
Infineum Italia S.r.l.
Cap. Soc. ? 20.000.000,00 Int. Vers.
Sede legale: Via Lepetit 8 - 20124 Milano
Sede amm.va e stabilimento: Strada di Scorrimento 2 - 17047 Vado Ligure
(SV)
Codice Fiscale e Partita IVA: IT12640380155
Reg. Imp. di Milano n. 255530/1998 - REA 1573108
Con Socio Unico
Informazione a norma dell'art. 2497-bis 1° c. CC: Infineum Netherlands
B.V. - Rotterdam (NL)
Questa nota può contenere informazioni ritenute confidenziali per
Infineum. Se è stata ricevuta non intenzionalmente: (a) si prega di non
considerare le informazioni contenute nella stessa; (b) non rivelare,
distribuire o duplicare alcuna informazione contenuta in questa nota; e
(c) contattare l?autore.
This note may contain Infineum confidential information. If you are an
unintended recipient: (a) place no reliance on the information contained
herein; (b) do not disclose, distribute, or duplicate any information from
this note; and (c) please contact the author.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of dirk.pauwels@xxxxxxxxxx
Sent: giovedì 9 luglio 2009 11.59
To: foxboro@xxxxxxxxxxxxx
Subject: 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
_______________________________________________________________________
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
** Confidentiality Notice:
This e-mail, including any associated or attached files, is intended
solely for the individual or entity to which it is addressed. This e-mail
is confidential and may well also be legally privileged. If you have
received it in error, you are on notice of its status. Please notify the
sender immediately by reply e-mail and then delete this message from your
system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person.
This email is from the Invensys Process Systems business unit of the
Invensys Group, a group of companies owned by Invensys plc, which is a
company registered in England and Wales with its registered office at
Portland House, Bressenden Place, London, SW1E 5BF (Registered number
166023). For a list of European legal entities within the Invensys Group,
please go to
http://www.invensys.com/legal/default.asp?top_nav_idw&nav_id?&prev_idw
.
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto may
be subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries
and affiliates).
_______________________________________________________________________
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
_______________________________________________________________________
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: