Contents
Notes on installation
1
Scope of delivery
Hardware requirements
3
Software requirements
3.1 Runtime environment
3.2 Memory requirements
4
Installation
4.1 Installing AS-OS Engineering
4.2 Uninstalling AS-OS Engineering
Release notes
1
Upgrades and changes compared to previous versions
1.1 What's new?
2
Notes on configuration and operation
2.1 Changing between various versions of AS-OS Engineering
2.2 General
3
Notes on documentation
Notes on installation
The notes on installation contain essential information you require for the installation of
the AS-OS Engineering V7.1.2 software. Please read these notes before you start this
installation.
Scope of delivery
This consignment contains the following product:
Hardware requirements
As for SIMATIC STEP 7 and SIMATIC WinCC.
Software requirements
3.1
Runtime environment
AS-OS Engineering is an optional software package and requires the installation of the
following additional software an your PG or PC:
SIMATIC STEP 7 V5.4 + SP1 or higher
SIMATIC WinCC V6.2 or higher
3.2
Memory requirements
AS-OS Engineering requires approx. 7 MB of free hard disk space.
Installation
4.1
4.2
The uninstaller may fail to remove some of the dynamic data generated in AS-OS
Engineering. The uninstall tool will recognize these data and output the message "Some
elements could not be removed. You should manually remove items related to the
application.". You can delete these dynamic data, though it is not necessary to do so.
Release Notes
These release notes override information in the Manuals and in the Online Help.
1.1
What's new ?
Please read the section "What's new in AS-OS Engineering?" in the AS-OS Engineering
online help.
2.1
2.2
General
Please note:
If you assign an area to multiple OSs in a multiproject during area-oriented OS
compilation, or if you assign multiple OSs to an S7 program during AS-oriented OS
compilation, the compilation of changes only functions properly when these changes
are compiled on all assigned OSs, before new changes are made.
Any invalid characters in the names forming the variable name are replaced with the $
character. Invalid characters are: % . ' \ ? * :, as well as the empty string.
The origin of interrupt-capable message blocks is entered automatically in WinCC
messages, provided you do not change the default entry $$AKZ$$ in the "Origin" field
when you configure your PCS 7 messages or nothing is entered there. The PH path
(only the folders forming the name), the path name and the block name entered
indicate the origin. The program name, path name and block names are entered if a
PH has not been configured.
The area names are entered automatically in the WinCC block list and WinCC
messages, provided these were configured in the plant hierarchy and the default entry
$$AREA$$ in the "OS area" field remains unchanged when you configure your PCS 7
messages or nothing is entered there. Consistency between the area-specific filtering
function "Select picture via reference tags ", the area-specific user administration and
Notes on documentation
The Online Help contains essential information relevant to AS-OS Engineering. After you
have installed AS-OS Engineering, you can access this help either by calling the "Help"
menu or the context-sensitive menu via F1 key, or by means of the "?" question mark.
Asset Management: The OS process control engineering from PC stations are now
always assigned to the Diagnostics area.
To take advantage of this improvement, Update 1 of TH 7.1 SP2 has to be installed.
The use of blocks from the powerrate library no longer increases the license
requirement in WinCC.
Unchanged container names in the picture tree are no longer transferred during the
compilation of changes.
After copying and renaming CFC charts, the tags of all structure types from the
original charts are retained during subsequent OS delta compiling.