Sunteți pe pagina 1din 4


Update 1 on AS-OS Engineering V7.1 SP2

Assistant for the compilation of Operator Stations
Release notes on installation and usage
The notes and information found here override relevant information in all other documentations.
Please read this information thoroughly, for it contains essential information on installation and
usage of AS-OS Engineering.
You can find important information on Update 1 for AS-OS Engineering V7. 1 incl. SP2 in
the section Notes on Usage (Release Notes) / 4 Notes on the Update.

Notes on installation

Scope of delivery

Hardware requirements

Software requirements
3.1 Runtime environment
3.2 Memory requirements
4.1 Installing AS-OS Engineering
4.2 Uninstalling AS-OS Engineering

Release notes
Upgrades and changes compared to previous versions
1.1 What's new?
Notes on configuration and operation
2.1 Changing between various versions of AS-OS Engineering
2.2 General

Notes on documentation

Notes on the Update

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

Scope of delivery
This consignment contains the following product:

AS-OS Engineering V7.1.2 Update 1

Hardware requirements

Software requirements


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


Memory requirements
AS-OS Engineering requires approx. 7 MB of free hard disk space.



Installing AS-OS Engineering

You can install AS-OS Engineering V7.1.2 over an existing AS-OS Engineering
Installation of SIMATIC STEP 7 and SIMATIC WinCC is prerequisite for an installation of
AS-OS Engineering. The STEP 7 package and the WinCC configuration system must be
installed on the same PG or PCs, including the WinCC component "Communication:
Object Manager".
AS-OS Engineering setup is menu controlled. Start this SETUP.EXE by double-clicking
on its program in your MS Windows Explorer. You must install your AS-OS Engineering
system on the drive that contains the STEP 7 package. Sufficient hard disk space must
be available.
AS-OS Engineering is registered in the MS Windows system files. Do not use Microsoft
Windows tools such as the Explorer to move AS-OS Engineering data and folders or
manipulate AS-OS Engineering data in the MS Windows Registry; otherwise program
execution errors are to be expected.


Uninstalling AS-OS Engineering

---------------------------------------------------------------------------------------------------------------Important note:
The removal of software products must conform with the requirements of MS Windows.
Uninstall your software package (e.g. "SIMATIC AS-OS Engineering V7.1.2") only via the
MS Windows application "Software" (from the MS Windows Task bar select: Start >
Settings > Control panel > Software). The uninstall routine under MS Windows is the
only way to uninstall the software.

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.

Upgrades and modifications compared to previous versions


What's new ?
Please read the section "What's new in AS-OS Engineering?" in the AS-OS Engineering
online help.

Notes on configuration and operation


Changing between various AS-OS Engineering versions

When working with AS-OS Engineering V7.1.2 in projects whose AS data were previously
transferred to WinCC using and AS-OS Engineering version < V7.1.2, the scope
"Compile OS with CPU memory reset" must be set when the Assistant function "Compile
OS " is called the first time.
You can find more information about upgrading to PCS 7 V7.1.2 in the PCS 7 manuals
"Software Update without utilization of the new functions" and "Software Update with
utilization of the new functions."


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

the "Arrange curves online " function is prerequisite.

AS-OS Engineering creates containers with area-specific names in the WinCC Picture
Tree Manager, provided you have selected the option "Derive Picture Tree from PH"
in the PH settings (SIMATIC Manager: Options > Plant Hierarchy > Settings...) and
the compilation scope "Picture Tree" in the "Select compilation data and scope " in the
"Compile OS" dialog of the assistant. All configuration data of the Picture Tree
Manager will be deleted before the Picture Tree data are created.
With interrupt-capable blocks, the block comment configured by the user at the block
instance is automatically entered as event text in the WinCC messages, provided you
do not change the default entry $$BlockComment$$ in the "Event" field when you
configure your PCS 7 messages.
The CPU name is entered at the corresponding location when you set the keyword
$$CpuName$$ in the "Text1" or "Text2" field of a STEP 7 message.
It is required in all S7 programs that the structure of messages and system attributes
S7_m_c and S7_qc and the parameter addresses is the same for all block types (FBs)
with identical symbolic name, which are assigned to an OS. It is otherwise not
possible to compile OS data correctly, and will lead to the entry of a corresponding
error message in the compilation log.
Please make sure the S7 program names are unambiguous in your project (or
multiproject), since these names are verified prior to the compilation of OS data,
including the program names not assigned to a specific CPU.
When using operator controlled and monitored symbols in your project, you should
make sure each one of these symbols is assigned a unique name. Always assign
unique names to CFC and SFC charts when using the PH and if the name of the
hierarchy folder does not contribute to these names. Naming is not case-sensitive and
you should thus avoid identical block names in your CFC chart. Compilation will be
aborted otherwise in all these cases, since variables with ambiguous names can not
be created in the OS. AS-OS Engineering supports analysis of ambiguous names with
corresponding entries of these names in the compilation log.
The symbolic names of operator controlled and monitored global data blocks and
instances of block types may not exceed a length of 16 characters.

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.

Notes on the Update

Update 1 contains the following extensions or corrections:

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.