ETL600 1KHW001489-EN ABB Switzerland Ltd
firm- or software will generally inherit the compatibility relations from its
predecessors. Thus for each HMI600 version there is a compatibility
range – shown graphically in Fig. 4-10 - containing all ETL600
releases and updates thereof to which it is compatible (fully or
restricted). It is identical to the compatibility range mentioned in section
4.8.5. A specific HMI600 version will not be compatible (symbol 'X' in
Fig. 4-10) to all releases and updates thereof which are not within the
HMI compatibility range.
Restricted compatibility: In a situation of restricted compatibility,
when starting an upload or download operation, messages will
sometimes be displayed informing about some unavailable function
and corrective action. One such situation arises when new functions
have been added for a new release, which will not be known by
previous releases.
Note:
Inquire about the most recent HMI600 version each
time new ETL600 modules are purchased.
4.8.5. Compatibility of HMI600 to configuration files
The compatibility relations between HMI600 and a configuration file
can best be explained referring to Fig. 4-11. As shown, the
compatibility issue is coupled to the operation 'File / Open'. Testing of
this operation for configuration files generated by the present and by
past HMI600 versions is part of the system tests carried out for each
release of the ETL600 system.
HMI600
for Release N.N
Configuration file
File/
Open
Release N.N
HMI600
for Release < N.N
HMI600
for Release << N.N
Update of
HMI600
for Release N.N
HMI600
for Release > N.N
Configuration file Configuration file Configuration file Configuration file
File/
Save
File/
Sav
Present FuturePast
MMI compatibility range
Fig. 4-11 Compatibility relations for HMI600 configuration files
A specific HMI600 version is fully compatible to a configuration file, if
all information contained within the file can be correctly read
(Operation File / Open). It will have restricted compatibility (symbol '
U '
in Fig. 4-11; definition: refer to the explanations below) to configuration
User Interface Program November 2005 4-17