VASS Standard Configuration Guideline V 1.7

VASS Standard
Configuration Guideline
VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

Saved on: 06.12.2012
Siemens AG Page 1 of 402
General
Safety Guidelines
This documentation contains information which you must adhere to for your own personal safety and
to avoid property damage. The notices referring to your personal safety are highlighted in the manual
by a safety alert symbol, notices referring to property damage only have no safety alert symbol. The
notices shown below are graded according to the degree of danger.
Danger
indicates that death or severe personal injury will result if proper precautions are not taken.
Warning
indicates that death or severe personal injury may result if proper precautions are not taken.
Caution
with warning triangle indicates that minor personal injury can result if proper precautions are not
taken.
Caution
without a safety alert symbol indicates that property damage can result if proper precautions are
not taken.
Notice
indicates that an undesirable result or status can occur if the relevant notice is ignored.
If more than one degree of danger is present, the warning notice representing the highest degree of
danger will be used. A notice warning of injury to persons with a safety alert symbol may also include
a warning relating to property damage.
Typographical Conventions
Note
This symbol identifies information to facilitate understanding the machine processes. It points to
important information about the system or handling the system.
Reference / Note (to other documentation)

This symbol references information from other pieces of documentation that are connected with the
existing system in a broader context.
In development, technical clarification / initial processing or revision

This symbol references a text segment in the documentation that has not been completed yet.
Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

Saved on 06.12.2012
Page 2 of 402 Siemens AG
General
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Only
qualified personnel should be allowed to install and work on this device/system. Within the context of
the safety notices in this documentation qualified persons are defined as persons who are authorized
to commission, ground and label devices, systems and circuits in accordance with established safety
practices and standards.
Correct Usage
Warning
This device and its components may only be used for the applications described in the catalog or
the technical description, and only in connection with devices or components from other
manufacturers which have been approved or recommended by Siemens. Correct, safe operation of
the product depends on correct transportation, correct storage, installation and mounting as well as
careful operator control and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in
this publication may be trademarks whose use by third parties for their own purposes could violate the
rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and
software described. Since variance cannot be precluded entirely, we cannot guarantee full
consistency. However, the information in this publication is reviewed regularly and any necessary
corrections are included in subsequent editions.
Legal Notice
The transfer, reproduction, distribution and utilization of this document as well as the communication
of its content are permitted only with the express permission of the Volkswagen Group or Siemens
AG. Offenders will be held liable for payment of damages.
All rights created by patent grant or registration of a utility model are reserved.

Saved on 06.12.2012
General
Document Identification
Project name: VASS Standard Configuration Guideline
Scope: Volkswagen Group, body manufacturing
Document type: Configuration guideline
Name of document: VASS Standard Configuration_Guideline_V_1_7.doc
Author: Michael Stengel (evopro AG) on behalf of Siemens AG
Saved on: 21.11.2012
Current version
Version
Editor Change reason Remarks
Status Date
1.7 12.11.2012 Michael Stengel Correction and Update ---
Version History
Version
Editor Change reason Remarks
Status Date
1.2.1 21.06.2011 Carsten Zickner Correction ---
1.0 16.02.2011 Michael Stengel --- Initial issue
Changes to the preceding revision level

The following significant changes were made compared to the published version (V1.6 / 22.08.2012):
 Ch. 1.2.1 Text change to "WinCC flexible" (2008 Advanced HmiES.exe) in the
"Function" column.
 Ch. 1.2.2 Text change to "WinCC flexible" (2008 Advanced HmiES.exe) in the
"Function" column.
 Ch. 2.2.3.1.4 Text passages and note in ch. "Modification of WinCC flexible system
with specific data" were updated.
 Ch. 2.2.3.1.6 Ch. "SIMATIC WinCC flexible setup - Start center" was added.
 Ch. 2.3.1.4.2 Link "Fig. 2.27 Messages application settings" (p. 43) was
updated.

Saved on 06.12.2012
General
 Ch. 3.1.3 Link "Chapter 6 SiVArc" (p. 52) was updated.

 Ch. 4.1 Link "Fig. 4.4 . - Structure of PROFINET device names" (p. 65) was
updated.
 Ch. 4.1.2 Link "Fig. 4.6 PROFINET General settings" (p. 66) was
updated.
 Ch. 4.8.7.1 Ch. "Meld_4" was expanded (text and Tab. 4.3 "Structure after the
$-character").
 Ch. 4.8.8.2.1 Fig. 4.60 "S7G_Control module" was expanded by the green border
(incl. corresponding link).
 Ch. 4.8.8.2.4 Fig 4.65 "FC_Trans module" was expanded by a green border
(SNO_Time).
An additional note was inserted after Fig. 4.65.
 Ch. 4.8.8.2.5 Ch. "AS_xxyyyy module" was expanded by two list items and by
Fig. 4.60 "Declaring an initial step".
 Ch. 6.1.2 Link "Tab 1.1 Software tools for Windows XP" was updated.
 Ch. 6.2 Fig. 6.2 "Install standard selection" was updated.
 Ch. 6.3.1 Link "Chapter 4.2.3 Report system errors" was updated.
 Ch. 6.4.2.2 Note at subitem "Automatic faceplate update" was added.
Fig. 6.30 "Updating the project" was updated.
 Ch. 6.4.2.3.1 Note (p. 198) was newly added.
 Ch. 7.2.3.16 "Post-processing" was updated.
Fig. 7.49 "Post-processing" was newly added.
 Ch. 7.2.4 Link / "Fig. 6.47 Selection to Overwrite picture or Create Delta picture"
was updated.
 Ch. 7.2.6 Text, Fig. 7.81 "Generating via generation symbol" and note were added.
 Ch. 8 Ch. "Multiple languages" was completely revised and updated.
Existing text passages from V 1.6 were partially changed only with respect to
their order.
 Ch. 9.1.3 Text and Fig. 9.9 "SIMATIC WinCC flexible - Start center" were added.
 Ch. 9.1.3.1 Note (p. 335) was newly added.
 List of abbreviations:
Under "W" WCF (= WinCC flexible) was added.
 Appendix D Changes in the table "F-parameter application examples":
- "Type 1 – Articulated flap variant 2" added,
- "Type 3 – Articulated flap" renamed to "Type 3 – Articulated flap variant 1"
- "Type 1 – Emergency-stop robot" renamed to "Type 1 – Emergency-stop
robot (VKRC2)".
 Appendix D Caption for Fig. 9.37 "Example of F-parameter (type 1) input 4/8 F-DI
emergency-stop robot (VKRC2)" was updated.
 Appendix D Fig. 9.41 "Example F-parameter (type 1) input 4/8 F-DI articulated flap
variant 2" was added.
 Appendix D Caption for Fig. 9.47 "Example of F-parameter (type 3) input 4/8 F-DI
articulated flap variant 1" was updated.

Saved on 06.12.2012
General
Siemens AG Siemens AG Copyright ©

Automation and Drives Planung Anlagenelektrik Siemens AG / Volkswagen AG
38436 WOLFSBURG
Postfach 48 48 Subject to change
GERMANY
90437 NÜRNBERG
GERMANY

Saved on 06.12.2012
General
Contact person
VOLKSWAGEN AG Technical
Carsten Zickner
Department: PMP-A/B Planung Anlagenelektrik Karosseriebau
Location: Wolfsburg
Telephone: +49 (0)5361 / 9-42165
Mobile: +49 (0)151 - 16807985
Fax: +49 (0)5361 / 9-70085
mailto: carsten.zickner@volkswagen.de
VOLKSWAGEN AG Technical
Name: Frank Hennig
Department: PMP-A/B Planung Anlagenelektrik Karosseriebau
Location: Wolfsburg
Telephone: +49 (0)5361 / 9-123003
Mobile: +49 (0)1522 - 2923003
Fax: +49 (0)5361 / 9-70085
mailto: frank.hennig@volkswagen.de
AUDI AG Technical
Name: Felix Niederbacher
Department: N/PN11 Karosseriebau
Location: Neckarsulm
Telephone: +49 (0)7132 / 31-72489
Mobile: +49 (0)160 - 97295871
Fax: +49 (0)7132 / 31-8472489
mailto: felix.niederbacher@audi.de
evopro systems engineering AG Document Authoring

Name: Michael Stengel
Department: Media-Solutions
Location: Nürnberg
mailto: michael.stengel@evopro-ag.de

Saved on 06.12.2012
Contents
Contents
Safety Guidelines ...................................................................................................... 2
Typographical Conventions ..................................................................................... 2
Qualified Personnel ................................................................................................... 3
Correct Usage ............................................................................................................ 3
Trademarks ................................................................................................................ 3
Disclaimer of Liability ............................................................................................... 3
Legal Notice ............................................................................................................... 3
Document Identification ............................................................................................ 4
Current version .......................................................................................................... 4
Version History .......................................................................................................... 4
Changes to the preceding revision level ................................................................. 4
Contact person .......................................................................................................... 7
Contents ..................................................................................................................... 8
1 . Introduction and Objectives ............................................................................... 19

1.1 .... Introduction ................................................................................................................................19
1.1.1 ....... Objective of this documentation ..............................................................................................19
1.1.2 ....... Basics of the objective ............................................................................................................19
1.1.3 ....... Target groups ..........................................................................................................................19
1.1.4 ....... Follow-up versions ..................................................................................................................20
1.2 .... Software tools for the configuration ........................................................................................20
1.2.1 ....... Software tools for the configuration with Windows XP ...........................................................20
1.2.2 ....... Software tools for the configuration with Windows 7 / 64 bit ..................................................21
2 . System Configuration ......................................................................................... 22

2.1 .... Hardware requirements for programming environment ........................................................22
2.2 .... Software installation ..................................................................................................................23
2.2.1 ....... SIMATIC STEP 7 Professional ...............................................................................................23
2.2.1.1 ......... Installing the software ........................................................................................................23
2.2.2 ....... S7 Distributed Safety ..............................................................................................................24
2.2.2.1 ......... Installing the software ........................................................................................................24
2.2.3 ....... WinCC flexible .........................................................................................................................25
2.2.3.1 ......... Software installation for WinCC flexible 2008 Advanced SP2 / SP3 .................................25
2.2.3.1.1 ........... WinCC flexible 2008 Advanced with SP2 / SP3 ...........................................................25
2.2.3.1.2 ........... WinCC flexible 2008 Advanced with SP2 .....................................................................26
2.2.3.1.3 ........... WinCC flexible 2008 Activate .......................................................................................26

Saved on 06.12.2012
Contents
2.2.3.1.4 ........... Modification of WinCC flexible system with specific data .............................................27
2.2.3.1.5 ........... 16-K variable .................................................................................................................28
2.2.3.1.6 ........... Setup of "SIMATIC WinCC flexible – Start center" .......................................................29
2.2.4 ....... SiVArc Screen Generator........................................................................................................30
2.2.4.1 ......... Installation ..........................................................................................................................30
2.3 .... System settings for STEP 7 ......................................................................................................33
2.3.1 ....... Settings for STEP 7.................................................................................................................33
2.3.1.1 ......... Settings of LAD, FBD, STL editor ......................................................................................33
2.3.1.2 ......... Settings of address priority in STEP 7 programming .........................................................35
2.3.1.3 ......... Settings of the columns ......................................................................................................37
2.3.1.4 ......... S7 GRAPH settings ...........................................................................................................38
2.3.1.4.1 ........... Application settings .......................................................................................................38
2.3.1.4.2 ........... Block settings ................................................................................................................42
2.3.1.5 ......... Settings in S7 SCL .............................................................................................................44
2.4 .... SiVArc Screen Generator system settings ..............................................................................47
2.5 .... System settings for WinCC flexible..........................................................................................47
3 . Data storage......................................................................................................... 48
3.1 .... Description of the folders in the directory structure ..............................................................51
3.1.1 ....... 01_Werk ..................................................................................................................................51
3.1.2 ....... 02_S7 ......................................................................................................................................51
3.1.2.1 ......... 01_Bibliothek......................................................................................................................51
3.1.2.2 ......... 02_Projekte ........................................................................................................................51
3.1.2.3 ......... 03_Archive .........................................................................................................................51
3.1.2.4 ......... 04_Gerätekatalog ..............................................................................................................51
3.1.2.5 ......... 05_Referenzen...................................................................................................................51
3.1.3 ....... 03_SiVArc ...............................................................................................................................52
3.1.3.1 ......... 01_Metamodell...................................................................................................................52
3.1.3.2 ......... 02_Textlisten ......................................................................................................................52
3.1.3.3 ......... 03_Sprachdatenbank .........................................................................................................52
3.1.3.4 ......... 04_Registry_Onlinehilfen ...................................................................................................52
3.1.4 ....... 04_WinCC flexible...................................................................................................................53
3.1.4.1 ......... 01_Vorlagen .......................................................................................................................53
3.1.4.2 ......... 02_Symbolbibliothek ..........................................................................................................53
3.1.4.3 ......... 03_Runtime ........................................................................................................................53
3.1.4.4 ......... 04_UserDictionary .............................................................................................................53
3.1.5 ....... 05_Remote_Operate...............................................................................................................53
3.1.6 ....... 06_Dokumentation ..................................................................................................................53
3.1.7 ....... 07_ZAÜ ...................................................................................................................................53
3.2 .... Block help ...................................................................................................................................54

Saved on 06.12.2012
Contents
3.2.1 ....... Block help for Windows XP .....................................................................................................54

3.2.2 ....... Block help for Windows 7 / 64 bit ............................................................................................55
3.2.2.1 ......... Preparatory measures .......................................................................................................55
3.2.2.2 ......... Setting up a directory and registering ................................................................................59
4 . Project creation ................................................................................................... 61

4.1 .... PROFINET ...................................................................................................................................65
4.1.1 ....... Structure of PROFINET device names ...................................................................................65
4.1.2 ....... Nodes in the PROFINET IO system .......................................................................................66
4.1.3 ....... PROFINET topology ...............................................................................................................69
4.1.4 ....... Ethernet node ..........................................................................................................................78
4.2 .... CPU settings ...............................................................................................................................79
4.2.1 ....... Protection ................................................................................................................................79
4.2.2 ....... Cycle monitoring time OB1 .....................................................................................................80
4.2.3 ....... Report system errors...............................................................................................................80
4.3 .... VASS term definition for function and function blocks .........................................................84
4.3.1 ....... Structure FC ............................................................................................................................84
4.3.2 ....... Structure FB ............................................................................................................................84
4.3.3 ....... Module FB ...............................................................................................................................84
4.3.4 ....... Module FC ...............................................................................................................................84
4.4 .... Overview of block distribution ..................................................................................................85
4.5 .... Variables .....................................................................................................................................86
4.5.1 ....... Global variables ......................................................................................................................86
4.5.1.1 ......... I/O area ..............................................................................................................................86
4.5.1.2 ......... Bit memory address area ...................................................................................................88
4.5.1.3 ......... DBs ....................................................................................................................................88
4.5.1.4 ......... Instance DB........................................................................................................................89
4.5.2 ....... Local variables ........................................................................................................................90
4.5.3 ....... Data types (UDTs) ..................................................................................................................91
4.6 .... General rules for generating the visualization ........................................................................93
4.6.1 ....... Symbolic names of structure FCs ...........................................................................................93
4.6.2 ....... Instance name and declaration comment of module FCs ......................................................93
4.6.3 ....... HMI keyword ...........................................................................................................................94
4.6.4 ....... Variable interconnection at the module FB interface ..............................................................95
4.6.5 ....... Introduction for the text representation in the faceplate ..........................................................97
4.7 .... Project base structure ...............................................................................................................99
4.7.1 ....... Call structure OB1 ...................................................................................................................99
4.8 .... Program .....................................................................................................................................102
4.8.1 ....... Programming guidelines for ladder logic (LAD) ....................................................................103
4.8.2 ....... Designation guideline for function blocks..............................................................................106

Saved on 06.12.2012
Contents
4.8.3 ....... F Call .....................................................................................................................................106

4.8.4 ....... "PoT" structure FC ................................................................................................................107
4.8.5 ....... "Basic functions" structure FC...............................................................................................108
4.8.5.1 ......... FB_Steuerung ..................................................................................................................109
4.8.5.2 ......... SFC51 "RDSYSST" (PROFINET)....................................................................................109
4.8.5.3 ......... FB_Visu ............................................................................................................................109
4.8.5.4 ......... FB_Mobile ........................................................................................................................109
4.8.5.5 ......... Meld_4 .............................................................................................................................109
4.8.5.6 ......... FB_PDE_Schicht / FB_PDE_Statistik / FB_Statistik_Typ ...............................................110
4.8.5.6.1 ........... FB_PDE_Schicht ........................................................................................................110
4.8.5.6.2 ........... FB_PDE_Statistik .......................................................................................................110
4.8.5.6.3 ........... FB_Statistik_Typ .........................................................................................................110
4.8.6 ....... Structure FC "Preselections".................................................................................................111
4.8.6.1 ......... FB_Vorwahl......................................................................................................................111
4.8.6.2 ......... FB_Druckluft ....................................................................................................................111
4.8.6.3 ......... FB_Kuehlwasser ..............................................................................................................111
4.8.6.4 ......... FB_Energie ......................................................................................................................111
4.8.7 ....... Structure FC "Operating Modes" ..........................................................................................112
4.8.7.1 ......... Meld_4 .............................................................................................................................113
4.8.7.2 ......... FB_NotHalt.......................................................................................................................113
4.8.7.3 ......... FB_Schutzkreis ................................................................................................................113
4.8.7.4 ......... Traffic light ........................................................................................................................114
4.8.7.5 ......... FB_BA / FB_BA_LSP / FB_BA_UBA...............................................................................114
4.8.7.5.1 ........... "FB_BA" block .............................................................................................................114
4.8.7.5.2 ........... "FB_BA_LSP" block (operating modes for station) ....................................................114
4.8.7.5.3 ........... "FB_BA_UBA" block (operating modes for substation) ..............................................114
4.8.7.6 ......... FB_Sammelstatus ............................................................................................................115
4.8.8 ....... "STxxyyyy" station structure FC ............................................................................................116
4.8.8.1 ......... FB_Status / FB_ST_Status / FB_ST_Status_K100 .........................................................117
4.8.8.1.1 ........... "FB_Status" block .......................................................................................................117
4.8.8.1.2 ........... "FB_ST_Status" block.................................................................................................117
4.8.8.1.3 ........... "FB_ST_Status_K100" block ......................................................................................117
4.8.8.2 ......... Sequential control ............................................................................................................118
4.8.8.2.1 ........... "S7G_Control" block ...................................................................................................119
4.8.8.2.2 ........... "AST_xxyyyy" block ....................................................................................................122
4.8.8.2.3 ........... "FC_Trans_Init" block .................................................................................................123
4.8.8.2.4 ........... "FC_Trans" block ........................................................................................................124
4.8.8.2.5 ........... "AS_xxyyyy" block ......................................................................................................126
4.8.8.3 ......... FB_Statistik / FB_Statistik_Typ / FB_Taktzeit / FB_Zähler .............................................128
4.8.8.3.1 ........... "FB_Statistik" block .....................................................................................................128

Saved on 06.12.2012
Contents
4.8.8.3.2 ........... "FB_Statistik_Typ" block .............................................................................................128

4.8.8.3.3 ........... "FB_Taktzeit" block .....................................................................................................128
4.8.8.3.4 ........... "FB_Zähler" block .......................................................................................................128
4.8.8.4 ......... FB_Sammelstatus ............................................................................................................128
4.8.9 ....... "Robot" structure FC .............................................................................................................129
4.8.9.1 ......... FB_Rob_PN_A.................................................................................................................130
4.8.9.2 ......... FB_RobFolge_8 / FB_Rob / FB_Rob_Korr .....................................................................130
4.8.9.2.1 ........... "FB_RobFolge_8" block ..............................................................................................130
4.8.9.2.2 ........... "FB_Rob" block ...........................................................................................................130
4.8.9.2.3 ........... "FB_Rob_Korr" block ..................................................................................................130
4.8.9.3 ......... FB_Rob_FM / FB_Status_Global ....................................................................................131
4.8.9.3.1 ........... "FB_Rob_FM" block....................................................................................................131
4.8.9.3.2 ........... "FB_Status_Global" block ...........................................................................................131
4.8.9.4 ......... FB_Rob_Frg_Ver / FB_Rob_Frg .....................................................................................131
4.8.9.4.1 ........... "FB_Rob_Frg_Ver" block ............................................................................................131
4.8.9.4.2 ........... "FB_Rob_Frg" block … ...............................................................................................131
4.8.9.5 ......... FB_Rob_Kleben / FB_Rob_Schweissen / FB_RobMedien .............................................132
4.8.9.5.1 ........... "FB_Rob_Kleben" block..............................................................................................132
4.8.9.5.2 ........... "FB_Rob_Schweissen" block .....................................................................................132
4.8.9.5.3 ........... "FB_RobMedien" block ...............................................................................................132
4.8.9.6 ......... FB_Taktzeit_Plus .............................................................................................................132
4.8.9.7 ......... FB_Rob_PN_E.................................................................................................................132
4.8.9.8 ......... FB_Sammelstatus ............................................................................................................132
4.8.9.9 ......... "Layer" ..............................................................................................................................133
4.8.9.9.1 ........... Robot ..........................................................................................................................133
4.8.9.9.2 ........... Robot process device .................................................................................................134
4.8.9.9.3 ........... Machine process .........................................................................................................135
4.8.10 ..... "Interfaces" structure FC .......................................................................................................136
4.8.10.1 ....... FB_KommKon ..................................................................................................................136
4.8.11 ..... FB "MessageFB" ...................................................................................................................137
4.8.11.1 ....... MessageFB ......................................................................................................................137
4.8.12 ..... "GBA" structure FC ...............................................................................................................138
4.8.12.1 ....... FB_GBA ...........................................................................................................................138
4.8.12.2 ....... FB_GBA_Wertanzeige .....................................................................................................138
4.8.13 ..... "ZAU" structure FC ................................................................................................................139
4.8.13.1 ....... ZAÜ_GrundFkt .................................................................................................................140
4.8.13.2 ....... ZAÜ_Schalt ......................................................................................................................140
4.8.13.3 ....... ZAÜWerte ........................................................................................................................140
4.8.13.4 ....... ZAÜSollwert .....................................................................................................................140
4.8.13.5 ....... ZAÜAnlStatus...................................................................................................................140

Saved on 06.12.2012
Contents
4.9 .... Block update .............................................................................................................................141
5 . S7 Distributed Safety ........................................................................................ 142

5.1 .... Configuration steps .................................................................................................................142
5.2 .... PROFIsafe components ...........................................................................................................143
5.2.1 ....... ET 200S station, PROFIsafe components ............................................................................143
5.2.1.1 ......... Address switch for setting the PROFIsafe address .........................................................143
5.3 .... Configuration of the F-modules in the hardware configuration ..........................................144
5.3.1 ....... Configuring the CPU 317F, CPU 319F .................................................................................144
5.3.1.1 ......... Protection level.................................................................................................................144
5.3.1.2 ......... F Parameters ...................................................................................................................144
5.3.1.3 ......... PROFINET device numbers and PROFIsafe F_Ziel_Adressen ......................................145
5.3.1.4 ......... Setting of F_Überwachungszeit (F_WD_Time) of PROFINET safe devices ...................145
5.3.2 ....... Configuring stations with I/O modules ..................................................................................146
5.3.2.1 ......... Configuring a fail-safe 4/8 F-DI module ...........................................................................146
5.3.2.2 ......... Configuring a fail-safe 4 F-DO module ............................................................................148
5.3.2.3 ......... Configuring a fail-safe 4 F-RO module ............................................................................149
5.4 .... Save and compile hardware ....................................................................................................150
5.4.1 ....... F-I/O devices DB ...................................................................................................................150
5.4.2 ....... Configuration of a PN/PN coupler .........................................................................................152
5.4.3 ....... Configuration of hardware for fail-safe communication ........................................................153
5.5 .... Creating the safety program ...................................................................................................157
5.5.1 ....... Overview of the block list of the safety program ...................................................................157
5.5.2 ....... Variables ...............................................................................................................................159
5.5.3 ....... Structure of safety program ..................................................................................................160
5.5.4 ....... Integrating safety blocks in STEP 7 ......................................................................................162
5.5.4.1 ......... "ARG" block call ...............................................................................................................162
5.5.4.2 ......... "SK_xy" block calls...........................................................................................................163
5.5.4.3 ......... "NOT_HALT_ANTRIEBE" block call ................................................................................163
5.5.4.4 ......... "LAST_SK_xy" block calls ...............................................................................................164
5.5.4.5 ......... Creating an F-runtime group ............................................................................................165
5.6 .... Generating the safety program ...............................................................................................166
5.6.1 ....... Procedure for generating the safety program .......................................................................166
5.6.2 ....... Generating the safety program .............................................................................................166
5.7 .... Block update .............................................................................................................................167
6 . SiVArc (Siemens Visualization Architect) ....................................................... 168

6.1 .... Introduction ..............................................................................................................................168
6.1.1 ....... Required basic experience ...................................................................................................168
6.1.2 ....... Scope of this documentation .................................................................................................168
6.2 .... SiVArc Update Manager ..........................................................................................................169

Saved on 06.12.2012
Contents
6.3 .... Preparing the S7 project ..........................................................................................................173

6.3.1 ....... Report system errors.............................................................................................................173
6.3.2 ....... STEP 7 integration of the VASS body project ......................................................................173
6.4 .... Screen Generator .....................................................................................................................176
6.4.1 ....... Settings .................................................................................................................................179
6.4.2 ....... Project generation .................................................................................................................182
6.4.2.1 ......... Generating the import file for "Complete" import type .....................................................182
6.4.2.1.1 ........... "Complete import type" ...............................................................................................184
6.4.2.2 ......... Required preparations for "Delta" import type .................................................................185
6.4.2.3 ......... Generating the import file for "Delta" import type ............................................................195
6.4.2.3.1 ........... "Delta import type" ......................................................................................................197
6.4.3 ....... Generating messages ...........................................................................................................203
7 . WinCC flexible ................................................................................................... 204

7.1 .... Starting ......................................................................................................................................204
7.2 .... Post-processing in WinCC flexible.........................................................................................205
7.2.1 ....... Integrating a WinCC flexible project in STEP 7 ....................................................................205
7.2.1.1 ......... Integration steps from within WinCC flexible ...................................................................205
7.2.1.2 ......... Configuring the connection in STEP 7 .............................................................................207
7.2.1.3 ......... Renaming the SIMATIC HMI station ................................................................................209
7.2.1.4 ......... Selecting the corresponding S7 station under the "S7-HMI"connection..........................210
7.2.2 ....... Step sequencer display with ProAgent .................................................................................211
7.2.3 ....... Description and post-processing of operating screens .........................................................217
7.2.3.1 ......... Manual operating screens of the station, roller conveyor and buffering belt ...................219
7.2.3.2 ......... Tool screen of the station ("ST_110030_WZ_004") ........................................................226
7.2.3.3 ......... Detailed robot display with pertinent process devices ("Rob_110010R01_006") ...........228
7.2.3.4 ......... Basic screen for menu navigation ("Grundbild_010") ......................................................229
7.2.3.5 ......... System overview ("Anlagenübersicht_011") ....................................................................230
7.2.3.6 ......... Operating modes ("Betriebsarten_012") ..........................................................................232
7.2.3.7 ......... Preselections ("Vorwahlen_013") ....................................................................................233
7.2.3.8 ......... Robot overview screen ("Roboter_014_Layer1") ............................................................234
7.2.3.9 ......... Overview screen of robot process devices ("Rob-Prozessgeräte_015") .........................235
7.2.3.10 ....... Machine processes ("Maschinenprozesse_016") ............................................................236
7.2.3.11 ....... System completion reports ("GlobaleStati_017") .............................................................237
7.2.3.12 ....... Request screen for system operator and parts ("Werkerruf_018") ..................................238
7.2.3.13 ....... Statistics & number of units ("Statistik_020") ...................................................................239
7.2.3.14 ....... Clock time overview screen ("Taktzeiten_022") ..............................................................240
7.2.3.15 ....... PLC & bus info/diagnostics ("SPS+PN_030") ..................................................................241
7.2.3.16 ....... PNIO-100 station overview ("PNIO-100_Stationsübersicht") ..........................................243
7.2.3.17 ....... PROFINET overview ("PN-Übersicht_019") ....................................................................244

Saved on 06.12.2012
Contents
7.2.3.18 ....... PLC status value ("SPS_StatusValue") ...........................................................................246

7.2.3.19 ....... Step sequencer overview ("Schrittketten_031") ..............................................................247
7.2.3.20 ....... Interfaces ("PN/PN_Koppler_ARG2_101") ......................................................................248
7.2.3.21 ....... Screen of current messages ("Message display") ...........................................................249
7.2.3.22 ....... Message archive ("Meldearchiv_250") ............................................................................250
7.2.3.23 ....... Administration ("Administration") .....................................................................................251
7.2.3.24 ....... Screen for starting external applications ("Applikationen") ..............................................252
7.2.3.25 ....... Detailed screen of SEW drive with AMA binary setpoint value ("Detail_SEW_AMA_Bin")253
7.2.3.26 ....... Detailed screen of SEW drive with AMA variable setpoint value ("Detail_SEW_AMA_Var")254
7.2.3.27 ....... Detailed screen of SEW drive with Modulo ("Detail_SEW_Modulo") ..............................255
7.2.3.28 ....... Detailed screen of SEW drive with AMX_RB ("Detail_SEW_AMX_RB") ........................256
7.2.3.29 ....... Detailed screen of SEW drive with AMX_VR ("Detail_SEW_AMX_VR") ........................257
7.2.3.30 ....... Detailed screen for display of switching list ("Detail_SchaltlisteSchicht_105") ...............258
7.2.3.31 ....... Detailed screen for display of stylus stamping system ("Detail_Markator120050PR1") .259
7.2.3.32 ....... Detailed screen for display of measuring system ("Detail_Messen_Perceptron1_1M1")260
7.2.3.33 ....... Step sequencer display for manual operating screen ("Station_Ablaufsteuerung") ........261
7.2.3.34 ....... Configuration of user-defined pictures .............................................................................262
7.2.4 ....... Roles for post-processing for Delta imports (SiVArc Screen Generator) .............................263
7.2.4.1 ......... Overwritten pictures .........................................................................................................264
7.2.4.2 ......... Newly added pictures .......................................................................................................265
7.2.4.3 ......... Delta pictures ...................................................................................................................266
7.2.5 ....... Updating faceplates ..............................................................................................................267
7.2.6 ....... Generating the WinCC flexible runtime project .....................................................................270
7.3 .... GBA (large picture display) .....................................................................................................273
7.3.1 ....... Description for merging from several GBA projects ..............................................................275
8 . Multiple languages ............................................................................................ 283

8.1 .... STEP 7 .......................................................................................................................................284
8.1.1 ....... Language-neutral saving.......................................................................................................284
8.1.2 ....... Managing multilingual texts ...................................................................................................285
8.1.2.1 ......... Setting the language for the indicators ............................................................................285
8.1.2.2 ......... Preparing the symbol table in the S7 program ................................................................286
8.1.2.3 ......... Export of project texts ......................................................................................................287
8.1.2.3.1 ........... Preparing target language and text types for translation files / executing the export .287
8.1.2.3.2 ........... Selection of text types .................................................................................................288
8.1.2.3.3 ........... Providing the created text files from the export directory for translation ....................288
8.1.2.3.4 ........... Example of an Excel file with German source and target text ....................................289
8.1.2.4 ......... Import of translated project texts......................................................................................290
8.1.2.4.1 ........... Example of an Excel file with German source and English target text .......................290
8.1.2.4.2 ........... Opening the project to be edited .................................................................................290

Saved on 06.12.2012
Contents
8.1.2.4.3 ........... Filling out the "Import User Texts" dialog and executing the import ...........................291
8.1.2.4.4 ........... Completion report of the import ..................................................................................291
8.1.3 ....... Implementing the language management block in the S7 program .....................................292
8.1.3.1 ......... Executing FB 651 "LMsg" ................................................................................................292
8.1.3.1.1 ........... Input parameter...........................................................................................................293
8.1.3.1.2 ........... Output parameter ........................................................................................................293
8.1.3.1.3 ........... Input and output parameter ........................................................................................294
8.1.3.1.4 ........... Fault / Warning / Message diagnostics .......................................................................294
8.1.3.2 ......... Executing FB 650 "MeldeFB" ...........................................................................................296
8.1.3.2.1 ........... Block process image ...................................................................................................296
8.1.3.2.2 ........... Input parameter...........................................................................................................296
8.1.3.2.3 ........... Output parameter ........................................................................................................297
8.1.3.2.4 ........... Input and output parameter ........................................................................................297
8.1.4 ....... Multilingual S7 Graph step sequencer displays ....................................................................298
8.2 .... SiVArc ........................................................................................................................................302
8.2.1 ....... Provisioning the WinCC flexible project ................................................................................302
8.2.2 ....... Integrating a WinCC flexible project in STEP 7 ....................................................................302
8.2.3 ....... Activating the multilingual support ........................................................................................305
8.3 .... WinCC flexible ..........................................................................................................................306
8.3.1 ....... User dictionary in WinCC flexible ..........................................................................................306
8.3.1.1 ......... User dictionary .................................................................................................................306
8.3.1.1.1 ........... Opening the "User dictionary" editor ...........................................................................306
8.3.1.1.2 ........... Design of the "User dictionary" editor .........................................................................306
8.3.1.1.3 ........... Working area...............................................................................................................307
8.3.1.2 ......... Adding a term to a user dictionary ...................................................................................307
8.3.1.2.1 ........... Introduction .................................................................................................................307
8.3.1.2.2 ........... Requirements..............................................................................................................307
8.3.1.2.3 ........... Adding a new term ......................................................................................................307
8.3.1.2.4 ........... Alternative procedure ..................................................................................................307
8.3.1.2.5 ........... Result ..........................................................................................................................307
8.3.1.3 ......... Managing user dictionaries ..............................................................................................308
8.3.1.3.1 ........... Introduction .................................................................................................................308
8.3.1.3.2 ........... Renaming a user dictionary ........................................................................................308
8.3.1.3.3 ........... Integrating a user dictionary in a project .....................................................................308
8.3.1.3.4 ........... Removing a user dictionary from the project ..............................................................308
8.3.1.3.5 ........... Deleting a user dictionary ...........................................................................................308
8.3.1.3.6 ........... Copying a user dictionary ...........................................................................................309
8.3.1.3.7 ........... Uninstalling WinCC flexible .........................................................................................309
8.3.2 ....... Managing the project texts ....................................................................................................310
8.3.2.1 ......... Opening the project text overview....................................................................................310

Saved on 06.12.2012
Contents
8.3.2.2 ......... Automatically translating missing texts ............................................................................310

8.3.3 ....... Project-specific texts .............................................................................................................311
8.3.3.1 ......... Providing the created text files from the export directory for translation..........................312
8.3.3.2 ......... Example of an Excel file with German source and target text .........................................313
8.3.3.3 ......... Example of an Excel file with German source and English target text ............................313
8.3.3.4 ......... Importing the translated Excel files in the WinCC flexible project ...................................314
8.3.4 ....... Step sequencer display with ProAgent .................................................................................314
8.3.5 ....... Subsequent creation of a multilingual project via Delta import .............................................315
9 . Commissioning at the system .......................................................................... 326

9.1 .... PC677 B .....................................................................................................................................326
9.1.1 ....... Setting up the PC677 ............................................................................................................326
9.1.1.1 ......... Calibrating the touchscreen .............................................................................................327
9.1.1.2 ......... Assigning the computer name .........................................................................................327
9.1.1.3 ......... Assigning the IP address .................................................................................................328
9.1.2 ....... Transferring configuration data to the target system ............................................................330
9.1.2.1 ......... Data storage.....................................................................................................................330
9.1.2.2 ......... S7 project .........................................................................................................................330
9.1.2.2.1 ........... Complete download of the safety program .................................................................330
9.1.2.2.2 ........... Loading changes of the safety program in the "Safety Program" dialog ....................331
9.1.2.2.3 ........... Download after changing "HW Config" .......................................................................332
9.1.2.2.4 ........... Complete download of the sequence programs .........................................................332
9.1.3 ....... WinCC flexible .......................................................................................................................332
9.1.3.1 ......... Transfer of the project to the HMI device .........................................................................332
9.1.4 ....... Configuring RemoteOperate .................................................................................................336
9.1.4.1 ......... Configuring the server ......................................................................................................336
9.1.4.1.1 ........... Adding a client ............................................................................................................337
9.2 .... MP377 / MP277RO ....................................................................................................................338
9.2.1 ....... Configuring the MPs ..............................................................................................................338
9.2.1.1 ......... Calibrating the touchscreen .............................................................................................339
9.2.1.2 ......... Setting the computer name of the HMI device .................................................................339
9.2.1.3 ......... Assigning the IP address .................................................................................................340
9.2.2 ....... Configuring the RemoteOperate client ..................................................................................341
9.2.2.1 ......... Creating/editing the server selection list ..........................................................................341
9.2.2.2 ......... Creating a new server ......................................................................................................342
9.2.2.3 ......... Changing the properties of a server.................................................................................343
9.2.2.4 ......... Removing a server ...........................................................................................................343
9.2.2.5 ......... Connecting a client ..........................................................................................................344
List of Figures ........................................................................................................ 349
List of Tables ......................................................................................................... 360

Saved on 06.12.2012
Contents
List of Abbreviations / Glossary........................................................................... 362

Appendix ................................................................................................................ 366
A: PROFINET Device Names...............................................................................................................366
B: Hardware Configuration for PROFINET Nodes ...............................................................................368
C: List for Labeling Rules .....................................................................................................................377
distributed safety ..................................................................................................................................384

Saved on 06.12.2012
Introduction and Objectives
1 Introduction and Objectives
1.1 Introduction
1.1.1 Objective of this documentation
This documentation, "VASS Standard Configuration Guideline", serves system suppliers of the
Volkswagen Group as specification and guidelines for implementing their project-specific tasks.
The documentation describes the demands from the perspective of the Volkswagen Group on an
automation system, the software and the procedure for the configuration of SIMATIC WinCC flexible.
The relation between demands and implementation is explained by means of practical examples.
1.1.2 Basics of the objective
The documentation "VASS Standard Configuration Guideline" is intended to establish the basics of a
principal objective for the project.
 Ensuring a high-quality overall result
 Ensuring a high availability and flexibility of the overall system
 Minimizing investment, operating and required expansion costs
 Implementing optimal work contents and working conditions for the user group
 Modularizing the complex overall control system into manageable exchangeable units
 Simplifying and standardizing the interfaces between individual modules
Note
Detailed items that were not included in the documentation "VASS Standard Configuration
Guideline" or in additional standard specifications must be arranged with the contact person in
charge of the Volkswagen Group.
For this purpose, the project partner should prepare suggestions to be submitted to the contact
person in charge of the Volkswagen Group based on the existing documentation.
1.1.3 Target groups
The manual is intended for all system operators, project managers and project engineers,
maintenance and service personnel, who have to create or edit projects in the context of the VASS
standard. It provides solutions for implementing automation projects using SIMATIC STEP 7 and
WinCC flexible.

Saved on 06.12.2012
1.1.4 Follow-up versions
If changes and additions of the present documentation should become necessary in the context of the
document maintenance by the Volkswagen Group during the project execution, they will be
incorporated in the corresponding follow-up versions of the document.
Notice
The documentation "VASS Standard Configuration Guideline" does not release the system supplier
from his responsibility to ensure that the version of systems and documentation to be supplied is
professional and meets the local regulations.
1.2 Software tools for the configuration

Note
When configuring the software tools, the program versions released in the projects in each case
must be observed.
1.2.1 Software tools for the configuration with Windows XP
The software tools listed below with the specified versions are absolutely necessary for the
configuration with Windows XP according to VASS standard:
Program Version Function Uses
STEP 7 V5.5 + HF3 Configuration Programming device,
S7 controller control panel
S7 GRAPH V5.3 + SP6 Configuration of step Programming device,
sequencer control control panel
S7 SCL V5.3 + SP5 Programming of Programming device,
function blocks control panel
S7 Distributed V5.4 + SP5 Configuration of safety wiring Programming device,
Safety control panel
WinCC flexible 2008 Advanced Configuration of control Programming device,
+ SP2 / Update 3 panels control panel
WinCC flexible 2008 Advanced Modified file for use of the 3- Programming device,
HmiES.exe GB work memory by control panel
WinCC flexible
WinCC flexible 2009.03.17WCF2008. Enabling the import interface Programming device,
Activate Activate for WinCC flexible control panel
WinCC flexible 2008 RUNTIME 4096 Runtime environment for Programming device,
POWERTAGS WinCC flexible control panel
WinCC flexible / For WinCC flexible Use for step sequencer Programming device,
ProAgent runtime diagnostics in WinCC flexible control panel
Remote Operate V2.1.5.x Coupling of auxiliary control Control panel
Server units
SiVArc V2.0.77 Generating Programming device,
user interfaces control panel
Tab. 1.1 Software tools for Windows XP

Saved on 06.12.2012
1.2.2 Software tools for the configuration with Windows 7 / 64 bit
The software tools listed below with the specified versions are absolutely necessary for the
configuration with Windows 7 / 64 bit according to VASS standard:
Program Version Function Uses
STEP 7 V5.5 + SP2 + HF1 Configuration Programming
S7 controller device, control panel
S7 GRAPH V5.3 + SP7 Configuration of step Programming
sequencer control device, control panel
S7 SCL V5.3 + SP6 Programming of function Programming
blocks device, control panel
S7 Distributed V5.4 + SP5 + Configuration of safety wiring Programming
Safety Update 1 device, control panel
WinCC flexible 2008 Advanced + SP3 + Configuration of control Programming
Update 2 panels device, control panel
WinCC flexible 2008 Advanced HmiES.exe Modified file for use of the 3- Programming
GB work memory by device, control panel
WinCC flexible
Common.Utils.Resources.dll
HmiES.exe.config
WinCC flexible 2009.03.17WCF2008. Enabling the import interface Programming
Activate Activate for WinCC flexible device, control panel
WinCC flexible 2008 RUNTIME 4096 Runtime environment for Programming
POWERTAGS WinCC flexible device, control panel
WinCC flexible / For WinCC flexible runtime Use for step sequencer Programming
ProAgent diagnostics in WinCC flexible device, control panel
Remote Operate V3.1.x Coupling of auxiliary control Control panel
Server units
SiVArc V2.0.77 and higher Generating Programming
user interfaces device, control panel
Tab. 1.2 Software-Tools for Windows 7 / 64 bit
The VASS standard software package was created on this basis. If newer versions should be in
circulation, the contact person in charge of the Volkswagen Group should be notified prior to the
configuration with these versions.
Version numbers of the software tools that are used in a new configuration are defined in the
corresponding project workshop in each case.
Note
If older software versions are used, the functionality of the control software is no longer
guaranteed.

Saved on 06.12.2012
System Configuration
2 System Configuration
2.1 Hardware requirements for programming environment

Editing projects for the VASS standard requires a programming device or a PC with the following
minimum requirements concerning processor capability, RAM main memory and graphics.
Operating system with minimum requirements for:
Processor RAM Graphic
MS Windows XP Professional *) 2 GHz 4 GB XGA 1024x768 / 16-bit color depth
MS Windows Vista Business *) 2 GHz 4 GB XGA 1024x768 / 16-bit color depth
MS Windows Vista Ultimate *) 2 GHz 4 GB XGA 1024x768 / 16-bit color depth
MS Windows 7 Ultimate / 64 bit 2 GHz 6 GB XGA 1024x768 / 16-bit color depth
*) To be used only as 32-bit version
Tab. 2.1 Hardware requirements
The use of a PC also requires an external prommer for SIMATIC memory cards/MMC if you intend to
save your application programs in EPROMs on these media and a SIMATIC NET connection if you
want to use online functions for the automation system with your PC.
Configuring the "3-GB switch function" for Microsoft Windows XP

To be able to generate the runtime of WinCC flexible projects, it is necessary for large projects that the
application is given sufficient working memory.
In this case, the "3-GB switch function" should be configured on the system.

Additional information about this topic is available directly from the Microsoft support pages on the
Internet.

Saved on 06.12.2012
2.2 Software installation

2.2.1 SIMATIC STEP 7 Professional

Observe the instructions and notes in the "Readme.rtf" file.
It is located in the main menu (root directory) of the installation CD for SIMATIC STEP 7.
User authorizations
The following should be observed concerning the user authorizations for STEP 7 Professional Edition
2004 / SR2 and higher:
In order to work with STEP 7 Professional under MS Windows, you must have logged in at least at the
user level (no guest login). You need administrator rights for the installation of the STEP 7
Professional software and for configuring modules using the "Set PG/PC Interface" application. Main
user rights are required for the use of S7 GRAPH.
2.2.1.1 Installing the software
No special points need to be observed during the software installation for STEP 7 Professional 2010.
Before starting the setup, exit all applications (e.g. MS Word, etc.) and close the "Control Panel"
window since you have to restart MS Windows after completing the installation of STEP 7 Professional
so that all system variables can be completely registered.
Insert the STEP 7 Professional DVD in the drive. The installation of STEP 7 Professional is done via a
user-guided setup, which is started by calling up MS Windows Explorer and double-clicking on the
"Setup.exe" program of the STEP 7 Professional DVD.
In the component selection box, select all software components listed for the installation.
The selected components are subsequently installed, including the entries in the MS Windows files.

Saved on 06.12.2012
2.2.2 S7 Distributed Safety
Note
"S7 Distributed Safety Programming" is part of the "S7 Distributed Safety" option package and is
installed as part of the installation of "S7 Distributed Safety".
User authorizations
 The installation of the software is possible only with administrator rights.
 In order to work with "S7 Distributed Safety Programming", you must have logged in at least
at the user level (no guest login).
F-block libraries
 During the installation, an existing "Distributed Safety (V1)" F-library on the PG/PC is
replaced with the "Distributed Safety (V1)" F-library installed by "S7 Distributed Safety, V5.4 /
SP5".
2.2.2.1 Installing the software
Before starting the installation, exit all applications and close the "Control Panel" window. Insert the
CD with the "S7 Distributed Safety" option package in the drive. The installation of the software is
done via a user-guided setup which is started either automatically with the Autostart function or via
Windows Explorer by double-clicking on the "SETUP" program located on the "S7 Distributed Safety"
software CD-ROM. The program is installed under the installation path of STEP 7 and cannot be
changed.

Saved on 06.12.2012
2.2.3 WinCC flexible
2.2.3.1 Software installation for WinCC flexible 2008 Advanced SP2 / SP3
2.2.3.1.1 WinCC flexible 2008 Advanced with SP2 / SP3
For the installation of WinCC flexible, it must be observed that you do not select the suggested
"Complete Installation", but the "Custom Installation" (due to the required "ProAgent" option).
The following selection of the software components should be applied:
SIMATIC WinCC flexible 2008 SP2 / SP3

 Custom installation (due
to "ProAgent")
 Support for "Save as
Version 2007"
 Runtime/Simulation
License Management
 License Manager
Utilities
 ProSave
Fig. 2.1 Selecting the software

components
"ProAgent" must be selected

manually during the installation.
Fig. 2.2 Selecting ProAgent

Saved on 06.12.2012
2.2.3.1.2 WinCC flexible 2008 Advanced with SP2
"Update3" is a separate package which is provided on a project basis and must be installed in addition
to "WinCC flexible 2008 Advanced with SP2".
Fig. 2.3 WinCC flexible 2008 Advanced with SP2 / Update 3
2.2.3.1.3 WinCC flexible 2008 Activate
This add-on package is required to be able to use the auto-import function with the SiVArc Screen
Generator in conjunction with WinCC flexible.
To install it, start the "Activate.bat" file.

Observe the instructions and notes in the "WCFImportdeDE.pdf" file.
It is located in the ZIP file of the "Activate package".

Saved on 06.12.2012
2.2.3.1.4 Modification of WinCC flexible system with specific data
In order for the larger working memory provided by the "3 GB Switch" function to be made available for
32-bit systems or generally for 64-bit systems to be used by WinCC flexible, especially modified files
are required which are distributed by Volkswagen.
Simatic WinCC flexible 2008 Advanced SP2 / Update 3:
"HmiES.exe"
That means, the "HmiES.exe" file created during the installation in the installation directory of
WinCC flexible "Siemens\Simatic WinCC flexible\WinCC flexible 2008" must be replaced with the
modified "HmiES.exe" file.
Simatic WinCC flexible 2008 Advanced SP3 / Update 2:

"HmiES.exe", "Common.Utils.Resources.dll" and "HmiES.exe.config"
That means the files "HmiES.exe", "Common.Utils.Resources.dll" and "HmiES.exe.config" created
during the installation in the installation directory of WinCC flexible "Siemens\Simatic WinCC
flexible\WinCC flexible 2008" must be replaced with the modified files "HmiES.exe",
"Common.Utils.Resources.dll" and "HmiES.exe.config".
Note
This "HmiES.exe" file is available in two versions, one for SP2 / Update 3 and one for
SP3 / Update 2.
This avoids storage problems during the import of very large projects.
Processing of "boot.ini" only for 32-bit XP systems

A corresponding addition must be entered in the "boot.ini" file.
But it should be checked first whether the graphics card can manage it.
Suppleme
nt
Fig. 2.4 3-GB switch for 32-bit XP system

Saved on 06.12.2012
2.2.3.1.5 16-K variable
Under Windows, the "WinCC flexible Add-on" must be installed.
Note
This "WinCC flexible Add-on" is available in two versions, one for the SP2 application and one for
the SP3 application!
Fig. 2.5 Installation of "WinCC flexible Add-on"
Open body project
In the "Device
settings", open the
"Device settings" tab Open
Select "HMI device

type"
Fig. 2.6 Selection of HMI device type

Saved on 06.12.2012
Make the selection before integrating in STEP 7, but do not save the setting, otherwise the body
project will be changed.
Afterwards, integrate in the STEP 7 project and save when closing.
Fig. 2.7 Changing the HMI device type
Note
If a project was generated with 8K integrated body project and the integration fails because the
number of variables is too low, a new body project with changed device settings must be
integrated.
Afterwards, it is not possible to switch from 8K to 16K.
2.2.3.1.6 Setup of "SIMATIC WinCC flexible – Start center"
Autostart must be disabled on the taskbar in the "SIMATIC WinCC flexible - Start center".
Fig. 2.8 SIMATIC WinCC flexible - Start center

Saved on 06.12.2012
2.2.4 SiVArc Screen Generator
2.2.4.1 Installation
Check under "Start  Control Panel  Software (on the "Add and Remove Programs" tab)",
whether the "Microsoft.NET Framework 3.5" file exists. If not, the "dotNetFx35setup.exe" file must be
executed.
Fig. 2.9 Executing the "dotNetFx35setup.exe" setup file
Executing the "setup.exe" file for VASS

The "setup.exe" file checks whether all required components for SiVArc (Siemens Visualization
Architect) are present. If not, they are automatically installed.
Fig. 2.10 Executing "SiVArc.msi" for VASS

Saved on 06.12.2012
Double-clicking on the "setup.exe" file opens the setup start page of SiVArc.
Fig. 2.11 Installation of SiVArc setup for VASS

Saved on 06.12.2012
The destination folder for the

installation must be specified
here.
In English operating systems, enter
"C:\Program Files\Siemens\
SiVArc\".
Confirm with "Next".
Fig. 2.12 SiVArc setup destination folder
Three additional windows open next:

 "Ready to install SiVArc",
 "Installing SiVArc" (progress bar),
 "SiVArc Setup is completed"
in which certain buttons (e.g. "Install" or "Finish") must be clicked on to start or complete the
installation of SiVArc.
After completing the installation, the desktop features the icons of "SiVArc Screen Generator" and
"SiVArc Update Manager".
Fig. 2.13 SiVArc desktop icons

Saved on 06.12.2012
2.3 System settings for STEP 7

2.3.1 Settings for STEP 7
2.3.1.1 Settings of LAD, FBD, STL editor
To achieve a uniform appearance of different programs and an optimal utilization of the screen or the
printout, the settings of the LAD, FBD, STL editor should be accepted as shown.
The following subitems on the "General" tab should have a check mark:
Additional Options
 "Save window arrangement on exit"
 "Set network title automatically"
Program status
 "Control at contact"
 "Terminate ONLINE connection after program
status"
 Delay time "5" (seconds)
Additional information is available by pressing the Help

button.
Fig. 2.14 "General" settings
The following subitems on the "View" tab should have a check mark:
View after Block Open

 "Symbolic representation"
 "Automatic symbol selection (for LAD/FBD)"
 "Block/network comments"
 "Address identification"
 "Permanently forced addresses"
 "Process diagnostic addresses"
 With background color "GREEN"
 Not fail-safe addresses "RED"

button.
Fig. 2.15 "View" settings

Saved on 06.12.2012
On the "LAD/FBD" tab, the following entries should be made or subitems should have a check mark:
Layout
 "DIN A4 Portrait"
Address Field Width
 "13"
Element
 Representation "2-dimensional"
Line/Color
 Reference "Status fulfilled"
 Line weight "Medium"
 Color "GREEN"
Place a check mark at"Type check of addresses" and
"Display comments for the interface variables".

button.
Fig. 2.16 "LAD/FBD" settings
The following subitems on the "Block" tab should have a check mark:
With the Creation of a Block

 "Generate reference data"
Create Logic Blocks
 Language: "LAD"
 Disable "Function blocks with multiple instance
capability"

button.
Fig. 2.17 "Block" settings

Saved on 06.12.2012
2.3.1.2 Settings of address priority in STEP 7 programming
Right-clicking on "Blocks" and clicking on

"Object properties“ opens the "Properties -
Block folder offline" window.
Fig. 2.18 Opening the "Properties - Block folder

offline" window
On the "Address priority" tab,

the field "For all accesses
(I,Q,M,T,C and DB)" must be
selected.
Additional information is
available by pressing the Help
button.
Fig. 2.19 Setting the address priority
Notice
This setting is very important.
Otherwise, the generator does not generate the robot text lists.

Saved on 06.12.2012
Notice
Only one S7 program is allowed!
If a project contains more than one S7 program, the generator aborts with this error message.
Fig. 2.20 Error message
Notice
Before the generation, verify that only one S7 program exists!
Fig. 2.21 Verifying before generating

Saved on 06.12.2012
2.3.1.3 Settings of the columns
Settings for the columns are made under the menu item "Options  Setting  Columns".
The "Date of change" column should be moved to 7th position.
The settings must be made for the two windows "User projects" and "Libraries".
Example for the "User projects" window:
Fig. 2.22 Settings of the columns
Note
When sorting by the date of change, it can immediately be seen which blocks were affected by the
last change.
Only these blocks have to be loaded in the CPU (saving time).

Saved on 06.12.2012
2.3.1.4 S7 GRAPH settings
S7 GRAPH as an option package of STEP 7 is completely integrated in the SIMATIC Manager. As a

result, S7 GRAPH can access data of the SIMATIC Manager and vice versa.
The following settings are required:
 Address priority of STEP 7 = symbolically leading for all accesses
 HMI integration
S7 GRAPH distinguishes between:

 Application settings
 Block settings
Fig. 2.23 Differentiating settings
2.3.1.4.1 Application settings
Application settings are made under the menu item "Options  Application Settings" and form a
type of template for newly created blocks (step sequencers).
Notice
Settings that are changed here have no effect on already existing step sequencer blocks.

Saved on 06.12.2012
Settings that apply to the general representation and to views as well as the behavior while saving are
made on the "General" tab.
Apply the settings as shown in the dialog.
Conditions in new blocks

 LAD (display / program)
For saving
 Also handle instance DB
 Create reference data
 Create diagnostics data
 Use name extension for display systems
Addresses in sources
 Symbolic
Additional information is available by pressing the

Help button.
Fig. 2.24 "General" application settings
Color assignment and display content are set on the

"Editor" tab.
Do not place a check mark next to "Only display first

line"!

Help button.
Fig. 2.25 "Editor" application settings
Notice
Here, it is important to place no check mark in the "Conditions and Actions" area at "Only display
first line".

Saved on 06.12.2012
The settings on the "Compile / Save" tab are important for the behavior of the step sequencer. They
have serious effects of the runtime characteristics of the step sequencer and its memory demand.
Use the following settings as default for new blocks:
FB Parameter
 "Standard"
Executability
 "Independently executable"
(minimal cycle time load approx. 30 % less)
Warnings
 "None"
Interface description
 "Individual structures"
 Enable "Load In AS"
(due to decompilability)
Sequencer properties
 No "Criteria analysis data in DB"
( not allowed)
 No "Skip steps"
( Minimal cycle time load  can only
be determined individually)
 Synchronization (V4.0 or higher)
 Secured switching behavior (V5.1 or
higher)
only one step can be activated for each
simultaneous branch
this means, structure is taken into
account upon step selection

Help button.
Fig. 2.26 "Compile / Save" application settings

Saved on 06.12.2012
The following settings must be made on the "Messages" tab:
Message handling
Select "Report with Alarm_SQ / Alarm_S" (SFC17 /
SFC18) and enable both subdirectories.
Creating messages
"Alarm message" must be selected for "Interlock"
and "S7GRAPH Interlock Error" must be entered as
text.
"Alarm message" must also be selected for
"Supervision" and "S7GRAPH Supervision Fault"
must be entered as text.

Help button.
Fig. 2.27 "Messages" application settings

Saved on 06.12.2012
2.3.1.4.2 Block settings
Block settings are set under the menu item "Options  Block Settings" and, in contrast to the
application settings, only change the behavior of the currently open block (of the currently open step
sequencer). They are not applied as defaults.
On the "Compile / Save" tab, you perform the same settings as those for the application settings of the
same tab.
FB Parameter
 User-defined (V5.0 or higher)
Executability
 "Independently executable"
(minimal cycle time load approx. 30 % less)
Warnings
 "None"
Interface description
 "Individual structures"
 Enable "Load In AS"
(due to decompilability)
Sequencer properties
 No "Criteria analysis data in DB"
( not allowed)
 No "Skip steps"
( Minimal cycle time load
 can only be determined individually)
 Synchronization (V4.0 or higher)
 Secured switching behavior (V5.1 or
higher)
only one step can be activated for
each simultaneous branch
this means, structure is taken into
account upon step selection.

button.
Fig. 2.28 "Compile / Save" block settings
Note
Observe the check mark "Apply as default for new blocks".
It applies any changes made as default for new blocks.

Saved on 06.12.2012
The "Messages" tab looks different than the one in the application settings (Fig. 2.27 "Messages
application settings").
Message handling
Select "Report with Alarm_SQ / Alarm_S" (SFC17 /
SFC18) and enable both subdirectories.

Help button.
Fig. 2.29 "Messages" block settings
Note
Observe the check mark "Apply as default for new blocks".
It applies any changes made as default for new blocks.

Saved on 06.12.2012
2.3.1.5 Settings in S7 SCL
The following subitems must feature a check mark on the "Create Blocks" tab:
Overwrite blocks
Already existing blocks in the "Blocks" folder of an S7 program are overwritten here if the compiling
process results in blocks with the same designation. In the same way, blocks with the same name that
already exist in the target system, will be overwritten during the loading process. If this option is not
selected, you have to confirm a message before the block is overwritten.
Display warnings
This option defines whether warnings will be
displayed in addition to faults after a compilation run.
Errors before Warnings
This option defines whether faults are listed before
warnings in the message window.
Create reference data
Selecting this option automatically generates
reference data when a block is created. However, the
menu command "Options  Reference Data"
provides the opportunity to create or update the
reference data at a later time.

Help button.
Fig. 2.30 S7 SCL "Create Blocks"

Saved on 06.12.2012
The following settings must be made on the "Format" tab:

To show a differentiation between old and new values in debug mode, the following color settings are
made here.
In the debug window, select the color "GREEN" for

"Value (new)".
Fig. 2.31 Value (new)
In the debug window, select the color "ORANGE" for

"Value (old)".
Fig. 2.32 Value (old)

Saved on 06.12.2012
The following subitems on the "Compiler" tab should have a check mark:
Create Object Code
With this option you define whether you want to create an executable code or not. The compiling
process without this option is used only as a syntax check.
Optimize Object Code
If selected, this option optimizes the generated blocks with respect to their memory demand and
runtime in AS. It is recommended to always select this option since the optimization does not create
any disadvantages that affect the functionality of the block.
Create debug information
This option enables you to execute a test run with the debugger after the program has been compiled
and loaded into the CPU. However, the memory demand of the program and the runtimes in the AS
increase with this option. If this option is enabled, the reference data required for testing are
automatically generated.
Allow nested comments
Select this option if you want to nest several
comments into each other in your S7 SCL source.
Maximum string length
Here you can reduce the default length of the
STRING data type. The basic setting is
254 characters. The setting applies only to the
return values of an FC as well as to output and
through-type parameters. Note that the setting
applies to all STRING variables in the source. The
set value may not be less than the STRING variables
used in the program.

Help button.
Fig. 2.33 S7-SCL "Compiler"

Saved on 06.12.2012
2.4 SiVArc Screen Generator system settings

See also Chapter 6.4.1 "Settings".
2.5 System settings for WinCC flexible

See also Chapter 7 "WinCC flexible".

Saved on 06.12.2012
Data storage
3 Data storage
The data storage on the destination device is located on drive "D:\".
For this reason, it is absolutely necessary to set up an identical data storage on the configuration
device as shown in Fig. 3.1 "Project data - Folder structure" since all the settings and mechanisms are
adjusted to it.
Note
Fig. 3.1 Project data - Folder structure

Saved on 06.12.2012
Data storage
The following notes apply only to the Windows 7 installation:

On the drive "Data (D:)" in the "Data (D:) Properties" window under "Security  Users
(SIMATIC\Users)", the permissions for the users must be set to full access.
Fig. 3.2 Defining permissions for users

Saved on 06.12.2012
Data storage
When using the Windows language setting in German/English, the list separator must be set to ";"
under
"Control Panel  Region and Languages  Formats  Additional settings  Customize
Format  Numbers (see also Ch. 8.1 "Multiple languages – STEP 7" because of the format
conversion "xls-csv").
Fig. 3.3 Defining the list separator ";"

Saved on 06.12.2012
Data storage
3.1 Description of the folders in the directory structure

3.1.1 01_Werk
The "01_Werk" directory contains general documents that are important to the system builder and
operator (e.g. car body codes, etc.). These documents will be provided by the Volkswagen Group.
3.1.2 02_S7
3.1.2.1 01_Bibliothek
The current VASS library must be deposited here.
3.1.2.2 02_Projekte
Only the currently valid S7 project must be deposited here.
3.1.2.3 03_Archive
Archived predecessor versions are deposited here.
3.1.2.4 04_Gerätekatalog
The current VASS device catalog containing the device description files (GSD) that are relevant to the
current project is stored here.
3.1.2.5 05_Referenzen
Comparison projects are temporarily stored here during the commissioning phase.
They must be deleted prior to handing over the system to the operator.

Saved on 06.12.2012
Data storage
3.1.3 03_SiVArc
The SiVArc Screen Generator requires certain guideline files, the so-called meta-model, for generating
the visualization.
It is provided for the project and automatically placed in the folders described below by the Update
Manager.
For more information about the operating principle of the SiVArc system, see also Chapter 6 "SiVArc".
3.1.3.1 01_Metamodell
The meta-model contains all the guideline files required for the automatic generation of the system
visualization. These files exist as XML files and are stored in the subfolders.
 Configuration file:
The Meta-model main folder also contains the configuration file for operating the SiVArc
Screen Generator.
 Block descriptions:
Every function block features a description file that describes the connection between
STEP 7 block and WinCC flexible faceplate and that contains the pertinent message texts.
 Picture descriptions:
The picture description files contain the information for the picture design.
 Device descriptions:
A separate device description exists for every device type to be configured with
WinCC flexible. It contains all the required information for the description of the device.
3.1.3.2 02_Textlisten
Text lists required during the course of the project are stored here in CSV or XLS format.
3.1.3.3 03_Sprachdatenbank
It contains all the texts available in multiple languages that are relevant to the project.
The language database is currently not being distributed.
3.1.3.4 04_Registry_Onlinehilfen
This folder contains a file that needs to be started so that the entries for using the S7 online help for
the project-specific function blocks can be made to the registry.

Saved on 06.12.2012
Data storage
3.1.4 04_WinCC flexible
3.1.4.1 01_Vorlagen
The project-specific WinCC flexible body project is stored under templates.
3.1.4.2 02_Symbolbibliothek
This directory contains the project-specific faceplate library.
3.1.4.3 03_Runtime
The generated runtime project must be stored in this folder.

It must be ensured that it contains only the current project.
3.1.4.4 04_UserDictionary
The UserDictionary must be stored in this folder.

It must be ensured that it contains only the current UserDictionary.
3.1.5 05_Remote_Operate
The configuration data for the Remote_Operate connections are stored in this folder.
3.1.6 06_Dokumentation
All documentation, such as this configuration guideline, is stored here.
3.1.7 07_ZAÜ
CSM stands for "Central System Monitoring".

The message list for the CSM system that is automatically generated by the Screen Generator is
stored in this directory.
This file must be forwarded to the CSM control center.

Saved on 06.12.2012
Data storage
3.2 Block help

In order to provide the corresponding online help during the configuration of the S7 logic for the
project-specific function blocks by means of function key F1, a corresponding directory must be
created.
3.2.1 Block help for Windows XP
A corresponding directory with the structure "\VASS_Onlinehilfen\VASS_V04" must be created in

the "S7LIBS" folder in the installation directory of STEP 7.
Note
This function is not available if the directory is created elsewhere.
The project-specific help files "FB_number_FB_name_a.hlp" (e.g. FB_100_FB_BA_a.hlp) must be

stored in this directory. "_a" in the file name represents the German language.
Fig. 3.4 S7 online help
Notice
To ensure the function of the online help, the supplied "VASS_Help.reg" registration file must be
executed.

Saved on 06.12.2012
Data storage
3.2.2 Block help for Windows 7 / 64 bit
3.2.2.1 Preparatory measures
Installation of the STEP 7 online help ("MSHelp" for x64).
Fig. 3.5 Installation of STEP 7 online help
The installation of "MSHelp" requires activating the "Windows Update" service. This is done under:
"Computer Management  Service and Applications  Services 
Windows Update  Manual Start".
Fig. 3.6 Activating "Windows Update"

Saved on 06.12.2012
Data storage
The "Windows Update" service has now been started and is active.
Fig. 3.7 "Windows Update" has been started and is active
Select the following file on the DVD:

"S7 Professional 2010 SR2  CD2  MSHelp  x64  Windows6.1 KB917607-x64".
The installation is started with a click of the mouse.
Fig. 3.8 Installation

Saved on 06.12.2012
Data storage
Next, confirm the execution of "Update for Windows (KB917607)".
Fig. 3.9 Confirming the "Update for Windows (KB917607)"
Next, confirm the license requirements of "Update for Windows (KB917607)".
Fig. 3.10 Confirming the license requirements for "Update for Windows (KB917607)"

Saved on 06.12.2012
Data storage
After the "MSHelp" installation, the "Windows Update" service must be deactivated. This is done
under: "Computer Management  Service and Applications  Services 
Windows Update  Manual Stop"
Fig. 3.11 Deactivating "Windows Update"

Saved on 06.12.2012
Data storage
3.2.2.2 Setting up a directory and registering
A corresponding directory with the structure "\VASS_Onlinehilfen\VASS_V05" must be created in

the "S7LIBS" folder in the installation directory of STEP 7.
Note
This function is not available if the directory is created elsewhere.
The project-specific help files "FB_number_FB_name_de.hlp" (e.g. FB_100_FB_BA_de.hlp) must be

stored in this directory. "_de" in the file name represents the German language.
Fig. 3.12 Creating the folders "VASS_Onlinehilfen" and "VASS_V05"
Notice
To ensure the function of the online help, the supplied "VASS_V05_HELP_W7_64bit_Vx.x.reg"
registration file must be executed.

Saved on 06.12.2012
Data storage
If Block online help in German is used (file endings "_de"), then "Options  Customize 
Language" in the SIMATIC Manager must be set to "German". Confirm the entry with a click of the
mouse.
Fig. 3.13 Setting for block online help in German
If Block online help in English is used (file endings "_en"), then "Options  Customize 
Language" in the SIMATIC Manager must be set to "English". Confirm the entry with a click of the
mouse.
Fig. 3.14 Setting for block online help in English

Saved on 06.12.2012
Project creation
4 Project creation
Principal procedure for project creation:
Using S7 base project as basis and adjusting project names
Install hardware configuration according to EPlan
Importing symbol table from EPlan
Copying all sources and blocks from the library to the project
Compiling required sources
Creating DB100 to DB1xx for work group and protective circuits filling them accordingly
Supplementing symbol table with project-specific bit memories, times, counters
Creating structure FCs and filling them Creating and filling F-FBs accordingly
according to the system
Programming the FB step sequencers with

transitions and interlocks
Creating F-run-time group
Checking block consistency
Deleting unused blocks Generating the safety program
Finished S7 project
Fig. 4.1 Principal procedure for project creation

Saved on 06.12.2012
Project creation
Extensive documentation is provided for creating the project.
S7 function block library:

In the library, elements are made available according to different categories:
 "Base symbols" folder: Contains all the symbols required in every project
 "Objects with sources" folder: Contains all the current module FBs as SCL source file
for the common technologies used in the project
 "Objects without sources" folder: Contains blocks and data structures that are not
provided via sources
Blocks that are not available in the S7 project library must be created by the system supplier in
consultation with the responsible electrical engineering.
S7 function block library:

Required safety blocks are provided in the "S7-Safe library".
S7 base project:
The S7 base project forms the basis for creating a system-specific project.
It features all the S7-specific basic settings and an integrated WinCC flexible body project so that all
the essential communication settings are preset here.
The following must be adjusted:
 Expanding the symbol table:
System-specific I/Os are generated from the EPLAN of the system and imported into the
symbol table. It already contains fundamental symbolics and comments.
 Reserving bit memory address areas:
In the symbol table, the bit memory address area from M 0.0 to M 100.0 must be reserved
for the VASS system function, and the bit memory address area starting at M 4000.0 must
be assigned to the safety area. Any additional required bit memories must be created
between these areas.
 Adjusting the OB:
The system OBs "OB82", "OB83", "OB85", "OB86" are already integrated in the sample
project and must be used. The STEP 7 standard OBs under the same name do not contain
all the VASS functions. OB1 is present as template and must be expanded by the user with
the calls of the structure FCs.
 Creating the module components:
The SCL source files in the module FBs must be compiled for all the required system
functions.
 Creating the sequence programming:
The call structure must be created according to the sequence of the system or the defined
sequence plan of the mechanical engineer.
 Maintaining the PLC project:
All excess blocks must be deleted. Use the reference data to check whether any double
assignments exist.
Note
All sources must remain in the "Sources" folder and may not be deleted at all.

Saved on 06.12.2012
Project creation
Device catalog:
The device catalog can be integrated in the STEP 7 hardware and contains the project-relevant device
descriptions, at least as far as they are known to date.
VWGKV04_0
1
VWGKV04_01.da
t
Fig. 4.2 Integrating the device catalog

Saved on 06.12.2012
Project creation
Installing the GSD files

For the devices from the device catalog to be used, the required GSD files must be introduced to the
installed STEP 7 environment. To do so, open the provided base project and install the GSD files from
the STEP 7 project via the menu item "Options – Install GSD Files" in the "Hardware configuration".
Fig. 4.3 Installing the GSD files
Reference projects:
The reference projects are fully designed model systems and serve as reference as well as an
illustrative project for design interrelationships. Form and structure of the created system project must
correspond to those of the references.

Saved on 06.12.2012
Project creation
4.1 PROFINET
The basis for creating a hardware configuration with PROFINET nodes is the PROFINET naming
convention which is illustrated in the following overview (Fig. 4.4 "Structure of PROFINET device
names").
Each node receives a 22-digit PROFINET device name that results from the EPLAN circuit
documentation.
"Appendix A: PROFINET Device Names" contains a sample table for this purpose.
4.1.1 Structure of PROFINET device names
Fig. 4.4 Structure of PROFINET device names
* Expanded station designation

** Device labeling
 Spaces must be filled with minus signs ("-")

 If the last digit (no. 22) is not used, this digit must be filled with an "X".
 The device names within a location (plant) must be unique!

Saved on 06.12.2012
Project creation
4.1.2 Nodes in the PROFINET IO system
A "Class C network" is intended for every PLC which contains 256 IP addresses accordingly. These
256 IP addresses are assigned according to the defined scheme.
Double-clicking on "X3"
(KASTAN1-----BS-ALLGKUX) opens the window
"Properties - KASTAN-----BS-ALLGKUX (R0/S2.3)"
(Fig. 4.6 "General PROFINET settings").
Fig. 4.5 CPU properties
Selecting the "Properties" button

under "Interface" on the "General"
tab opens the window
(Fig. 4.8 "PROFINET parameter
settings").
Fig. 4.6 PROFINET "General" settings
Supporting a device replacement without removable medium

Under certain conditions, the replacement of an IO device can be performed without inserting a
removable medium (e.g. MMC) or without a PG. For this purpose, the neighboring relationships
between the individual IO devices and the IO controller are analyzed via Ethernet mechanisms. Based
on these neighboring relationships, which are stored in the IO controller, the IO controller recognizes
which IO device was replaced and redefines the device name.
Configuration:
For an IO device to be replaceable without inserting a removable medium or without the
parameterization with a PG, the check box "Support device replacement without removable medium"
at the interface of the IO controller on the "General" tab must be enabled.

Saved on 06.12.2012
Project creation
Fig. 4.7 Example of the message in the consistency check of the hardware
If individual IO devices of the automation system do not support the device replacement without
removable medium, a corresponding message is output for the IO device in the consistency check.
The following settings must be made on the "Parameters" tab:
IP address
 Enter the first IP
address
Subnet mask
 Enter the address of
the subnet mask
Subnet
 Select the default
gateway
Fig. 4.8 PROFINET "Parameter"

settings

Saved on 06.12.2012
Project creation
The other PROFINET nodes must be created in the hardware configuration according to the
PROFINET bus design and adjusted and labeled with the corresponding parameters.
Fig. 4.9 PROFINET

hardware configuration
Examples for all the common PROFINET nodes are located in "Appendix B: HW Configuration for
PROFINET Nodes".
For PROFINET, the update time for each node is set individually. By default, the update time is set to
"Automatic" to achieve a very short update time.
The communication
portion for PROFINET
IO must be set to
100 %, the transmission
clock pulse to 1.0 ms.
Fig. 4.10 PROFINET

"Update time" settings
Note
The PROFINET node settings are absolutely necessary.
Deviations must be coordinated with electrical engineering.

Saved on 06.12.2012
Project creation
4.1.3 PROFINET topology
The topological view must also be represented for the entire PROFINET IO system.
Note
It is recommended to wait with setting up the PROFINET topology until the commissioning of the
system.
First, an "offline/online comparison" must be performed to check whether all configured nodes
correspond to the actual state of the system.
Fig. 4.11 Topology editor - "Offline/online comparison"

Saved on 06.12.2012
Project creation
After the comparison, the deviations are displayed.

The online configuration must be accepted.
Required adaptations for port interconnection of the devices without automatic recognition must be
edited manually at the node.
Fig. 4.12 Topology editor - "Offline/online comparison" result

Saved on 06.12.2012
Project creation
The color codings have the following meaning:
Offline entry Online entry Meaning

green green A configured module and a module detected online could
be uniquely assigned to each other (identical
module type, identical device name, identical
order number, identical port number and identical port
interconnections).
yellow yellow A configured module and a module detected online could

be assigned to each other (identical module type,
identical device name, identical order number, identical
port number), but there are differences in the
interconnections. With manual assignment, the device names
may also be different.
What do you have to do?
In this case, adapt either the system configuration
or the configured configuration accordingly.
orange --- If a configured module could not be assigned to any detected

module, then the corresponding list section in the
"Online" topology is empty.
--- orange If a detected module could not be assigned to a configured
module, then the detected module is inserted at the end
of the "Detected topology (online)" list.
white white A configured module and a module detected online could

be assigned to each other. However, these modules do not
contain any topological information.
--- white A module was detected that does not correspond to any
configured module and also does not contain any topological
information.
gray gray Based on the interconnection, it was detected that the module
is part of a tool (docking unit) (i.e. interconnected behind
a "changing partner port"). For such
modules, the online detection is partially not possible:
At the time of the detection process, not all modules
are connected with the network.

Saved on 06.12.2012
Project creation
Graphic view
To create a graphic view, a suitable system overview picture, e.g. from the EPLAN documentation or
something similar, must be stored as BMP file.
This must be done in the following steps:
Step 1:
Select Options and open the correct BMP file via the tabs "Background pictures" and "Add…".
Fig. 4.13 Topology editor - "Graphic view"

Saved on 06.12.2012
Project creation
Step 2:
Right-click and activate the "Move Picture Mode" function.
It should be noted that the miniature view shows the zoom slider positioned completely on the left.
Fig. 4.14 Topology editor - Activating "Move Picture Mode"
Step 3:
If possible, the inserted BMP file should be scaled to the entire area.
Fig. 4.15 Topology editor - Scaling the BMP file to the entire area

Saved on 06.12.2012
Project creation
Step 4:
The PN nodes must be moved in such a way that the spatial assignment is recognizable.
Fig. 4.16 Topology editor - Moving PN nodes
Note
Exit the Topology editor and accept the changes.
The topological interconnection is now stored offline in STEP 7.
Save and compile the hardware configuration and load the hardware into the CPU.

Saved on 06.12.2012
Project creation
To be able to use the detection of the damping values, the following setting must be made at the
PROFINET nodes in the hardware configuration.
In the property view of the

respective port settings, the
connection of "Automatic
settings" must be changed to
"Automatic settings (monitor)"
under "Options".
Fig. 4.17 Properties of PN-IO port
After that, the following diagnostics can be analyzed online:
Fig. 4.18 Status: OK

Saved on 06.12.2012
Project creation
Fig. 4.19 Status: Maintenance required
Fig. 4.20 Status: Maintenance demanded

Saved on 06.12.2012
Project creation
Fig. 4.21 Status: Module not available
Note
If the aforementioned port settings are not made, "no" status window is displayed in the hardware
configuration in online mode.
The setting means the following:

"Automatic settings (monitor)"  same as "Automatic settings", but additionally with port diagnostics.
Examples for port diagnostics:

For "Fiber Optic Ports", the link power margin is monitored.

Saved on 06.12.2012
Project creation
4.1.4 Ethernet node
To obtain a complete representation of all network nodes, the pure Ethernet nodes in NetPro must be
inserted and configured either as SIMATIC-HMI stations or as other stations.
Fig. 4.22 Ethernet node

Saved on 06.12.2012
Project creation
4.2 CPU settings

4.2.1 Protection
The following settings must be made on the "Protection" tab:
The initial password is "VWKB".
The "CPU contains safety program" check box

must be enabled.
Fig. 4.23 Protection
Note
The password must be managed independently by the system supplier during the implementation
phase of the project.
When handing over the system, the password must be given to the operator with the note that it
should be changed.

Saved on 06.12.2012
Project creation
4.2.2 Cycle monitoring time OB1
Fig. 4.24 Cycle / clock memory
Notice
The watchdog must be set to 50 ms.
This setting is absolutely necessary since the Safe program in OB1 is called and a forced
shutdown may take place via the watchdog.
4.2.3 Report system errors
"Report system errors" performs an automatic generation of texts and their assignment to message
numbers. The system is based on the "ALARM_S message channel" and uses a process that is based
on message numbers for the message display. Message texts are generated with the existing
configuration and entered in the STEP 7 database. This allows the message texts to be read or
imported by display systems from Siemens AG.
Note
After every change of the hardware configuration, "Report system errors" must be generated again.
The configuration takes just a few clicks since the required diagnostic program is being generated
automatically.

Saved on 06.12.2012
Project creation
First, select a CPU module in the hardware

configuration.
In the "Options" menu entry, click on the
"Report system errors" selection.
Fig. 4.25 Selection of a hardware configuration
The dialog boxes that open subsequently must be filled out as specified.
First define the numbers and their symbolic
designation of the blocks on the "General" tab
as specified.
Fig. 4.26 "General" dialog box
On the "OB Configuration" tab, you specify

which of the interrupt requests are modified.
"Report system errors" places a call of FB840 in
the selected OB.
If the OB should not yet be located in the block
container, it is being generated.
Fig. 4.27 "OB Configuration" dialog box

Saved on 06.12.2012
Project creation
The CPU reaction to an error is defined on the

"CPU in STOP" tab. The following question is
being asked: "Which errors are so serious that
the CPU should change to the STOP state
after a message has been generated?"
Fig. 4.28 "CPU in STOP" dialog box
The "Messages" tab provides text blocks

(available message information) that are used
for displaying messages.
In this case, free texts and text templates can
be combined freely.
Do not place a check mark at "Optimized

creation of messages".
"AS Process Control Message - Error" must be

selected here for the "Message class".
Fig. 4.29 "Messages" dialog box
If the check mark is set at "Optimized creation of messages", the following warnings may be issued
during the generation:
Fig. 4.30 Warnings during generation if check mark is set

Saved on 06.12.2012
Project creation
On the "Diagnostic Support" tab, a check mark

must be placed next to "PROFINET IO-DB"
(the DB number must be set to "851").
In addition, a check mark must be placed next
to "Diagnostic Status DB" (the DB number
must be set to "850").
Finally, a storage path must be specified for
the export file.
This path must be entered manually.
The "Global" folder in the project folder under
the respective S7 system project must be used
for it.
The final operation consists of activating the

"Generate" button. This generates the required
message texts, numbers and text lists as well
as the PNIO message DB.
Fig. 4.31 "Diagnostic Support" dialog box

Saved on 06.12.2012
Project creation
4.3 VASS term definition for function and function blocks

In the VASS standard software, a distinction is made between the following types of FC and FB:
4.3.1 Structure FC
Blocks that are used for configuring the user program. In general, instances for the control of actuators
are defined in these blocks. Structure FC are called from within an OB.
4.3.2 Structure FB
Blocks that are used for configuring the user program. These blocks are used for the control of the
system process via step sequencers.
4.3.3 Module FB
Blocks for controlling function modules for actuators and units or other FBs that execute a certain
function.
Module FBs (starting at FB100) are generally integrated as single instance in the structure FCs (FC10
to FC99) from the libraries.
4.3.4 Module FC
Blocks for controlling function modules that execute a certain function.

Module FCs (starting at FC600) are generally integrated in the structure FCs (FC10 to FC99) from the
libraries.

Saved on 06.12.2012
Project creation
4.4 Overview of block distribution

Reserved 1…9
PoT 10
Basic function 11
Preselections 12
Operating modes 13
User 1 … 99
ST(n)/AS/robot 14
/F range
ST(n+1)/AS/robot 15 … 96
FC Interface 97
GBA 98
CSM 99
Library 100 … 799
System 800 … 899
User 900 … 929 F call block 900
F range Library 930 … 999
System 1000
Reserved 1…9
User 1 … 99
Sequential control 10 … 99
General 100 … 199
Robot 200 … 249
Robot processes 250 … 299
Machine processes 300 … 349
Drive technology 350 … 399
Clamping technology 400 … 449
Internal conveying
450 … 499
technology
/F range Technologies 500 … 549
Library 100 … 799
Job management 550 … 599
ZAU 600 … 619
FB PDE/PDA 620 … 639
Step sequencer blocks 640 … 649
Message system 650 … 659
Utility blocks 660 … 699
External conveying
700 … 749
technology
Assemblies 750 … 799
System 800 … 899
F program block 900
User 900 … 929 Protective circuit (n) 901
Additional protective
F range 902 … 929
circuits
Library 930 … 999
System 1000

Saved on 06.12.2012
Project creation
Reserved 1…9
1 … 99
User
Sequential control 10 … 99
/F range
100 … 119 TXT, structures 100 … 119
Library 120 … 799
DB
System 800 … 899
F_Ablaufgruppe 900
User 900 … 929 PN/PN coupler 1 901
F range
Other PN/PN couplers 902 … 929
System 1000 … 1999 1000 … 1999
/F range User 2000 … Instance DBs 2000 …
Tab. 4.1 Overview of block distribution
4.5 Variables
4.5.1 Global variables
For global variables, a distinction is made whether they are declared in the I/O area, the bit memory
address area or in DBs.
4.5.1.1 I/O area
The I/O area is essentially defined via the EPLAN project and can be exported using an export
function of EPLAN and imported in STEP 7.
I/O nodes, which can be configured in the control program only via a start address in the block, e.g.
robots, drives, measuring systems, coupler interfaces, etc., must be declared in the symbol table using
the individual bits. The declaration can be taken from the references.
This declaration is required to generate corresponding label texts for the visualization.

Saved on 06.12.2012
Project creation
Fig. 4.32 Excerpt of robot I/O area

Saved on 06.12.2012
Project creation
4.5.1.2 Bit memory address area
Bit memory address areas are declared variables of simple data type.
The following groups are available here:
 System variables
 PLC standard variables
 Visu standard variables
 Project standard variables
 System-specific variables
 Configuring stations
 Safety replacement variables
The bit memory address area from M 0.0 to M 100.0 must be reserved for the VASS library and the bit
memory address area 4000 for the safety area.
4.5.1.3 DBs
All variables of a higher data type are declared in DBs.

The DB number is assigned as follows:
 DB100
 All variables are declared here that are globally assigned to the complete work group. The
symbolic name is "DB_ARG".
 DB100 "DB_ARG"
DB101 "DB_ARG_TXT"
 DB102 … 119
 All variables are declared here that are assigned to a protective circuit. The symbolic
name can be: "11" (protective circuit 11).
 DB102 "11"
DB103 "11_TXT"
DB104 "12"
DB105 "12_TXT"
Note
Each protective circuit receives a separate DB.
It is not allowed to declare structure variables of several protective circuits in one DB.

Saved on 06.12.2012
Project creation
4.5.1.4 Instance DB
OB1 Structure FCs

Instances of module FBs Instance data
blocks
Rotary table
Valve
Valve
e.g. St110020
Roller
conveyor
Lifter
e.g. St110030
Fig. 4.33 Instance DB
Note
Each module block must be assigned an instance data block.
The assignment is done randomly in succession starting with DB2000.

Saved on 06.12.2012
Project creation
4.5.2 Local variables
Local variables are differentiated as follows:

 Static variables
 Temporary variables
Static variables are used in module FBs (library blocks and step sequencers) as auxiliary variables for
step enabling.
In the structure FCs, the auxiliary variables, which are being used as step enabling, are preferably
formed via global system-specific station variables.
The variables that are required in the structure FCs for interconnecting the parameters, are stored in
the temporary variable containers to be able to read a status in online mode.

Saved on 06.12.2012
Project creation
4.5.3 Data types (UDTs)
Two different types of structures are used:

 "Structures" which are accessed by the logic of a module FB
 "Interconnecting structures" that are interconnected at an FB with the structure name and the
element from the structure. They are used to reduce bit memory declarations and to enable
a standardized parameterization of the functional units. For each module block to be
interconnected, a declaration must be made in DB100 to DB1xx with the corresponding
UDT.
Fig. 4.34 Different types of structures
Application of an interconnecting structure using "FB_Ventil" as an example:
Fig. 4.35 FB_Ventil

Saved on 06.12.2012
Project creation
The interconnecting structure is interconnected at the FB with the structure "12"._0050MZ11 and the
element "Frg_V1". The element is stored in the structure of data type "STB_Ventil".
Fig. 4.36 Interconnecting structure "STB_Ventil" with the structure "12"._0050MZ11
The element "Frg_V1" is declared in the interconnecting structure "STB_Ventil".
Fig. 4.37 Interconnecting structure "STB_Ventil" with the element "Frg_V1"

Saved on 06.12.2012
Project creation
4.6 General rules for generating the visualization

Since the visualization is largely being generated automatically based on the analysis of the S7 project
using the SiVArc Screen Generator, certain rules must be followed particularly for the project creation
in S7.
This refers specifically to the arrangement of structure and module components in the program as well
as their labeling and text entries.
4.6.1 Symbolic names of structure FCs
The symbolic name of the structure FCs is defined via the object properties. For this purpose, right-
click on the corresponding block in the SIMATIC Manager and select the "Object Properties" menu
item.
Fig. 4.38 Properties - Function
4.6.2 Instance name and declaration comment of module FCs
You define the instance name of the single instance call when you integrate the module FCs in your
user program.
Note
Do not use any special characters in the declaration comments.

Saved on 06.12.2012
Project creation
4.6.3 HMI keyword
This keyword is used in every structure FC whose elements are shown in the visualization. This
results in a unique assignment of module FBs to one or several panels on which the visualization of
the module FBs should be placed. The keyword is used in the network comments within the structure
FC.
Syntax
"HMI=I<[1..32]>" (or: ";I<[1..32]>" for assignment to additional panels)
Example
Fig. 4.39 Example for calling HMI = I1

Saved on 06.12.2012
Project creation
4.6.4 Variable interconnection at the module FB interface
For some of the assignments in the visualization, the variables configured for the interface of the
corresponding module FBs ("FB_Nothalt", "Meld_4" and "FB_Schutzkreis") are important.
Fig. 4.40 FB_NotHalt
Fig. 4.41 Meld_4

Saved on 06.12.2012
Project creation
Fig. 4.42 Properties - Instance data block for FB126
Note
Only the symbolic names of the bit memory area declared in the symbol table may be used at the
parameters! Unused parameters remain without connection.
Temporary variables may not be used at these parameters that are required for the visualization!
This may lead to the error message "System.NullReferenceException" (Fig. 4.43 "Generating
error").
Fig. 4.43 Generating error

Saved on 06.12.2012
Project creation
4.6.5 Introduction for the text representation in the faceplate
In STEP 7, the module FB is called in the structure FC, each module FB is assigned an InstanceDB.
In the symbol table, a symbolic name and a symbol comment are entered for this InstanceDB.
"FB125" is shown here as an example:

 Symbolic name: Status_110011_FM1
 Symbol comment: Robot completion report 110010R01
The faceplate "Status_03" for the "FB125" is shown here as an example:

In the corresponding XML file, "FBInstance.InstanceDB.SymbolicName" and "FBInstance.
InstanceDB.SymbolComment" are used for the text selection. Those text portions to be selected are
separated in STEP 7 by means of the underscore character "_".
 TextField1: fix "Status"
 TextField2: "FBInstance.InstanceDB.SymbolicName [1] +
FBInstance. InstanceDB.SymbolComment "
 110011 (here the station name) + completion report 110010R01
Calling the module FB "FB125"
Fig. 4.44 Calling the module FB FB125
Result in the faceplate
Fig. 4.45 Faceplate for "Status" example

Saved on 06.12.2012
Project creation
For the configuration in the S7 project, it must be observed that those text portions which are selected
individually must be separated by an underscore character "_".
Notice
If one or several underscore characters "_" are missing between the text portions, the text is
incorrectly selected and does not appear on the faceplate.
In case of missing or incorrect text, the faceplate does not appear in the picture. It is not being
created.
Example:
KommKon_ARG2  Bildbaustein wird erstellt
FbInstance.Name[0] FbInstance.Name[1]
_________________________________________________
KommKonARG2 fehlt  kein Bildbaustein
FbInstance.Name[0] FbInstance.Name[1]
Fig. 4.46 Example for missing underscore characters
The labeling of each module FB is represented schematically in the list in "Appendix C: List for
Labeling Rules".

Saved on 06.12.2012
Project creation
4.7 Project base structure

The base structure and call sequence of a project is represented below.
4.7.1 Call structure OB1
Zyklisches Programm OB1
FC 900 F-Call
FC 10 PoT
FC 11 Grundfunktionen
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FC 15 1. Roboter R01
Weitere Stationen und Roboter:
FC 97 Schnittstellen
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.47 Call structure of OB1
Note
The call structure in OB1 must be followed.

Saved on 06.12.2012
Project creation
Program Network block Function block calls Function

PoT PoT xx --- networks for simulating
component checks
Basic functions Control system FB_Steuerung Control-specific functions,

generating date, time of day,
VKE0, VKE1, …
PROFINET SFC51 "RDSYSST" Diagnostic block for
PROFINET
Visualization FB_Visu Monitoring module for
visualization
Messages Meld_4 User-defined messages, e.g.
for production without part,
fuse failure, etc.
Statistics FB_PDE_Schicht Block for system statistics,
FB_PDE_Statistik clock time, number of units
FB_Statistik_Typ
Preselections Preselections FB_Vorwahl Preselections for stations,

Media FB_Druckluft Switching on compressed air
FB_Energie Measurement of air
consumption
Operating modes General Meld_4 Operating mode-specific

error messages
Emergency Stop FB_NotHalt Evaluation of Emergency
Stop and drive switches
Schutzkreis_xx FB_Schutzkreis Evaluation of protective
doors and cross-protective
circuit safety signals
Ampel_xx ..... Network for traffic light
control and display control
Betriebsarten_STxxyyyy FB_BA Operating mode block, load
FB_BA_LSP voltage block and operating
FB_BA_UBA submode block (evaluation
K100)
Status_Allgemein FB_Sammelstatus Creation of the collection
status for the POU Stoe,
Warn, Wart

Saved on 06.12.2012
Project creation
Program Network block Function block calls Function

STxxyyyy STxxyyyy_Allgemein FB_Status Preparation of the station
FB_ST_Status status for visualization,
FB_ST_Status_K100 copying the K100 for
FB_AS_xxxx substructures
STxxyyyy_Rohbau_FT FB_Drehtisch_2S All FBs for controlling valves,
_Spanntechnik FB_Ventil drives, etc. are programmed
_Mitarbeiter FB_MIA.... here, employee information
STxxyyyy_Technologie FB_PF_IDENT Optional for technology
(optional) FB_SEW_AMA functions,
e.g. Perceptron Measuring
STxxyyyy_Meldungen FB_Bauteilkontrolle Evaluation of component
controls with error message
STxxyyyy_Statistik FB_Statistik Statistic functions for the
FB_Statistik_Typ station
FB_Taktzeit
FB_Zähler
STxxyyyy_Status FB_Sammelstatus Creation of collection status
for the structure FB: Stoe,
Warn, Wart
STxxyyyy_Rxx STxxyyyy_Rxx_In FB_Rob_A Copy inputs from robot to
structure
STxxyyyy_Rxx_Roboter FB_Rob_Folge_8 Creation of robot sequences,
FB_Rob block for evaluating robot
FB_Rob_Korr points for stop for correction
STxxyyyy_Rxx_Fertigmeld FB_Rob_FM Completion report of robot,
FB_Status_Global display of status in
visualization with global
FB_Status
STxxyyyy_Rxx_StellFrg FB_Rob_Frg_Ver Position releases of robot
FB_Rob_Frg
STxxyyyy_Rxx_Prozess FB_Rob_Kleben All process devices of the
FB_Rob_Schweissen robot are programmed here
FB_RobMedien
STxxyyyy_Rxx_Statistik FB_Taktzeit Clock time evaluation for the
robot
STxxyyyy_Rxx_Out FB_Rob_E Robot structure is copied to
outputs
STxxyyyy_Rxx_Status FB_Sammelstatus Creation of collection status
for the structure FB: Stoe,
Warn, Wart
Interfaces Schnittstelle_xxx FB_KommKon_PN Interfaces for data exchange
to adjacent systems
Messages Messages MessageFB Call of message
management block for error
management
GBA GBA FB_GBA Control of large picture
display
ZAU (optional) Connection FB_ZAU Connection to control system
Tab. 4.2 Call sequence and base structure of a project

Saved on 06.12.2012
Project creation
4.8 Program
The structuring of the programs is predefined according to the following scheme.
Base program
is always
present Application program
is individual
Fig. 4.48 Program structure
Note
The reference program "R001V03" is used as the basis for describing the structure FBs, networks,
module FBs and step sequencers.

Saved on 06.12.2012
Project creation
4.8.1 Programming guidelines for ladder logic (LAD)
Fig. 4.49 Permissible network width
The maximum network width is seven contacts plus one coil. If more contacts are required, the
network must be split up by using temporary auxiliary bit memories (here: type STB AS).

Saved on 06.12.2012
Project creation
Fig. 4.50 Safety program  Standard program replacement variable
Replacement variables from the safety program to the standard program are designated with
"F_<variable_name>".

Saved on 06.12.2012
Project creation
Fig. 4.51 Standard program  Safety program replacement variable
Replacement variables from the standard program to the safety program are designated with
"<variable_name>_F".
VKE=0, VKE=1
Only the bit memories "VKE=0" and "VKE=1" created by the FB_Steuerung must be used as
constants for the statuses "True" and "False". Other bit memories, such as "True" and "False", are not
allowed

Saved on 06.12.2012
Project creation
4.8.2 Designation guideline for function blocks
The designation guideline for function blocks is described in detail in Chapter 4.6.5 "Introduction for
the text representation in the faceplate".
4.8.3 F Call
"F Call" is used to call the safety program.

Detailed information is located in Chapter 5 "S7 Distributed Safety".
FC 900 F-Call
FB 900 ARG
FB 901 SK21
FB 90x …
FB 906 Last SK22
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.52 FC900 F-Call

Saved on 06.12.2012
Project creation
4.8.4 "PoT" structure FC
In the "PoT" (production without parts) structure FC, the individual inspections are set if "PoT" is
selected.
For each station, setting the individual inspections must be programmed.
FC 900 F-Call
FC 10 PoT
--
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.53 FC10 PoT

Saved on 06.12.2012
Project creation
4.8.5 "Basic functions" structure FC
In the "Basic functions" structure FC, the following basic functions are implemented for the control
program:
FC 900 F-Call
FC 10 PoT
FB_Steuerung
SFC51 “RDSYSST”
FB_Visu
FB_Mobile
Meld_4
FB_PDE_Schicht
FB_PDE_Statistik
FB_Statistik_Typ
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.54 FC11 basic functions

Saved on 06.12.2012
Project creation
4.8.5.1 FB_Steuerung
The "FB_Steuerung" block is used for monitoring the contactor K0, "Steuerspannung_Ein". In addition,
the time stamp (of the real-time clock) of the control is mapped as string. The block generates two
flashing rates, 1 Hz and 2 Hz. The block provides the cycle time of the OB1 and the overall signature
of the F program for visualization.
4.8.5.2 SFC51 "RDSYSST" (PROFINET)
With the system function "SFC51 RDSYSST" (read system status), you read a system status list or a
partial system status list..
The partial list with SSL-ID W#16#0x94 contains information about the expected and actual
configuration of module racks in central configurations and stations of a PROFIBUS DP master
system/PROFINET IO controller system.
4.8.5.3 FB_Visu
The "FB_Visu" block is used for connection monitoring between PLC and panel PC. The block must
be instantiated individually for every panel PC. The block communicates with the respective PC via
two bit memory variables that must be created for the respective panel PC.
4.8.5.4 FB_Mobile
The FB_Mobile block is used for coupling a mobile panel 277 RO.
When using the mobile panel, an exclusive operating mode is conjunction with the E2 lock is possible.
For this purpose, the box ID of the mobile connection box must be configured in conjunction with the
input of the E2 lock at the block.
The corresponding box ID can be found in the EPLAN documentation:
Rotary encoding switch

Box ID: 255
Fig. 4.55 Setting of rotary encoding switch
4.8.5.5 Meld_4
The "Meld_4" block acquires up to four user messages and enters the message number with status
and time stamp in the DB801 "message buffer".

Saved on 06.12.2012
Project creation
4.8.5.6 FB_PDE_Schicht / FB_PDE_Statistik / FB_Statistik_Typ
4.8.5.6.1 FB_PDE_Schicht
This block initializes the switching list with a weekday-dependent day switching program (shift model)
defined on the "Init" worksheet.
The values are entered in the switching list and processed. In addition, the block calculates the shift
duration and current working time since shift start and provides early shift/late shift/night shift, shift
change pulse and break signal as output parameter.
Switching lists are displayed in the visualization for the current day and the next day.
4.8.5.6.2 FB_PDE_Statistik
This block is used for measuring times and for preparing the clock time and number of units
information for superordinated systems. For this purpose, the clock times and number of units are
entered in the "arStat" array, whereby index positions 0 to 3 are occupied. In addition, number of units,
availability and degree of utilization per shift and for the display in the visualization are created. These
data are written to the flash card with time stamp of the shift start at the change of a shift. The shift
history of the last 24 shifts is also displayed in the visualization.
The function block can be used to measure the time passed between positive edge to the "Start" input
parameter and the positive edge to the "Stop" input parameter. The time passed is output to the output
parameter during the measurement and remains after the stop occurs until the next positive edge for
"Start" is issued.
"Cfg.x1" can be used to reset the time measurement during a measurement with a another positive
edge and to start a new measurement.
The time measurement can be interrupted by setting the "Pause" input parameter. After withdrawing
the input, the time measurement continues.
The "Reset" input parameter causes the unit counter to be reset.
4.8.5.6.3 FB_Statistik_Typ
information of the types used for superordinated systems. For this purpose, the clock times and
number of units are entered in the "arStat" array, whereby index positions 3 to 10 are occupied.
For this purpose, the "Eingangs_Parameter Typ_Index" must be configured with a value between 1
and 8 at the block. If another value is assigned, index 10 is allocated in the "arStat" array.
The function block can be used to measure the time passed between positive edge to the "Start" input
parameter and the positive edge to the "Stop" input parameter. The time passed is output to the output
parameter during the measurement and remains after the stop occurs until the next positive edge for
"Start" is issued.
"Cfg.x1" can be used to reset the time measurement during a measurement with a another positive
edge and to start a new measurement.
The time measurement can be interrupted by setting the "Pause" input parameter. After withdrawing
the input, the time measurement continues.
The "Reset" input parameter causes the unit counter to be reset.

Saved on 06.12.2012
Project creation
4.8.6 Structure FC "Preselections"
In the "Preselections" structure FC, the following basic functions are implemented for the control
program:
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FB_Vorwahl
FB_Druckluft
FB_Kuehlwasser
FB_Energie
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.56 FC12 preselections
4.8.6.1 FB_Vorwahl
The "FB_Vorwahl" block is used for selecting and deselecting equipment (e.g. stations) from the
visualization. It implements the functions "Release Preselection" and "Startup characteristics" for the
system restart.
4.8.6.2 FB_Druckluft
The "FB_Druckluft" block is used for switching on the compressed air. It monitors the signal of the
pressure switches whether low pressure or high pressure is enabled and, in case of an error, initiates
an error message to the message system.
4.8.6.3 FB_Kuehlwasser
The "FB_Kuehlwasser" block is used for switching on the coolant and activating the suction. It must be
configured only if machine welding guns controlled by the PLC are used in the equipment.
4.8.6.4 FB_Energie
The "FB_Energie" block is used for measuring the energy consumption.

Saved on 06.12.2012
Project creation
4.8.7 Structure FC "Operating Modes"
In the "Operating Modes" structure FC, the following basic functions are implemented for the control
program:
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
Meld_4
FB_NotHalt
FB_Schutzkreis
…..
FB_BA
FB_BA_LSP
FB_BA_UBA
FB_Sammelstatus
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.57 FC13 operating modes

Saved on 06.12.2012
Project creation
4.8.7.1 Meld_4
The error messages for

 protective circuits
 diagnostics for PROFINET
 additional general messages
are configured here at the "Meld_4" block.
Every error message must be given an additional identifier which is based on the following table.
A "0" must always be entered for the 3rd character for the user-defined messages. The 4th to 7th
character is omitted.
The structure after the $ character is firmly defined.
1st character Message class
S Fault
M Messages
T TPM
2nd character Message Type
T Technical
S System-dependent
O Organizational
3rd character Radio relevance
E Forwarding with initial value
0 No forwarding
1 General forwarding
2 General forwarding, no entry in CMS database
4th to 7th
Radio number
character
An optional radio number can be specified at this point
Tab. 4.3 Structure after the $ character
4.8.7.2 FB_NotHalt
The "FB_NotHalt" block acquires up to four emergency shutdown messages and forwards them (time-
delayed) to the message system.
4.8.7.3 FB_Schutzkreis
The "FB_Schutzkreis" block implements the functions of a protective circuit with up to five protective
doors.

Saved on 06.12.2012
Project creation
4.8.7.4 Traffic light
Displays must be programmed for every protective circuit. The logic must be created in "LAD" (ladder
logic).
The following logic operations are programmed:
 Protective area jamming display
 Display of electrode cap changes
 Display of stud welding errors
4.8.7.5 FB_BA / FB_BA_LSP / FB_BA_UBA
4.8.7.5.1 "FB_BA" block
The "FB_BA" block is used for creating operating modes. This block operates together with the
"FB_BA_LSP" block (see also Chapter 4.8.7.5.2 "FB_BA_LSP Block") and the "FB_BA_FRG" block.
The "FB_BA_FRG" block is required only if several load voltages are present in an OM circuit (e.g.
insertion areas, etc.). For each load voltage circuit, in which motions are performed, this block must be
called once. This block copies the "OM structure" to the "ST_BA_LSP structure" and recreates the
signals "FrHand" and "FrAuto".
The "FB_BA_FRG" block is not used in the VASS standard. It is replaced with "FB_Status_K100"
which assumes the same task and also visualizes the status of the load voltage circuit.
The operating mode must be programmed once for every protective circuit. For this purpose, the
"FB_BA" and the "FB_BA_LSP" are used as a pair.
4.8.7.5.2 "FB_BA_LSP" block (operating modes for station)
The "FB_BA_LSP" block forms the start.

This block operates together with the "FB_BA" block and forms the signals "Start" and "Start Chained".
This block may be called only once per "FB_BA"
4.8.7.5.3 "FB_BA_UBA" block (operating modes for substation)
The "FB_BA_UBA" block is used for creating operating submodes, e.g. for insertion areas. The block
is called once for each insertion area in the structure FB "operating modes". It operates like a regular
"FB_BA", but it accepts special operating mode functions, such as production without part (PoT), etc.,
from the upstream operating mode structure.

Saved on 06.12.2012
Project creation
4.8.7.6 FB_Sammelstatus
The "FB_Sammelstatus" block is used to supply the visualization navigation bar with the status of an
ST (station). In addition, the status information of the ST is mapped to output variables.

Saved on 06.12.2012
Project creation
4.8.8 "STxxyyyy" station structure FC
In the "Station" structure FC, all station-relevant module FBs are called.
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB_Status
FB_ST_Status
FB_ST_Status_K100
S7G_Control
AST_xxyyyy
FC_Trans_init
FC_Trans
AS_xxyyyy
Prozess Modul-FBs
FB_Statistik
FB_Statistik_Typ
FB_Taktzeit
FB_Zähler
FB_Sammelstatus
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.58 FC14 1. "STxxyyyy" station

Saved on 06.12.2012
Project creation
4.8.8.1 FB_Status / FB_ST_Status / FB_ST_Status_K100
4.8.8.1.1 "FB_Status" block
This is an interactive block for visualization, which toggles the "Status" IO variable upon demand and
depending on the input "Enable" and "Cfg".
4.8.8.1.2 "FB_ST_Status" block
This block is used to supply the visualization navigation bar with the status of an ST. In addition, the
status information of the ST is mapped to a byte output variable.
The block must be called once per station.
4.8.8.1.3 "FB_ST_Status_K100" block
This block is used to supply the visualization navigation bar with the status of an ST. In addition, the
status information of the ST is mapped to a byte output variable. The block forms an operating
submode circuit with separate load voltage feedback, e.g. for insertion areas.

Saved on 06.12.2012
Project creation
4.8.8.2 Sequential control
Fig. 4.59 Schematic interaction of sequential control

Saved on 06.12.2012
Project creation
Every sequential control features the blocks listed below.

Every sequential control is called in the station-based structure FC.
In certain cases, several sequential controls may also be required for each station.
4.8.8.2.1 "S7G_Control" block
The "S7G_Control" block takes over the sequential control-based step sequencer management.
For each sequential control, it must be called once.
FC x Station y
The block takes over the following
functionalities:
while switching the system operating
modes from manual to automatic, it is For Fig.
used for synchronizing the step "Automatic
sequencer. If it is not in a uniquely retraction (1)"
defined state, it sets the permission for
automatic retracting of the system
components that belong to the
sequencer.
In the active "Automatic" operating
mode, the permission for the defined
hold of the step sequencer is output,
unless this is an exclusion step.
Call of the "AST_xxyyyy" structure FC

for the corresponding "AS_xxyyyy"
structure FB.
Call of the "AS_xxyyyy" structure FB.
*)
*)  see ch. 4.8.8.2.5

"AS_xxyyyy" block
Fig. 4.60 "S7G_Control" block

Saved on 06.12.2012
Project creation
Automatic retraction (AutoVR)

"AutoVR" is formed in "AST FC" (1.) and is used in the "Structure FC" of the station (2.).
"AutoVR" is used only for the clamping technology, i.e. all valves and "FU_2S" twister!
The "AutoVR" structure is used to execute the function of automatic retraction with FB "S7G_Control".
1. 2.
FC x+1 AST Station y FC x Station y
from Fig. "S7G_Control block"
Fig. 4.61 Automatic retraction (1)
Note
It is absolutely necessary to program the "AutoVR" function.

Saved on 06.12.2012
Project creation
The following synchronization logarithm is used to check all transitions of a step sequencer:
(((Trans x) & (Trans x+1)) & uniqueness) = "Sync_1S" step + y (btw. Tx+Tx+1)
The synchronization result leads to the following responses/displays:

 Sync_1S =1: The step sequencer is set to the located step y, the output parameter
"FrgAutoVR" is reset and the step sequencer is started in Automatic.
The command output of the actions is released again.
 Sync_1S = 0: The step sequencer remains in manual mode with "SW_MAN".
Depending on the input parameter "FrgSync", the output parameter "FrgAutoVR" is set for
automatic retracting of the system components.
The input parameter "TW_Sync" is used for the time debouncing of the synchronization
result "Sync_1S", i.e. at least the time "TW_Sync" must be present so that an actual
synchronization can take place.
Process cell Manual 

Auto
= Start
synchronization
Synchronization
possible to 1
step?
No: "Sync_1S"=0 Yes: "Sync_1S"=1
Step sequencer = Step sequencer = "SW_Auto"

"SW_Man" Step sequencer in Auto
Step sequencer in "FrAutoVR" =0
Manual Set step sequencer to located
FrSync=1  step
"FrAutoVR"=1
Aggregate wie z. B. Spanner

"Automatic retracting" zurück zu fahren,
can be executed with um erneut auf
"FrAutoVR" Synchronisation zu prüfen
 back until synchronization is possible
Fig. 4.62 Automatic retraction (2)

Saved on 06.12.2012
Project creation
4.8.8.2.2 "AST_xxyyyy" block
In the sequential control-based "AST_xxyyyy" block, the interlocking conditions or permissions for
manual and automatic as well as the transition conditions, including the transition management, are
being programmed. Such a block must be called once for each step sequencer.
Within the "AST_xxyyyy" structure FC, the module FCs "FC_Trans_Init" and "FC_Trans" are called.
But before the block "AST_xxyyyy" can be created, the variables must be declared in the
corresponding FB "S7-Graph".
The static variables must be created by the user in the "Overview" area on the "Variable" tab under
"Environment \ Interface \ STAT".
They are required to be able to create the interlock and trans conditions in "AST FC".
Fig. 4.63 Creating static variables

Saved on 06.12.2012
Project creation
4.8.8.2.3 "FC_Trans_Init" block
FC x+1 AST Station y FB x+1 AS Station y
The "FC_Trans_Init" does not internally evaluate the

configuration bit since this step is the initial step. If the
access request is selected, a stop is always carried out
("MOP_HALT" = True).
An exclusion step is not available here since the station is
in the initial state in this step.
Fig. 4.64 "FC_Trans_Init" block

Saved on 06.12.2012
Project creation
4.8.8.2.4 "FC_Trans" block
FC x+1 AST Station y FB x+1 AS Station y
The "FC_Trans" block evaluates internally via the

configuration bit whether it is an exclusion step. If
the access request is selected, a stop is carried out
in case of an exclusion step (MOP_HALT = True) if
the step is active and the transition is met.
If the transition should not be met for any reason or
due to a breakdown, a stop is carried out in case of
an access request after a configured delay time
(TUe_S). (MOP_Halt = True)
In this case, it is not relevant whether the access
request is an exclusion step or not.
Fig. 4.65 "FC_Trans" block

Saved on 06.12.2012
Project creation
Note
The stepping time "+ 10 s" must be parameterized as delay time (TUeS).
The stepping times must be written during a process by setting the bit memory "M10.7" and can be
read at the "SNO_Time" parameter in the online status.
The determination must be performed during a process in cycle time.
Note
If a system-specific requirement demands no stop in certain steps, the "_Cfg" parameter must be
connected with W#16#2 (no stop in this step). If the "_Cfg" parameter is connected with W#16#0
(wait step with time monitoring), a stop is performed in this step.
Defined hold
Step sequencer in automatic mode: "Defined hold"
The switching of the input parameter "_Cfg" at block "FC_Trans" can be used to determine whether is
allowed to hold in this step or not.
S4
Time of request
for defined hold (S6)
S5
Exclusion step list

e. g. Empty steps S6 excluded
S6
cfg.X1 = true
S7
1. permissible hold step = S7
reached and motions finished
(transition fulfilled)
S8 cfg.X0 = true
Fig. 4.66 Defined hold

Saved on 06.12.2012
Project creation
4.8.8.2.5 "AS_xxyyyy" block
The programmed step sequencer is called with the sequential control-based "AS_xxyyyy" block. This
block must be programmed with GRAPH-7.
Fig. 4.67 "AS_xxyyyy" block
The following rules must be observed when programming a step sequencer:

 All transitions within a step sequencer must be programmed uniquely.
Cases in which several transitions are met simultaneously may not occur.
 The transition must be dealt with as long as the subsequent active step is being processed.
 Only linear steps must be set up within a step sequencer.
 Alternative branches are allowed. They are used for rotary tables or type changes.
 Instance DBs with identical numbers must be created for graph FBs.
 To implement the function of initializing a step sequencer via the "Init_SQ" input, a step via
the object properties must be declared as initial step.
The "S_Init" step must be declared as initial step.
(see Fig. 4.60 - Block "S7G_Control" / green border)
Fig. 4.68 Declaring the initial step

Saved on 06.12.2012
Project creation
Notice
- Simultaneous branches may not be used.
- Several sequencers in a step sequencer block may not be used.
- Multi-instance calls for the step sequencer block may not be used.
Notice
If several processes are controlled in one step, it must be ensured that the permission for control of
the other processes is granted if a process is finished (cycle control).
Example: Upon releasing the robots for welding, the dropped cycle controls of the robots must be
connected in parallel. In case of a robot malfunction, it is possible that a process is no longer being
controlled.
Note
In case of multilingual projects, step comments may not contain any umlauts (ä, ö, ü).

Saved on 06.12.2012
Project creation
4.8.8.3 FB_Statistik / FB_Statistik_Typ / FB_Taktzeit / FB_Zähler
4.8.8.3.1 "FB_Statistik" block
information for superordinated systems. For this purpose, the clock times and number of units are
entered in the "arStat" array, whereby index positions 0 to 3 are occupied.
4.8.8.3.2 "FB_Statistik_Typ" block
information of the types used for superordinated systems. For this purpose, the clock times and
number of units are entered in the "arStat" array, whereby index positions 3 to 10 are occupied.
4.8.8.3.3 "FB_Taktzeit" block
This block is used for measuring times. The function block can be used to measure the time passed
between positive edge to the "Start" input parameter and the positive edge to the "Stop" input
parameter.
4.8.8.3.4 "FB_Zähler" block
This block is used for processing (count) values. The function block allows incrementing or
decrementing values starting at a defined value.
The "FB_Sammelstatus" block is used to supply the visualization navigation bar with the status of an
ST (station). In addition, the status information of the ST is mapped to output variables.

Saved on 06.12.2012
Project creation
4.8.9 "Robot" structure FC
A "Robot" structure FC must be created for each robot.
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB_Rob_PN_A
FB_RobFolge_8
FB_Rob
FB_Rob_Korr
FB_Rob_FM
FB_Status_Global
FB_Rob_Frg_Ver
FB_Rob_Frg
FB_Rob_Kleben
FB_Rob_Schweissen
FB_RobMedien
FB_Taktzeit
FB_Rob_PN_E
FB_Sammelstatus
FB_Sammelstatus
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.69 FC15 1. robot R01

Saved on 06.12.2012
Project creation
4.8.9.1 FB_Rob_PN_A
This module copies the output data of the robot to the robot structure.
4.8.9.2 FB_RobFolge_8 / FB_Rob / FB_Rob_Korr
4.8.9.2.1 "FB_RobFolge_8" block
Depending on which sequential release ("SeqRel1", "SegRel2", ..., "SeqRel8") is available, this block
outputs the corresponding sequential number ("Seq1", "Seq2", ..., "Seq8") at the "Sequence" block
output.
4.8.9.2.2 "FB_Rob" block
This block is used to control the motion sequences of a robot and visualizing the information belonging
to the robot.
4.8.9.2.3 "FB_Rob_Korr" block
This block is used for controlling the robot process point correction via the visualization.

Saved on 06.12.2012
Project creation
4.8.9.3 FB_Rob_FM / FB_Status_Global
4.8.9.3.1 "FB_Rob_FM" block
The robot sends the completion reports as binary-coded decimal numbers to the PLC. This module
sets the completion report that corresponds to the value. At the same time, the block reflects the value
back to the robot. In addition, one input each is available for setting or resetting all completion reports.
4.8.9.3.2 "FB_Status_Global" block
Interaction block for the visualization that sets the outputs "Steu_S" or "Steu_R" and provides the two
inputs "Status" and "Message" to the visualization upon demand depending on the "Status" input.
4.8.9.4 FB_Rob_Frg_Ver / FB_Rob_Frg
4.8.9.4.1 "FB_Rob_Frg_Ver" block
The block coordinates the interlock queries between the individual robots.
To prevent a "dead interlock" among the robots, they issue the interlock query before entering the
interlock and wait for acknowledgment from the PLC.
Note
It must be observed that robot interlock numbers must be assigned once PLC-wide.
4.8.9.4.2 "FB_Rob_Frg" block …
This block is used to prepare the robot releases. The releases are internally linked with "SAK", all
releases are set with deselected robot and with "PF0". With "Cfg", the behavior can be influenced with
"PF0" and with deselected robot.

Saved on 06.12.2012
Project creation
4.8.9.5 FB_Rob_Kleben / FB_Rob_Schweissen / FB_RobMedien
4.8.9.5.1 "FB_Rob_Kleben" block
This block is used for the control of a "Bonding" process device and the visualization of the
corresponding information.
4.8.9.5.2 "FB_Rob_Schweissen" block
This block is used for the control of a welding apparatus and the visualization of the corresponding
information.
4.8.9.5.3 "FB_RobMedien" block
This block has the same function as the "FB_Medien" block. The block is used only for robots with
welding function.
This block is used for the control of media, e.g. water, compressed air, gas, etc. It monitors the flow
and initiates an error message to the message system in case of an error.
4.8.9.6 FB_Taktzeit_Plus
This block is used for measuring the clock times and their visualization. The function block can be
used to measure the time passed between positive edge to the "Start" input parameter and the
positive edge to the "Stop" input parameter.
4.8.9.7 FB_Rob_PN_E
This module copies the data of the robot structure to the input data area of the robot.
The "FB_Sammelstatus" block is used to supply the visualization navigation bar with the status of the
robots and the robot process devices. A separate call of the "FB_Sammelstatus" is required in each
case for the analysis for the robot and for the process device.

Saved on 06.12.2012
Project creation
4.8.9.9 "Layer"
The layer is used for "robots", "robot process devices" and "machine processes".
6 objects from the generator are placed on these pages in sequence by the robot as it locates them.
If more than 6 objects are located in a project, they should preferably be combined to groups. The
layer number is used to determine the page on which the object from the generator should be placed.
Below are three examples for the "Layer".
4.8.9.9.1 Robot
Fig. 4.70 Layer – Robot

Saved on 06.12.2012
Project creation
4.8.9.9.2 Robot process device
Fig. 4.71 Layer – Robot process device

Saved on 06.12.2012
Project creation
4.8.9.9.3 Machine process
Fig. 4.72 Layer – Machine process
Note
If nothing is entered at the "Layer", the layer screen is being created, but it is empty.
The screen is stored in the XML, but the corresponding elements are not being placed.

Saved on 06.12.2012
Project creation
4.8.10 "Interfaces" structure FC
In the "Interfaces" structure FC, signals are sent to adjacent PLCs and received.
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB_KommKon
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.73 FC97 interfaces
4.8.10.1 FB_KommKon
The communication between two PLCs is handled via PN/PN couplers.

FB_KommKon is used as interface block for visualization.

Saved on 06.12.2012
Project creation
4.8.11 FB "MessageFB"
The call of the FB "MessageFB" is required for the message system.
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 4.74 FB650 general contact indicator lights
4.8.11.1 MessageFB
This FB is used to enter messages of the module FBs in the central message archive and the central
alarm view. The texts for visualizing the messages are stored in the text libraries 0 to 7
(DB804 … DB811).

Saved on 06.12.2012
Project creation
4.8.12 "GBA" structure FC
The values for the large picture display are prepared in the "GBA" structure FC.
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FB_GBA
FB_GBA_Wertanzeige
FC 99 ZAU
Fig. 4.75 FC98 GBA
4.8.12.1 FB_GBA
This block is used to prepare data for the large picture display (GBA).
4.8.12.2 FB_GBA_Wertanzeige
This block is used to prepare data for the large picture display (GBA).

Saved on 06.12.2012
Project creation
4.8.13 "ZAU" structure FC
The "ZAU" structure FC is called if the control is connected to a higher-level control system.
FC 900 F-Call
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
ZAÜ_GrundFkt
ZAÜ_Schalt
ZAÜWerte
ZAÜSollwert
ZAÜAnlStatus
Fig. 4.76 FC99 ZAU

Saved on 06.12.2012
Project creation
4.8.13.1 ZAÜ_GrundFkt
The entire log for coupling to a CSM is implemented in this FB. The internal interfaces of the PN CPUs
are used for this purpose. As a result, the use of the T blocks (TSEND, TRCV, TCON and TDISCON)
is required.
4.8.13.2 ZAÜ_Schalt
The switching times transferred by the CSM are evaluated with this FB. For this purpose, an ID which
is used within the switching list is assigned for each call. A comparison with the desired switching time
and the internal clock of the PLC is performed cyclically.
4.8.13.3 ZAÜWerte
This function is used to enter the actual values of the system, such as number of units and clock
times, in the value buffer in six groups of ten values each. End of shift (= 1) can be entered as send
reason.
4.8.13.4 ZAÜSollwert
This block is used for withdrawing a setpoint from the setpoint list. This list is provided by a CSM and
stored in the ZAÜ_DB.
4.8.13.5 ZAÜAnlStatus
This function is used to cyclically compile a byte for the system status from the input parameters
"Status1" to "Status8" and entered at the corresponding position in the system state for the CSM.

Saved on 06.12.2012
Project creation
4.9 Block update

If updated blocks or symbols must be made available via a library update, they must be adopted into
the system project.
To do so, proceed as follows:
 From the "Grund_Symbolik" folder, copy the complete content of the symbol table into the
system "symbol table".
 For the "Sources" folder in the "Objects with sources" main folder, copy the complete content
into the "Sources" system folder.
 From the "Blocks" folder in the "Objects without sources" main folder, copy all required
elements into the "Blocks" system folder.
Note
The block for the CSM interface represents a special case.
If the interface has already been tested, then the block may not be copied since the connection
configuration will otherwise be lost.
 Updating blocks from Safe library

 Checking block consistency
 Performing the Visu update (see Ch. 6.4.2.2 "Required preparations for Delta import type")

Saved on 06.12.2012
S7 Distributed Safety
5 S7 Distributed Safety
The PROFIsafe safety profile allows connecting fail-safe, distributed I/O devices to an F-CPU (F = fail-
safe). This makes it possible to safely and flexibly process safety information from emergency stop
switches, light barriers, two-hand operation, etc. in the S7 program. In the safety program, the
functions of the safety relays are replicated with simple LAD logic operations. Conventional
electromechanical solutions are omitted. In this case, the PROFIsafe communication operates in
conventional PROFINET systems.
The PROFIsafe safety profile requires corresponding PROFINET hardware components.
Note
In the designations used below, "F-" and "fail-safe" are used synonymously.
5.1 Configuration steps

The following configuration steps must be followed for the design of an S7 project with safety program
in order to maintain the VASS specifications (block addresses, etc.):
 For hardware:
 Configuration
 Save and compile hardware
 For software:
 Create user program
 Create safety program:
 Create the required FB900 to FB90x and DB900 to DB9xx
 Configure the FC900 call

Saved on 06.12.2012
5.2 PROFIsafe components

5.2.1 ET 200S station, PROFIsafe components
5.2.1.1 Address switch for setting the PROFIsafe address
An address switch (10-pin DIP switch) is located on the left side of every fail-safe module. This
address switch is used to enter the PROFIsafe address of the F-module.
To obtain a unique PROFIsafe F_Ziel_Adresse at all times, the I/O start address of the respective fail-
safe module is configured as PROFIsafe address.
It must also be set as F_Ziel_Adresse via the DIP switches at the module.
Fig. 5.1 F_Ziel_Adresse
Note
For ET 200 modules, a safe address can be assigned only up to 1023.
If there are fail-safe I/O modules with start addresses greater than 1023 in the system, free
addresses below 1023 must be used for this purpose.

Saved on 06.12.2012
5.3 Configuration of the F-modules in the hardware

configuration
5.3.1 Configuring the CPU 317F, CPU 319F
In addition to the settings for the CPU properties described in the Volkswagen standard software
documentation, the settings for the safety program of the CPU must be performed on the "Protection"
tab and on the "F Parameter" tab.
5.3.1.1 Protection level
The provided projects are set up with the password "VWKB". The passwords are adjusted and
managed by the system supplier and after system handover by maintenance for each division.
Notice
The "CPU contains safety program" check box must be enabled.
Fig. 5.2 Setting of access protection and activation of safety program
5.3.1.2 F Parameters
The following settings must be accepted for the

PROFIsafe base addresses, the ranges of
numbers of the F data blocks and F function
blocks:
Fig. 5.3 Setting of F parameters

Saved on 06.12.2012
5.3.1.3 PROFINET device numbers and PROFIsafe F_Ziel_Adressen
The number of the last block of the IP address is used as PROFINET device number.
The PROFIsafe F-Ziel_Adressen must be accepted according to the DIP switch settings. For the rules
for addressing, see also Chapter 5.2.1.1 "Address switch for settings of the PROFIsafe address".
5.3.1.4 Setting of F_Überwachungszeit (F_WD_Time) of PROFINET safe devices
Configure the specific monitoring times of the F-system with respect to availability. Approximate the
calculation of the minimum monitoring time by means of an Excel file.

The Excel file for S7 Distributed Safety is located on the Internet under
http://support.automation.siemens.com/WW/view/de/11669702/133100.
Also observe the operating instructions of the PROFINET devices from other manufacturers.
Use the Excel file to calculate the maximum response time and ensure that the error tolerance time of
the process is not being exceeded. If necessary, the specific monitoring times of the F-system must be
reduced.
Notice
The "F_Überwachungszeit" / "F_WD_Time" must be checked and configured.
The "F_Überwachungszeit" is an influencing factor for dimensioning the clearance between the
safety switching device and the critical point. This requires a corresponding consultation with the
person conducting the hazard analysis for the system.

Saved on 06.12.2012
5.3.2 Configuring stations with I/O modules
The general configuration of an ET 200S station is performed as described below.
5.3.2.1 Configuring a fail-safe 4/8 F-DI module
Double-clicking on a line of the ET 200S station opens the "Properties" dialog.
The device identifier derived from the

EPLAN must be entered in the "Name"
field.
The module type and the short circuit test

- if the parameter is configured - must be
entered in the "Comment" field.
Fig. 5.4 Assigning name and comment for the fail-safe module

Saved on 06.12.2012
The I/O base address must be entered on the "Addresses" tab according tom the specifications from
the EPLAN.
Fig. 5.5 Setting the I/O base address for the fail-safe input module
On the "Parameter" tab, the "F_Ziel_Adresse" must be entered according to the I/O start address. See
also Chapter 5.2.1.1 "Address switch for settings of the PROFIsafe address".
The channels must be set depending on the type of connected sensor (see examples in "Appendix D:
Distributed Safety").
Binary representation of the PROFIsafe

address for the fail-safe module
(F_Ziel_Adresse). The DIP switch setting
for the PROFIsafe address at the module
must match the switch setting specified
here.
The channel settings (channel 0,4) must

be adjusted to the sensor used.
Fig. 5.6 Setting the PROFIsafe parameters for 4/8-DI
Note
If a fail-safe module is replaced, the DIP switch setting on the new module must be set to the
configured PROFIsafe address.

Saved on 06.12.2012
5.3.2.2 Configuring a fail-safe 4 F-DO module
Double-clicking on a line of the ET 200S station opens the "Properties" dialog for the fail-safe module
configured in this line.
The tabs "General" and "Addresses" must be filled out according to the previously described 4/8 F-DI
module.
Fig. 5.7 Assigning name and comment for the fail-safe module
Fig. 5.8 Setting the I/O base address for the fail-safe output module

Saved on 06.12.2012
On the "Parameter" tab, the "F_Ziel_Adresse" must be entered according to the I/O start address. See
also Chapter 5.2.1.1 "Address switch for settings of the PROFIsafe address".
All channels must be activated and, if necessary or requested, monitored with "Diagnostic: Wire
break".
The read-back time must be configured

with the default value "1 ms".
If application-specific higher read-back
times are required, it must be determined
separately and viewed from a safety
perspective.
Fig. 5.9 Setting the PROFIsafe parameters for 4 F-DO
5.3.2.3 Configuring a fail-safe 4 F-RO module
Double-clicking on a line of the ET 200S station opens the "Properties" dialog for the fail-safe module
configured in this line.
The tabs "General" and "Addresses" must be filled out according to the previously described 4/8 F-DI
module.
Fig. 5.10 Setting the I/O base address for the fail-safe output module

Saved on 06.12.2012
5.4 Save and compile hardware

When compiling the configured hardware, the F-I/O devices DB, the F_GLOBDB and FBs for the
sequence of the safety program are generated and stored in the block container. These blocks are
processed by the system and may not be changed or deleted.
5.4.1 F-I/O devices DB
For each F-I/O devices module, an F-I/O devices DB is automatically being generated while compiling
in "HW Config" and a symbolic name is entered in the symbol table at the same time.
The symbolic name is formed by the fixed prefix "F", the start address of the F-I/O devices and the
name entered in "HW Config" in the object properties for the F-I/O devices.
Example: F00014_1BSALLGKA131 ( maximum 17 characters)
The F-I/O devices DB contains variables that are used in the safety program.
Access to the F-I/O devices DB variables is done via a "fully qualified DB access" (this means, by
specifying the symbolic name of the F-I/O devices DB and by specifying the name of the variable).
Note
If an F-I/O devices DB is being accessed from whose F-I/O devices no single channel is used in
the safety program, it can lead to a STOP of the F-CPU.

Saved on 06.12.2012
The following table shows the variables of an F-I/O devices DB that can be evaluated by the user:
Variable Data type Function Default
Variables that PASS_ON BOOL 1 = Activate passivation 0
can/must be ACK_NEC BOOL 1 = Acknowledgment for reintegration 1
described required for F-I/O devices /
channel faults
ACK_REI BOOL 1 = Acknowledgment for reintegration 0
IPAR_EN BOOL Variable for re-parameterization of fail-safe 0
DP standard slaves /
IO standard devices or for SM 336;
F-AI 6 x 0/4 … 20 mA HART for enabling
the HART communication
Variables that PASS_OUT BOOL Passivation output* 1
can be QBAD BOOL 1 = Substitute values are output 1
evaluated
ACK-REQ BOOL 1 = Acknowledgment request for 0
reintegration
IPAR_OK BOOL Variable for re-parameterization of fail-safe 0
DP standard slaves /
IO standard devices or for SM 336;
F-AL 6 x 0/4 … 20 mA HART for enabling
the HART communication
DIAG BYTE Service information
QBAD_I_xx BOOL 1 = Substitute values are output to 1
input channel xx
QBAD_O_xx BOOL 1 = Substitute values are output to 1
output channel xx
Tab. 5.1 Variables of an F-I/O devices DB
Note
The parameter assignment of the ACK_NEC = 0 variable is allowed only if an automatic
reintegration is allowed for the respective process from a safety perspective.
Note
The default for ACK_NEC after creating the F-I/O devices DB is 1. If you do not require an
automatic reintegration, ACK_NEC does not have to be written to.
Note
For F-I/O devices with outputs, an acknowledgment because of required test signal connections
can be possible only in the minute range after removing the fault following F-I/O devices / channel
faults.

Saved on 06.12.2012
5.4.2 Configuration of a PN/PN coupler
The modules of a PN/PN coupler are listed in the hardware catalog under "PROFINET IO  Gateway
 PN/PN Coupler".
Select "PN/PN Coupler" in the hardware catalog copy it to the Ethernet(1): PROFINET IO system
(100) (drag-and-drop). The device number and the device name must be entered according to the
VASS specifications.
Fig. 5.11 Configuration of a PN/PN coupler
In the "User Properties" dialog for the

PN/PN coupler, the PROFINET device
name must be entered in the "Device
Name" field.
The device number must be assigned

under "Node of PROFINET IO System".
Fig. 5.12 Properties of a PN/PN coupler

Saved on 06.12.2012
5.4.3 Configuration of hardware for fail-safe communication
Module configuration of the PN/PN coupler for fail-safe communication

In the hardware configuration, one PN/PN coupler each must be inserted at the PROFINET for the
send and receive CPU and assembled with the following modules:
 Module of send CPU: 12-byte output and 6-byte input
 Module of receive CPU: 12-byte input and 6-byte output
The consistency of the data across the entire length is ensured if the mixed module (IN/OUT) is used.
The input and output start address of a module must be identical for all modules.
Fig. 5.13 Input and output start address of a module must be identical
In the hardware catalog, the corresponding page of the PN/PN coupler must be selected for each
CPU. X1 for the left side, X2 for the right side. The matching configuration file must be placed as node
in the PROFINET IO system. The transfer of the data contents must be configured for the fail-safe
data exchange via mixed modules.
Note
Important is a mutual configuration on the send and receive side that is matching the data volume!
Whatever is sent on the side X1 must be received on the other side X2.

Saved on 06.12.2012
Sending side (configuration example):
Device
Configure PN/PN coupler with order number
6ES7 158-3AD00-0XA0 via X1 (port 1 and 2 left
side of coupler).
Module
Select mixed module with IN/OUT 6 bytes/12
bytes for slot 1 and select with same start byte
for input and output byte.
Fig. 5.14 Sending side (configuration example):

Saved on 06.12.2012
Receiving side (configuration example):
Device
Configure PN/PN coupler with order number
6ES7 158-3AD00-0XA0 via X2 (port 1 and 2
right
side of coupler).
Module
Select mixed module with IN/OUT 12 bytes/6
bytes for slot 1 and select with same start byte
for input and output byte.
Fig. 5.15 Receiving side (configuration example):
Note
The data volume that is specified as OUT output on the sending side (12 bytes) must be configured
as IN input on the receiving side (12 bytes).
In the same way, the IN input data from the sending side (6 bytes) must be present as OUT on the
receiving side (6 bytes). And this must take place on the same slot!
Specific mixed modules must be configured here for fail-safe communication.

Saved on 06.12.2012
Safety-oriented CPU-CPU communication via PROFINET IO

For the safety-oriented CPU-CPU communication, 16 boolean and 2 integer values are transferred for
each F_SENDDP / F_RCVDP connection in one communication direction. The communication is
established with the send/receive blocks from the VASS project library.
Fig. 5.16 Safety-oriented CPU-CPU communication via PROFINET IO
The F-application blocks are located in the "F-Application Blocks" block container of the "S7
Distributed Safety" F-library.
F_RCVDP must be called at the start of the F-program block (FB900 "ARG"), F_SENDDP at the end.

Observe the Statements and notes about fail-safe communication and configuration in the
SIMATIC program engineering, configuring, planning and operating manual "S7 Distributed Safety
- Configuring and Programming" (chapter 8 "Configuring and Programming Communication").

Saved on 06.12.2012
5.5 Creating the safety program

To create the safety program, the required FB900 to FB90x and DB900 to DB9xx must be
programmed system-dependent.
Next, the FC900 ("F-Call") must be configured in the F-runtime group.
5.5.1 Overview of the block list of the safety program
Templates to be created and adjusted by the user:

Symbol Block no. assoc. Language Function in Author Comment
DB of the safety
creation program
ARG FB900 DB900 F_KOP F-FB User Working group safety
program
Safety program runtime
group
Sending and receiving
Reintegration of
passivated modules
SKxx FB901 F_KOP F-FB User Evaluation of protective
doors and cross-protective
circuit safety signals
Emergenc FB9xx F_KOP F-FB User Safety program
y Stop Emergency stop and drive
switch
Last_SKxx FB9xx F_KOP F-FB User Safety program
Load voltage
F Call FC900 F Call F Call User Call of the safety program
Tab. 5.2 Safety program block list

Saved on 06.12.2012
F-application blocks in the VASS project library

Symbol Block no. Language Function in Author Comment
of the safety
creation program
F_CTU FB941 F-STL F-application DSAFETY1 Up-counter
F_CTD FB942 F-STL F-application DSAFETY1 Down-counter
F_CTUD FB943 F-STL F-application DSAFETY1 Up/down-counter
F_TP FB944 F-STL F-application DSAFETY1 Timer pulse
F_TON FB945 F-STL F-application DSAFETY1 On-delay timer
F_TOF FB946 F-STL F-application DSAFETY1 Off-delay timer
F_FDback FB947 F-STL F-application DSAFETY1 Feedback monitoring
F_ACK_GL FB948 F-STL F-application DSAFETY1 Reintegration
F_FBback FB949 F-STL F-application VW_1399 Feedback monitoring
F_FRG FB950 F-STL F-application VW_1399 Enable for F-function

PROFIsafe robot emergency
F_Rob_Not FB951 F-LAD F-application VW_1399
stop
F_Rob FB952 F-LAD F-application VW_1399 PROFIsafe robot
F_2H_EN FB971 F-STL F-application DSAFETY1 2-hand operation
F_MUT_P FB972 F-STL F-application DSAFETY1 Muting

DP-DP coupler fail-safe
F_SENDDP FB983 F-STL F-application DSAFETY1
sending
DP-DP coupler fail-safe
F_RCVDP FB984 F-STL F-application DSAFETY1
receiving
Fail-safe sending via S7
F_SENDS7 FB985 F-STL F-application DSAFETY1
connection
Fail-safe receiving via S7
F_RCVS7 FB986 F-STL F-application DSAFETY1
connection
F_SHL_W FC934 F-STL F-application DSAFETY1 Word content move left
F_SHR_W FC935 F-STL F-application DSAFETY1 Word content move right

Type change
F_BO_W FC936 F-STL F-application DSAFETY1
16 boolean  word
Type change
F_W_BO FC937 F-STL F-application DSAFETY1
word  16 boolean
F_INT_WR FC938 F-STL F-application DSAFETY1 Indirect writing
F_INT_RD FC939 F-STL F-application DSAFETY1 Indirect reading
Tab. 5.3 F-application blocks in the VASS project library

Saved on 06.12.2012
5.5.2 Variables
The following conventions must be observed for naming the variables in the safety program:
 F_Name: replacement variable from F-program to default program
 Name_F: replacement variable from default program to F-program
 FM_Name: fail-safe bit memory
 F_GLOBDB.VKE0: fail-safe bit memory with logic operation result 0
 F_GLOBDB.VKE1: fail-safe bit memory with logic operation result 1
 F_True: fail-safe input with 1-signal
as long as the bridge for commissioning is inserted.
Fig. 5.17 Bridge for commissioning
Note
If safety switching devices are not yet completely installed in the commissioning phase, they may
be covered in the safety program exclusively with the "F_True" input.
In this case, risks to personnel will have to be ruled out using different measures.
This is the responsibility of the system supplier.

Saved on 06.12.2012
5.5.3 Structure of safety program
An example for configuring and designing the safety program can be found in the project-specific
reference projects.
OB1 is used for calling the safety program.
The call of the FC900 "F_Call" is performed in OB1.
Fig. 5.18 OB1 with call of the safety program
In the FC900 "F_Call", the system blocks generated by the "HW Config" and the FB900 "ARG"
created by the user are called.

Saved on 06.12.2012
FC 900 F-Call
FB 900 ARG
F_RCVDP
FB 901 SK21
FB 90x …
FB 906 Last SK22
F_SENDDP
FC 10 PoT
FC 12 Vorwahlen
FC 13 Betriebsarten
FC 14 1. Station
FB 650 MeldeFB
FC 98 GBA
FC 99 ZAU
Fig. 5.19 Call of the safety program

Saved on 06.12.2012
5.5.4 Integrating safety blocks in STEP 7
The safety blocks are contained in the VASS project library.

The application can be seen in the reference project.
5.5.4.1 "ARG" block call
The FB900 "ARG" is used for configuring the safety program. The blocks for the individual start
circuits, emergency stop drives, load voltages and, if needed, the fail-safe communication via
PROFINET PN/PN coupler, are called in this block. The FB900 blocks contained in the sample
projects as well as the blocks from FB901 to FB9xx serve as template for the safety program to be
created and have to be adapted to the system conditions by the user.
Note
The change log for the safe area, including the entries for the processing person and the checksum
of the safety program must be maintained in the comment field of the FB900.
Fig. 5.20 Comment field of the FB900 block
Note
It must be observed that the ID and I/O addresses have to be adapted to the FSEND and
FRECEIVE block calls.

Saved on 06.12.2012
5.5.4.2 "SK_xy" block calls
The safe input signals for each protective circuit are evaluated in these blocks and summarized
accordingly. For improved program diagnostics, the logic operation results are forwarded using
corresponding output parameters.
Fig. 5.21 "SK_xy" block calls
The following are not components of these blocks:

 Emergency stop signals ( component of the "Not_Halt_Antriebe" block)
 Safe input signals that are effective only within one protective circuit
( direct processing in the load block for the respective protective circuit)
5.5.4.3 "NOT_HALT_ANTRIEBE" block call
In this clock, the signals of the emergency stop operator controls, the robot emergency stop circuits
and the drive switches are evaluated and summarized. Forwarding the logic operation results is done
via corresponding output parameters.
Fig. 5.22 "NOT_HALT_ANTRIEBE" block call

Saved on 06.12.2012
5.5.4.4 "LAST_SK_xy" block calls
In these blocks, the previously built and safe signals are combined with each other and the logic
operation results are output to the safe IO devices. Blocks for protection control are also called in
these blocks. For each protective circuit, a corresponding Last_SK block is formed.
Fig. 5.23 "LAST_SK_xy" block calls

Saved on 06.12.2012
5.5.4.5 Creating an F-runtime group
Fig. 5.24 Creating an F-runtime group
Notice
The maximum cycle time of the F-runtime group must be entered as 50 (ms)

Saved on 06.12.2012
5.6 Generating the safety program

Note
Before generating the safety program, close the applications "LAD/FBD Editor", "Display S7
Reference Data" and "Check Block Consistency" as well as the symbol table.
5.6.1 Procedure for generating the safety program
1. Select the correct F-CPU or the S7 program assigned to it.

2. In the SIMATIC Manager, select the menu command:
"Options  Edit Safety Program".
The "Safety Program" dialog appears.
3. Activate the "Generate" button.
This compiles the safety program.

Alternatively, you can generate the safety program with the "Check Block Consistency" function in
the SIMATIC Manager (see also the "Check Block Consistency" function in Chapter 4.3.2 "Creating
and Editing F-FB/F-FC" in the documentation "Configuring and Programming SIMATIC - S7
Distributed Safety").
5.6.2 Generating the safety program
Generating is possible only for valid F-runtime groups, i.e., no F-blocks may be missing in the F-
runtime group which you defined in the "Edit F-Runtime Groups" dialog.
When generating the safety program, a consistency check is performed. That means, the safety
program is checked for errors and F-blocks which you created in the block container, but do not use in
the F-runtime group. Any error messages are displayed in an error window.
Only those F-blocks that belong to the safety program receive the F-attribute. After a successful
compiling, a consistent safety program is always located in the block container consisting of all the F-
blocks with F-attribute.
The offline block container may contain F-blocks without F-attribute. These are blocks that require the
safety program, but do not have an F-attribute (e.g. SFC14).
After the successful consistency check, the additionally required F-system blocks and the
automatically generated F-blocks are supplemented.
Error messages or warnings detected during compiling are collectively output in a dialog at the end of
the generating process. Warnings are specially marked.
The expand button of the "Generate" button allows you to:

 view and save the generating log of the last generation
 check for "Access from Default"
 enable or disable "Update Reference Data"

Saved on 06.12.2012
5.7 Block update

If updated blocks must be made available via a library update, they must be adopted into the system
project.
To do so, proceed as follows:
 From the "Blocks" folder, copy all required elements into the "Blocks" system folder.
 Regenerating the safety program
 Updating blocks from the standard library
 Checking block consistency
 Performing the Visu update (see Ch. 6.4.2.2 "Required preparations for Delta import type")

Saved on 06.12.2012
SiVArc (Siemens Visualization Architect)
6 SiVArc (Siemens Visualization Architect)
6.1 Introduction
6.1.1 Required basic experience
Good knowledge of SIMATIC STEP 7 and WinCC flexible is required for an understanding of this
documentation. The content is intended to explain the design of this standard to the user and to
enable him or her to independently perform the project-specific adjustments.
6.1.2 Scope of this documentation
The information described in this documentation applies to the software versions of WinCC flexible
and SiVArc according to Tab. 1.1 "Software tools for Windows XP" or Tab. 1.2 "Software tools for
Windows 7 / 64 bit".
Note
The following screen shots are intended only as examples.
The version number shown does not correspond to the released version.
Fig. 6.1 SiVArc Screen Generator
SiVArc is used to carry out various tasks. The Screen Generator automatically generates message
texts and operating screens of the visualization. The SiVArc Screen Generator represents a
connecting link between the control program of the PLC and the visualization project with
WinCC flexible. The functioning of the Screen Generator requires rules set files which are provided by
the Update Manager according to the requirements.

Saved on 06.12.2012
6.2 SiVArc Update Manager

All files required for the VASS standard or the use of the SiVArc Screen Generator are copied to the
corresponding target folder by the SiVArc Update Manager.
At runtime, the Update Manager checks whether the target folders exist in the specified path. If this is
not the case, the folders are automatically created.
Before using the SiVArc Update Manager, it must be checked whether new updates (VASSxxx.zip)
are available.
Double-clicking on the "SiVArc Update Manager" desktop icon opens the "SiVArc Update Manager"
window.
Select the
"Install Standard" option.
Fig. 6.2 "Install standard" selection

Saved on 06.12.2012
Double-clicking opens the "ZIP file" window.
Enter the path in which the new

"VASS.zip" file can be found.
Click on "Next".
Fig. 6.3 Path entry for the "VASS.zip" file

Saved on 06.12.2012
The "Installation of artifacts" window opens.

Under "HmiMetaModel", enter the path where the meta model should be stored.
Under "RootProjects", enter the path where the root project from the "VASS.zip" file should be
unzipped.
Fig. 6.4 Paths in which "Root Project" should be unpacked and "Meta model" should be stored
"Finish" completes the installation of the ZIP file.
Note
The installation of the "VASS.zip" file requires that both directories ("HmiMetaModel" and
"RootProjects") must be entered at all times.

Saved on 06.12.2012
The Setup application properly installs the SiVArc Screen Generator in the program folder of the
system drive.
This is generally:
"C:\Programme\Siemens\SiVArc" (on German operating systems)
Fig. 6.5 Installation in the program folder
or
"C:\Program Files\Siemens\SiVArc" (on English operating systems)

Saved on 06.12.2012
6.3 Preparing the S7 project

6.3.1 Report system errors
Before starting the SiVArc Screen Generator, the CSV files generated with RSE (Report System
Errors) must be checked first. They are required for the PROFINET diagnostics.
See also Chapter 4.2.3 "Report system errors".
Fig. 6.6 Checking the CSV files generated with RSE
6.3.2 STEP 7 integration of the VASS body project
Note
This is required only if the supplied VASS base project is not used.
In the folder "D:\Projects\Siemens\04_WinCCflexible\01_Vorlagen", the "PC677.hmi" file must be

opened.
Fig. 6.7 Opening the "PC677.hmi" file
On the "Project" tab, select

"Integrate in STEP 7" to start the
integration.
Fig. 6.8 Starting the integration

Saved on 06.12.2012
Select the desired STEP 7 project to be

integrated.
Fig. 6.9 Selecting the STEP 7 project
This progress bar shows the status of the

integration.
Fig. 6.10 Progress bar of the integration

Saved on 06.12.2012
After the integration is completed, the following view appears.
Fig. 6.11 View after integration
After the integration, the "HmiEs" folder was created. This folder contains the new WinCC flexible
project.
Fig. 6.12 "HmiEs" folder with new WinCC flexible project

Saved on 06.12.2012
6.4 Screen Generator

The main dialog window of the SiVArc Screen Generator is used to select all the functionalities of the
SiVArc Screen Generator.
1. Select a STEP 7 project

With the first menu item, you select the
STEP 7 project to be generated.
2. Select the program container to

be generated
Of a project contains more than just
one program container, an additional
list provides the option of analyzing a
different container than the preselected
one.
Fig. 6.13 Main dialog window
3. Select a car brand:

This menu item allows selecting the design of the operating screens for the generation according to
the respective group brand.
Fig. 6.14 Selecting a car brand
Note
The selection made becomes active in WinCC flexible only at runtime.
In engineering mode, all brand layouts are visible.

Saved on 06.12.2012
4. Select additional options

If you select the "Check block consistency" item under the fourth menu item, a block consistency
check of the selected program container is performed first after activating the "Generate" button. This
is a standard functionality of SIMATIC STEP 7.
If you select the "Generate messages only" option, no WinCC flexible projects are generated. See also
Chapter 6.4.3 "Generating messages".
Multilingual support:
Under the "Multilingual support" menu item, a second language can be activated for a project so that
switching languages is possible in the project and message texts are also available in two languages.
Fig. 6.15 Multilingual support
Further information about Multilingual support can be found in Chapter 8 "Multiple Languages"

Saved on 06.12.2012
If the STEP 7 project to be generated does not appear in the list in the first menu item, search for it via
the "plus" symbol.
Fig. 6.16 Selecting a STEP 7 project via the "plus" symbol

Saved on 06.12.2012
6.4.1 Settings
Right-clicking on the main window opens a context menu with different setting options.
Language
With the "Language" menu item in the context menu, you toggle the user interface language of the
SiVArc Screen Generator between German and English.
Fig. 6.17 Selecting the user interface language
Settings
With the "Settings..." menu item (or the keyboard shortcut "<Ctrl+O>") in the context menu, clicking on
this item opens the "Settings" dialog of the same name.
Fig. 6.18 Selecting the "Settings" dialog

Saved on 06.12.2012
The input field contains the export

path of the CSM file, which contains
the message texts and message IDs
generated by the SiVArc Screen
Generator.
Fig. 6.19 Export path of the CSM file
Ensure that both paths are valid.

 If the message path is invalid, the XML files of the blocks found are not copied into the
project-specific template folder.
 If the export path should be invalid, no CSV file is being generated.
Under the input field for the export path, you find a selection box named "Open last/only
WinCC flexible project after the import".
Here you specify whether the

respective last (or only) imported
WinCC flexible project should be
opened for editing after a
successfully performed project
import.
Fig. 6.20 Opening a project for editing
To apply your settings, close this dialog with "OK".

Saved on 06.12.2012
Size of system function blocks

The next menu item in the context menu is labeled "Block sizes". Left-clicking on this item (or with the
keyboard shortcut "<Ctrl+B>") opens the "Block Sizes" dialog:
Fig. 6.21 "STEP 7 Block Sizes" dialog
This dialog features a listing of all the system function blocks known to the SiVArc Screen Generator
and used in the project. With the know-how protection of SFBs, they are not read by the SiVArc
Screen Generator.
Note
It is absolutely necessary here to adjust the sizes of the SFBs in the project before the project
generation to the values according to Fig. 6.21 "STEP 7 Block Sizes" dialog ("Block size" column).
Left-clicking on "Add" or "Change" opens the

"Enter Size" input dialog.
Fig. 6.22 "Enter Size" dialog
Close the "Enter Size" dialog with "OK" to apply your settings.
Protocol
A "SiVArc.log" log file is always created in the folder "…\SiVArc\Log". It contains the error messages
after the generation.

Saved on 06.12.2012
6.4.2 Project generation
6.4.2.1 Generating the import file for "Complete" import type
If all desired settings have been made, activating the "Generate" button starts the project generation.
Fig. 6.23 Starting the project generation

Saved on 06.12.2012
Device type selection

After starting the project generation, the "Settings of Panel Type" window opens automatically. Here,
you select the device type for the listed HMI devices.
PC677 15" (1024 x 768):

This selection should be used to
generate the visualization for the
main control station.
A selection at "I1" is required.
MobilePanel 10":
This selection should be used
exclusively to generate independent
WinCC flexible projects for folding
systems.
GBA 15" (1024 x 768):

generate the visualization for a large
screen display.
Fig. 6.24 Setting of the panel type
Close the "Settings of Panel Type" dialog with "Apply" to save your settings.
Note
The generation of the WinCC flexible import file takes approx. 10 … 15 minutes.

Saved on 06.12.2012
After completing the project generation, the following window appears automatically with further notes.
Fig. 6.25
Overview of created text libraries
In the "Import type" column, select individually for every project whether it should be completely
imported or only updated according to the changes in the STEP 7 project.
A "Delta" import type is possible only if the "Complete" import type of the corresponding project was
executed previously.
6.4.2.1.1 "Complete import type"
Selection of the WinCC flexible project and subsequent import of the content of the corresponding
XML file into this project.
Note
For the S7 project it must also be observed that the DB804 to DB811 listed below must be loaded
into the control!
Fig. 6.26 Selection of the WinCC flexible project (Complete import type)
The "Status" field signals the successful completion of the import.

Saved on 06.12.2012
6.4.2.2 Required preparations for "Delta" import type
If a finished system project is available and new elements were added in the S7 logic (e.g. valves),
which are relevant to visualization, it is possible to supplement the visualization for these new
elements.
If faceplates change in the WinCC flexible project library or new faceplates are added, then these
changed or new faceplates are used to create a new external WinCC flexible update library. This
library is also output to the OEMs.
The following pages show an example step by step.
First, the existing WinCC flexible project in which the Delta import should be performed must be
opened. Next, an external WinCC flexible update library is opened in the "Project library" folder.
This is done by marking "Project library"  right-clicking  "Library"  Open.
The "Open global library" window appears next.
Fig. 6.27 Opening the global library

Saved on 06.12.2012
"Open" brings up a new WinCC flexible update library (e. g. "2011.11.17 PC677 update library") under
"Library".
Fig. 6.28 "New" WinCC flexible update library
Marking "Update available type" and  "OK" copies the faceplates from the external WinCC
flexible update library into the existing project library.
If the block exists, it must subsequently be updated.
Fig. 6.29 Search for already existing types
If all blocks have been copied, the update library is closed again.
This is done by marking "Update library"  right-clicking  "Library"  Close.

Saved on 06.12.2012
Automatic faceplate update
Note
This function can be used only for the version "WinCC flexible 2008 SP2 / Update 3" at the present
time!
The SiVArc Update Manager version 2.0.90 and up offers the possibility to automatically update the
faceplates contained in the project.
For this purpose, the "Update project" function under the SiVArc Update Manager must be used.
Select the
"Update project" option.
Fig. 6.30 Update project

Saved on 06.12.2012
Next, the "SIMATIC WinCC flexible module comparison" opens.

In the "SIMATIC WinCC flexible module comparison" window, the WinCC flexible-project to be
updated must be selected under "WCF project file".
Next, the current body project which contains all the current faceplates must be selected under "WCF
project library or external library".
Under the "Setting faceplate comparison/update" menu, "Update (version-independent)" must be
activated.
The update is started with the " " icon.
Fig. 6.31 SIMATIC WinCC flexible module comparison
Next, the updated WinCC flexible project must be opened and the updated faceplates must be
checked.

Saved on 06.12.2012
To be able to check that the same structure names do not appear twice due to new or edited blocks,
the "Structures" folder must be opened.
Fig. 6.32 Opening the "Structures" folder
If structure names have been used multiple times,

these "new" structure names are generated with the
additional ending "_0", "_1", etc. (e.g. "ROBKORR_0",
"ROBKORR_1", etc.).
Fig. 6.33 Creating "new" structure names with endings

Saved on 06.12.2012
Clicking on the "old" existing structure name (here e.g. "ROBKORR") opens the "old" structure.
Fig. 6.34 Opening the "old" structure
Marking "ROBKORR"  right-clicking  on "Cross-reference list" opens the window "Cross-

references for ROBKORR".
The "Comment" field is marked here individually and for all entries in the table and opened by double-
clicking.
Fig. 6.35 Opening the cross-references in the "old" structure

Saved on 06.12.2012
The "Roboter_Kor" line must be selected here.
Fig. 6.36 Adapting the variable name in the "old" structure (1)
"ROBKORR_0" is selected in the "Data type" column to accept the new functionalities.
Fig. 6.37 Adapting the variable name in the "old" structure (2)

Saved on 06.12.2012
Afterwards, the table may no longer have any entry in the "Cross-references for ROBKORR" window.
Fig. 6.38 Checking the "old" structure
In the following figure, the new structure name is adapted in a faceplate (e.g. "SEWAMAV_0"):
Fig. 6.39 Adapting the new structure name in a faceplate

Saved on 06.12.2012
As soon as all existing elements of the old structure have been adapted to the new structure name,
the old structure name should be marked in the structure folder and deleted.
As the following figure shows, only the new structure ("ROBKORR_0") remains.
Fig. 6.40 "Old" structure was deleted
Afterwards, the "Strukturname_0" is renamed. This is done by (marking "ROBKORR_0"  right-

clicking  "Rename").
Fig. 6.41 Renaming the "new" structure

Saved on 06.12.2012
Only the original structure name (without "_0", "_1", etc.) exists now, but it features the new
functionalities.
Fig. 6.42 "New" structure was renamed

Saved on 06.12.2012
6.4.2.3 Generating the import file for "Delta" import type
If all desired settings have been made, activating the "Generate" button starts the project generation.
Fig. 6.43 Starting the project generation

Saved on 06.12.2012

After starting the project generation, the "Settings of Panel Type" window opens automatically. Here,
you select the device type for the listed HMI devices.
GBA 15":
generate the visualization for a large
screen display.
MobilePanel 10":
This selection should be used
exclusively to generate independent
WinCC flexible projects for folding
systems.
PC677 15":
generate the visualization for the
main control station.
Fig. 6.44 Setting of the panel type
Close the "Settings of Panel Type" dialog with "Apply" to save your settings.
Note
The generation of the WinCC flexible import file takes approx. 10 … 15 minutes.

Saved on 06.12.2012
After completing the project generation, the following window appears automatically with further notes.
Fig. 6.45
Overview of created text libraries
In the "Import type" column, select individually for every project whether it should be completely
imported or only updated according to the changes in the STEP 7 project.
A "Delta" import type is possible only if the "Complete" import type of the corresponding project was
executed previously.
6.4.2.3.1 "Delta import type"
This requires selecting the WinCC flexible project. After that, the content of the corresponding XML file
is imported into the selected project.
Note
For the S7 project it must also be observed that the DB804 to DB811 listed below must be loaded
into the control!
Fig. 6.46 Selection of the WinCC flexible project (Delta import type)

Saved on 06.12.2012
For the "Delta" import type, you can select whether to overwrite the content in existing pictures to
generate separate Delta pictures.
Note
Note that the picture link to the template picture for Delta pictures is missing and, for this reason,
must be added manually!
Fig. 6.47 Selection to Overwrite picture or Create Delta picture
Click on "Apply" (in the "Picture Selection for Device Type" dialog at the bottom right) as soon as you
have made the desired settings. The "Cancel" button (also at the bottom right) returns you to the
previous picture. (Fig. 6.46 "Selection of WinCC flexible project - Delta import type").
Note
For all static pictures (basic screen, robot, robot process devices and machine process devices),
only the "Create Delta Image" setting may be used.

Saved on 06.12.2012
After the start, a progress bar appears (replacing data) for the automatic import into the WinCC flexible
body project.
Fig. 6.48 "Replacing Data" progress bar

Saved on 06.12.2012
Fig. 6.49 "Compiling project" progress bar
Note
The import into the WinCC flexible body project requires approx. 20 minutes.

Saved on 06.12.2012
After the project analysis is complete for the desired project, the "Import complete" message appears
under "Status".
This message represents a successful completion of the import.
Fig. 6.50 Import is completed

Saved on 06.12.2012
Changes in the existing WinCC flexible project are displayed in the "DeltaImport.log" file (here e.g.
panel "I1").
Fig. 6.51 Generated "DeltaImport.log" file
This WinCC flexible project must now be opened and the scaling must be performed according to the
listing in the "DeltaImport.log" file.
For this purpose, the "actual" figure and the corresponding "Delta figure" must be opened.
The changes from the "Delta figure" must be cut out and inserted in the "actual" figure.
At the end, after all adaptations have been executed, the "Delta figure" is deleted.

Saved on 06.12.2012
6.4.3 Generating messages
For a control center system, all binary individual messages are co-generated by the SiVArc Screen
Generator and stored in a CSV file under the path "D:\Projects\Siemens\07_ZAÜ".
With a change in the S7 logic that does not affect the visualization, it is also possible to generate the
message list individually.
For this purpose, a check mark must

be placed next to "Generate
messages only" in the adjacent
window.
Fig. 6.52 Generating messages
Note
If the projects become multilingual, a check mark must be placed next to "Multilingual support".
The data block must be copied to the project and the control.

Saved on 06.12.2012
WinCC flexible
7 WinCC flexible
7.1 Starting
This chapter is intended as a support for working with WinCC flexible and lays no claim to
completeness.

An exact description of the functionalities of WinCC flexible can be found in the user manual.
Current information is also available from the contact person in charge at Siemens AG or on the
Internet under the following Internet address: "http://support.automation.siemens.com".
Opening WinCC flexible projects

WinCC flexible distinguishes between two executable files:
 Files with the extension ".hmi" are opened with "WinCC flexible ES". They contain all the
visualization-relevant data. Open these files to edit projects, generate runtime data and
transfer them to the control station.
 Files with the extension ".fwx" are created while generating the project in "WinCC flexible
ES". These files contain all the runtime information and are executed by WinCC flexible RT.

Saved on 06.12.2012
WinCC flexible
7.2 Post-processing in WinCC flexible

7.2.1 Integrating a WinCC flexible project in STEP 7
This is required only if the VASS base project was not used.
According to the project path information (see also Fig. 3.1 "Project data - Folder structure"), a
WinCC flexible body project with the name "PCI677.hmi" exists.
Otherwise, an installation with the SiVArc Update Manager ("VASS.zip") must be performed.
To use the TIA advantages, the WinCC flexible project must be integrated in STEP 7. With integrated
configuring, you access the configuration data of STEP 7 which you created during the configuration
of the control with STEP 7. This provides support for the system error messages and the step
sequencer visualization configured in STEP 7 in WinCC flexible and outputs them on the HMI device.
7.2.1.1 Integration steps from within WinCC flexible
In the "Project" menu, select the "Integrating in STEP 7 …" command.
Fig. 7.1 WinCC flexible - Starting the integration
The "Integrating in STEP 7 …" dialog opens.

Saved on 06.12.2012
WinCC flexible
Select your current STEP 7 project in the dialog.
Fig. 7.2 WinCC flexible - Selecting the STEP 7 project
Confirm the selection with "OK".

Saved on 06.12.2012
WinCC flexible
7.2.1.2 Configuring the connection in STEP 7
In integrated WinCC flexible projects, the communication configuration is performed in the SIMATIC
Manager.
For this purpose, select the newly integrated SIMATIC HMI station in the project window of STEP 7
and open the context menu. IN the context menu, select the "Open Object" command (<Ctrl+Alt+O>).
The properties dialog opens.
For the TCP/IP communication, an Industrial Ethernet CP must be integrated in the hardware
configuration.
In the hardware catalog under "SIMATIC HMI Station", open the "IE General" folder and select the
entry "SW V7.1…".
Add it via drag & drop to slot 1 of your hardware configuration.
Fig. 7.3 WinCC flexible - Configuring the connection in STEP 7

Saved on 06.12.2012
WinCC flexible
After inserting it, the "Properties" dialog opens automatically.
Fig. 7.4 Properties / IE General Ethernet interface (R0&S1)
In the "Properties - IE General Ethernet interface (R0/S1)" dialog window, the following settings must
be made:
 Place a check mark next to "Set MAC address / Use ISO protocol" and enter the MAC
address.
 Place a check mark next to "IP protocol is used". Enter IP address and subnet mask.
 Select "Ethernet[1]" under "Subnet".
The "Assignment" tab opens automatically.
Configure the interfaces you are using.
Confirm the selection with "OK".

Fig. 7.5 Assignment of the interface

Saved on 06.12.2012
WinCC flexible
On the menu bar of "HW Config", select the command "Station  Save and Compile".
Next, close "HW Config".
Result:
The STEP 7 connection between WinCC flexible runtime and the S7 control created in WinCC flexible
in the "Connections" editor is symbolically connected.
7.2.1.3 Renaming the SIMATIC HMI station
In the SIMATIC Manager, you change the name by clicking on the text field of the SIMATIC HMI
station. The name of the SIMATIC HMI station corresponds to the panel number.
In the VASS standard, the system starts with "I1" and counts up sequentially with additional HMI
stations up to "I32".
Fig. 7.6 SIMATIC Manager - Renaming the SIMATIC HMI station
Renaming the SIMATIC HMI station is automatically transferred to the WinCC flexible project file. For
this purpose, "WinCC flexible ES" is briefly opened after the name change.

Saved on 06.12.2012
WinCC flexible
7.2.1.4 Selecting the corresponding S7 station under the "S7-HMI"connection
Fig. 7.7 Enter name under connections with S7-HMI
After the configuration in STEP 7, a new "Verbindung_1" connection is automatically created in the
WinCC flexible project. This new "Verbindung_1" connection must be removed again since the
existing variables in the corresponding variable tables see only the "S7-HMI" connection.
The S7 station must be selected for this "S7-HMI" connection.
Fig. 7.8 Selecting the S7 station
Result for the "S7-HMI" connection and after deleting the "Verbindung_1" connection.
Fig. 7.9 Result for the "S7-HMI" connection and after deleting the "Verbindung_1" connection

Saved on 06.12.2012
WinCC flexible
7.2.2 Step sequencer display with ProAgent
To obtain a display of the step sequencers in the system visualization, the following steps must be
carried out in ProAgent under WinCC flexible:
ProAgent is called up in the WinCC flexible project under "Diagnostics  ProAgent".
Fig. 7.10 Calling up ProAgent

Saved on 06.12.2012
WinCC flexible
1. Mark S7-HMI
Place the check mark accordingly for "S7-HMI" and wait until the progress bar disappears
Fig. 7.11 Marking S7-HMI
2. Step sequencer selection

Selection of the step sequencer (sequential control) in the STEP 7 project
Fig. 7.12 Selection of the step sequencer (sequential control) in the STEP 7 project

Saved on 06.12.2012
WinCC flexible
3. Text entry for using the faceplate

In the "Schrittketten_031" picture, the "Sequential control 110011" text is entered under
"Schrittkettenanzeige_Rahmen_SK02 (faceplate use)  Texts  TextField1".
Afterwards, it appears at the top of the display.
Fig. 7.13 Text entry (faceplate use)
4. Selection of FB/DB
Selection of FB/DB in the "Schrittketten_031" picture under "Schrittanzeige_SK02 (step display)".
Fig. 7.14 Selection of FB/DB

Saved on 06.12.2012
WinCC flexible
5. Mark and copy the prepared step display

Mark the prepared step display in the "Station_Ablaufsteuerung" picture and copy it to the station
picture.
Fig. 7.15 Copying the prepared step display with four buttons to the station picture
6. Insert a function for a button

Mark the button (e.g. "Sequential control").
"Clicking" (under events) attaches a corresponding function to the button as it was parameterized in
advance (e.g. under "Unit Selection").
Fig. 7.16 Parameterization of the "Sequential control" button by "clicking" (under events)

Saved on 06.12.2012
WinCC flexible
7. Change picture pointer instrument

The marked pointer instrument for a picture change must be parameterized for updating the step
sequencer display, as shown in the example.
Fig. 7.17 Parameterizing the pointer instrument for "picture change"
8. Calling up ProAgent
Result: S7 languages in German and in the selected second project language (here: Chinese).
Fig. 7.18 Calling up ProAgent

Saved on 06.12.2012
WinCC flexible
9. All post-processing must be performed in the "German" language.
Fig. 7.19 All post-processing must be performed in the "German" language
10. All post-processing must be performed in the selected second project language (here:
Chinese).
Fig. 7.20 All post-processing must be performed in the selected second project language (here: Chinese)

Saved on 06.12.2012
WinCC flexible
7.2.3 Description and post-processing of operating screens
The SiVArc Screen Generator generates operating screens of the following type:
Name Explanation
ST_xxyyyy_WZ_003 Manual operating screen of station
ST_xxyyyy_RB_003-Rollenbahn Manual operating screen of roller conveyor *)
ST_xxyyyy_SB_003-Stauband Manual operating screen of buffering belt *)
ST_xxxxxx_FWx_003-Framer Manual operating screen of framer *)
ST_xxyyyy_WZ_004 Tool screen of station
Rob_xxyyyy_Rzz_006 Detailed robot display with pertinent process devices
Grundbild_010 Basic screen for menu navigation
Anlagenübersicht_011 System overview
Betriebsarten_012 Operating modes
Vorwahlen_013 Preselections
Roboter_014_Layer1 Robot overview screen
Rob-Prozessgeräte_015 Overview screen of robot process devices
Maschinenprozesse_016 Machine processes
GlobaleStati_017 System completion reports
Werkerruf_018 Request screen for system operator and parts
Statistik_020 Statistics & number of units
Taktzeiten_022 Clock time overview screen
SPS+PN_030 PLC & bus info/diagnostics
PNIO-100_Stationsübersicht Status of PROFINET nodes in list form
PN-Übersicht_019 Status of PROFINET nodes based on spatial arrangement.
SPS_StatusValue SPS_StatusValue
Schrittketten_031 Step sequencer overview
PN/PN_Koppler_ARGx _101 Interfaces
Message display Screen of current messages
Meldearchiv_250 Message archive
Administration Administration
Applications Screen for starting external applications
Detail_SEW_AMA_Bin Detailed screen of SEW drive with AMA binary setpoint value
Detail_SEW_AMA_Var Detailed screen of SEW drive with AMA variable setpoint value
Detail_SEW_Modulo Detailed screen of SEW drive with Modulo
Detailed screen with expanded operating and interface
Detail_SEW_AMX_RB information
Detailed screen with expanded operating and interface
Detail_SEW_AMX_VR information
Detail_SchaltlisteSchicht_105 Detailed screen for display of switching list
Detail_MarkatorxxyyyyPR1 Detailed screen for display of stylus stamping system
Detail_Messen_Perceptron1_1M1 Detailed screen for display of measuring system
Station_Ablaufsteuerung Step sequencer display for manual operating screen
Tab. 7.1 Overview of operating screens

Saved on 06.12.2012
WinCC flexible
*) In order to use the correct template pages, the respective corresponding term "Roller conveyor",
"Buffering belt" and "Framer" must first be entered in the block symbol comment.
However, these terms may not be compiled and, for this reason, receive the ending "_@" (roller
conveyor_@, buffering belt_@ and framer_@).
Some of the operating screens are generated in such a way that they can be used in the visualization
without modification. Other operating screens require a post-processing which is described in the
following chapters.
The operating screens contain all of the brand layouts. They may not be used; otherwise, it could lead
to errors during activation in runtime mode.
Note
The automatic generating process may create additional operating screens for a main screen
which can be called with the "Next screen" navigation.
In this case, it must be checked in general whether a meaningful merging of the screen contents
allows reducing the operating screens.

Saved on 06.12.2012
WinCC flexible
7.2.3.1 Manual operating screens of the station, roller conveyor and buffering
belt
Variant 1: Manual operating screen of the station ("ST_xxyyyy_WZ_003")
Fig. 7.21 Example - manual operating screen of the station before processing ("ST_xxyyyy_WZ_003")

Saved on 06.12.2012
WinCC flexible
Variant 2: Manual operating screen of the roller conveyor ("ST_xxyyyy_RB_003-Rollenbahn")

On the manual operating screen of the roller conveyor, the screen switching buttons for the lifter must
be left-aligned (position x=2).
Fig. 7.22 Example - manual operating screen of the roller conveyor before processing ("ST_xxyyyy_RB_003-
Rollenbahn")

Saved on 06.12.2012
WinCC flexible
Variant 3: Manual operating screen of the buffering belt ("ST_xxyyyy_SB_003-Stauband")

On the manual operating screen of the buffering belt, the "Buffering belt" control element must be
moved to the right until it is completely visible.
Fig. 7.23 Example - manual operating screen of the buffering belt before processing ("ST_xxyyyy_SB_003-
Stauband")

Saved on 06.12.2012
WinCC flexible
Variant 4: Manual operating screen of the framer("ST_xxxxxx_FWx_003-Framer")

On the manual operating screen of the framer, three transparent buttons must be moved onto the
three yellow buttons "Framer TM1", "Framer TM3" and "Framer TM5".
Fig. 7.24 Example - manual operating screen of the framer before processing ("ST_xxxxxx_FWx_003-Framer")
Screen names ST_xxyyyy_WZ_003

ST_xxyyyy_RB_003-Rollenbahn
ST_xxyyyy_SB_003-Stauband
ST_xxxxxx_FWx_003-Framer
Description The operating screens contain the operating elements required
for manual operation.
Dependency Can occur multiple times for each project.
Post-processing Screen elements that are too wide for the intended space are not
correctly positioned by the generator. These elements must be
aligned in a suitable way.
For the step sequencer visualization to be available on the
manual operating screen, it must be taken from the
"Station_Ablaufsteuerung" screen and placed at the intended
position. In addition, the assignment of the step sequencer must
be carried out. See also the explanation in Chapter 7.2.2 "Step
sequencer display with ProAgent".
Tab. 7.2 Manual operating screen of station
Note
The status indicators are built "from bottom to top"; function blocks for the status indicator
instantiated last in S7 are output at the top position in the visualization.

Saved on 06.12.2012
WinCC flexible
Step sequencer display for manual operating screen ("Station_Ablaufsteuerung")
Fig. 7.25 Example - step sequencer display for the manual operating screen ("Station_Ablaufsteuerung")
Variant 1: Manual operating screen of the station ("ST_110030_WZ_003")
Fig. 7.26 Example - manual operating screen of the station after processing ("ST_110030_WZ_003")

Saved on 06.12.2012
WinCC flexible
Variant 2: Manual operating screen of the roller conveyor ("ST_210050_WZ_003-Rollenbahn")
Fig. 7.27 Example - manual operating screen of the roller conveyor after processing ("ST_210050_WZ_003-
Rollenbahn")
Variant 3: Manual operating screen of the buffering belt ("ST_210050_SB1_003-Stauband")
Fig. 7.28 Example - manual operating screen of the buffering belt after processing ("ST_210050_SB1_003-Stauband")

Saved on 06.12.2012
WinCC flexible
Variant 4: Manual operating screen of the framer("ST_xxxxxx_FWx_003-Framer")
Fig. 7.29 Example - manual operating screen of the framer after processing ("ST_xxxxxx_FWx_003-Framer")

Saved on 06.12.2012
WinCC flexible
7.2.3.2 Tool screen of the station ("ST_110030_WZ_004")
Fig. 7.30 Example - tool screen of the station before processing ("ST_110030_WZ_004")
Screen name ST_xxyyyy_WZ_004

Description The operating screens contain the views of the tool with all the
partial and end position checks.
Post-processing The symbols for end positions and component checks are
positioned on the screen according to a fixed grid.
First, a suitable photo of the tool must be inserted. Next, the
symbols must be dragged with the mouse to a specified location
in the visualization.
Tab. 7.3 Tool screen of station

Saved on 06.12.2012
WinCC flexible
Fig. 7.31 Example - tool screen of the station after processing ("ST_110030_WZ_004")

Saved on 06.12.2012
WinCC flexible
7.2.3.3 Detailed robot display with pertinent process devices

("Rob_110010R01_006")
Fig. 7.32 Example - detailed robot screen with corresponding process devices ("Rob_110010R01_006")
Screen name Rob_xxyyyyRzz_006

Description Contains all operating and interface information for the robot,
including the operation of the process devices that belong to the
robot.
Post-processing In online mode, it must be checked whether the texts for the
individual bits of the interface are correctly entered. If not, is must
be checked whether the entries in the symbol table of S7 have
been made correctly.
Tab. 7.4 Detailed robot display with pertinent process devices

Saved on 06.12.2012
WinCC flexible
7.2.3.4 Basic screen for menu navigation ("Grundbild_010")
Fig. 7.33 Example - basic screen for menu navigation ("Grundbild_010")
Screen name Grundbild_010

Description Contains the basic screen of the system with navigation options
to all other screens.
Dependency Exists only once for each project.
Post-processing None.
Tab. 7.5 Basic screen for menu navigation

Saved on 06.12.2012
WinCC flexible
7.2.3.5 System overview ("Anlagenübersicht_011")
Fig. 7.34 Example - system overview screen before processing ("Anlagenübersicht_011")
Screen name Anlagenübersicht_011

Description Contains the system overview.
Post-processing - The system overview screen must be designed according to the
system overview screen in EPLAN. The system overview in
EPLAN must first be checked for correspondence using the
system layout.
- Outlines must be created using static lines or circle elements.
- For emergency stop and protective screen door elements, the
real name of the element must be determined based on the
symbol name via the parameter assignment at the module FB
and positioned according to the layout.
- Light barriers must be aligned accordingly, whereby element
and text field can be aligned separately.
- The individual station symbols must be positioned according to
the layout.
- Two faceplates are positioned for each robot, aligned at 45° and
90°. The matching one must be rotated and positioned according
to the EPLAN. The remaining one must be deleted.
The corresponding invisible button must be positioned over the
faceplate and the text field must be aligned.
Tab. 7.6 System overview

Saved on 06.12.2012
WinCC flexible
Fig. 7.35 Example - system overview screen after processing ("Anlagenübersicht_011")

Saved on 06.12.2012
WinCC flexible
7.2.3.6 Operating modes ("Betriebsarten_012")
Fig. 7.36 Example - operating modes ("Betriebsarten_012")
Screen name Betriebsarten_012

Description Contains the operating modes.
Post-processing If several operating mode screens are being generated, then the
individual operating mode screen symbols must be distributed
meaningfully on the screens according to protective circuits.
Tab. 7.7 Operating modes

Saved on 06.12.2012
WinCC flexible
7.2.3.7 Preselections ("Vorwahlen_013")
Fig. 7.37 Example - preselections ("Vorwahlen_013")
Screen name Vorwahlen_013

Description Contains the preselections.
Post-processing The generator places almost all symbols automatically. It is
possible that symbols are not placed optimally. They should be
moved to the locations that are meaningful for the respective
system configuration.
If several preselection screens are being generated, then the
individual preselection screen symbols must be distributed
meaningfully on the screens according to protective circuits.
Tab. 7.8 Preselections

Saved on 06.12.2012
WinCC flexible
7.2.3.8 Robot overview screen ("Roboter_014_Layer1")
Fig. 7.38 Example - robot overview screen ("Roboter_014_Layer1")
Screen name Roboter_014_Layer1

Description Contains the overview of all robots contained in the system
project.
Post-processing All robot symbols are automatically generated by the generator.
In the process, up to six robot symbols are automatically placed
on a screen. For system configurations with more than six robots,
they are arranged on additional robot overview screens. Screen
navigation buttons are automatically created for this purpose in
order to call up these screens.
For certain system configurations, it may be meaningful that the
first six robots are already distributed to several operating
screens in order to achieve a logical grouping.
Tab. 7.9 Robot overview screen

Saved on 06.12.2012
WinCC flexible
7.2.3.9 Overview screen of robot process devices ("Rob-Prozessgeräte_015")
Fig. 7.39 Example - overview screen of robot process devices ("Rob-Prozessgeräte_015")
Screen name Rob-Prozessgeräte_015

Description Contains the overview of robot process devices.
Post-processing Procedure is analogous to the robot overview screens.
All robot process devices symbols are automatically generated
by the generator. In the process, up to six robot process devices
symbols are automatically placed on a screen. For system
configurations with more than six robot process devices, they are
arranged on additional overview screens of robot process
devices. Screen navigation buttons are automatically created for
this purpose in order to call up these screens.
For certain system configurations, it may be meaningful that the
first six robot process devices are already distributed to several
operating screens in order to achieve a logical grouping.
Tab. 7.10 Overview screen of robot process devices

Saved on 06.12.2012
WinCC flexible
7.2.3.10 Machine processes ("Maschinenprozesse_016")
Fig. 7.40 Example - machine processes ("Maschinenprozesse_016")
Screen name Maschinenprozesse_016

Description Contains the overview of machine processes.
Post-processing None
Tab. 7.11 Machine processes

Saved on 06.12.2012
WinCC flexible
7.2.3.11 System completion reports ("GlobaleStati_017")
Fig. 7.41 Example - system completion reports ("GlobaleStati_017")
Screen name GlobaleStati_017

Description Contains the overview of all completion reports of the system.
Post-processing All global statuses are collected by the generator and displayed
on the operating screen. The completion reports are formed from
bottom to top. If necessary, the completion reports must be
brought into a logical order that corresponds to the system
sequence.
Tab. 7.12 System completion reports

Saved on 06.12.2012
WinCC flexible
7.2.3.12 Request screen for system operator and parts ("Werkerruf_018")
Fig. 7.42 Example - request screen for operators and parts ("Werkerruf_018")
Screen name Werkerruf_018

Description For each manual work station, it contains a selection for
requesting an operator or up to five types of part supply.
Tab. 7.13 Request screen for system operator and parts

Saved on 06.12.2012
WinCC flexible
7.2.3.13 Statistics & number of units ("Statistik_020")
Fig. 7.43 Example - statistics & number of units ("Statistik_020")
Screen name Statistik_020

Description Contains statistical information about clock time, number of units
and buffer statuses.
Post-processing Generally none.
Tab. 7.14 Statistics & number of units
Notice
In exceptional cases, a post-processing may be required. It must be coordinated with electrical
engineering.

Saved on 06.12.2012
WinCC flexible
7.2.3.14 Clock time overview screen ("Taktzeiten_022")
Fig. 7.44 Example - clock time overview screen ("Taktzeiten_022")
Screen name Taktzeiten_022

Description Contains all clock time detections contained in the S7 project.
Post-processing If necessary, a meaningful grouping must be performed.
Tab. 7.15 Clock time overview screen

Saved on 06.12.2012
WinCC flexible
7.2.3.15 PLC & bus info/diagnostics ("SPS+PN_030")
Fig. 7.45 Example - PLC & bus info/diagnostics before processing ("SPS+PN_030")
Screen name SPS+PN_30

Description Contains the diagnostic information for PROFINET and PLC.
Post-processing From the "Vorlage_SPS+PN_30" screen, the two message
indicator elements and the navigation button must be copied and
inserted in the "SPS+PN_30" screen. This is required since these
elements cannot be placed automatically.
Tab. 7.16 PLC & bus info/diagnostics

Saved on 06.12.2012
WinCC flexible
Fig. 7.46 Example - template for PLC & bus info/diagnostics ("SPS+PN_030")
Fig. 7.47 Example - PLC & bus info/diagnostics after processing ("SPS+PN_030")

Saved on 06.12.2012
WinCC flexible
7.2.3.16 PNIO-100 station overview ("PNIO-100_Stationsübersicht")
Fig. 7.48 Example – PNIO-100 station overview ("PNIO-100_Stationsübersicht")
Screen name PNIO-100_Stationsübersicht

Description This screen represents the status of the PROFINET nodes in list
form.
Dependency None
Post-processing Select the "PN overview" button and enter "PN Overview_019"
under "Events  Click  Activate picture" as picture name or
select from the list of pictures (see Fig. 7.49 Post-processing).
Tab. 7.17 PNIO-100_Stationsübersicht
Fig. 7.49 Post-processing

Saved on 06.12.2012
WinCC flexible
7.2.3.17 PROFINET overview ("PN-Übersicht_019")
Fig. 7.50 Example – PN overview 019 ("PN-Übersicht_019")
Screen name PN-Übersicht_019

Description This screen represents the status of the PROFINET nodes based
on the spatial arrangement in the system.
Dependency None
Post-processing - The PROFINET overview screen must be designed according
to the system overview screen in EPLAN. The system overview
in EPLAN must first be checked for correspondence using the
system layout.
- Outlines must be created using static lines or circle elements.
- The PROFINET nodes must be placed on the screen based on
their spatial position.
Tab. 7.18 PN-Übersicht_019

Saved on 06.12.2012
WinCC flexible
Fig. 7.51 Example – PN overview 019 after processing ("PN-Übersicht_019")

Saved on 06.12.2012
WinCC flexible
7.2.3.18 PLC status value ("SPS_StatusValue")
Fig. 7.52 Example - PLC status value ("SPS_StatusValue")
Screen name SPS_StatusValue

Description This screen allows monitoring the status of PLC variables without
having to start S7.
Dependency None
Tab. 7.19 SPS_StatusValue

Saved on 06.12.2012
WinCC flexible
7.2.3.19 Step sequencer overview ("Schrittketten_031")
Fig. 7.53 Example - step sequencer overview ("Schrittketten_031")
Screen name Schrittketten_031

Description Contains the overview of all step sequencers set up in the
system.
Post-processing See chapter 7.2.2 "Step sequencer display with ProAgent".
Tab. 7.20 Step sequencer overview
Note
If an S7 project should not contain any step sequencers, all "Schrittketten_031" screens must be
deleted from the WinCC flexible project.
In addition, the "Step sequencer" button must be removed from the basic screen.
This prevents warnings from being generated when generating the "runtime".

Saved on 06.12.2012
WinCC flexible
7.2.3.20 Interfaces ("PN/PN_Koppler_ARG2_101")
Fig. 7.54 Example - interfaces ("PN/PN_Koppler_ARG2_101")
Screen name PN/PN_Koppler_ARG2_101

Description The status of the single bits of the interface via the PN/PN
coupler to the adjacent PLC can be monitored on this screen.
Post-processing In online mode, it must be checked whether the texts for the
individual bits of the interface are correctly entered. If not, is must
be checked whether the entries in the symbol table of S7 have
been made correctly.
Tab. 7.21 Interfaces

Saved on 06.12.2012
WinCC flexible
7.2.3.21 Screen of current messages ("Message display")
Fig. 7.55 Example - screen of current messages ("Message display")
Screen name Message display

Description Contains the display of the currently queued message.
Tab. 7.22 Screen of current messages

Saved on 06.12.2012
WinCC flexible
7.2.3.22 Message archive ("Meldearchiv_250")
Fig. 7.56 Example - message archive ("Meldearchiv_250")
Screen name Meldearchiv_250

Description Contains the display of all messages saved in the archive.
Tab. 7.23 Message archive

Saved on 06.12.2012
WinCC flexible
7.2.3.23 Administration ("Administration")
Fig. 7.57 Example - administration ("Administration")
Screen name Administration

Description Contains cross-project functionalities.
Tab. 7.24 Administration

Saved on 06.12.2012
WinCC flexible
7.2.3.24 Screen for starting external applications ("Applikationen")
Fig. 7.58 Example - screen for starting external applications ("Applikationen")
Screen name Applications

Description Contains the starting of external applications.
Post-processing Depending on the operating system, the button that is not
required as well as the information field must be deleted.
Tab. 7.25 Screen for starting external applications

Saved on 06.12.2012
WinCC flexible
7.2.3.25 Detailed screen of SEW drive with AMA binary setpoint value
("Detail_SEW_AMA_Bin")
Fig. 7.59 Example- detailed screen of SEW drive with AMA binary setpoint value ("Detail_SEW_AMA_Bin")
Screen name Detail_SEW_AMA_Bin

Description Contains the detailed screen with expanded operating and
interface information.
Tab. 7.26 Detailed screen of SEW drive with AMA binary setpoint value

Saved on 06.12.2012
WinCC flexible
7.2.3.26 Detailed screen of SEW drive with AMA variable setpoint value
("Detail_SEW_AMA_Var")
Fig. 7.60 Example - detailed screen of SEW drive with AMA variable setpoint value ("Detail_SEW_AMA_Var")
Screen name Detail_SEW_AMA_Var

Tab. 7.27 Detailed screen of SEW drive with AMA variable setpoint value

Saved on 06.12.2012
WinCC flexible
7.2.3.27 Detailed screen of SEW drive with Modulo ("Detail_SEW_Modulo")
Fig. 7.61 Example - detailed screen of SEW drive with Modulo ("Detail_SEW_Modulo")
Screen name Detail_SEW_Modulo

Tab. 7.28 Detailed screen of SEW drive with Modulo

Saved on 06.12.2012
WinCC flexible
7.2.3.28 Detailed screen of SEW drive with AMX_RB ("Detail_SEW_AMX_RB")
Fig. 7.62 Example - detailed screen of SEW drive with AMX_RB ("Detail_SEW_Modulo")
Screen name Detail_SEW_AMX_RB

Tab. 7.29 Detailed screen of SEW drive with AMX_RB

Saved on 06.12.2012
WinCC flexible
7.2.3.29 Detailed screen of SEW drive with AMX_VR ("Detail_SEW_AMX_VR")
Fig. 7.63 Example - detailed screen of SEW drive with AMX_VR ("Detail_SEW_AMX_VR")
Screen name Detail_SEW_AMX_VR

Tab. 7.30 Detailed screen of SEW drive with AMX_VR

Saved on 06.12.2012
WinCC flexible
7.2.3.30 Detailed screen for display of switching list

("Detail_SchaltlisteSchicht_105")
Fig. 7.64 Example - detailed screen for display of switching list ("Detail_SchaltlisteSchicht_105")
Screen name Detail_SchaltlisteSchicht_105

Description Contains the display of the switching list with daily events for the
current and following day.
Tab. 7.31 Detailed screen for display of switching list

Saved on 06.12.2012
WinCC flexible
7.2.3.31 Detailed screen for display of stylus stamping system

("Detail_Markator120050PR1")
Fig. 7.65 Example - detailed screen for display of stylus stamping system ("Detail_Markator120050PR1")
Screen name Detail_Markator120050PR1

Tab. 7.32 Detailed screen for display of stylus stamping system

Saved on 06.12.2012
WinCC flexible
7.2.3.32 Detailed screen for display of measuring system

("Detail_Messen_Perceptron1_1M1")
Fig. 7.66 Example - detailed screen for display of measuring system ("Detail_Messen_Perceptron1_1M1")
Screen name Detail_Messen_Perceptron1_1M1

Tab. 7.33 Detailed screen for display of measuring system

Saved on 06.12.2012
WinCC flexible
7.2.3.33 Step sequencer display for manual operating screen

("Station_Ablaufsteuerung")
Fig. 7.67 Example - step sequencer display for the manual operating screen ("Station_Ablaufsteuerung")
Screen name Station_Ablaufsteuerung

Description Contains the template of the step sequencer display for the
"manual operating screen of the station" (see also Chapter
7.2.3.1 "Manual operating screen of the station").
Tab. 7.34 Step sequencer display for manual operating screen

Saved on 06.12.2012
WinCC flexible
7.2.3.34 Configuration of user-defined pictures
In exceptional cases, it may be necessary to create your own pictures.

To create a new WinCC flexible picture, click on the "Pictures" folder in the project tree and then on
the "New" icon. A new, empty picture is being generated and placed in the "Pictures" project folder.
Change the picture name and place the desired picture objects.
Fig. 7.68 Creating a new picture
All user-defined variables must be stored in the "User-defined" folder. It is created in the project path
under "Communication  Variables". The acquisition cycle must be entered as 200 ms for all
variables.
Fig. 7.69 Variable window

Saved on 06.12.2012
WinCC flexible
7.2.4 Roles for post-processing for Delta imports (SiVArc Screen

Generator)
Depending on the selection made for the Delta import in Chapter 6.4.2.3 "Generating the import file for
Delta import type" / Fig. 6.47 "Selection to Overwrite picture or Create Delta picture", new pictures and
Delta pictures are created after the Delta import or existing pictures are overwritten, and different post-
processing is required.
Note
For all variants (Overwrite picture, Create Delta picture and Create picture), the check mark must
be placed next to "Use Template" in each case in the pictures of the WinCC flexible project.
Fig. 7.70 Check mark set for "Use Template"

Saved on 06.12.2012
WinCC flexible
7.2.4.1 Overwritten pictures
No special procedure is required here. You can proceed as described under Chapter 7.2.3
"Description and post-processing of operating screens".
Fig. 7.71 Result of overwritten picture with added valve

Saved on 06.12.2012
WinCC flexible
7.2.4.2 Newly added pictures
If newly added pictures are created, it must be checked whether the picture symbols they contain must
be manually assigned to an existing picture. If this is the case, the elements should be copied to the
correct position in the existing picture. Afterwards, the new picture should be deleted.
If the elements must not be assigned to any existing picture, proceed as described under Chapter
7.2.3 "Description and post-processing of operating screens".
Fig. 7.72 Result of new picture with added valves

Saved on 06.12.2012
WinCC flexible
7.2.4.3 Delta pictures
If delta pictures are created, it must be checked whether the picture symbols they contain must be
manually assigned to an existing picture. If this is the case, the elements should be copied to the
correct position in the existing picture. Afterwards, the delta picture must be deleted.
If the elements must not be assigned to any existing picture, proceed as described under Chapter
7.2.3 "Description and post-processing of operating screens".
Fig. 7.73 Result of delta picture with added valves

Saved on 06.12.2012
WinCC flexible
7.2.5 Updating faceplates
Faceplates can be updated in a finished WinCC flexible project.

This requires the following steps:
Integrate the faceplate library in WinCC flexible and open the library.
Fig. 7.74 Opening the library

Saved on 06.12.2012
WinCC flexible
Select the desired library.
Fig. 7.75 Selecting the library
Next, select the faceplate to be updated from the faceplate library.
Fig. 7.76 Selecting the faceplate

Saved on 06.12.2012
WinCC flexible
The faceplate to be updated must be transferred to the project library.
Fig. 7.77 Copying and transferring the faceplate
Finally, close the library.
Fig. 7.78 Closing the library

Saved on 06.12.2012
WinCC flexible
7.2.6 Generating the WinCC flexible runtime project
To use a WinCC flexible project in runtime, it is necessary to generate a runtime project. To do so, all
temporary project files must first be deleted. On the menu bar, click on "Options" and select "Delete
Temporary Files". A corresponding message appears next in the message window.
Fig. 7.79 "Delete Temporary Files" menu item

Saved on 06.12.2012
WinCC flexible
Upon selecting the "Regenerate All…" button, the WinCC flexible project is completely being
generated.
It is located in the project path under "Project  Generator".
Fig. 7.80 "Regenerate All…" menu item
Note
The generation of the WinCC flexible project must be free of errors.
Only error-free generated projects are transferred into the runtime loaded on the target device in
the system.

Saved on 06.12.2012
WinCC flexible
If the project should be generated after the import to WINCC flexible, two different generating
processes are available for version SP3 / Update2 with modified "HmiES.exe.config" file.
1. Regenerate everything via the menu "Project  Generator  Regenerate all":

This generation process features synchronization. As such, synchronization is performed
first after the start of the generation process.
2. Generating via generation symbol:

This generation process does not feature synchronization. In this case, the initial
synchronization is skipped, leading to significantly shorter generation times.
Fig. 7.81 Generating via generation symbol
Note
For initial generation and for changes in the "HW_Config", it is mandatory to use variant 1
"Regenerate all".

Saved on 06.12.2012
WinCC flexible
7.3 GBA (large picture display)

For the required FBs (FB105, …, FB621), the entry must be supplemented with "I33".
See also Chapter 4.6.3 "Keyword HMI".
Fig. 7.82 Supplement entry of required FBs with "I33"

After starting the project generation,
the "Settings of Panel Type"
window opens automatically. Here,
you select the "GBA" device type.
Fig. 7.83 Device type selection
The additional steps for the project generation are described in detail starting with Chapter 6.4.2.1
"Generating the import file for "Complete" import type".

Saved on 06.12.2012
WinCC flexible
Fig. 7.84 Sample – GBA_Bild
Note
For each protective screen door that is detected via the module FB_105 (protective circuit) or
FB_106 (protective circuit_16), 8 screen elements are created via the generator to have one
element for each orientation.
The doors may not be rotated or mirrored, otherwise they will no longer be correctly displayed on
the GBA.
From these 8 elements, the matching one must be selected for the proper position representation
of the respective door.
The other 7 elements for this door must be deleted.

Saved on 06.12.2012
WinCC flexible
7.3.1 Description for merging from several GBA projects
Renaming "GBA_Bild" to "GBA_Bild_control name"

e.g. "GBA_Bild"  "GBA_Bild_KASTAN1"
Fig. 7.85 Renaming "GBA_Bild"
Renaming the variables from "@Generator" with prefix "ControlName_"

e.g. "GBA_11"  "KASTAN1_GBA_11"
Fig. 7.86 Renaming the variables from "@Generator"

Saved on 06.12.2012
WinCC flexible
Renaming the name from "Connections" from "S7-HMI" to "S7-HMI_ControlName"

e.g. "S7-HMI"  "S7-HMI_KASTAN1"
Fig. 7.87 Renaming the name from connections
Renaming the instantiated faceplates with the prefix "ControlName_"

Since all GBA faceplates start with "GBA_", the function "Replace in working area" can be used.
e.g. Find what: "GBA_"  Replace with: "KASTAN1_GBA_"  "Replace All"
Fig. 7.88 Renaming the instantiated faceplates

Saved on 06.12.2012
WinCC flexible
Merging the GBA figures from several WinCC flexible projects into a common WinCC flexible project.
Fig. 7.89 Merging the GBA figures from several WinCC flexible projects
Adaptation of the TCP/IP address of the HMI device while observing different TCP/IP addresses of the
controllers.
Fig. 7.90 Merging the GBA figures from several WinCC flexible projects

Saved on 06.12.2012
WinCC flexible
The "Protective circuit" template must be copied accordingly before being used.
e.g. 10 protective circuits in the system require 10 copies
Fig. 7.91 Copy of "Protective circuit" template

Saved on 06.12.2012
WinCC flexible
Selection of the generated variable from the "@Generator" folder for "Schutzkreis_AnimFlaeche" and
"Schutzkreis_AnimText" under "Properties Animation  Design".
Fig. 7.92 Selection of generated variable from the "@Generator" folder
For the system overview, the required faceplates must be placed on the real system on the
"GBA_Vorderseite" and with a copy of it on the "GBA_Rückseite".
Fig. 7.93 Copy of required faceplates for system overview

Saved on 06.12.2012
WinCC flexible
Creation of system overview with the faceplates from the project-based GBA screens in
"GBA_Anlagenuebersicht_01".
The front and back sides are identical.
Fig. 7.94 Creation of system overview with the faceplates from the project-based GBA screens
All faceplates "Fire alarm pre-alarm" and "Fire alarm main alarm" in the system project coming from
different controllers must be placed at level 30 (and in all figures to be used).
Fig. 7.95 View of levels 00 - 30
Fig. 7.96 View of levels 00 - 29

Saved on 06.12.2012
WinCC flexible
The "Statistics" faceplates are placed before the last controller in the project sequence.
Fig. 7.97 Placing the "Statistics" faceplates before the last controller
Remove the "Bildumschaltung_01-02" pointer instrument if all the required information can be placed
in a screen "GBA_Anlagenuebersicht_01".
Fig. 7.98 Removing the "Bildumschaltung_01-02" pointer instrument

Saved on 06.12.2012
WinCC flexible
Fill the next "GBA_Anlagenuebersicht_02" screen, preferably only with Statistics, if the
"GBA_Anlagenuebersicht_01" screen is insufficient.
Fig. 7.99 Filling the next "GBA_Anlagenuebersicht_02" screen
The screen switching is done time-controlled. This currently corresponds to 20 seconds.

Under "Events  Change  Activate screen", change the screen name from
"GBA_Anlagenuebersicht_03" to "GBA_Anlagenuebersicht_01".
Fig. 7.100 Changing the screen name "GBA_Anlagenuebersicht_03" to "…_01"
If the aforementioned screens are insufficient, the next "GBA_Anlagenuebersicht_03" screen can be
used following the above scheme.

Saved on 06.12.2012
Multiple languages
8 Multiple languages
Overview table for multilingual texts
Source Intended use Creating multiple languages

STEP 7
Symbol table - Meld_4- & Creation of a multilingual
Meld_8 message texts symbol table in CSV format by the
plant constructor for processing with the
- Inputs and outputs for SiVArc generator
robot details
- Inputs and outputs for

gateways
Report system - Message texts of PROFInet No special measure required

errors devices error messages
Message system
Message text Display of messages in Using provided resource files in
WinCC flexible D:\Projects\Siemens\03_SiVArc\01_Metamodell\
VASS\HmiMetaModel\Resources
WinCC flexible
Project texts Default texts for static Translation of project texts using the
graphics, provided user dictionary
e.g. for "Detail_SEW_AMA"
etc.
Other texts Translation of project texts by the

plant constructor
Faceplate texts Faceplate interface Using provided resource files in

D:\Projects\Siemens\03_SiVArc\01_Metamodell\
VASS\HmiMetaModel\Resources
Tab. 8.1 Overview for multilingual texts

Saved on 06.12.2012
Multiple languages
8.1 STEP 7
8.1.1 Language-neutral saving
You reach the following property view by selecting the project name, right-clicking and selecting
"Object properties".
The setting must be performed as shown in the following screenshot.
Fig. 8.1 Language-neutral saving
Note
For STEP 7 projects, a check mark must be placed next to "Can be opened under any Windows
language settings (language-neutral)" in the "Properties - Project" window on the "General" tab in
order to save them language-neutral.

Saved on 06.12.2012
Multiple languages
8.1.2 Managing multilingual texts
8.1.2.1 Setting the language for the indicators
Fig. 8.2 Setting the language for the indicators
The following language selections must be made exclusively for the languages used in the company
group:
Language
English (US)
Czech (Czech Republic)
Spanish (International Sort)
Portuguese (Brazil)
Russian (Russia)
Slovak (Slovakia)
Chinese (PRC)
Tab. 8.2 Permissible language selections

Saved on 06.12.2012
Multiple languages
8.1.2.2 Preparing the symbol table in the S7 program
DB numbers of TextLibs
Symbol Address Data type Comment

TextLib0de-DE DB804 DB804 Text library 0 (max. 1024 message texts)
TextLib0zh-CN DB814 DB814 Text library 0 (max. 1024 message texts)
TextLib0xx-XX DB824 DB824 Text library 0 (max. 1024 message texts)
Tab. 8.3 DB numbers of TextLibs
Replacement code for country ID in symbol table (for xx-XX):
Language Identification
English en-US
Czech cs-CZ
Spanish es-ES
Portuguese (BR) pt-BR
Russian ru-RU
Slovak sk-SK
Tab. 8.4 Replacement code for country ID in symbol table

Saved on 06.12.2012
Multiple languages
8.1.2.3 Export of project texts
In SIMATIC Manager, open the project to be edited.

Select the menu item "Options  Manage Multilingual Texts  Export...".
Fig. 8.3 Export of project texts
8.1.2.3.1 Preparing target language and text types for translation files / executing the
export
Storage location (path)

 Select the project folder of your STEP 7 user project.
Format
 Select "Excel Workbook (*.xls)".
Languages
 Select your desired target language.
The source language is "German".
Text Types
 "Title and Comments" must be
selected and "Display Texts"
deselected. Click on "Select" to
select the text types.
Fig. 8.4 Exporting user texts

Saved on 06.12.2012
Multiple languages
8.1.2.3.2 Selection of text types
 SymbolComment Symbol comment

 NetworkTitle Network title
 NetworkComment Network
comment
 BlockTitle Block title
 BlockComment Block
comment
 S7GraphStateName
S7-GRAPH step
name extension
 S7GraphStateComment S7 GRAPH
step comment
Fig. 8.5 Selecting text types
8.1.2.3.3 Providing the created text files from the export directory for translation
Fig. 8.6 Providing the created text files from the export directory for translation
In the export directory, an Excel file is created for each text type.
In addition, the "export.txt" log file is created with information about the export process.
In the Excel files, the corresponding text is entered in two columns.
The 1st column features the source text, the 2nd column the previous source text or already existing
text in the target language.
The target text must now be entered in the respective language.

Saved on 06.12.2012
Multiple languages
8.1.2.3.4 Example of an Excel file with German source and target text
Fig. 8.7 Sample Excel file (Ger / Ger)

Saved on 06.12.2012
Multiple languages
8.1.2.4 Import of translated project texts
8.1.2.4.1 Example of an Excel file with German source and English target text
Fig. 8.8 Sample Excel file (Ger / Eng)
8.1.2.4.2 Opening the project to be edited
In SIMATIC Manager, open the project to be edited.

Now select the menu item "Options  Manage Multilingual Texts  Import…".
Fig. 8.9 Importing the translated Excel files

Saved on 06.12.2012
Multiple languages
8.1.2.4.3 Filling out the "Import User Texts" dialog and executing the import

 Select the storage
location of the files
to be exported.
Format
 Select the file
format (generally
"*.xls").
Start the import with "OK".
Fig. 8.10 Importing user texts
8.1.2.4.4 Completion report of the import
The log file that was created directly during the import, can be displayed by clicking on "Yes".
Fig. 8.11 Language Tool
Note
For later use of the SiVArc Screen Generator, the "SymbolComment.xls" file must be stored as
"SymbolComment.csv" in the STEP 7 project.
Note
For the Russian and Chinese language, the xls files must be saved with Excel in the "Unicode-txt"
format.
Afterwards, the file extension ".txt“ must be changed in Explorer to ".csv".

Saved on 06.12.2012
Multiple languages
8.1.3 Implementing the language management block in the S7 program
The PLC makes the messages from WinCC flexible available with the FB650. The FB650 also
represents the IDs of the messages as texts.
These texts are stored in a sequence of DBs (see Table 8.1.2.2 "DB numbers of TextLibs").
The FB651 directs the pointer of the FB650 to the correct DB sequence (language selection).
In OB1, FB651 must be called before FB650.
8.1.3.1 Executing FB 651 "LMsg"
To transfer the TextLibs required for the language selection, the "MeldeFBDB_TextLibs" IN parameter
must be supplied with a pointer at the FB 651 "LMsg" (Language Message). It points to the first
TextLib (TextLib0) in the instance DB of FB 650 ("P#DB650.DBX2.0")
Fig. 8.12 FB 651 "LMsg"

Saved on 06.12.2012
Multiple languages
8.1.3.1.1 Input parameter
Name Type Description

Release BOOL "1" signal: The release for language switching is set.
"0" signal: The release for language switching is not set.
However, the DB numbers of the selected "target language"
are copied to the instance DB of the FB800
("MeldeFBDB_TextLibs" pointer).
Target language INT The desired target language must be specified as numeric
value at this parameter. The following values represent the
following target languages:
1: German (single-byte character)
2: Placeholder for additional language (single-byte character)
3: Chinese (double-byte character)
The corresponding DB TextLibs are used depending on the
selected target language. If an invalid target language is
specified, a new error is output and the target language is
internally set to "1: German".
MsgView POINTER Pointer in the pointer format to the start area of the data block
for the message view.
MsgArchive POINTER Pointer in the pointer format to the start area of the data block
for the message archive.
MeldeFBDB_TextLibs ANY Pointer in ANY pointer format to the first DB TextLib (TextLib0)
in the instance data block of the FB800 "Report FB". The DB
numbers of the TextLibs are ranged/copied on/starting at this
address. Reason for ANY and not POINTER: If the POINTER
type is used, it leads to a fault/warning in an FB consistency
check since it is not allowed tom access a BLOCK_DB type
using POINTER. For this reason, the ANY type is used.
However, the ANY type should not be parameterized as
"P#DB800.DBX2.0 WORD 1", since the first BLOCK_DB would
be recognized, the symbolic address be entered and a
POINTER be created; better would be "P#DB800.DBX2.0
WORD 8" (Note: The ANY pointer length is not being analyzed
in the FB.)
Tab. 8.5 Input parameter
8.1.3.1.2 Output parameter

StoerWarnMeld BOOL Collective bit for fault, warning and message. If a fault, warning
and message is present, the FB sets the parameter to "1"
signal. The individual faults, warnings and messages are
mapped to STAT variables in the FB (StoerIntern,
WarnMeldIntern) (partially assigning/setting). In addition, if a
MsgID is not found in the TextLibs, this MsgID is stored in
STAT variables "Daten.MsgID_FehlerBeiView" and
"Daten.MsgID_FehlerBeiArch".
Tab. 8.6 Output parameter

Saved on 06.12.2012
Multiple languages
8.1.3.1.3 Input and output parameter

StartMsgView BOOL Start starts the processing of the language switching in the data
block for the message view with "1" signal. If the processing is
ended by the FB, the signal is set to "0" signal by the FB. The
start is executed only with "release=1".
StartMsgArchive BOOL Start starts the processing of the language switching in the data
block for the message archive with "1" signal. If the processing
of the FB is finished, the FB sets the signal to "0" signal. The
start is executed only with "release=1".
QuittStoer BOOL Setting to "1" signal resets all queued faults, warnings and
messages. The parameter is then independently reset by the
FB to "0" signal.
Tab. 8.7 Input and output parameter
8.1.3.1.4 Fault / Warning / Message diagnostics
Problems
The following faults are being formed:
 based on checking the IN parameter "target language"
 If a message number (MsgID) entered in the DB View or DB Archive cannot be found in the
DBTextLibs
Fig. 8.13 Problems
Note
The two faults "MsgIDinViewNichtFind" and "MsgIDinArchivNichtFind" can also indicate that other
DB TextLibs numbers are being using as specified in the STAT area of the FB802.

Saved on 06.12.2012
Multiple languages
Warnings
If a start for a language switch for the message view (DB View) is issued at the FB802 or the message
archive (DB Archive) without the FB802 being released, the following warnings are set and the
corresponding start bit is reset by the FB.
In this case, no processing takes place.
Fig. 8.14 Warnings
Messages
The following messages are displayed at a start of the language switch and an empty DB View
(message view) or DB Archive (message archive).
Fig. 8.15 Messages

Saved on 06.12.2012
Multiple languages
8.1.3.2 Executing FB 650 "MeldeFB"
8.1.3.2.1 Block process image
Fig. 8.16 FB 650 "MeldeFB"
8.1.3.2.2 Input parameter

COM_RST BOOL Restart
TextLib0 BLOCK_DB Text library 0
Tab. 8.8 Input parameter

Saved on 06.12.2012
Multiple languages
8.1.3.2.3 Output parameter

Over BOOL Overflow of internal buffer
Tab. 8.9 Output parameter
8.1.3.2.4 Input and output parameter

MsgV UDT DB message view
MsgQ UDT DB message buffer
MsgA POINTER DB message archive
Tab. 8.10 Input and output parameter

Saved on 06.12.2012
Multiple languages
8.1.4 Multilingual S7 Graph step sequencer displays
Under "Available languages", select the desired language and add it under "Languages installed
in the project (Chinese)".
Fig. 8.17 Selecting and inserting the desired language
Select the corresponding text types (see also Ch. 8.1 "STEP 7").
Fig. 8.18 Selecting corresponding text types

Saved on 06.12.2012
Multiple languages
Export the user texts.
Import the user texts as xls files or, for Russian and Chinese, as "csv files".

Saved on 06.12.2012
Multiple languages
Perform the language change for the Installed Language (Chinese).
Fig. 8.21 Performing the language change for the installed language (Chinese)
Execute the item "Check block consistency".
Fig. 8.22 Checking block consistency

Saved on 06.12.2012
Multiple languages
Perform the language change for the Installed Language (German).
Fig. 8.23 Performing the language change for the installed language (German)
Execute the item "Check block consistency".
Fig. 8.24 Checking block consistency

Saved on 06.12.2012
Multiple languages
8.2 SiVArc
8.2.1 Provisioning the WinCC flexible project
In the folder "D:\Projects\Siemens\04_WinCCflexible\01_Vorlagen", the "PC677.hmi" file must be

opened.
Fig. 8.25 Opening the "PC677.hmi" file
8.2.2 Integrating a WinCC flexible project in STEP 7
The WinCC flexible project must be integrated in STEP 7 under "Project  Integrating in Step 7…".
Fig. 8.26 Integrating WinCC flexible project in STEP 7

Saved on 06.12.2012
Multiple languages
After integrating the body project, the second language for it must be selected in the "Project
languages" folder.
The following language selections must be made exclusively for the languages used in the company
group:
Language
English (US)
Czech (Czech Republic)
Spanish (International Sort)
Portuguese (Brazil)
Russian (Russia)
Slovak (Slovakia)
Chinese (PRC)
Tab. 8.11 Permissible language selections
Selection of the desired languages under "Language support  Project language".
Fig. 8.27 Selecting the desired languages

Saved on 06.12.2012
Multiple languages
In the "Languages and fonts" folder (under Device settings), a check mark must also be placed for the
second language.
Fig. 8.28 Placing a check mark also at the second language
After integrating the project and selecting a second project language, the "WinCC flexible" program is
saved and closed.

Saved on 06.12.2012
Multiple languages
8.2.3 Activating the multilingual support
Activate the "Multilingual support" and then select the desired second language.
Fig. 8.29 Multilingual support
After activating the "Generate" button, you are requested to select the "SymbolComment.csv" file you
created previously, which contains the translated project texts of the symbol table (see also Chapter
8.1.2 "Managing multilingual texts").
Fig. 8.30 Storage location of the symbol

comments
Note
If this selection dialog is exited with "Cancel" or "Close window", only German message text DBs
are generated.
After completing the generation, the Screen Generator automatically generates the message text DBs
in German and the selected target language. They must subsequently be loaded in the PLC.

Saved on 06.12.2012
Multiple languages
8.3 WinCC flexible

8.3.1 User dictionary in WinCC flexible
The user dictionary in WinCC flexible contains texts that occur in the same way in all projects. Project-
specifically added texts in the project must be post-edited by the system supplier.
Note
The basic user dictionary is supplied via "VASS.zip" and copied to the correct storage location with
the Update Manager.
8.3.1.1 User dictionary
8.3.1.1.1 Opening the "User dictionary" editor
The user dictionary is displayed in the project window in the group

"Language support  Dictionaries  User dictionaries".
Double-click on the name of a user dictionary to open the "User dictionary" editor. Here, you can now
view and edit terms of a user dictionary.
8.3.1.1.2 Design of the "User dictionary" editor
Project window Working area
Fig. 8.31 Design of the "User dictionary" editor

Saved on 06.12.2012
Multiple languages
8.3.1.1.3 Working area
In the work area, the texts of the user dictionary are displayed in table form. When you create a user
dictionary, you select which languages the user dictionary should contain. For each of these
languages, the table of the editor contains a column. Each table row contains a term in the reference
language as well as its translations if you applied them to the user dictionary.
8.3.1.2 Adding a term to a user dictionary
8.3.1.2.1 Introduction
In a user dictionary, you store translations of terms that occur multiple times in your project texts. You
can edit a user dictionary in the "User dictionary" editor or insert terms from project texts directly from
the editors in a user dictionary.
8.3.1.2.2 Requirements
A user dictionary is open in the "User dictionary" editor.
8.3.1.2.3 Adding a new term
Click on an empty table row.

Enter the new term.
Enter the corresponding translations in the corresponding cells of the same row.
8.3.1.2.4 Alternative procedure
If you want to enter a term directly from the point of use in a user dictionary, use the "Texts  Copy
to Dictionary" command in the "Options" menu. In the dialog, select the user dictionary in which the
term should be inserted.
8.3.1.2.5 Result
The term and, if you entered them, its translations are applied to the user dictionary. They can then be
used as translation suggestion by the "Translate Automatically" function.

Saved on 06.12.2012
Multiple languages
8.3.1.3 Managing user dictionaries
8.3.1.3.1 Introduction
All user dictionaries are physically managed in a single file. The user dictionaries used in a project are
displayed in the project window in the group "Language support  Dictionaries  User
dictionaries".
8.3.1.3.2 Renaming a user dictionary
In the context menu of the user dictionary, select the "Rename" command.
Enter a new name.
Press "ENTER".
8.3.1.3.3 Integrating a user dictionary in a project
In the menu "Options  User dictionaries", select the "Add/remove user dictionary" command.
In the dialog, select the user dictionary to be integrated in the project.
Click on "OK".
After you integrated a user dictionary in a project, the process can no longer be undone. To remove
the user dictionary from the project, delete the user dictionary.
8.3.1.3.4 Removing a user dictionary from the project
In the dialog, select the user dictionary to be removed from the project.
Click on "OK".
The user dictionary is being removed from the project.
8.3.1.3.5 Deleting a user dictionary
In the dialog, select the user dictionary to be deleted.
Click on "Delete Permanently".
The user dictionary is being deleted.

Saved on 06.12.2012
Multiple languages
8.3.1.3.6 Copying a user dictionary
The user dictionary is copied with Windows Explorer, e.g. when you want to use the user dictionary on
another configuration PC.
Disable the "WinCC flexible Start Center".
Note
Disable the "WinCC flexible Start Center" in the following cases:
- For "Copy" and "Paste".
- For copying from one version to another higher version.
- For copying from one configuration PC to another configuration PC.
Copy the files "UserDictionary.dct" and "UserDictionary_log.LDF" from the storage location listed
below.
On the configuration PC, check whether you want to overwrite the existing user dictionary. If you want
to overwrite the dictionary, insert the files under the storage location listed below on the configuration
PC.
Windows XP storage location:

"C:\Documents and Settings\All Users\Application Data\Siemens AG\
WinCC flexible"
Windows 7 storage location:

"C:\ProgramData\Siemens AG\SIMATIC WinCC flexible"
8.3.1.3.7 Uninstalling WinCC flexible
During the uninstallation, the user dictionary is also being deleted. If you still require the data, you
should copy the user dictionary before uninstalling it.
At the storage location listed above, search for the file "UserDictionary.dct".
Copy the files "UserDictionary.dct" and "UserDictionary_log.LDF

Saved on 06.12.2012
Multiple languages
8.3.2 Managing the project texts
8.3.2.1 Opening the project text overview
Fig. 8.32 Opening the project text overview
8.3.2.2 Automatically translating missing texts
Fig. 8.33 Automatically translating missing texts
Select the complete column (second language) to be translated.

Right-click in the marked area. Select "Translate Automatically". All texts contained in the user
dictionary are automatically inserted.

Saved on 06.12.2012
Multiple languages
To apply the texts, right-click again in the marked area and select "Accept Automatic Translation".
Fig. 8.34 Accept automatic translation
8.3.3 Project-specific texts
Select the complete column (second language) for which the translation is missing. Right-click in the
marked area and select "Export Texts".
Fig. 8.35 Exporting texts

Saved on 06.12.2012
Multiple languages

Select the project folder of your STEP 7
user project.
Format
 Select "Excel Workbook (*.xls)“
as the file format.
Languages:
 Next, select the desired target
language. The source language
is "German".
Text Types
 "Display Texts" must be
selected.
By confirming with "OK" the files "Others.xls" and "Screens.xls" are generated at the selected storage
location.
8.3.3.1 Providing the created text files from the export directory for translation
Fig. 8.37 Export files
The files "Others.xls" and "Screens.xls" are being generated in the export directory.
In the Excel files, the corresponding text is entered in two columns. The 1st column features the
source text, the 2nd column the previous source text or already existing text in the target language.
The texts are each framed with the tags "<text>" and "</text>". they may not be removed.
The target text must now be entered in the respective language.

Saved on 06.12.2012
Multiple languages
8.3.3.2 Example of an Excel file with German source and target text
Fig. 8.38 Sample Excel file (Ger / Ger)
8.3.3.3 Example of an Excel file with German source and English target text
Fig. 8.39 Sample Excel file (Ger / Eng)

Saved on 06.12.2012
Multiple languages
8.3.3.4 Importing the translated Excel files in the WinCC flexible project
Fig. 8.40 Importing the translated Excel files
8.3.4 Step sequencer display with ProAgent
Note
For multilingual projects, the steps 8 to 10 of Ch. 7.2.2 "Step sequencer display with
ProAgent". must be observed.

Saved on 06.12.2012
Multiple languages
8.3.5 Subsequent creation of a multilingual project via Delta import
If an existing project should be designed as multilingual, the following steps are required:
 In SIMATIC Manager:
Preparing the export of the project texts and text types (see Ch. 8.1.2.3 "Export of project
texts") for the translation files.
 Opening the existing WinCC Flexible project
Fig. 8.42 Opening the existing WinCC flexible project
 Selection of desired language (e.g. Spanish) in the "Language support" folder via project
languages
Fig. 8.43 Language selection

Saved on 06.12.2012
Multiple languages
 Under "Device settings  Languages and fonts", a check mark is placed in the "Runtime
language" column for the expanded language (e.g. Spanish).
Fig. 8.44 Placing a check mark at "Runtime language"

Saved on 06.12.2012
Multiple languages
 Under "Language support  Dictionaries", the "VASS_Benutzerwörterbuch" can be

linked via
"Add/Remove user dictionary".
Fig. 8.45 Adding/removing the VASS_Benutzerwörterbuch
Confirming with "OK" links the

"VASS_Benutzerwörterbuch".
Fig. 8.46 Linking the "VASS_Benutzerwörterbuch"

Saved on 06.12.2012
Multiple languages
 Updating the faceplates

(see ch. 6.4.2.2 Required preparations for the "Delta" import type).
 Saving and closing the project
Fig. 8.47 Saving and closing the current project
 Adjusting the symbol table in the S7 project for the additional language (here Spanish). The
DB numbers of TextLibs (DB824 - DB831) must be adjusted
(from "xx-XX" to "es-ES").
Fig. 8.48 Adjusting DB numbers of TextLibs (DB824 - DB831)

Saved on 06.12.2012
Multiple languages
 Starting the SiVArc screen generator and selecting the language for multilingual support
Fig. 8.49 Selecting the language for multilingual support
Fig. 8.50 Starting the generation

Saved on 06.12.2012
Multiple languages
 Selection of the required CSV file (exported and translated by the plant constructor).
Clicking on "OK"
Fig. 8.51 Selecting the storage location of the symbol comments
Selecting and opening the required CSV file:
Fig. 8.52 Selecting and opening the required CSV file

Saved on 06.12.2012
Multiple languages
 Selection of device type for the device
Clicking on "Accept"
Fig. 8.53 Selecting the device type for the device
 Selection of the following settings after the generation process:

 Placing the check mark in the "Selection" column
 Selecting "Delta" import type
 Selecting the correct WinCC flexible project
Clicking on "OK"
Fig. 8.54 Settings after the generation

Saved on 06.12.2012
Multiple languages
Clicking on "Import"
Fig. 8.55 Importing the selected panels
 Adopting the drop-down list box
Fig. 8.56 Adopting the drop-down list box

Saved on 06.12.2012
Multiple languages
 Opening the WinCC flexible project after importing and finishing the manual adaptations for
the Delta import.
 Right-click in the marked area.

Select "Translate Automatically".
All texts contained in the user dictionary are now automatically inserted.
Fig. 8.57 "Translate Automatically" selection
At the end of the automatic translation, click on

"OK".
Fig. 8.58 Completing the automatic translation

Saved on 06.12.2012
Multiple languages
 Applying the texts:

To apply the texts, right-click again in the marked area and select "Accept Automatic
Translation".
Fig. 8.59 Accept automatic translation
 Untranslated texts should be translated by the plant constructor

(translate texts via Excel and insert them in the project texts with the "Copy-Paste" function).
Fig. 8.60 Manual insertion of untranslated texts in the project texts

Saved on 06.12.2012
Multiple languages
 Open the Administrator screen and position the buttons for the selected languages.
Fig. 8.61 Positioning buttons for selected languages on the Administrator screen
 In the "Scripts" folder, open the "Set_Sprache" script.

Adjust this script for the selected languages (here e.g. "German" and "Spanish"). The
second language must be enabled by removing the comment identifier (quotes).
Fig. 8.62 Adjusting the script for selected languages

Saved on 06.12.2012
Commissioning at the system
9 Commissioning at the system
9.1 PC677 B
For the VASS standard, the PC677 15" is used as main
control panel. The following chapter describes the setup and
backup options.
The Microsoft Windows operating system as well as all
required drivers, software and licenses are already part of
the image. The following section describes which
customizations must be performed by the OEM.
9.1.1 Setting up the PC677
After starting the operating system, the following settings

must be changed:
 The touchscreen must be recalibrated
 The computer name must be adapted
 The network settings must be configured according
to the project specifications
Fig. 9.1 Computing unit (1) and control unit (2)

Saved on 06.12.2012
9.1.1.1 Calibrating the touchscreen
You call up the settings of the touchscreen via the "Start" menu dialog and the command "Programs
 UPDD  Settings".
If the touchscreen does not respond as expected
upon touching it, repeat the calibration. To do so,
first activate the 25-point calibration and then
calibrate the touchscreen.
Fig. 9.2 Calibrating the touchscreen
9.1.1.2 Assigning the computer name
The "Computer name" is derived from the

PROFINET specifications.
You change the computer name via the "Start"
menu dialog and the command "Settings 
Control Panel  System".
Fig. 9.3 Assigning a computer name

Saved on 06.12.2012
9.1.1.3 Assigning the IP address
First, the Ethernet network card must be selected whose interface is to be used for the
communication. By default, the SIMATIC PANEL PC 677 features two Ethernet network cards.
Fig. 9.4 Network cards selection window
You change the network setting via the "Start" menu dialog and the command "Settings  Network
Connections  Network Adapter". Open the "Properties of Network Card Used" dialog. The
"Properties of ... " dialog opens. Mark "Internet Protocol (TCP/IP)". Open the properties. The IP
settings are made on the "General" tab.
Fig. 9.5 LAN connection 1 Internet Protocol (TCP/IP) selection

Saved on 06.12.2012
Fig. 9.6 LAN connection 2 Internet Protocol (TCP/IP) selection
Before starting the runtime of the WinCC flexible project, the PG/PC interface must be firmly set to
TCP/IP with the network card activated beforehand!
Fig. 9.7 PG/PC selection window of network cards

Saved on 06.12.2012
9.1.2 Transferring configuration data to the target system
9.1.2.1 Data storage
The data storage on the target system must be performed according to the defaults of Chapter 3 "Data
Storage".
9.1.2.2 S7 project
Commissioning in three steps of the configuration

 Configure and compile hardware
 Create and generate safety program
 Create sequence program according to Chapter 4.8 "Program" and check block consistency
Note
After every change of the hardware configuration, "Report system errors" must be generated again.
This changes message DBs. They must be transferred to the controller so that the PROFINET
diagnostics works properly in the visualization.
Afterwards, everything must be transferred.
9.1.2.2.1 Complete download of the safety program

2. In the SIMATIC Manager, select the menu command"Options  Edit Safety Program".
3. Activate the "Load" button.
It determines all F-blocks with F-attribute that belong to the safety program and loads them
into the F-CPU.
Together with a corresponding note, you are given the option to load the standard user
program together with the safety program.
If the safety program is changed or not consistent, you are given a corresponding note and
the option to create a consistent safety program (i.e. to generate it).
4. Confirm the query about stopping the F-CPU.
Note
You perform the loading of the complete safety program only in the STOP operating state. If you
load only the F-blocks, then the block in which the F-CALL blocks are called is not loaded.

Saved on 06.12.2012
Note
After the loading in the "Safety Program" dialog, an online/offline comparison is automatically
performed for all F-blocks with F-attribute in the safety program. In the F-CPU, all F-blocks without
F-attribute are deleted. Afterwards, the F-CPU contains exactly the same F-blocks with F-attribute
as are available in the offline block container.
5. In the "Safety Program" dialog, activate the tabs "Offline" and "Online" in succession and
check whether the collective signature of all F-blocks with F-attribute of the block container
match online and offline. If they match, the loading was successful. If this is not the case,
repeat the load procedure.
6. To activate the safety mode, perform a STOP/RUN transition of the F-CPU.
Note
If the loading process is canceled, you have to repeat the loading (step 3) and the check of the
collective signatures of all F-blocks with F-attribute of the block container online and offline (step
5).
9.1.2.2.2 Loading changes of the safety program in the "Safety Program" dialog

2. In the SIMATIC Manager, select the menu command"Options  Edit Safety Program".
3. Activate the "Load Changes" expand button of the "Load" button. It determines all new and
changed F-blocks with F-attribute in the safety program and loads them into the F-CPU.
The further procedure corresponds to that of loading the complete safety program in the "Safety
Program" dialog (see also Chapter 8.1.2.2.1 "Complete download of the safety program").
Fig. 9.8 Editing the

safety program

Saved on 06.12.2012
9.1.2.2.3 Download after changing "HW Config"
If you change a safety-relevant parameter for F-I/O devices, a fail-safe DP standard slave, a fail-safe
IO standard device or an F-CPU, then you have to regenerate and load the safety program.
The same applies to changes of the configuration of safety-related communication, particularly the
change of S7 connections for safety-related communication via S7 connections.
9.1.2.2.4 Complete download of the sequence programs
After the safety program, all blocks of the sequence program must be transferred to the CPU and, if
necessary, edited further.
Note
To monitor the module FBs in SCL with respect to status, it is absolutely necessary that the SCL
source files in the S7 program source files container are retained.
9.1.3 WinCC flexible
9.1.3.1 Transfer of the project to the HMI device
The WinCC flexible project to be transferred must be opened with the WinCC flexible Engineering
System.
Next, the following settings must be made on the HMI device:
Autostart must be disabled on the taskbar in the "SIMATIC WinCC flexible - Start center".
Fig. 9.9 SIMATIC WinCC flexible - Start center

Saved on 06.12.2012
In the Start menu under "SIMATIC  WinCC flexible Runtime 2008", start the "WinCC flexible
Runtime Loader" (variant A).
Or:
In the Start menu under "Programs  Siemens Automation  Runtime Systems 
WinCC flexible Runtime 2008"", start the "WinCC flexible Runtime Loader" (variant B).
Fig. 9.10 "WinCC flexible Runtime Loader" start dialog
First, click on "Settings" and check the setting in the following dialog and adjust it, if necessary.
Under "Connection", "ETHERNET" must be selected

for "Channel 2" and the check mark must be set next
to "Activate" and "Remote Control".
Next, check in the "Directories" context that the

path "D:\Projects\Siemens\02_S7\02_Projekte\
R001v04" is set under "Configuration file:" and under
"Return transfer file:".
The following path must be specified under "Start

application automatically:"
"C:\Programs\Siemens\SIMATIC WinCC flexible\
WinCC flexible 2008 Runtime\HmiRtm.exe"
Confirm the settings with "OK".

Fig. 9.11 "Settings" dialog window

Saved on 06.12.2012
After the "Settings" dialog has been closed, click on "Transfer" in the
main dialog of the runtime loader.
Fig. 9.12 Runtime loader "Transfer"
Another window opens next with "Waiting for connection…".

Leave it open, the runtime automatically starts after successful transfer.
Fig. 9.13 Transfer settings

Saved on 06.12.2012
Settings in the project

Next, you open the WinCC flexible project to be transferred to the HMI device, and click on "Settings
for the Transfer".
Select "Ethernet" for "Mode" in the "Select HMI Devices for Transfer". For Panels, enter the IP
address, and for PanelPCs the computer name.
The fields "Overwrite User Management" and "Overwrite Data Records" must be activated only for the
first transfer. The check marks can be removed for subsequent transfers.
Finally, click on "Transfer" to start the transfer.
Afterwards, the runtime starts automatically.
Note
If the transfer is not initiated, the old, previously loaded project starts upon restarting the panel PC.

Saved on 06.12.2012
9.1.4 Configuring RemoteOperate
If auxiliary control units of type MP377 or mobile panels of type MP277RO are used in the system,
they must be coupled with the main control unit (PC677) via a remote connection. This is done via the
RemoteOperate software.
In this case, the server is located on the main control unit and the client on the respective MP.
9.1.4.1 Configuring the server
Opening the "Server - RemoteOperate V2" dialog

In the bottom right corner of the Windows taskbar is the "RemoteOperate Server"
icon.
With the "RemoteOperate

Server" icon, you open the "Server -
Remote Operate V2" dialog.
Alternatively, open the "Server -
Remote Operate V2" dialog with a
keyboard shortcut which you
defined in the server settings.
Fig. 9.15 Server - Remote Operate V2
No. Description
① Port of RemoteOperate Server
② IP address of the network card of the RemoteOperate Server
③ List of available Clients
④ Status, rights, IP address and description of a Client
⑤ "Add Client" button
⑥ "Edit Client" button
⑦ "Remove Client" button
⑧ "Edit Server Settings" button
⑨ "Close Server Dialog" button
Tab. 9.1 Term description of the "Server - RemoteOperate V2" dialog
Closing the "Server - RemoteOperate V2" dialog

Minimize the "Server - RemoteOperate V2" dialog with the button.

Saved on 06.12.2012
9.1.4.1.1 Adding a client
Requirements
The "Server - RemoteOperate V2" dialog is open.
Procedure
With the button, open the "RemoteOperate V2" dialog for creating a new client.
In the "IP address:" field, enter the physical address of the
client which you want to add to the list of clients.
Optional: Enter a comment in the "comment:" field.
The comment is subsequently displayed as text description of
the client next to its IP address in the "available clients" list.
Select a meaningful comment, e.g. the name or type of the
HMI device.
Fig. 9.16 Creating a new client
Activate the button to confirm your entries.

The "RemoteOperate V2" dialog closes.
Result
You added a new client to the list of
"available clients". You can enter up
to six clients in the list of "available
clients" of a server.
Fig. 9.17 Client was added

Saved on 06.12.2012
9.2 MP377 / MP277RO

The VASS standard uses the MP377 15" as auxiliary control
panel and the mobile panel MP277RO. The following chapter
describes the configuration.
Fig. 9.18 Auxiliary control panel MP377
9.2.1 Configuring the MPs
After starting the operating system, the "Loader" is displayed.

The buttons of the "Loader" have the following function:
 With the "Transfer" button, you switch the HMI device to the
"Transfer" operating mode.
 With the "Start" button, you start the RemoteOperate client.
 With the "Control Panel" button, you start the control panel of the
HMI device.
 With the "Taskbar" button, you show the taskbar and start menu.
Fig. 9.19 Configuring the MP377
Control Panel
In the control panel of the HMI device, you can also set the following:
 Calibrating the touchscreen
 Setting the computer name
 Defining network settings

Saved on 06.12.2012
Defining transfer settings
9.2.1.1 Calibrating the touchscreen
Depending on the mounting position and viewing angle, a parallax may occur at the touchscreen. To
avoid any operator errors resulting from it, recalibrate the touchscreen in the startup phase or during
operation.
With the "OP" icon, you open the "OP Properties" dialog ("Touch" tab).
After activating the "Recalibrate" button, the calibration dialog
opens. Briefly touch the center of the calibration cross in
each case. The new calibration is saved at the end if you
touch the touchscreen within 30 seconds.
Fig. 9.21 OP properties
9.2.1.2 Setting the computer name of the HMI device
With the "System" icon, you open the "System

Properties" dialog (the "Device Name" is derived from the
PROFINET specifications).
Fig. 9.22 System properties

Saved on 06.12.2012
9.2.1.3 Assigning the IP address
With the "Network and Dial-Up Connections" icon, you open the following dialog window.
Open the entry "LAN90001".
 The "'SMC LAN91C111 Ethernet' Settings" dialog opens.
Fig. 9.23 "SMC LAN91C111 Ethernet" settings
Change to the "Name Servers" tab to enter the name server

(the Ethernet setting is derived from the PROFINET
specifications).
Fig. 9.24 Name server
Changing login data
You opened the "Network ID" dialog with the "Network ID" icon.
 Enter the user name in the "User name" input field.
 Enter your password in the "Password" input field.
 Enter the domain name in the "Domain" input field.
Fig. 9.25 Network ID

Saved on 06.12.2012
9.2.2 Configuring the RemoteOperate client
9.2.2.1 Creating/editing the server selection list
When you switch on the HMI

device, the server selection list is
displayed in the "Client -
RemoteOperate V2" dialog after
the start of the HMI device.
Fig. 9.26 Server selection list
Note
When you switch on the HMI device for the first time, the server selection list is still empty. First,
create a new server.
Password protection
If your HMI device is protected by a password, then the "Client - RemoteOperate V2" dialog also
displays the icon.
The password is requested once per connection attempt and for the following actions:
 Create server
 Change server properties
 Delete server
 Exit RemoteOperate client

Saved on 06.12.2012
9.2.2.2 Creating a new server
Note
Limited number of servers per client:
RemoteOperate supports up to ten servers in the server selection list of a client.
Ensure that a maximum of nine servers are located in the server selection list when you want to
create a new server.
To create a server, open the "RemoteOperate V2" dialog with

the button.
Fig. 9.27 RemoteOperate V2
Tree path
In the "tree path:" field, enter the path
of the server within the server
selection list.
"Path" indicates under which node of
the server tree the server is created.
For example, if you specify "\Area1\",
then the IP address of the server will
subsequently be shown underneath
the "Area1" node:
The respective subsystems, e.g. UB1,

Aufbau2, etc., are entered as tree
path.
Fig. 9.28 Tree path
Note
The path of the server selection list can be up to three levels deep. Enter a maximum of three path
levels for a server, e.g. "\Area2\Segment1\Place2\". If the path already exists in the server
selection list, the newly added server is positioned at this location. If the path does not yet exist, it
is automatically being created.

Saved on 06.12.2012
IP address
Enter the IP address of the new server in the "IP address:" input field.
Comment
Enter a designation for the new server in the "comment:" input field which is displayed next to the IP
address in the tree of the server selection list. The designation used here is the PROFINET device
name of the respective server.
Confirmation
Confirm your entries with the button.
9.2.2.3 Changing the properties of a server
Follow the steps below:

 Select the server whose properties you want to edit.
 Use the button to open the "RemoteOperate V2" dialog for changing the server
properties.
 Follow the steps of the aforementioned description of "Create New Server"
("Tree path" - "IP address" - "Comment" - "Confirm").
9.2.2.4 Removing a server

 Select the server you want to remove from the server selection list.
 Remove the selected server from the server selection list with the button.
 Result:
You created a new server selection list or changed an existing server selection list.

Saved on 06.12.2012
9.2.2.5 Connecting a client
Requirements
 You switched on the HMI device.
 You authorized yourself with your password if your HMI device is protected by a password.
Note
When you switch on the HMI device for the first time, the server selection list is empty. Create a
new server selection list.
Procedure
Select the name of the server with which you want to connect.
Full access to the server

If you connect with the server, you
have full access to the server
depending on your access rights.
Fig. 9.29 Full access to the server
Danger
Improper operation of the server by unauthorized personnel can lead to malfunctions of the server.
Malfunctions can lead to death or serious physical injuries! Assign passwords at the HMI devices.
Create an operating authorization concept. This ensures that only authorized personnel receives
full access to the server.
Connect the client with the selected server with the button.
While the client attempts to connect with the server, the adjacent message is displayed on your HMI
device:
Fig. 9.30 Connection to the server

Saved on 06.12.2012
Note
Behavior in case of a problem of the network:
In case of a short-term or permanent problem of the network, the client continuously attempts to
establish a connection to the server. You cancel the continuous connection attempts with the
button.
Result
If a connection to the server has been established, the following options are available:
 The server grants you access. The project running on the server is being displayed.
Depending on your authorization at the server, you may either view or operate the project.
 The server grants you access. The Windows desktop of the server is being displayed. If you
are authorized for operation, start your project with the corresponding desktop icon.
 The server grants you access. You see the Windows login window of the server. Touch the
touchscreen until the RemoteOperate toolbar is
displayed.
Fig. 9.31 RemoteOperate toolbar
Note
Set the duration until the display of the toolbar:
The time required for you to touch the touchscreen until the RemoteOperate toolbar is displayed is
defined in the "roServer.ini" file.
If you are authorized for operation, press the "<Ctrl+Alt+Del>" button.

Next, press on the button and enter your login at the server.
Start your project via the corresponding desktop icon.
The server does not grant you access. The adjacent
message is displayed on your HMI device:
You cancel the connection attempt with the button.
Fig. 9.32 No access to the server
Once the server has rejected your access attempt, your client remains unauthorized until your server
grants explicit access.

Saved on 06.12.2012
The operating authorization window ("traffic light")

On the server screen and the screens of all connected and operation-authorized clients, the operating
authorization window, the so-called "traffic light", is displayed in the foreground.
The traffic light can show the following statuses:
Traffic light Activated by Meaning
symbol
Touching the touchscreen at an You are allowed to operate.
operation-authorized client or Other clients can issue an operating request.
release of the exclusive operator
authorization at another operation-
authorized client.
Two touches in quick succession You have exclusive operating permission.

(double-click) on the traffic light at Other clients can issue an operating request
the currently operation-authorized only after you released the exclusive
client. operating right with another double-click on
the traffic light.
Activation of the "Forced Exclusive" You have exclusive operating permission.

mode, e.g. via a switch close to the Other clients can issue an operating request
mobile panel. only after you released the exclusive
operating right by deactivating the "Forced
Exclusive" mode.
Touching the touchscreen at Another client is operating.

another operation-authorized client. You can issue an operating request at your
client by touching the touchscreen.
Double-clicking on the traffic light at Another client is operating exclusively.

another operation-authorized client. You can issue an operating request only after
the other client has released the exclusive
operating right with another double-click on
the traffic light.
Activation of the "Forced Exclusive" Another client is operating exclusively.

mode at another client, e.g. via a You can issue an operating request only after
switch close to the mobile panel. the other client has released the exclusive
operating right by deactivating the "Forced
Exclusive" mode.
Tab. 9.2 Operating authorization window ("traffic light")

Saved on 06.12.2012
PN connection box
If mobile panels are used in the protective circuit via PN connection boxes, an automatic exclusive
mode for the mobile panel is activated via the E2 lock.
For this purpose, it is absolutely necessary that the box ID is set according to the specification. This
setting must be checked, if necessary.
Rotary encoding switch

Box ID: 255
Fig. 9.33 Example - setting of the rotary encoding switches
The number of the connection box must be set according to the specification (unique for body
structure), the setting is done in hexadecimal.
The RemoteOperate toolbar

If you touch the touchscreen for longer than five seconds, the RemoteOperate toolbar is displayed in
the foreground on your screen.
Fig. 9.34 RemoteOperate toolbar
Note
Set the duration until the display of the toolbar:
The time required for you to touch the touchscreen until the RemoteOperate toolbar is displayed is
defined in the "roServer.ini" file.

Saved on 06.12.2012
The following table shows the special functions of the RemoteOperate toolbar:
Button Function
Executes a right-click on the server.
- Select a screen object that features a function for the right mouse button.
- Activate the button "Right mouse button".
- Operate the desired function.

Opens the screen keyboard.
Operates the Windows key on the server.
Executes the keyboard shortcut "<Ctrl+Alt+Del>" on the server,

e.g. to log onto the server.
Cancels the connection to the server.
Closes the RemoteOperate toolbar.
Tab. 9.3 Special functions of the RemoteOperate toolbar

Saved on 06.12.2012
List of Figures
List of Figures
Fig. 2.1 Selecting the software components ...................................................................................25
Fig. 2.2 Selecting ProAgent ............................................................................................................25
Fig. 2.3 WinCC flexible 2008 Advanced with SP2 / Update 3 ........................................................26
Fig. 2.4 3-GB switch for 32-bit XP system ......................................................................................27
Fig. 2.5 Installation of "WinCC flexible Add-on" ..............................................................................28
Fig. 2.6 Selection of HMI device type .............................................................................................28
Fig. 2.7 Changing the HMI device type ...........................................................................................29
Fig. 2.8 SIMATIC WinCC flexible - Start center ..............................................................................29
Fig. 2.9 Executing the "dotNetFx35setup.exe" setup file ................................................................30
Fig. 2.10 Executing "SiVArc.msi" for VASS ......................................................................................30
Fig. 2.11 Installation of SiVArc setup for VASS ................................................................................31
Fig. 2.12 SiVArc setup destination folder ..........................................................................................32
Fig. 2.13 SiVArc desktop icons .........................................................................................................32
Fig. 2.14 "General" settings ..............................................................................................................33
Fig. 2.15 "View" settings ...................................................................................................................33
Fig. 2.16 "LAD/FBD" settings ............................................................................................................34
Fig. 2.17 "Block" settings ..................................................................................................................34
Fig. 2.18 Opening the "Properties - Block folder offline" window......................................................35
Fig. 2.19 Setting the address priority ................................................................................................35
Fig. 2.20 Error message....................................................................................................................36
Fig. 2.21 Verifying before generating ................................................................................................36
Fig. 2.22 Settings of the columns .....................................................................................................37
Fig. 2.23 Differentiating settings .......................................................................................................38
Fig. 2.24 "General" application settings ............................................................................................39
Fig. 2.25 "Editor" application settings ...............................................................................................39
Fig. 2.26 "Compile / Save" application settings ................................................................................40
Fig. 2.27 "Messages" application settings ........................................................................................41
Fig. 2.28 "Compile / Save" block settings .........................................................................................42
Fig. 2.29 "Messages" block settings .................................................................................................43
Fig. 2.30 S7 SCL "Create Blocks" .....................................................................................................44
Fig. 2.31 Value (new) .......................................................................................................................45
Fig. 2.32 Value (old) .........................................................................................................................45
Fig. 2.33 S7-SCL "Compiler".............................................................................................................46
Fig. 3.1 Project data - Folder structure ...........................................................................................48
Fig. 3.2 Defining permissions for users ...........................................................................................49
Fig. 3.3 Defining the list separator ";" ..............................................................................................50
Fig. 3.4 S7 online help ....................................................................................................................54

Saved on 06.12.2012
List of Figures
Fig. 3.5 Installation of STEP 7 online help ......................................................................................55

Fig. 3.6 Activating "Windows Update" .............................................................................................55
Fig. 3.7 "Windows Update" has been started and is active ............................................................56
Fig. 3.8 Installation ..........................................................................................................................56
Fig. 3.9 Confirming the "Update for Windows (KB917607)" ...........................................................57
Fig. 3.10 Confirming the license requirements for "Update for Windows (KB917607)" ....................57
Fig. 3.11 Deactivating "Windows Update" ........................................................................................58
Fig. 3.12 Creating the folders "VASS_Onlinehilfen" and "VASS_V05".............................................59
Fig. 3.13 Setting for block online help in German .............................................................................60
Fig. 3.14 Setting for block online help in English ..............................................................................60
Fig. 4.1 Principal procedure for project creation .............................................................................61
Fig. 4.2 Integrating the device catalog ............................................................................................63
Fig. 4.3 Installing the GSD files .......................................................................................................64
Fig. 4.4 Structure of PROFINET device names ..............................................................................65
Fig. 4.5 CPU properties...................................................................................................................66
Fig. 4.6 PROFINET "General" settings ...........................................................................................66
Fig. 4.7 Example of the message in the consistency check of the hardware .................................67
Fig. 4.8 PROFINET "Parameter" settings .......................................................................................67
Fig. 4.9 PROFINET hardware configuration ...................................................................................68
Fig. 4.10 PROFINET "Update time" settings ....................................................................................68
Fig. 4.11 Topology editor - "Offline/online comparison" ....................................................................69
Fig. 4.12 Topology editor - "Offline/online comparison" result ..........................................................70
Fig. 4.13 Topology editor - "Graphic view" ........................................................................................72
Fig. 4.14 Topology editor - Activating "Move Picture Mode" .............................................................73
Fig. 4.15 Topology editor - Scaling the BMP file to the entire area ..................................................73
Fig. 4.16 Topology editor - Moving PN nodes...................................................................................74
Fig. 4.17 Properties of PN-IO port ....................................................................................................75
Fig. 4.18 Status: OK ..........................................................................................................................75
Fig. 4.19 Status: Maintenance required ............................................................................................76
Fig. 4.20 Status: Maintenance demanded ........................................................................................76
Fig. 4.21 Status: Module not available ..............................................................................................77
Fig. 4.22 Ethernet node.....................................................................................................................78
Fig. 4.23 Protection ...........................................................................................................................79
Fig. 4.24 Cycle / clock memory .........................................................................................................80
Fig. 4.25 Selection of a hardware configuration ...............................................................................81
Fig. 4.26 "General" dialog box ..........................................................................................................81
Fig. 4.27 "OB Configuration" dialog box ...........................................................................................81
Fig. 4.28 "CPU in STOP" dialog box .................................................................................................82
Fig. 4.29 "Messages" dialog box .......................................................................................................82
Fig. 4.30 Warnings during generation if check mark is set ...............................................................82

Saved on 06.12.2012
List of Figures
Fig. 4.31 "Diagnostic Support" dialog box .........................................................................................83

Fig. 4.32 Excerpt of robot I/O area ....................................................................................................87
Fig. 4.33 Instance DB........................................................................................................................89
Fig. 4.34 Different types of structures ...............................................................................................91
Fig. 4.35 FB_Ventil ............................................................................................................................91
Fig. 4.36 Interconnecting structure "STB_Ventil" with the structure "12"._0050MZ11 .....................92
Fig. 4.37 Interconnecting structure "STB_Ventil" with the element "Frg_V1" ...................................92
Fig. 4.38 Properties - Function ..........................................................................................................93
Fig. 4.39 Example for calling HMI = I1 ..............................................................................................94
Fig. 4.40 FB_NotHalt.........................................................................................................................95
Fig. 4.41 Meld_4 ...............................................................................................................................95
Fig. 4.42 Properties - Instance data block for FB126 .......................................................................96
Fig. 4.43 Generating error .................................................................................................................96
Fig. 4.44 Calling the module FB FB125 ............................................................................................97
Fig. 4.45 Faceplate for "Status" example..........................................................................................97
Fig. 4.46 Example for missing underscore characters ......................................................................98
Fig. 4.47 Call structure of OB1 ..........................................................................................................99
Fig. 4.48 Program structure ............................................................................................................102
Fig. 4.49 Permissible network width ...............................................................................................103
Fig. 4.50 Safety program  Standard program replacement variable ...........................................104
Fig. 4.51 Standard program  Safety program replacement variable ...........................................105
Fig. 4.52 FC900 F-Call ....................................................................................................................106
Fig. 4.53 FC10 PoT .........................................................................................................................107
Fig. 4.54 FC11 basic functions .......................................................................................................108
Fig. 4.55 Setting of rotary encoding switch .....................................................................................109
Fig. 4.56 FC12 preselections ..........................................................................................................111
Fig. 4.57 FC13 operating modes ....................................................................................................112
Fig. 4.58 FC14 1. "STxxyyyy" station ..............................................................................................116
Fig. 4.59 Schematic interaction of sequential control .....................................................................118
Fig. 4.60 "S7G_Control" block ........................................................................................................119
Fig. 4.61 Automatic retraction (1) ....................................................................................................120
Fig. 4.62 Automatic retraction (2) ....................................................................................................121
Fig. 4.63 Creating static variables ...................................................................................................122
Fig. 4.64 "FC_Trans_Init" block ......................................................................................................123
Fig. 4.65 "FC_Trans" block .............................................................................................................124
Fig. 4.66 Defined hold .....................................................................................................................125
Fig. 4.67 "AS_xxyyyy" block............................................................................................................126
Fig. 4.68 Declaring the initial step ...................................................................................................126
Fig. 4.69 FC15 1. robot R01 ...........................................................................................................129
Fig. 4.70 Layer – Robot...................................................................................................................133

Saved on 06.12.2012
List of Figures
Fig. 4.71 Layer – Robot process device .........................................................................................134

Fig. 4.72 Layer – Machine process .................................................................................................135
Fig. 4.73 FC97 interfaces ................................................................................................................136
Fig. 4.74 FB650 general contact indicator lights .............................................................................137
Fig. 4.75 FC98 GBA ........................................................................................................................138
Fig. 4.76 FC99 ZAU ........................................................................................................................139
Fig. 5.1 F_Ziel_Adresse ................................................................................................................143
Fig. 5.2 Setting of access protection and activation of safety program ........................................144
Fig. 5.3 Setting of F parameters ...................................................................................................144
Fig. 5.4 Assigning name and comment for the fail-safe module ...................................................146
Fig. 5.5 Setting the I/O base address for the fail-safe input module .............................................147
Fig. 5.6 Setting the PROFIsafe parameters for 4/8-DI ..................................................................147
Fig. 5.7 Assigning name and comment for the fail-safe module ...................................................148
Fig. 5.8 Setting the I/O base address for the fail-safe output module ..........................................148
Fig. 5.9 Setting the PROFIsafe parameters for 4 F-DO................................................................149
Fig. 5.10 Setting the I/O base address for the fail-safe output module ..........................................149
Fig. 5.11 Configuration of a PN/PN coupler ....................................................................................152
Fig. 5.12 Properties of a PN/PN coupler .........................................................................................152
Fig. 5.13 Input and output start address of a module must be identical .........................................153
Fig. 5.14 Sending side (configuration example): ............................................................................154
Fig. 5.15 Receiving side (configuration example): ..........................................................................155
Fig. 5.16 Safety-oriented CPU-CPU communication via PROFINET IO ........................................156
Fig. 5.17 Bridge for commissioning .................................................................................................159
Fig. 5.18 OB1 with call of the safety program .................................................................................160
Fig. 5.19 Call of the safety program ................................................................................................161
Fig. 5.20 Comment field of the FB900 block ...................................................................................162
Fig. 5.21 "SK_xy" block calls...........................................................................................................163
Fig. 5.22 "NOT_HALT_ANTRIEBE" block call ................................................................................163
Fig. 5.23 "LAST_SK_xy" block calls ...............................................................................................164
Fig. 5.24 Creating an F-runtime group ............................................................................................165
Fig. 6.1 SiVArc Screen Generator ................................................................................................168
Fig. 6.2 "Install standard" selection ...............................................................................................169
Fig. 6.3 Path entry for the "VASS.zip" file .....................................................................................170
Fig. 6.4 Paths in which "Root Project" should be unpacked and "Meta model" should be stored 171
Fig. 6.5 Installation in the program folder......................................................................................172
Fig. 6.6 Checking the CSV files generated with RSE ...................................................................173
Fig. 6.7 Opening the "PC677.hmi" file ..........................................................................................173
Fig. 6.8 Starting the integration .....................................................................................................173
Fig. 6.9 Selecting the STEP 7 project ...........................................................................................174
Fig. 6.10 Progress bar of the integration .........................................................................................174

Saved on 06.12.2012
List of Figures
Fig. 6.11 View after integration .......................................................................................................175

Fig. 6.12 "HmiEs" folder with new WinCC flexible project .............................................................175
Fig. 6.13 Main dialog window ..........................................................................................................176
Fig. 6.14 Selecting a car brand .......................................................................................................176
Fig. 6.15 Multilingual support ..........................................................................................................177
Fig. 6.16 Selecting a STEP 7 project via the "plus" symbol ............................................................178
Fig. 6.17 Selecting the user interface language .............................................................................179
Fig. 6.18 Selecting the "Settings" dialog .........................................................................................179
Fig. 6.19 Export path of the CSM file ..............................................................................................180
Fig. 6.20 Opening a project for editing ............................................................................................180
Fig. 6.21 "STEP 7 Block Sizes" dialog ............................................................................................181
Fig. 6.22 "Enter Size" dialog ...........................................................................................................181
Fig. 6.23 Starting the project generation .........................................................................................182
Fig. 6.24 Setting of the panel type ..................................................................................................183
Fig. 6.25 Overview of created text libraries.....................................................................................184
Fig. 6.26 Selection of the WinCC flexible project (Complete import type) ......................................184
Fig. 6.27 Opening the global library ................................................................................................185
Fig. 6.28 "New" WinCC flexible update library ................................................................................186
Fig. 6.29 Search for already existing types .....................................................................................186
Fig. 6.30 Update project ..................................................................................................................187
Fig. 6.31 SIMATIC WinCC flexible module comparison .................................................................188
Fig. 6.32 Opening the "Structures" folder .......................................................................................189
Fig. 6.33 Creating "new" structure names with endings .................................................................189
Fig. 6.34 Opening the "old" structure ..............................................................................................190
Fig. 6.35 Opening the cross-references in the "old" structure ........................................................190
Fig. 6.36 Adapting the variable name in the "old" structure (1) ......................................................191
Fig. 6.37 Adapting the variable name in the "old" structure (2) ......................................................191
Fig. 6.38 Checking the "old" structure .............................................................................................192
Fig. 6.39 Adapting the new structure name in a faceplate ..............................................................192
Fig. 6.40 "Old" structure was deleted ..............................................................................................193
Fig. 6.41 Renaming the "new" structure .........................................................................................193
Fig. 6.42 "New" structure was renamed ..........................................................................................194
Fig. 6.43 Starting the project generation .........................................................................................195
Fig. 6.44 Setting of the panel type ..................................................................................................196
Fig. 6.45 Overview of created text libraries .....................................................................................197
Fig. 6.46 Selection of the WinCC flexible project (Delta import type) .............................................197
Fig. 6.47 Selection to Overwrite picture or Create Delta picture.....................................................198
Fig. 6.48 "Replacing Data" progress bar .........................................................................................199
Fig. 6.49 "Compiling project" progress bar .....................................................................................200
Fig. 6.50 Import is completed ..........................................................................................................201

Saved on 06.12.2012
List of Figures
Fig. 6.51 Generated "DeltaImport.log" file ......................................................................................202

Fig. 6.52 Generating messages ......................................................................................................203
Fig. 7.1 WinCC flexible - Starting the integration ..........................................................................205
Fig. 7.2 WinCC flexible - Selecting the STEP 7 project ................................................................206
Fig. 7.3 WinCC flexible - Configuring the connection in STEP 7 ..................................................207
Fig. 7.4 Properties / IE General Ethernet interface (R0&S1) ........................................................208
Fig. 7.5 Assignment of the interface .............................................................................................208
Fig. 7.6 SIMATIC Manager - Renaming the SIMATIC HMI station...............................................209
Fig. 7.7 Enter name under connections with S7-HMI ...................................................................210
Fig. 7.8 Selecting the S7 station ...................................................................................................210
Fig. 7.9 Result for the "S7-HMI" connection and after deleting the "Verbindung_1" connection ..210
Fig. 7.10 Calling up ProAgent .........................................................................................................211
Fig. 7.11 Marking S7-HMI ...............................................................................................................212
Fig. 7.12 Selection of the step sequencer (sequential control) in the STEP 7 project....................212
Fig. 7.13 Text entry (faceplate use) ................................................................................................213
Fig. 7.14 Selection of FB/DB ...........................................................................................................213
Fig. 7.15 Copying the prepared step display with four buttons to the station picture .....................214
Fig. 7.16 Parameterization of the "Sequential control" button by "clicking" (under events)............214
Fig. 7.17 Parameterizing the pointer instrument for "picture change" ............................................215
Fig. 7.18 Calling up ProAgent .........................................................................................................215
Fig. 7.19 All post-processing must be performed in the "German" language .................................216
Fig. 7.20 All post-processing must be performed in the selected second project language (here:
Chinese) ...........................................................................................................................216
Fig. 7.21 Example - manual operating screen of the station before processing
("ST_xxyyyy_WZ_003") ...................................................................................................219
Fig. 7.22 Example - manual operating screen of the roller conveyor before processing
("ST_xxyyyy_RB_003-Rollenbahn") ................................................................................220
Fig. 7.23 Example - manual operating screen of the buffering belt before processing
("ST_xxyyyy_SB_003-Stauband") ...................................................................................221
Fig. 7.24 Example - manual operating screen of the framer before processing
("ST_xxxxxx_FWx_003-Framer") ....................................................................................222
Fig. 7.25 Example - step sequencer display for the manual operating screen
("Station_Ablaufsteuerung") .............................................................................................223
Fig. 7.26 Example - manual operating screen of the station after processing
("ST_110030_WZ_003") ..................................................................................................223
Fig. 7.27 Example - manual operating screen of the roller conveyor after processing
("ST_210050_WZ_003-Rollenbahn") ..............................................................................224
Fig. 7.28 Example - manual operating screen of the buffering belt after processing
("ST_210050_SB1_003-Stauband") ................................................................................224
Fig. 7.29 Example - manual operating screen of the framer after processing
("ST_xxxxxx_FWx_003-Framer") ....................................................................................225
Fig. 7.30 Example - tool screen of the station before processing ("ST_110030_WZ_004") ..........226
Fig. 7.31 Example - tool screen of the station after processing ("ST_110030_WZ_004") .............227

Saved on 06.12.2012
List of Figures
Fig. 7.32 Example - detailed robot screen with corresponding process devices
("Rob_110010R01_006") .................................................................................................228
Fig. 7.33 Example - basic screen for menu navigation ("Grundbild_010") .....................................229
Fig. 7.34 Example - system overview screen before processing ("Anlagenübersicht_011") .........230
Fig. 7.35 Example - system overview screen after processing ("Anlagenübersicht_011") ............231
Fig. 7.36 Example - operating modes ("Betriebsarten_012") .........................................................232
Fig. 7.37 Example - preselections ("Vorwahlen_013") ...................................................................233
Fig. 7.38 Example - robot overview screen ("Roboter_014_Layer1").............................................234
Fig. 7.39 Example - overview screen of robot process devices ("Rob-Prozessgeräte_015") ........235
Fig. 7.40 Example - machine processes ("Maschinenprozesse_016") ..........................................236
Fig. 7.41 Example - system completion reports ("GlobaleStati_017") ............................................237
Fig. 7.42 Example - request screen for operators and parts ("Werkerruf_018") ............................238
Fig. 7.43 Example - statistics & number of units ("Statistik_020") ..................................................239
Fig. 7.44 Example - clock time overview screen ("Taktzeiten_022") ..............................................240
Fig. 7.45 Example - PLC & bus info/diagnostics before processing ("SPS+PN_030") ..................241
Fig. 7.46 Example - template for PLC & bus info/diagnostics ("SPS+PN_030") ............................242
Fig. 7.47 Example - PLC & bus info/diagnostics after processing ("SPS+PN_030") .....................242
Fig. 7.48 Example – PNIO-100 station overview ("PNIO-100_Stationsübersicht") ........................243
Fig. 7.49 Post-processing ...............................................................................................................243
Fig. 7.50 Example – PN overview 019 ("PN-Übersicht_019") ........................................................244
Fig. 7.51 Example – PN overview 019 after processing ("PN-Übersicht_019") .............................245
Fig. 7.52 Example - PLC status value ("SPS_StatusValue") ..........................................................246
Fig. 7.53 Example - step sequencer overview ("Schrittketten_031") ..............................................247
Fig. 7.54 Example - interfaces ("PN/PN_Koppler_ARG2_101") .....................................................248
Fig. 7.55 Example - screen of current messages ("Message display") ..........................................249
Fig. 7.56 Example - message archive ("Meldearchiv_250") ...........................................................250
Fig. 7.57 Example - administration ("Administration") ....................................................................251
Fig. 7.58 Example - screen for starting external applications ("Applikationen") .............................252
Fig. 7.59 Example- detailed screen of SEW drive with AMA binary setpoint value
("Detail_SEW_AMA_Bin") ................................................................................................253
Fig. 7.60 Example - detailed screen of SEW drive with AMA variable setpoint value
("Detail_SEW_AMA_Var") ...............................................................................................254
Fig. 7.61 Example - detailed screen of SEW drive with Modulo ("Detail_SEW_Modulo") .............255
Fig. 7.62 Example - detailed screen of SEW drive with AMX_RB ("Detail_SEW_Modulo") ..........256
Fig. 7.63 Example - detailed screen of SEW drive with AMX_VR ("Detail_SEW_AMX_VR") .......257
Fig. 7.64 Example - detailed screen for display of switching list ("Detail_SchaltlisteSchicht_105")258
Fig. 7.65 Example - detailed screen for display of stylus stamping system
("Detail_Markator120050PR1") ........................................................................................259
Fig. 7.66 Example - detailed screen for display of measuring system
("Detail_Messen_Perceptron1_1M1")..............................................................................260
Fig. 7.67 Example - step sequencer display for the manual operating screen
("Station_Ablaufsteuerung") .............................................................................................261

Saved on 06.12.2012
List of Figures
Fig. 7.68 Creating a new picture .....................................................................................................262

Fig. 7.69 Variable window ...............................................................................................................262
Fig. 7.70 Check mark set for "Use Template" .................................................................................263
Fig. 7.71 Result of overwritten picture with added valve ................................................................264
Fig. 7.72 Result of new picture with added valves ..........................................................................265
Fig. 7.73 Result of delta picture with added valves ........................................................................266
Fig. 7.74 Opening the library ...........................................................................................................267
Fig. 7.75 Selecting the library .........................................................................................................268
Fig. 7.76 Selecting the faceplate .....................................................................................................268
Fig. 7.77 Copying and transferring the faceplate ............................................................................269
Fig. 7.78 Closing the library ............................................................................................................269
Fig. 7.79 "Delete Temporary Files" menu item ...............................................................................270
Fig. 7.80 "Regenerate All…" menu item .........................................................................................271
Fig. 7.81 Generating via generation symbol ...................................................................................272
Fig. 7.82 Supplement entry of required FBs with "I33" ...................................................................273
Fig. 7.83 Device type selection .......................................................................................................273
Fig. 7.84 Sample – GBA_Bild .........................................................................................................274
Fig. 7.85 Renaming "GBA_Bild" .....................................................................................................275
Fig. 7.86 Renaming the variables from "@Generator" ...................................................................275
Fig. 7.87 Renaming the name from connections ............................................................................276
Fig. 7.88 Renaming the instantiated faceplates ..............................................................................276
Fig. 7.89 Merging the GBA figures from several WinCC flexible projects ......................................277
Fig. 7.90 Merging the GBA figures from several WinCC flexible projects ......................................277
Fig. 7.91 Copy of "Protective circuit" template ................................................................................278
Fig. 7.92 Selection of generated variable from the "@Generator" folder .......................................279
Fig. 7.93 Copy of required faceplates for system overview ............................................................279
Fig. 7.94 Creation of system overview with the faceplates from the project-based GBA screens .280
Fig. 7.95 View of levels 00 - 30 .......................................................................................................280
Fig. 7.96 View of levels 00 - 29 .......................................................................................................280
Fig. 7.97 Placing the "Statistics" faceplates before the last controller ............................................281
Fig. 7.98 Removing the "Bildumschaltung_01-02" pointer instrument............................................281
Fig. 7.99 Filling the next "GBA_Anlagenuebersicht_02" screen .....................................................282
Fig. 7.100 Changing the screen name "GBA_Anlagenuebersicht_03" to "…_01" ...........................282
Fig. 8.1 Language-neutral saving .................................................................................................284
Fig. 8.2 Setting the language for the indicators ............................................................................285
Fig. 8.3 Export of project texts ......................................................................................................287
Fig. 8.4 Exporting user texts .........................................................................................................287
Fig. 8.5 Selecting text types ..........................................................................................................288
Fig. 8.6 Providing the created text files from the export directory for translation..........................288
Fig. 8.7 Sample Excel file (Ger / Ger) ...........................................................................................289

Saved on 06.12.2012
List of Figures
Fig. 8.8 Sample Excel file (Ger / Eng) ...........................................................................................290

Fig. 8.9 Importing the translated Excel files ..................................................................................290
Fig. 8.10 Importing user texts .........................................................................................................291
Fig. 8.11 Language Tool .................................................................................................................291
Fig. 8.12 FB 651 "LMsg" .................................................................................................................292
Fig. 8.13 Problems ..........................................................................................................................294
Fig. 8.14 Warnings ..........................................................................................................................295
Fig. 8.15 Messages .........................................................................................................................295
Fig. 8.16 FB 650 "MeldeFB"............................................................................................................296
Fig. 8.17 Selecting and inserting the desired language ..................................................................298
Fig. 8.18 Selecting corresponding text types ..................................................................................298
Fig. 8.21 Performing the language change for the installed language (Chinese) ..........................300
Fig. 8.22 Checking block consistency .............................................................................................300
Fig. 8.23 Performing the language change for the installed language (German) ...........................301
Fig. 8.24 Checking block consistency .............................................................................................301
Fig. 8.25 Opening the "PC677.hmi" file ..........................................................................................302
Fig. 8.26 Integrating WinCC flexible project in STEP 7 ..................................................................302
Fig. 8.27 Selecting the desired languages ......................................................................................303
Fig. 8.28 Placing a check mark also at the second language.........................................................304
Fig. 8.29 Multilingual support ..........................................................................................................305
Fig. 8.30 Storage location of the symbol comments .......................................................................305
Fig. 8.31 Design of the "User dictionary" editor ..............................................................................306
Fig. 8.32 Opening the project text overview....................................................................................310
Fig. 8.33 Automatically translating missing texts ............................................................................310
Fig. 8.34 Accept automatic translation ............................................................................................311
Fig. 8.35 Exporting texts .................................................................................................................311
Fig. 8.37 Export files .......................................................................................................................312
Fig. 8.38 Sample Excel file (Ger / Ger) ...........................................................................................313
Fig. 8.39 Sample Excel file (Ger / Eng) ...........................................................................................313
Fig. 8.40 Importing the translated Excel files ..................................................................................314
Fig. 8.42 Opening the existing WinCC flexible project ....................................................................315
Fig. 8.43 Language selection ..........................................................................................................315
Fig. 8.44 Placing a check mark at "Runtime language" ..................................................................316
Fig. 8.45 Adding/removing the VASS_Benutzerwörterbuch ...........................................................317
Fig. 8.46 Linking the "VASS_Benutzerwörterbuch" ........................................................................317
Fig. 8.47 Saving and closing the current project .............................................................................318

Saved on 06.12.2012
List of Figures
Fig. 8.48 Adjusting DB numbers of TextLibs (DB824 - DB831) ......................................................318

Fig. 8.49 Selecting the language for multilingual support ...............................................................319
Fig. 8.50 Starting the generation .....................................................................................................319
Fig. 8.51 Selecting the storage location of the symbol comments .................................................320
Fig. 8.52 Selecting and opening the required CSV file ...................................................................320
Fig. 8.53 Selecting the device type for the device ..........................................................................321
Fig. 8.54 Settings after the generation ............................................................................................321
Fig. 8.55 Importing the selected panels ..........................................................................................322
Fig. 8.56 Adopting the drop-down list box.......................................................................................322
Fig. 8.57 "Translate Automatically" selection ..................................................................................323
Fig. 8.58 Completing the automatic translation ..............................................................................323
Fig. 8.59 Accept automatic translation ............................................................................................324
Fig. 8.60 Manual insertion of untranslated texts in the project texts ...............................................324
Fig. 8.61 Positioning buttons for selected languages on the Administrator screen ........................325
Fig. 8.62 Adjusting the script for selected languages .....................................................................325
Fig. 9.1 Computing unit (1) and control unit (2) ............................................................................326
Fig. 9.2 Calibrating the touchscreen .............................................................................................327
Fig. 9.3 Assigning a computer name ............................................................................................327
Fig. 9.4 Network cards selection window ......................................................................................328
Fig. 9.5 LAN connection 1 Internet Protocol (TCP/IP) selection ...................................................328
Fig. 9.6 LAN connection 2 Internet Protocol (TCP/IP) selection ...................................................329
Fig. 9.7 PG/PC selection window of network cards ......................................................................329
Fig. 9.8 Editing the safety program ...............................................................................................331
Fig. 9.9 SIMATIC WinCC flexible - Start center ............................................................................332
Fig. 9.10 "WinCC flexible Runtime Loader" start dialog .................................................................333
Fig. 9.11 "Settings" dialog window ..................................................................................................333
Fig. 9.12 Runtime loader "Transfer" ................................................................................................334
Fig. 9.13 Transfer settings ..............................................................................................................334
Fig. 9.15 Server - Remote Operate V2 ...........................................................................................336
Fig. 9.16 Creating a new client .......................................................................................................337
Fig. 9.17 Client was added..............................................................................................................337
Fig. 9.18 Auxiliary control panel MP377 .........................................................................................338
Fig. 9.19 Configuring the MP377 ....................................................................................................338
Fig. 9.21 OP properties ...................................................................................................................339
Fig. 9.22 System properties ............................................................................................................339
Fig. 9.23 "SMC LAN91C111 Ethernet" settings ..............................................................................340
Fig. 9.24 Name server.....................................................................................................................340
Fig. 9.25 Network ID .......................................................................................................................340

Saved on 06.12.2012
List of Figures
Fig. 9.26 Server selection list ..........................................................................................................341

Fig. 9.27 RemoteOperate V2 ..........................................................................................................342
Fig. 9.28 Tree path ..........................................................................................................................342
Fig. 9.29 Full access to the server ..................................................................................................344
Fig. 9.30 Connection to the server ..................................................................................................344
Fig. 9.31 RemoteOperate toolbar ...................................................................................................345
Fig. 9.32 No access to the server ...................................................................................................345
Fig. 9.33 Example - setting of the rotary encoding switches ..........................................................347
Fig. 9.34 RemoteOperate toolbar ...................................................................................................347
Fig. 9.35 Examples for device names .............................................................................................367
Fig. 9.36 Example of F-parameter (type 1) input 4/8 F-DI emergency stop system .......................386
Fig. 9.37 Example of F-parameter (type 1) input 4/8 F-DI emergency stop robot (VKRC2) ..........387
Fig. 9.38 Example of F-parameter (type 1) input 4/8 F-DI emergency stop multi-panel.................388
Fig. 9.39 Example of F-parameter (type 1) input 4/8 F-DI emergency stop drive switch ...............389
Fig. 9.40 Example of F-parameter (type 1) input 4/8 F-DI mobile panel acknowledgment button .390
Fig. 9.41 Example of F-parameter (type 1) input 4/8 F-DI articulated flap variant 2.......................391
Fig. 9.42 Example of F-parameter (type 2) input 4/8 F-DI E2 mobile panel ...................................392
Fig. 9.43 Example of F-parameter (type 2) input 4/8 F-DI non-contact safety switch ....................393
Fig. 9.44 Example of F-parameter (type 2) input 4/8 F-DI LVU ......................................................394
Fig. 9.45 Example of F-parameter (type 2) input 4/8 F-DI PLS ......................................................395
Fig. 9.46 Example of F-parameter (type 2) input 4/8 F-DI E2/protective circuit bypass .................396
Fig. 9.47 Example of F-parameter (type 3) input 4/8 F-DI articulated flap variant 1.......................397
Fig. 9.48 Example of F-parameter (type 4) input 4/8 F-DI stop cylinder .........................................398
Fig. 9.49 Example of F-parameter (type 5) input 4/8 F-DI bridge for commissioning .....................399
Fig. 9.50 Example of F-parameter output 4F-DO start positioners .................................................400
Fig. 9.51 Example of F-parameter for laser shutter switch .............................................................401

Saved on 06.12.2012
List of Tables
List of Tables
Tab. 1.1 Software tools for Windows XP..........................................................................................20
Tab. 1.2 Software-Tools for Windows 7 / 64 bit ...............................................................................21
Tab. 2.1 Hardware requirements .....................................................................................................22
Tab. 4.1 Overview of block distribution ............................................................................................86
Tab. 4.2 Call sequence and base structure of a project ................................................................101
Tab. 4.3 Structure after the $ character .........................................................................................113
Tab. 5.1 Variables of an F-I/O devices DB.....................................................................................151
Tab. 5.2 Safety program block list ..................................................................................................157
Tab. 5.3 F-application blocks in the VASS project library ..............................................................158
Tab. 7.1 Overview of operating screens ........................................................................................217
Tab. 7.2 Manual operating screen of station ..................................................................................222
Tab. 7.3 Tool screen of station .......................................................................................................226
Tab. 7.4 Detailed robot display with pertinent process devices .....................................................228
Tab. 7.5 Basic screen for menu navigation ....................................................................................229
Tab. 7.6 System overview ..............................................................................................................230
Tab. 7.7 Operating modes..............................................................................................................232
Tab. 7.8 Preselections....................................................................................................................233
Tab. 7.9 Robot overview screen ....................................................................................................234
Tab. 7.10 Overview screen of robot process devices ......................................................................235
Tab. 7.11 Machine processes ..........................................................................................................236
Tab. 7.12 System completion reports ..............................................................................................237
Tab. 7.13 Request screen for system operator and parts ................................................................238
Tab. 7.14 Statistics & number of units .............................................................................................239
Tab. 7.15 Clock time overview screen .............................................................................................240
Tab. 7.16 PLC & bus info/diagnostics ..............................................................................................241
Tab. 7.17 PNIO-100_Stationsübersicht ...........................................................................................243
Tab. 7.18 PN-Übersicht_019 ............................................................................................................244
Tab. 7.19 SPS_StatusValue ............................................................................................................246
Tab. 7.20 Step sequencer overview .................................................................................................247
Tab. 7.21 Interfaces .........................................................................................................................248
Tab. 7.22 Screen of current messages ............................................................................................249
Tab. 7.23 Message archive ..............................................................................................................250
Tab. 7.24 Administration ..................................................................................................................251
Tab. 7.25 Screen for starting external applications ..........................................................................252
Tab. 7.26 Detailed screen of SEW drive with AMA binary setpoint value .......................................253
Tab. 7.27 Detailed screen of SEW drive with AMA variable setpoint value .....................................254
Tab. 7.28 Detailed screen of SEW drive with Modulo ......................................................................255

Saved on 06.12.2012
List of Tables
Tab. 7.29 Detailed screen of SEW drive with AMX_RB ...................................................................256

Tab. 7.30 Detailed screen of SEW drive with AMX_VR ...................................................................257
Tab. 7.31 Detailed screen for display of switching list .....................................................................258
Tab. 7.32 Detailed screen for display of stylus stamping system ....................................................259
Tab. 7.33 Detailed screen for display of measuring system ............................................................260
Tab. 7.34 Step sequencer display for manual operating screen......................................................261
Tab. 8.1 Overview for multilingual texts .........................................................................................283
Tab. 8.2 Permissible language selections......................................................................................285
Tab. 8.3 DB numbers of TextLibs ..................................................................................................286
Tab. 8.4 Replacement code for country ID in symbol table ...........................................................286
Tab. 8.5 Input parameter ................................................................................................................293
Tab. 8.6 Output parameter .............................................................................................................293
Tab. 8.7 Input and output parameter ..............................................................................................294
Tab. 8.8 Input parameter ................................................................................................................296
Tab. 8.9 Output parameter .............................................................................................................297
Tab. 8.10 Input and output parameter ..............................................................................................297
Tab. 8.11 Permissible language selections......................................................................................303
Tab. 9.1 Term description of the "Server - RemoteOperate V2" dialog .........................................336
Tab. 9.2 Operating authorization window ("traffic light") ................................................................346
Tab. 9.3 Special functions of the RemoteOperate toolbar .............................................................348
Tab. 9.4 List of Abbreviations / Glossary .......................................................................................365
Tab. 9.5 Overview of F parameters input 4/8 F-DI .........................................................................384
Tab. 9.6 Overview of F-parameter outputs 4 F-DO .......................................................................384
Tab. 9.7 F-parameter application example ....................................................................................385

Saved on 06.12.2012
List of Abbreviations / Glossary
Abbreviation Full text Comment

A STL Statement list
AS Sequential control
ARG Working group
B CBE Conditional block end

BB Faceplate
C CRC Cyclic redundancy check Safety checksum
D DB Data block
DI Digital input
DO Digital output
E ET Electronic terminal
ES Engineering system
F FUP Functional diagram

FB Function block
F-… Fail-safe
FC Function
FM Completed message
FU Frequency converter
REL Release
G GBA Large Picture Display
H HMI Human-machine interface

HF Hotfix
K LAD Ladder logic

CommCon Communication control
L LV Load voltage
LVU Operator safety light barrier

Saved on 06.12.2012
O OB Organization block
OP Operator Panel
OEM Original equipment manufacturer
P PoT Production without parts

PS Process system
PN PROFINET
PLS Laser scanner operator protection
PDE Production data entry
PDD Production data display
PC Personal Computer
PG Programming device
Q
R RO RemoteOperate
Rob Robot
RT Runtime
S SCL Structured control language

PC Protective circuit
PLC Programmable logic controller
SP Service Pack
STI Interconnecting structure
ST Station
PC Sequences
PC Protective circuit
RSE Report system errors
SSL System status list
SiVArc Siemens Visualization Architect The system analyzes STEP 7
application projects and automatically
generates visualizations from them for
WinCC flexible.
The SiVArc system is divided into three
software packages:
- Template Designer
- Update Manager
- Screen Generator

Saved on 06.12.2012
Screen Generator (SiVArc) The Screen Generator generates the

WinCC flexible visualization from a
STEP 7 application project and the
rules sets.
- Automatic generation of WinCC
flexible visualization projects
- Flexible selection of HMI device
type
- Preview of auto-import result
- Generation of multilingual
message texts
- Automatic access to the
Volkswagen message text
database
- Automatic import in WinCC flexible
- Detailed instructions for manual
post-processing
- Convenient analysis of the result
using plain-text log files
T TIA Totally integrated automation

Template Designer (SiVArc) The Template Designer creates rules
sets for placing the elements, e.g.
pictures, faceplates, scripts, etc.
U UDT User-defined data type

UBA Operating submode
Update Manager (SiVArc) The Update Manager distributes all the
data required for the generation of
WinCC flexible projects to the
Engineering System.
- Storage and update of all
project files
- Libraries
- Documentation
- Reference projects
- SiVArc Setup
- Rules set
- Data distribution conveniently
configurable
- Distribution of STEP 7 block help
V VASS Volkswagen Audi Seat Skoda VASS Standard:

Software standard for Volkswagen
Audi Seat Skoda (currently for body
manufacturing)
V Version
RLO Logic operation result
W WCF WinCC flexible

Saved on 06.12.2012
Z CSM Central system monitoring
Tab. 9.4 List of Abbreviations / Glossary

Saved on 06.12.2012
Appendix
Appendix
A: PROFINET Device Names
Project creation (hardware configuration)

Examples for device names
PROFINET device names

= ++ + -
Protective circuit
Equipment designation IP ranges IP address EPLAN identifier
BMS/PLC no.
Ext. stations
designation
Plant / Unit
Segment
Station
Device
BMK
Area
CPU 319F-3 PN/DP PLC 192 . 168 . 0 . 10 =KASTAN++1BS+ALLG-KU K A S T A N 1 - - - - - B S - A L L G K U X
IM151-3PN FO 192 . 168 . 0 . 11 =KASTAN++1KV+-KA1 K A S T A N 1 - - - - - K V - - - - - K A 1
IM151-3PN FO 192 . 168 . 0 . 12 =KASTAN++1SV+-KA1 K A S T A N 1 - - - - - S V - - - - - K A 1
IM151-3PN FO 192 . 168 . 0 . 13 =KASTAN++1BS+ALLG-KA1 K A S T A N 1 - - - - - B S - A L L G K A 1
PN-PN Coupler ARG1 <> ARG2 192 . 168 . 0 . 14 =KASTAN++1BS+ALLG-K51 K A S T A N 1 - - - - - B S - A L L G K 5 1
IM151-3PN FO 192 . 168 . 0 . 20 =KASTAN++11+K1-KA1 K A S T A N 1 1 - - - - - - - K - - 1 K A 1
KP8 192 . 168 . 0 . 21 =KASTAN++11+I1-PB1 K A S T A N 1 1 - - - - - - - I - - 1 P B 1
IM151-3PN HF PROFINET devices 192 . 168 . 0 . 22 =KASTAN++11+I1-KA1 K A S T A N 1 1 - - - - - - - I - - 1 K A 1
EX245-PN-FX 192 . 168 . 0 . 27 =KASTAN++11HP+VI1-KA1 K A S T A N 1 1 - - - - H P - V I - 1 K A 1
IM151-3PN FO 192 . 168 . 0 . 28 =KASTAN++110010SF1+K1-KA1 K A S T A N 1 1 0 0 1 0 S F 1 K - - 1 K A 1
IM151-3PN FO 192 . 168 . 0 . 29 =KASTAN++110010DT1+K1-KA1 K A S T A N 1 1 0 0 1 0 D T 1 K - - 1 K A 1
SEW-MOVIPRO 192 . 168 . 0 . 30 =KASTAN++110010DT1+AE1-TM1 K A S T A N 1 1 0 0 1 0 D T 1 A E - 1 T M1
EX245-PN-FX 192 . 168 . 0 . 31 =KASTAN++110011+VI1-KA1 K A S T A N 1 1 0 0 1 1 - - - V I - 1 K A 1

Saved on 06.12.2012
Appendix

SCALANCE-X202-2PIRT 192 . 168 . 0 . 165 =KASTAN++1BS+ALLG-KA2 K A S T A N 1 - - - - - B S - A L L G K A 2
SCALANCE-XF206-1 192 . 168 . 0 . 166 =KASTAN++1BS+ALLG-KA3 K A S T A N 1 - - - - - B S - A L L G K A 3
SCALANCE-X201-3PIRT Switches 192 . 168 . 0 . 168 =KASTAN++110010R01+RS-KA1 K A S T A N 1 1 0 0 1 0 R 0 1 R S - - K A 1
SCALANCE-X201-3PIRTPRO 192 . 168 . 0 . 169 =KASTAN++110010DT1+VI1-KA1 K A S T A N 1 1 0 0 1 0 D T 1 - V I 1 K A 1
SCALANCE-X202-2PIRT 192 . 168 . 0 . 176 =KASTAN++12+I1-KA2 K A S T A N 1 2 - - - - - - - I - - 1 K A 2
PSS6000WeldTimer Welding controls 192 . 168 . 0 . 215 =KASTAN++110030SK1+1-KA1 K A S T A N 1 1 0 0 3 0 S K 1 - - - 1 K A 1
kuka-noname Robot 192 . 168 . 0 . 230 =KASTAN++110010R01+-KU K A S T A N 1 1 0 0 1 0 R 0 1 - - - - K U X
Fig. 9.35 Examples for device names

Saved on 06.12.2012
Siemens AG
Page 367 of 402
Appendix
B: Hardware Configuration for PROFINET Nodes
Note
The device name must be entered under the "General" properties view. In the "Comment" field, the
short name as well as the location identifier from the hardware plan must be entered. The device
number is formed by the last block of the IP address.
Integrating an ET200S

Saved on 06.12.2012
Appendix
Integrating a switch

Saved on 06.12.2012
Appendix
Integrating a valve terminal (SMC)

Saved on 06.12.2012
Appendix
Integrating a KUKA robot (VKRC4)

Saved on 06.12.2012
Appendix
Integrating an SEW converter (MOVIDRIVE)
The device name must be entered

under the properties view.
In the "Comment" field, the short name as

well as the location identifier from the
hardware plan must be entered to be
able to locate the object in EPLAN.
The address assignments can be found

in the address area in the hardware
plan.

Saved on 06.12.2012
Appendix
Integrating an SEW converter (MOVIFIT)

Saved on 06.12.2012
Appendix

Saved on 06.12.2012
Appendix
Integrating an SEW converter (MOVIPRO)

Saved on 06.12.2012
Appendix

Saved on 06.12.2012
Appendix
C: List for Labeling Rules

Text positions (black):  fixed texts
Text positions (blue/green):  variable texts
Syntax of the symbol name Example symbol name Example comment Syntax of
Module FB
of the instance DB of the instance DB of instance DB comment
FB 100 BA_protective circuit name BA_11 Operating modes
FB 101 BA_LSP_protective circuit name BA_LSP_11 Start On
FB 102 BA_station name BA_110011 Operating mode select
FB 104 BA_station name BA_110010 Operating modes
FB 105 SK_protective circuit name SK_11 Protective circuit
FB 106 SK_protective circuit name SK_11 Protective circuit_16
FB 107 SK_protective circuit name SK_external Protective circuit_external
FB 108 SK_protective circuit name SK_11 Protective circuit_oBA
FB 109 SN_emergency stop number SN_1 Emergency Stop
FB 113 RUF_station name RUF_110010 Operator call
FB 114 Status_robot or station name Status_110010R01 Collective status
FB 116 RobMedien_robot name RobMedien_110010R01 Media
FB 118 Druckluft_protective circuit name Druckluft_11 Compressed air
FB 120 Druckluft_protective circuit name Druckluft_11 Druckluft_VW370
FB 121 mobile panel name_RO 1I4_RO
FB 122 DB_RemoteOperate
FB 123 KommKon_name of adjacent working group KommKon_ARG2 Interface
FB 124 Visu_PanelPC name Visu_1I1
Status_station number_FMcompletion Completion report robot
FB 125 Status_110011_FM1 used in stations
report number 110010R01
FB 125 Status_station number_FMges Status_120050_FMGes Completion report overall used in stations
Status_robot number_FMcompletion report
FB 126 Status_110010R01_FM1 FM welding station 0011-0014 used in robots
number
FB 126 Status_robot number_FMges Status_120040R02_FMges FM overall used in robots
FB 127 KommKon_name of adjacent working group KommKon_ARG2 Interface
FB 128 LVU_light curtain name LVU_110010SF1B12 LVU

Saved on 06.12.2012
Siemens AG
Page 377 of 402
Appendix
FB 129 PLS_scanner name PLS_110030SF1B12 PLS

FB 130 ST_status_station name ST_status_110010 Station jams
FB 134 Z_station Z_110010 Counter
FB 135 Freigabe_station name Freigabe_120070 Release
FB 136 Vorwahl_manual or type Vorwahl_manual Manual preselection
(Direkt or Zentral)absaugung_protective
FB 137 Direktabsaugung_11 Suction
circuit
FB 138 Brand_protective circuit Brand_11
FB 140 Roboternummer_A80_profile-free robot 110010R01_A80_PF1V1 Status
_Stationsnummer
 used only if the profile-
Roboternummer_A80_profile-free
FB 140 110010R01_A80_PF1V1_11 Status free should be displayed on
robot_station number
several screens
(uniqueness of the element)
FB 141 Hauptschalter_main switch name Hauptschalter_1SVQ1 Main switch
FB 142 Leistungsschalter_item designation Leistungsschalter_1SVQ1 Circuit breaker
FB 143 Status_station nameK100 Status_110010K100 Status_K100
FB 143 Status_station name_tool Status_110040_DT1M1K100 Status_K100
FB 145 Vorwahl_station name Vorwahl_110011 Preselection
FB 146 VorwAusschl_station name VorwAusschl_120060 Preselection
FB 148 Vorwahl_station Vorwahl_110011 Preselection
FB 149 Schleusen_station name Schleusen_120060 Locks
FB 150 MIA_station name MIA_110010 Personnel information traffic light
FB 150 MIA_station name_additional info MIA_110030_Werker Personnel information traffic light
FB 152 KW_station name KW_110030 Coolant
FB 154 GBA_protective circuit number GBA_11 GBA
FB 156 Kuehlwasser_protective circuit number Kuehlwasser_11 Coolant
FB 157 Energie_name of work group Energie_ARG1 Energy
FB 158 GP_BMK GP_110010GP1 PermaStarControl
FB 200 Roboter_robot name Roboter_110010R01 Robot
FB 201 Rob_A_robot name Rob_A_110010R01 Inputs
FB 202 Rob_E_robot name Rob_E_110020R01 Robot inputs
FB 203 RobFolge_robot name RobFolge_110010R01 Sequence selection

Saved on 06.12.2012
Appendix
FB 205 Rob_FM_robot name Rob_FM_110010R01 Completion reports

FB 206 Rob_Korr_robot name Rob_Korr_110010R01 Process point correction
FB 207 Frg_Ver_robot name Frg_Ver_110010R01 Interlocks
FB 208 Rob_FRGnumber_robot name Rob_Frg1_110010R01 Tool releases
FB 209 Rob_Ver_robot name Rob_Ver_210070R01 External interlocks
FB 210 Rob_StellFrgnumber_robot name Rob_StellFrg1_110010R01 Position releases
FB 250 RobPG_robot nameprocess device identifier RobPG_110010R01G1 Gripping
FB 251 RobPG_robot nameprocess device identifier RobPG_110010R01SK1 Welding
FB 252 RobPG_robot nameprocess device identifier RobPG_110020R01KL1 Bonding
FB 253 RobPG_robot nameprocess device identifier RobPG_110040R01BZ1 Bolt
FB 254 RobPG_robot nameprocess device identifier RobPG_110020R02MS1 MIGMAG
FB 255 RobPG_robot nameprocess device identifier RobPG_110020R02BU1 Brushing
FB 256 RobPG_robot nameprocess device identifier RobPG_110020R02XX1 Joining
FB 257 RobPG_robot nameprocess device identifier RobPG_110020R02DAS1 DAS
FB 258 RobPG_robot nameprocess device identifier RobPG_110020R02LK1 LLBHead
FB 259 RobPG_robot nameprocess device identifier RobPG_110020R02DG1 DVG_K
FB 260 RobPG_robot nameprocess device identifier RobPG_110020R02XX1 DVG_H
FB 261 RobPG_robot nameprocess device identifier RobPG_110020R02LA1 Laser
FB 262 RobPG_robot nameprocess device identifier RobPG_110020R02LM1 Measuring
FB 263 RobPG_robot nameprocess device identifier RobPG_110020R02NZ1 Riveting
FB 264 RobPG_robot nameprocess device identifier RobPG_110020R02XX1 Punching
FB 265 Rob_Opt_robot name Rob_Opt12_113410R03 ROB_EA
FB 266 RobPG_robot nameprocess device identifier RobPG_110020R02XX1 Bulging
FB 267 RobPG_robot nameprocess device identifier RobPG_110020R02WI1 Wiping
FB 269 Auxiliary function Option
FB 270 RobPG_robot nameprocess device identifier RobPG_110020R02KP1 PFO
FB 271 RobPG_robot nameprocess device identifier RobPG_110020R02PZ1/EZ1 Electrode holder
FB 272 RobPG_robot nameprocess device identifier RobPG_110020R02XX1 Laser holder
FB 274 RobPG_robot nameprocess device identifier RobPG_110020R02SR11 Screws
FB 275 RobPG_robot nameprocess device identifier RobPG_110020R02LL1 Primes
FB 307 SST_Nr_name of welding control_ spot SST_Nr_1WS3A1_9336 Welding spot release

Saved on 06.12.2012
Siemens AG
Page 379 of 402
Appendix
number
FB 308 SST_name of welding control SST_1WS3A1 Welding control
Brief function description item
FB 350 DT_110040DT1M1_T SEW_STAN
designation_T
FB 351 DT_110040DT1M1_T SEW_FU
designation_T
FB 352 DT_110040DT1M1_T SEW_AMA_Var
designation_T
FB 356 DT_name of rotary table_T DT_110040DT1M1_T Rotary table D D = driver
only two positions,
FB 357 DT_name of rotary table_position DT_110040DT1M1_PosR Rotary table position
PosR and PosV
FB 359 DT_name of rotary table_T DT_110010DT1M1_T Rotary table D D = driver
FB 360 DT_name of rotary table_Posnumber DT_110010DT1M1_Pos1 Rotary table position
FB 364 DT_110040DT1M1_T MoviFit_AMX_VR
designation_T
FB 365 DT_110040DT1M1_T MoviFit_AMX_RB
designation_T
FB 378 DT_110040DT1M1_A SEW_FU_A
designation_A
FB 379 DT_110040DT1M1_E SEW_FU_E
designation_E
FB 380 DT_110040DT1M1_T MotorstartFRS1ex
designation_T
FB 400 MZ_cylinder name MZ_110011MZ11 Clamping cylinder
FB 401 Funktionskurzbezeichung_item designation MZ_110041MZ12 Valve hook SP
FB 402 MZ_cylinder name MZ_110020MZ12 Suction cylinder
FB 403 BT_name of component control BT_110011BT11/1 Main part
FB 404 MZ_cylinder name MZ_110041MZ12 Manual tensioner
FB 405 Funktionskurzbezeichung_item designation MZ_110041MZ12 Valve 1V 3S
FB 408 MZ_cylinder name MZ_110030MZ32 Offset cylinder
FB 409 KYP_name of switch-on valve KYP_110011VI1KYP01E Switch-on valve
FB 410 MZ_cylinder name MZ_110041MZ13 Clamping cylinder
FB 411 Funktionskurzbezeichung_item designation ST_110040M1 Twister FU_2S
FB 420 Funktionskurzbezeichung_item designation MZ_110011MZ11 Ventil_2
FB 453 RB_BMK RB_110040RB1M1 Elefant_AMX

Saved on 06.12.2012
Appendix
FB 454 RB_BMK RB_110040RB1M2 Elefant_AMX

Funktionskurzbezeichung_item designation
FB 461 DT_110040DT1M1 Drehtisch_2S
Funktionskurzbezeichung_item
FB 462 designation_ DT_110040DT1M1_Pos1 DT_POS
PosKennzeichung
FB 463 Funktionskurzbezeichung_item designation DT_110040DT1M1 Drehtisch_8S
FB 464 SF_name of protective window SF_110010SF1M1 Protective window
FB 467 Funktionskurzbezeichung_item designation M_110010M1 Motor_AMX_VR
FB 468 Funktionskurzbezeichung_item designation M_110010M1 Motor
FB 469 TB_BMK TB_210090SB1M1 Cycle conveyor
FB 474 HE_BMK HE_120020RB1_M2 HubExpert
FB 475 HE_BMK HE_120020RB1_M2 Hubremech
FB 476 SB_BMK SB_210050SB1M1 Motor_VR
FB 477 DT_name of rotary table DT_110040DT1M1 Rotary table Drive
FB 478 DT_name of rotary table DT_110010DT1M1 Rotary table Drive
FB 479 OH_BMK OH_110010M1 Overhead_Y
FB 480 OH_BMK OH_110010M2 Overhead_Z
FB 481 Funktionskurzbezeichung_item designation HE_110010M1 LineareinheitFU_8S
FB 482 Funktionskurzbezeichung_item designation DT_213460D1TM1 TrommelFU_8S
FB 483 Funktionskurzbezeichung_item designation HE_110010M1 FU_16S
FB 491 FWcar number_TMengine number FW1_TM1 Framer
FB 499 QG_BMK QG_110010M5 QF_AMX
FB 500 PR_BMK_Text PR_110010PR1_Text Stamping text
FB 501 PR_BMK_Text PR_110010PR1_Text Prägetext_VW37x
FB 503 Markator_name of marker Markator_120050PR1 Markator
FB 504 PR_BMK PR_120050PR1 Markator_IB

Saved on 06.12.2012
Siemens AG
Page 381 of 402
Appendix
FB 505 Markator_name of marker_DS Markator_120050PR1_DS Markator data

FB 506 Markator_name of marker_E Markator_120050PR1_E Markator inputs
FB 507 Markator_name of marker_A Markator_120050PR1_A Markator outputs
FB 508 Perceptron_name of measuring instrument Perceptron_120050LM1 Perceptron
Perceptron_name of measuring
FB 509 Perceptron_120050LM1_Dat Perceptron data
instrument_Dat
FB 510 Perceptron_120050LM1_E Perceptron inputs
instrument_E
FB 511 Perceptron_120050LM1_A Perceptron outputs
instrument_A
FB 513 LM_BMK LM_120050LM1 Inline measuring
FB 514 LM_BMK_Dat LM_120050LM1_Dat Inline data
FB 515 LM_BMK_E LM_120050LM1_E InlineMessen_E
FB 516 LM_BMK_A LM_120050LM1_A InlineMessen_A
FB 517 LL_BMK LL_120050LM1 Primes
FB 519 IS_BMK IS_120050IS1 Sick_RFU_Taufe
FB 520 IS_BMK IS_120050IS1 Sick_RFU
FB 521 TYP_station TYP_120050 Typ_WOB
FB 522 TYP_station TYP_120050 Typ_ZWI
FB 526 IS_BMK IS_120050IS1 PFD_IPT
FB 529 KP8_name of key field KP8_11I1PB1 Key field
FB 534 BG_BMK BG_110010M1 Falzen_Haupt
FB 535 BG_BMK BG_110010M1 Falzen_C_Bügel
FB 536 BG_BMK_E BG_110010M1_E Falzen_E
FB 537 BG_BMK_A BG_110010M1_A Falzen_A
FB 540 KG_BMK KG_120050KG1 DVS_Datamatrix
FB 541 IS_BMK IS_120050IS1 Sick_CLV
FB 550 FIFO_Station FIFO_120060 FIFO
FB 551 LIFO_Station LIFO_120060 LIFO
FB 600 ZAUE_GRD ZAUE_GRD
FB 601 ZAUE_Schalt_number ZAUE_Schalt_1
FB 604 SL_switching ID SL_20 ZAU_Schaltliste

Saved on 06.12.2012
Appendix
FB 620 PDE_Schicht_name of work group PDE_Schicht_ARG1

FB 621 PDE_Statistik_name of work group PDE_Statistik_ARG1
FB 622 Statistics Statistics Statistics
FB 623 Statistik_count request Statistik_2T Statistik_Typ e.g. 2-door
FB 624 TZ_BMK TZ_110010 Clock time
FB 625 TZ_equipment name TZ_110010DT1 Taktzeit_Plus
FB 642 AS_station name_S7GC AS_110010_S7GC Sequential control
FB 652 Melden_number Melden_1 Report
FB 653 Melden_number Melden_1 Meld_8

Saved on 06.12.2012
Siemens AG
Page 383 of 402
Appendix
D: Distributed safety
4/8F
entire component per channel
Type of
Behavior after Short circuit Sensor Discrepancy Reintegration after
Type Sensor evaluation sensor Discrepancy reaction
channel fault test supply time discrepancy error
interconnection
Passivating the
Disable internal 1oo2(2v2) evaluation 2-channel antivalent supply 0-value 10-30000 Test 0-Signal required
entire component
Passivating the channel Cyclic External 1oo2(2v2) evaluation 2-channel equivalent Supply last valid value Test 0-Signal not required
1oo2(2v2) evaluation 1-channel
1oo1(1v1) evaluation 1-channel
1 Passivating the channel Cyclic internal 1oo2(2v2) evaluation 2-channel equivalent supply 0-value 500 Test 0-Signal required
2 Passivating the channel Cyclic External 1oo2(2v2) evaluation 2-channel equivalent supply 0-value 500 Test 0-Signal required
3 Passivating the channel Cyclic External 1oo2(2v2) evaluation 2-channel antivalent supply 0-value 500 Test 0-Signal required
4 Passivating the channel Cyclic External 1oo1(1v1) evaluation 1-channel Standard 10 Test 0-Signal required
5 Passivating the channel Cyclic internal 1oo2(2v2) evaluation 2-channel equivalent supply 0-value 30000 Test 0-Signal not required
6 Passivating the channel Cyclic internal 1oo2(2v2) evaluation 2-channel antivalent supply 0-value 500 Test 0-Signal required
Tab. 9.5 Overview of F parameters input 4/8 F-DI
4 F-DO
entire component per channel
Behavior after Diagnostic
Type Enabled Read-back time
channel fault wire break
Passivating the
yes 1 … 400 yes
entire component
Passivating the channel no no
all Passivating the channel yes 1 ms no
Tab. 9.6 Overview of F-parameter outputs 4 F-DO

Saved on 06.12.2012
Appendix
Type Example of an application

1 Emergency stop system
1 Emergency stop robot (VKRC2)
1 Mobile enabling key
1 Drive switch
1 Articulated flap variant 2
2 Non-contact safety switch

2 LVU
2 PLS
2 E2 robot
2 E2 mobile panel
3 Articulated flap variant 1
4 Stop cylinder
4 Drive On Enable from robot R01K61
5 IBS bridge
6 Two-hand panel
Tab. 9.7 F-parameter application example

Saved on 06.12.2012
Siemens AG
Page 385 of 402
Appendix
Fig. 9.36 Example of F-parameter (type 1) input 4/8 F-DI emergency stop system

Saved on 06.12.2012
Appendix
Fig. 9.37 Example of F-parameter (type 1) input 4/8 F-DI emergency stop robot (VKRC2)

Saved on 06.12.2012
Siemens AG
Page 387 of 402
Appendix
Fig. 9.38 Example of F-parameter (type 1) input 4/8 F-DI emergency stop multi-panel

Saved on 06.12.2012
Appendix
Fig. 9.39 Example of F-parameter (type 1) input 4/8 F-DI emergency stop drive switch

Saved on 06.12.2012
Siemens AG
Page 389 of 402
Appendix
Fig. 9.40 Example of F-parameter (type 1) input 4/8 F-DI mobile panel acknowledgment button

Saved on 06.12.2012
Appendix
Fig. 9.41 Example of F-parameter (type 1) input 4/8 F-DI articulated flap variant 2

Saved on 06.12.2012
Siemens AG
Page 391 of 402
Appendix
Fig. 9.42 Example of F-parameter (type 2) input 4/8 F-DI E2 mobile panel

Saved on 06.12.2012
Appendix
Fig. 9.43 Example of F-parameter (type 2) input 4/8 F-DI non-contact safety switch

Saved on 06.12.2012
Siemens AG
Page 393 of 402
Appendix
Fig. 9.44 Example of F-parameter (type 2) input 4/8 F-DI LVU

Saved on 06.12.2012
Appendix
Fig. 9.45 Example of F-parameter (type 2) input 4/8 F-DI PLS

Saved on 06.12.2012
Siemens AG
Page 395 of 402
Appendix
Fig. 9.46 Example of F-parameter (type 2) input 4/8 F-DI E2/protective circuit bypass

Saved on 06.12.2012
Appendix
Fig. 9.47 Example of F-parameter (type 3) input 4/8 F-DI articulated flap variant 1

Saved on 06.12.2012
Siemens AG
Page 397 of 402
Appendix
Fig. 9.48 Example of F-parameter (type 4) input 4/8 F-DI stop cylinder

Saved on 06.12.2012
Appendix
Fig. 9.49 Example of F-parameter (type 5) input 4/8 F-DI bridge for commissioning

Saved on 06.12.2012
Siemens AG
Page 399 of 402
Appendix
Fig. 9.50 Example of F-parameter output 4F-DO start positioners

Saved on 06.12.2012
Appendix
Fig. 9.51 Example of F-parameter for laser shutter switch

Saved on 06.12.2012
Siemens AG
Page 401 of 402
Appendix

Saved on 06.12.2012

VASS Standard Configuration Guideline V 1.7

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VASS Standard Configuration Guideline V 1.7

Uploaded by

Copyright:

Available Formats

VASS Standard

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

Reference / Note (to other documentation)

In development, technical clarification / initial processing or revision

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

Changes to the preceding revision level

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

 Ch. 3.1.3 Link "Chapter 6 SiVArc" (p. 52) was updated.

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

Siemens AG Siemens AG Copyright ©

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

evopro systems engineering AG Document Authoring

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

1 . Introduction and Objectives ............................................................................... 19

2 . System Configuration ......................................................................................... 22

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

3.2.1 ....... Block help for Windows XP .....................................................................................................54

4 . Project creation ................................................................................................... 61

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

4.8.3 ....... F Call .....................................................................................................................................106

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

4.8.8.3.2 ........... "FB_Statistik_Typ" block .............................................................................................128

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

4.9 .... Block update .............................................................................................................................141

5 . S7 Distributed Safety ........................................................................................ 142

6 . SiVArc (Siemens Visualization Architect) ....................................................... 168

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

6.3 .... Preparing the S7 project ..........................................................................................................173

7 . WinCC flexible ................................................................................................... 204

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

7.2.3.18 ....... PLC status value ("SPS_StatusValue") ...........................................................................246

8 . Multiple languages ............................................................................................ 283

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

8.3.2.2 ......... Automatically translating missing texts ............................................................................310

9 . Commissioning at the system .......................................................................... 326

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

List of Abbreviations / Glossary........................................................................... 362

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

1 Introduction and Objectives

1.1.2 Basics of the objective

1.1.3 Target groups

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

1.1.4 Follow-up versions

1.2 Software tools for the configuration

1.2.1 Software tools for the configuration with Windows XP

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

1.2.2 Software tools for the configuration with Windows 7 / 64 bit

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

2.1 Hardware requirements for programming environment

Tab. 2.1 Hardware requirements

Configuring the "3-GB switch function" for Microsoft Windows XP

Reference / Note (to other documentation)

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

2.2 Software installation

Reference / Note (to other documentation)

2.2.1.1 Installing the software

VASS Standard Configuration Guideline_V_1_7.doc Version 1.7

2.2.2 S7 Distributed Safety

2.2.2.1 Installing the software

Version 1.7 VASS Standard Configuration Guideline_V_1_7.doc

2.2.3 WinCC flexible