WinCC V11 Manual
WinCC V11 Manual
WinCC V11 Manual
WinCC
WinCC Advanced V11.0 SP1
System Manual
Online help printout
08/2011
System overview of STEP 7
and WinCC
1
Readme
2
Installation
3
Migrating projects
4
First steps
5
Introduction to the TIA Portal
6
Editing projects
7
Editing devices and networks
8
Visualizing processes
(Advanced)
9
Using online and diagnostics
functions
10
Glossary
11
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These 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 a safety alert symbol, 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 unintended result or situation can occur if the relevant information is not taken into account.
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.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by are registered trademarks of 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.
Siemens AG
Industry Sector
Postfach 48 48
90026 NRNBERG
GERMANY
08/2011
Copyright Siemens AG 2011.
Technical data subject to change
Table of contents
1 System overview of STEP 7 and WinCC....................................................................................................21
1.1 Scaling of STEP 7 and WinCC....................................................................................................21
1.2 Options for STEP 7 Engineering System....................................................................................23
1.3 Options for WinCC Engineering and Runtime systems...............................................................24
2 Readme......................................................................................................................................................27
2.1 General notes..............................................................................................................................27
2.1.1 General notes..............................................................................................................................27
2.1.2 Notes on the installation..............................................................................................................30
2.1.3 Use of communications processors.............................................................................................32
2.2 WinCC Readme...........................................................................................................................33
2.2.1 Functional Constraints.................................................................................................................33
2.2.2 Notes on use...............................................................................................................................33
2.2.3 Migration......................................................................................................................................36
2.2.4 Special considerations for Windows 7.........................................................................................37
2.2.5 Engineering System....................................................................................................................38
2.2.5.1 Screens and Screen Objects.......................................................................................................38
2.2.5.2 Tags.............................................................................................................................................41
2.2.5.3 Alarm system and alarm displays................................................................................................42
2.2.5.4 System functions and scripts.......................................................................................................42
2.2.5.5 Recipes........................................................................................................................................43
2.2.5.6 User administration......................................................................................................................43
2.2.5.7 Communication............................................................................................................................43
2.2.6 Compiling and loading.................................................................................................................46
2.2.7 Runtime.......................................................................................................................................49
2.2.7.1 Notes on operation in Runtime....................................................................................................49
2.2.7.2 Notes on operation of panels in Runtime....................................................................................49
2.2.7.3 Notes on operation of Runtime Advanced...................................................................................50
2.2.8 HMI devices.................................................................................................................................50
2.2.8.1 General notes..............................................................................................................................50
2.2.8.2 Printing via print server................................................................................................................51
3 Installation..................................................................................................................................................53
3.1 System requirements for installation...........................................................................................53
3.1.1 Notes on the system requirements..............................................................................................53
3.1.2 System requirement for WinCC Advanced..................................................................................54
3.1.2.1 Software and hardware requirements.........................................................................................54
3.1.2.2 Add-ons.......................................................................................................................................56
3.1.2.3 Licenses and Powerpacks...........................................................................................................59
3.2 Licenses......................................................................................................................................67
3.3 Installation log..............................................................................................................................68
3.4 Starting installation......................................................................................................................69
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 3
3.5 Installing Support Packages........................................................................................................71
3.6 Displaying the installed software.................................................................................................72
3.7 Modifying or updating installed products.....................................................................................73
3.8 Repairing installed products........................................................................................................75
3.9 Starting to uninstall......................................................................................................................77
3.10 Installing and uninstalling the migration tool................................................................................79
3.10.1 System requirements...................................................................................................................79
3.10.2 Installing the migration tool..........................................................................................................79
3.10.3 Uninstalling the migration tool.....................................................................................................80
4 Migrating projects.......................................................................................................................................81
4.1 Migrating projects........................................................................................................................81
4.2 Preparing projects with the migration tool...................................................................................83
4.2.1 Migrating projects with the migration tool....................................................................................83
4.2.2 Calling the migration tool.............................................................................................................84
4.2.3 Creating a migration file...............................................................................................................84
4.3 Migrating projects........................................................................................................................86
4.4 Displaying the history of the migration.........................................................................................88
4.5 Displaying the log file of the migration.........................................................................................89
4.6 Migrating WinCC flexible projects (Advanced)............................................................................90
4.6.1 Principles (WinCC flexible)..........................................................................................................90
4.6.1.1 Migration (WinCC flexible)...........................................................................................................90
4.6.1.2 Migration principles (WinCC flexible)...........................................................................................91
4.6.1.3 Migrating projects from WinCC flexible (WinCC flexible)............................................................92
4.6.1.4 Compiling and loading a migrated project (WinCC flexible)........................................................94
4.6.2 Migrating engineering data (WinCC flexible)...............................................................................95
4.6.2.1 HMI devices (WinCC flexible)......................................................................................................95
4.6.2.2 Object support during migration (WinCC flexible).....................................................................100
4.6.2.3 Changes of values of object properties by the migration (WinCC flexible)................................102
4.6.2.4 Connections (WinCC flexible)....................................................................................................103
4.6.2.5 Migration of tags (WinCC flexible).............................................................................................106
4.6.2.6 Migration of logs........................................................................................................................108
4.6.2.7 Migration of alarm classes and alarm groups (WinCC flexible).................................................108
4.6.2.8 Migration of scripts (WinCC flexible).........................................................................................111
4.6.2.9 Migration of language-specific content (WinCC flexible)...........................................................112
4.6.2.10 Migration of libraries (WinCC flexible).......................................................................................114
4.6.3 Migrating runtime data (WinCC flexible)....................................................................................115
4.6.3.1 Migration of runtime data (WinCC flexible)................................................................................115
4.6.3.2 Backing up recipe data and user administration (WinCC flexible).............................................116
4.6.3.3 Restoring recipe data and user administration (WinCC flexible)...............................................117
4.6.3.4 Backing up log data (WinCC flexible)........................................................................................118
4.6.4 Migrating integrated projects (WinCC flexible)..........................................................................118
4.6.4.1 Migration of integrated projects (WinCC flexible)......................................................................118
4.6.4.2 Migrating integrated project (WinCC flexible)............................................................................119
4.6.5 Reference (WinCC flexible).......................................................................................................121
4.6.5.1 Migration of data types (WinCC flexible)...................................................................................121
4.6.5.2 Migrating data types of Allen-Bradley DF1 (WinCC flexible).....................................................123
Table of contents
WinCC Advanced V11.0 SP1
4 System Manual, 08/2011,
4.6.5.3 Migrating data types of Allen-Bradley DF485 (WinCC flexible).................................................124
4.6.5.4 Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible)..........................................124
4.6.5.5 Migrating data types of GE Fanuc SNP (WinCC flexible)..........................................................125
4.6.5.6 Migrating data types of LG GLOFA GM (WinCC flexible).........................................................125
4.6.5.7 Migrating data types of Mitsubishi FX (WinCC flexible).............................................................126
4.6.5.8 Migrating data types of Mitsubishi Protocol 4 (WinCC flexible).................................................127
4.6.5.9 Migrating data types of Modicon Modbus (WinCC flexible).......................................................127
4.6.5.10 Migrating data types of Modicon Modbus TCP/IP (WinCC flexible)..........................................128
4.6.5.11 Migrating data types of Omron Hostlink/Multilink (WinCC flexible)...........................................128
4.6.5.12 Migrating data types of OPC (WinCC flexible)..........................................................................129
4.6.5.13 Migrating data types of SIMATIC 500/505 DP (WinCC flexible)................................................130
4.6.5.14 Migrating data types of SIMATIC 500/505 serial (WinCC flexible)............................................130
4.6.5.15 Migrating data types of SIMATIC HMI HTTP Protocol (WinCC flexible)...................................131
4.6.5.16 Migrating data types of SIMATIC S5 AS511 (WinCC flexible)..................................................131
4.6.5.17 Migrating data types of SIMATIC S5 DP (WinCC flexible)........................................................132
4.6.5.18 Migrating data types of SIMATIC S7 200 (WinCC flexible).......................................................133
4.6.5.19 Migrating data types of SIMATIC S7 300/400 (WinCC flexible)................................................133
4.6.5.20 Migrating data types of Telemecanique Uni-Telway (WinCC flexible).......................................136
4.7 Post-editing integrated projects.................................................................................................137
4.7.1 Migrating an integrated project..................................................................................................137
4.7.2 Post-editing integrated projects.................................................................................................138
4.7.3 Converting unspecified CPUs into specified CPUs...................................................................140
4.7.4 Creating an integrated HMI connection.....................................................................................141
4.7.5 Re-linking HMI tags...................................................................................................................143
4.7.6 Deleting an unspecified connection...........................................................................................144
5 First steps.................................................................................................................................................145
5.1 Getting Started Documentation.................................................................................................145
6 Introduction to the TIA Portal....................................................................................................................147
6.1 User interface and operation.....................................................................................................147
6.1.1 Starting, setting and exiting the TIA Portal...............................................................................147
6.1.1.1 Starting and exiting the TIA Portal.............................................................................................147
6.1.1.2 Overview of the program settings..............................................................................................147
6.1.1.3 Overview of the script and text editor settings...........................................................................149
6.1.1.4 Overview of the print settings....................................................................................................150
6.1.1.5 Changing the settings................................................................................................................151
6.1.2 Layout of the user interface.......................................................................................................151
6.1.2.1 Views.........................................................................................................................................151
6.1.2.2 Portal view.................................................................................................................................151
6.1.2.3 Project view...............................................................................................................................153
6.1.2.4 Project navigation......................................................................................................................155
6.1.2.5 Work area..................................................................................................................................158
6.1.2.6 Inspector window.......................................................................................................................167
6.1.2.7 Task cards.................................................................................................................................169
6.1.2.8 Details view...............................................................................................................................170
6.1.2.9 Overview window.......................................................................................................................172
6.1.2.10 Resetting the user interface layout............................................................................................175
6.1.3 Keyboard shortcuts....................................................................................................................176
6.1.3.1 Keyboard shortcuts for project editing.......................................................................................176
6.1.3.2 Keyboard shortcuts for windows................................................................................................177
6.1.3.3 Keyboard shortcuts in the project tree.......................................................................................177
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 5
6.1.3.4 Keyboard shortcuts in tables.....................................................................................................177
6.1.3.5 Keyboard shortcuts for text editing............................................................................................178
6.1.3.6 Using the on-screen keyboard...................................................................................................178
6.1.4 Special features specific to the operating system.....................................................................179
6.1.4.1 Influence of user rights..............................................................................................................179
6.1.4.2 Expanding user rights................................................................................................................180
6.2 Help on the information system.................................................................................................181
6.2.1 General remarks on the information system..............................................................................181
6.2.2 Opening the Help system..........................................................................................................184
6.2.3 Searching the Help system for keywords..................................................................................184
6.2.4 Full-text searches......................................................................................................................184
6.2.5 Using favorites...........................................................................................................................185
6.2.6 Printing help topics....................................................................................................................186
6.2.7 Disabling the automatic display of tooltip cascades..................................................................186
6.2.8 Safety Guidelines......................................................................................................................187
7 Editing projects.........................................................................................................................................189
7.1 The basics of projects................................................................................................................189
7.2 Creating and managing projects................................................................................................190
7.2.1 Creating a new project...............................................................................................................190
7.2.2 Opening projects.......................................................................................................................190
7.2.3 Displaying properties of the project...........................................................................................191
7.2.4 Saving projects..........................................................................................................................192
7.2.5 Closing projects.........................................................................................................................193
7.2.6 Deleting projects........................................................................................................................193
7.2.7 Working with multi-language projects........................................................................................194
7.2.7.1 Project text basics.....................................................................................................................194
7.2.7.2 Select project languages...........................................................................................................195
7.2.7.3 Setting the editing language......................................................................................................196
7.2.7.4 Translating texts directly............................................................................................................196
7.2.7.5 Translating texts using reference texts......................................................................................197
7.2.7.6 Exporting and importing project texts........................................................................................198
7.2.7.7 Application examples for multilanguage projects......................................................................200
7.3 Editing project data....................................................................................................................202
7.3.1 Compiling and loading project data...........................................................................................202
7.3.1.1 Compiling project data...............................................................................................................202
7.3.1.2 Downloading project data..........................................................................................................203
7.3.2 Comparing project data.............................................................................................................209
7.3.2.1 Basics of project data comparison.............................................................................................209
7.3.3 Protecting project data...............................................................................................................210
7.3.3.1 Protection concept for project data............................................................................................210
7.3.3.2 Revoking access rights for devices...........................................................................................210
7.3.4 Printing project contents............................................................................................................211
7.3.4.1 Documentation settings.............................................................................................................211
7.3.4.2 Printout of project contents........................................................................................................212
7.3.4.3 Changing the print settings........................................................................................................213
7.3.4.4 Specifying the print layout.........................................................................................................214
7.3.4.5 Entering document information..................................................................................................215
7.3.4.6 Managing cover pages and frames...........................................................................................216
7.3.4.7 Designing cover pages and frames...........................................................................................219
7.3.4.8 Displaying print preview.............................................................................................................225
Table of contents
WinCC Advanced V11.0 SP1
6 System Manual, 08/2011,
7.3.4.9 Printing project data...................................................................................................................228
7.4 Undoing and redoing actions.....................................................................................................231
7.4.1 Basics of undoing and redoing actions......................................................................................231
7.4.2 Undoing an action......................................................................................................................232
7.4.3 Redoing an action......................................................................................................................233
7.5 Finding and replacing in projects...............................................................................................235
7.5.1 Information on the search function............................................................................................235
7.5.2 Search and replace...................................................................................................................235
7.6 Working with text lists................................................................................................................238
7.6.1 Text lists....................................................................................................................................238
7.6.2 Creating user-defined text lists..................................................................................................239
7.6.3 Editing user-defined text lists.....................................................................................................240
7.6.4 Editing system-defined text lists................................................................................................240
7.7 Using memory cards..................................................................................................................242
7.7.1 Basics about memory cards......................................................................................................242
7.7.2 Adding a user-defined card reader............................................................................................242
7.7.3 Accessing memory cards..........................................................................................................243
7.7.4 Displaying properties of memory cards.....................................................................................243
7.8 Using libraries............................................................................................................................245
7.8.1 Library basics............................................................................................................................245
7.8.2 "Libraries" task card...................................................................................................................246
7.8.3 Using the elements and parts view............................................................................................248
7.8.4 Working with the project library.................................................................................................249
7.8.4.1 Project library basics.................................................................................................................249
7.8.4.2 Creating folders in the project library.........................................................................................249
7.8.4.3 Adding elements to the project library.......................................................................................250
7.8.4.4 Using elements of the project library.........................................................................................251
7.8.4.5 Editing elements of a project library..........................................................................................254
7.8.4.6 Removing elements from the project library..............................................................................255
7.8.4.7 Filtering the view........................................................................................................................256
7.8.5 Working with global libraries......................................................................................................257
7.8.5.1 Global library basics..................................................................................................................257
7.8.5.2 Creating a new global library.....................................................................................................257
7.8.5.3 Opening a global library.............................................................................................................258
7.8.5.4 Displaying properties of global libraries.....................................................................................259
7.8.5.5 Saving a global library...............................................................................................................260
7.8.5.6 Closing a global library..............................................................................................................261
7.8.5.7 Deleting a global library.............................................................................................................262
7.8.5.8 Creating folders in the global libraries.......................................................................................263
7.8.5.9 Adding elements to a global library...........................................................................................264
7.8.5.10 Using elements of a global library.............................................................................................265
7.8.5.11 Editing elements of a global library............................................................................................268
7.8.5.12 Removing elements from a global library..................................................................................270
7.8.5.13 Using a supplied global library...................................................................................................270
7.8.5.14 Filtering the view........................................................................................................................271
7.9 Using cross-references..............................................................................................................273
7.9.1 Using cross-references..............................................................................................................273
7.10 Simulating devices.....................................................................................................................274
7.10.1 Simulation of devices.................................................................................................................274
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 7
7.10.2 Starting the simulation...............................................................................................................274
8 Editing devices and networks...................................................................................................................275
8.1 Configuring devices and networks.............................................................................................275
8.1.1 Hardware and network editor....................................................................................................275
8.1.1.1 Overview of hardware and network editor.................................................................................275
8.1.1.2 Network view.............................................................................................................................277
8.1.1.3 Device view...............................................................................................................................279
8.1.1.4 Topology view............................................................................................................................282
8.1.1.5 Printing hardware and network configurations..........................................................................283
8.1.1.6 Activating the page break preview for printout..........................................................................285
8.1.1.7 Changing the print options.........................................................................................................285
8.1.1.8 Inspector window ......................................................................................................................286
8.1.1.9 Hardware catalog .....................................................................................................................287
8.1.1.10 Information on hardware components.......................................................................................289
8.1.1.11 Enabling product support...........................................................................................................290
8.1.1.12 Keyboard action in the hardware and network editor................................................................291
8.1.2 Configuring devices...................................................................................................................292
8.1.2.1 Basics........................................................................................................................................292
8.1.2.2 Configuring individual devices...................................................................................................300
8.1.3 Configure networks....................................................................................................................314
8.1.3.1 Networking devices...................................................................................................................314
8.1.3.2 Communication via connections................................................................................................332
8.1.3.3 Displaying and configuring topology..........................................................................................375
8.1.4 Creating configurations..............................................................................................................390
8.1.4.1 Configurations for automation systems.....................................................................................390
8.1.4.2 Configurations for PROFIBUS DP.............................................................................................422
8.1.4.3 Configurations for PROFINET IO..............................................................................................444
8.1.4.4 Bus coupling with PN/PN coupler..............................................................................................472
8.1.4.5 Configurations using external tools...........................................................................................473
8.1.4.6 Loading a configuration.............................................................................................................475
8.1.5 Additional information on configurations....................................................................................477
8.1.5.1 Functional description of S7-1200 CPUs...................................................................................477
8.1.5.2 Distributed I/O............................................................................................................................536
8.1.5.3 Parameters of analog modules..................................................................................................565
8.1.6 System diagnostics with 'Report System Errors'.......................................................................566
8.1.6.1 Introduction to system diagnostics with 'Report System Errors'................................................566
8.1.6.2 Basics of system diagnostics.....................................................................................................566
8.1.6.3 Components supported.............................................................................................................567
8.1.6.4 Diagnostics blocks for reporting system errors..........................................................................567
8.1.6.5 Properties of the blocks.............................................................................................................568
8.1.6.6 Supported error OBs.................................................................................................................569
8.1.6.7 Overview of the status DBs.......................................................................................................570
8.1.6.8 Diagnostics status DB...............................................................................................................570
8.1.6.9 PROFINET IO DB......................................................................................................................574
8.1.6.10 PROFIBUS DP DB....................................................................................................................576
8.1.6.11 Displaying settings of system diagnostics.................................................................................578
8.1.6.12 Basic settings............................................................................................................................578
8.1.6.13 Advanced settings.....................................................................................................................581
8.1.7 Displaying alarms......................................................................................................................584
8.1.7.1 Overview of the alarm display...................................................................................................584
8.1.7.2 Archive view..............................................................................................................................585
Table of contents
WinCC Advanced V11.0 SP1
8 System Manual, 08/2011,
8.1.7.3 Layout of the alarms in the archive view...................................................................................585
8.1.7.4 Receiving alarms.......................................................................................................................585
8.1.7.5 Export archive............................................................................................................................586
8.1.7.6 Clear archive.............................................................................................................................586
8.1.7.7 "Active alarms" view..................................................................................................................586
8.1.7.8 Layout of the alarms in the "Active alarms" view.......................................................................587
8.1.7.9 Status of the alarms...................................................................................................................587
8.1.7.10 Acknowledging alarms...............................................................................................................587
8.1.7.11 Ignoring alarms..........................................................................................................................588
8.1.7.12 Keyboard commands in the alarm display.................................................................................589
8.2 Device and network diagnostics................................................................................................590
8.2.1 Hardware diagnostics................................................................................................................590
8.2.1.1 Overview of hardware diagnostics.............................................................................................590
8.2.1.2 Showing non-editable and current values of configurable module properties...........................598
8.2.1.3 Showing the current values of dynamic modules properties.....................................................602
8.2.1.4 Checking a module for defects..................................................................................................605
8.2.1.5 Changing the properties of a module or the programming device / PC....................................610
8.2.1.6 Diagnostics in STOP mode.......................................................................................................618
8.2.1.7 Online accesses in the Online and Diagnostics view................................................................621
8.2.1.8 Checking PROFIBUS DP subnets for faults..............................................................................623
8.2.2 Connection diagnostics.............................................................................................................626
8.2.2.1 Overview of connection diagnostics..........................................................................................626
8.2.2.2 Displaying the connection status using icons............................................................................627
8.2.2.3 Detailed connection diagnostics................................................................................................628
9 Visualizing processes (Advanced)............................................................................................................633
9.1 Creating screens.......................................................................................................................633
9.1.1 Basics........................................................................................................................................633
9.1.1.1 Screen basics............................................................................................................................633
9.1.1.2 HMI device dependency for screens.........................................................................................635
9.1.1.3 Elements and basic settings......................................................................................................637
9.1.1.4 Working with screens................................................................................................................640
9.1.1.5 Working with templates.............................................................................................................643
9.1.2 Working with objects..................................................................................................................649
9.1.2.1 Overview of objects...................................................................................................................649
9.1.2.2 Overview of objects...................................................................................................................651
9.1.2.3 Options for Editing Objects........................................................................................................655
9.1.2.4 Inserting an object.....................................................................................................................656
9.1.2.5 Deleting an Object.....................................................................................................................658
9.1.2.6 Positioning an object.................................................................................................................659
9.1.2.7 Resizing an object.....................................................................................................................660
9.1.2.8 Aligning objects.........................................................................................................................661
9.1.2.9 Moving an object forward or backward......................................................................................663
9.1.2.10 Show objects outside the screen area.......................................................................................664
9.1.2.11 Rotating objects.........................................................................................................................665
9.1.2.12 Flipping objects..........................................................................................................................667
9.1.2.13 Flashing.....................................................................................................................................668
9.1.2.14 Designing an object...................................................................................................................668
9.1.2.15 Inserting multiple objects of the same type (stamping tool).......................................................669
9.1.2.16 Selecting multiple objects .........................................................................................................671
9.1.2.17 Repositioning and resizing multiple objects...............................................................................673
9.1.2.18 Managing My Controls...............................................................................................................673
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 9
9.1.2.19 External graphics ......................................................................................................................676
9.1.2.20 Managing external graphics......................................................................................................677
9.1.2.21 Storing an external image in the graphics library......................................................................679
9.1.2.22 Working with object groups.......................................................................................................681
9.1.2.23 Configuring the keyboard access..............................................................................................687
9.1.2.24 Examples...................................................................................................................................690
9.1.3 Working with text lists and graphics lists...................................................................................693
9.1.3.1 Working with text lists................................................................................................................693
9.1.3.2 Working with graphics lists........................................................................................................701
9.1.4 Dynamizing screens..................................................................................................................709
9.1.4.1 Basics on dynamizing screens..................................................................................................709
9.1.4.2 Basics on dynamizing screens..................................................................................................709
9.1.4.3 Dynamization in the inspector window......................................................................................710
9.1.4.4 Dynamization in the inspector window......................................................................................712
9.1.4.5 Dynamization with animations...................................................................................................715
9.1.4.6 Dynamization in the property list...............................................................................................728
9.1.4.7 Dynamize with system functions...............................................................................................732
9.1.5 Working with layers...................................................................................................................734
9.1.5.1 Basics on working with layers....................................................................................................734
9.1.5.2 Moving objects between layers.................................................................................................735
9.1.5.3 Setting the active layer..............................................................................................................736
9.1.5.4 Show and hide layers................................................................................................................737
9.1.5.5 Renaming layers........................................................................................................................738
9.1.6 Working with libraries................................................................................................................740
9.1.6.1 Basics on libraries.....................................................................................................................740
9.1.6.2 Copy templates and types.........................................................................................................741
9.1.6.3 Libraries in WinCC.....................................................................................................................742
9.1.6.4 Displaying library objects...........................................................................................................744
9.1.6.5 Managing library objects............................................................................................................747
9.1.6.6 Storing an object in a library......................................................................................................748
9.1.6.7 Inserting a library object............................................................................................................749
9.1.6.8 Creating a global library.............................................................................................................749
9.1.6.9 Saving a global library...............................................................................................................750
9.1.6.10 Opening a global library.............................................................................................................751
9.1.7 Working with faceplates.............................................................................................................752
9.1.7.1 Basics on faceplates..................................................................................................................752
9.1.7.2 Faceplate editor.........................................................................................................................755
9.1.7.3 Creating and managing faceplates............................................................................................758
9.1.7.4 Dynamizing faceplates..............................................................................................................773
9.1.7.5 Examples of faceplates.............................................................................................................775
9.1.8 Indicator and control objects......................................................................................................782
9.1.8.1 Device-Specific Nature of the Objects.......................................................................................782
9.1.8.2 Objects......................................................................................................................................791
9.1.9 Configuring screen navigation...................................................................................................864
9.1.9.1 Basics on screen navigation......................................................................................................864
9.1.9.2 Assigning button with screen change........................................................................................865
9.1.9.3 Assigning screen change to function key..................................................................................866
9.2 Working with Tags.....................................................................................................................867
9.2.1 Basics........................................................................................................................................867
9.2.1.1 Basics of tags............................................................................................................................867
9.2.1.2 Overview of HMI tag tables.......................................................................................................868
9.2.1.3 External tags..............................................................................................................................870
Table of contents
WinCC Advanced V11.0 SP1
10 System Manual, 08/2011,
9.2.1.4 Addressing external tags...........................................................................................................871
9.2.1.5 Internal Tags..............................................................................................................................873
9.2.2 Working with Tags.....................................................................................................................874
9.2.2.1 Creating tags.............................................................................................................................874
9.2.2.2 Editing tags................................................................................................................................878
9.2.2.3 Configuring Tags.......................................................................................................................883
9.2.3 Working with arrays...................................................................................................................901
9.2.3.1 Basics on arrays........................................................................................................................901
9.2.3.2 Creating array tags....................................................................................................................903
9.2.3.3 Examples of arrays....................................................................................................................904
9.2.4 Working with user data types....................................................................................................904
9.2.4.1 Basics on user data types.........................................................................................................904
9.2.4.2 Creating the user data type.......................................................................................................906
9.2.4.3 Creating user data type elements..............................................................................................908
9.2.4.4 Creating tags with a user data type data type...........................................................................911
9.2.4.5 Managing user data types.........................................................................................................913
9.2.5 Working with cycles...................................................................................................................915
9.2.5.1 Cycle basics..............................................................................................................................915
9.2.5.2 Defining cycles..........................................................................................................................916
9.2.6 Logging tags..............................................................................................................................917
9.2.6.1 Basic principles for data logging................................................................................................917
9.2.6.2 Data logging in Runtime Advanced and Panels........................................................................918
9.2.7 Displaying Tags.........................................................................................................................938
9.2.7.1 Displaying tags with Basic Panels.............................................................................................938
9.2.7.2 Displaying tags with Runtime Advanced and Panels................................................................940
9.3 Working with alarms..................................................................................................................948
9.3.1 Basics........................................................................................................................................948
9.3.1.1 Alarm Logging in WinCC...........................................................................................................948
9.3.1.2 Alarm Logging in WinCC...........................................................................................................949
9.3.1.3 Alarm Procedures......................................................................................................................950
9.3.1.4 Alarm states...............................................................................................................................955
9.3.1.5 Alarm classes............................................................................................................................956
9.3.1.6 Acknowledgement.....................................................................................................................959
9.3.1.7 Alarm groups.............................................................................................................................961
9.3.1.8 Alarm number............................................................................................................................962
9.3.2 Working with Alarms .................................................................................................................963
9.3.2.1 Alarm components and properties.............................................................................................963
9.3.2.2 Configuring Alarms....................................................................................................................964
9.3.2.3 Configuring the Outputting of Alarms........................................................................................986
9.3.2.4 Acknowledging alarms.............................................................................................................1002
9.3.2.5 Configuring alarm buffer overflow............................................................................................1005
9.3.3 Logging Alarms........................................................................................................................1006
9.3.3.1 Alarm Logging Basics..............................................................................................................1006
9.3.3.2 Storage locations for log files..................................................................................................1008
9.3.3.3 Creating an alarm log..............................................................................................................1010
9.3.3.4 Logging Alarms........................................................................................................................1014
9.3.3.5 Configuring an alarm view for logged alarms..........................................................................1015
9.3.3.6 Direct access to the ODBC log database................................................................................1016
9.3.3.7 Setting up the ODBC data source...........................................................................................1017
9.3.3.8 Configuring a checksum for a log............................................................................................1017
9.3.3.9 Evaluating the checksum of log data.......................................................................................1019
9.3.3.10 Log response to language switching in runtime......................................................................1020
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 11
9.3.3.11 Managing logging behavior when Runtime starts....................................................................1021
9.3.3.12 Controlling the Logging in relation to the Fill Level..................................................................1022
9.3.4 Using Alarms in Runtime.........................................................................................................1023
9.3.4.1 Alarms in Runtime...................................................................................................................1023
9.3.4.2 Alarms in Runtime...................................................................................................................1025
9.3.4.3 Using the Alarm Window or Alarm View..................................................................................1027
9.3.4.4 Using the Simple Alarm Window, Alarm View.........................................................................1030
9.3.4.5 Using the Alarm Indicator........................................................................................................1033
9.3.4.6 Acknowledging alarms.............................................................................................................1034
9.3.4.7 Filtering Alarms .......................................................................................................................1035
9.3.5 Reference................................................................................................................................1036
9.3.5.1 System functions for alarms....................................................................................................1036
9.3.5.2 Alarm events............................................................................................................................1037
9.3.5.3 System functions for logs........................................................................................................1038
9.3.5.4 Structure of *.csv files that contain alarms..............................................................................1038
9.3.5.5 System events.........................................................................................................................1040
9.4 Working with logs....................................................................................................................1074
9.4.1 Working with logs for Runtime Advanced and Panels.............................................................1074
9.4.1.1 Log Basics...............................................................................................................................1074
9.4.1.2 Properties of Logs...................................................................................................................1074
9.5 Working with recipes...............................................................................................................1076
9.5.1 Basics......................................................................................................................................1076
9.5.1.1 Definition and applications.......................................................................................................1076
9.5.1.2 Examples for using recipes.....................................................................................................1078
9.5.1.3 Recipe structure......................................................................................................................1078
9.5.1.4 Display of recipes....................................................................................................................1080
9.5.1.5 Transferring recipe data records.............................................................................................1082
9.5.1.6 Configuration of recipes...........................................................................................................1085
9.5.1.7 Special features of some devices............................................................................................1086
9.5.1.8 Synchronization of recipe data records with the PLC..............................................................1088
9.5.1.9 "Recipes" editor.......................................................................................................................1089
9.5.2 Displaying and Editing Recipes in Runtime.............................................................................1092
9.5.2.1 Recipe screen and recipe view................................................................................................1092
9.5.2.2 Simple recipe view...................................................................................................................1092
9.5.2.3 Configuration options of the simple recipe view......................................................................1094
9.5.2.4 Advanced recipe view..............................................................................................................1097
9.5.2.5 Configuration options of the advanced recipe view.................................................................1098
9.5.2.6 Response of the recipe view in Runtime.................................................................................1100
9.5.2.7 Basics on the recipe screen....................................................................................................1101
9.5.3 Configuring Recipes................................................................................................................1103
9.5.3.1 General configuration procedure.............................................................................................1103
9.5.3.2 Creating and Editing Recipes..................................................................................................1104
9.5.3.3 Configuring the display of recipes...........................................................................................1112
9.5.3.4 Importing recipes into the configuration and exporting them...................................................1117
9.5.4 Using Recipes in Runtime.......................................................................................................1120
9.5.4.1 Simple recipe view...................................................................................................................1120
9.5.4.2 Advanced recipe view..............................................................................................................1126
9.5.4.3 Exporting and importing recipe data records...........................................................................1133
9.5.4.4 Reactions to modifications of the recipe structure...................................................................1134
9.5.5 Examples.................................................................................................................................1135
9.5.5.1 Example of creating a recipe...................................................................................................1135
Table of contents
WinCC Advanced V11.0 SP1
12 System Manual, 08/2011,
9.5.5.2 Example of configuring a recipe screen..................................................................................1137
9.5.5.3 Scenario for Entering Recipe Data Records in Runtime.........................................................1139
9.5.5.4 Scenario for a manual production sequence...........................................................................1140
9.5.5.5 Scenario for an Automatic Production Sequence....................................................................1142
9.6 Working with reports................................................................................................................1144
9.6.1 Basics......................................................................................................................................1144
9.6.1.1 Reports....................................................................................................................................1144
9.6.1.2 Structure of reports..................................................................................................................1145
9.6.2 Working with reports................................................................................................................1146
9.6.2.1 Creating reports.......................................................................................................................1146
9.6.2.2 Printing reports........................................................................................................................1151
9.6.2.3 Working with objects................................................................................................................1152
9.6.3 Operation in Runtime...............................................................................................................1165
9.6.3.1 Printing reports........................................................................................................................1165
9.6.4 Objects in reports....................................................................................................................1166
9.6.4.1 Audit report..............................................................................................................................1166
9.6.4.2 Date/time field..........................................................................................................................1167
9.6.4.3 I/O field....................................................................................................................................1168
9.6.4.4 Graphic view............................................................................................................................1169
9.6.4.5 Graphic I/O field.......................................................................................................................1170
9.6.4.6 Alarm report.............................................................................................................................1171
9.6.4.7 Recipe report...........................................................................................................................1173
9.6.4.8 Page number...........................................................................................................................1174
9.6.4.9 Symbolic I/O field.....................................................................................................................1175
9.6.4.10 Text field..................................................................................................................................1175
9.7 Configuring user administration...............................................................................................1177
9.7.1 Field of application of the user administration.........................................................................1177
9.7.2 Form of the user administration...............................................................................................1177
9.7.3 Basics......................................................................................................................................1178
9.7.3.1 Users.......................................................................................................................................1178
9.7.3.2 Users work area......................................................................................................................1179
9.7.3.3 User groups.............................................................................................................................1180
9.7.3.4 User groups work area............................................................................................................1180
9.7.3.5 Settings for the user administration.........................................................................................1181
9.7.3.6 Settings for the user administration.........................................................................................1183
9.7.4 Building up and structuring a user administration....................................................................1185
9.7.4.1 Basics of user administration...................................................................................................1185
9.7.4.2 Administering users for Runtime ............................................................................................1186
9.7.4.3 Managing users on the server.................................................................................................1192
9.7.4.4 Administering users in Runtime...............................................................................................1196
9.7.4.5 Configuring access protection.................................................................................................1208
9.7.5 Reference................................................................................................................................1209
9.7.5.1 Objects with access protection................................................................................................1209
9.7.5.2 Objects with access protection................................................................................................1210
9.7.5.3 Default user groups and authorizations...................................................................................1210
9.7.6 Examples.................................................................................................................................1211
9.7.6.1 Example: Configuring a button with logon dialog box.............................................................1211
9.7.6.2 Example: Logging the logon and logoff events.......................................................................1212
9.7.6.3 Example of a user administration............................................................................................1213
9.8 Working with system functions and Runtime scripting............................................................1221
9.8.1 Working with system functions and Runtime scripting............................................................1221
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 13
9.8.1.1 Basics......................................................................................................................................1221
9.8.1.2 Working with function lists.......................................................................................................1226
9.8.1.3 Working with user-defined VB functions..................................................................................1230
9.8.1.4 Debugging user-defined VB functions.....................................................................................1244
9.8.1.5 Runtime behavior in Runtime..................................................................................................1252
9.8.1.6 Examples.................................................................................................................................1256
9.8.2 Reference................................................................................................................................1262
9.8.2.1 Function list.............................................................................................................................1262
9.8.2.2 Events......................................................................................................................................1446
9.8.2.3 VB scripts................................................................................................................................1462
9.9 Mobile Wireless.......................................................................................................................1816
9.9.1 Field of application of the Mobile Panel Wireless....................................................................1816
9.9.2 How does the transponder system work?...............................................................................1817
9.9.3 How does the RFID system work?..........................................................................................1819
9.9.4 Basics......................................................................................................................................1821
9.9.4.1 Zones.......................................................................................................................................1821
9.9.4.2 Zones working area.................................................................................................................1822
9.9.4.3 Effective ranges.......................................................................................................................1823
9.9.4.4 Effective ranges working area.................................................................................................1824
9.9.4.5 Effective ranges (RFID)...........................................................................................................1825
9.9.4.6 Work area for effective ranges (RFID).....................................................................................1826
9.9.5 Working with zones.................................................................................................................1827
9.9.5.1 Configuring a zone..................................................................................................................1827
9.9.5.2 Displaying the screen on entering a zone...............................................................................1828
9.9.5.3 Displaying an object in relation to the zone.............................................................................1829
9.9.6 Working with effective ranges..................................................................................................1830
9.9.6.1 Overview..................................................................................................................................1830
9.9.6.2 Configure effective range........................................................................................................1831
9.9.6.3 Configuring the effective range name......................................................................................1832
9.9.6.4 Configuring additional Mobile Wireless objects.......................................................................1833
9.9.7 Working with effective ranges (RFID)......................................................................................1834
9.9.7.1 Overview..................................................................................................................................1834
9.9.7.2 Configuring effective range (RFID)..........................................................................................1835
9.9.7.3 Configuring the effective range name (RFID)..........................................................................1836
9.9.8 Reference................................................................................................................................1836
9.9.8.1 PROFIsafe address.................................................................................................................1836
9.9.8.2 Power Management................................................................................................................1837
9.9.8.3 Zone ID / connection point ID..................................................................................................1838
9.10 Planning tasks.........................................................................................................................1839
9.10.1 Field of application of the Scheduler.......................................................................................1839
9.10.2 Working with tasks and triggers...............................................................................................1840
9.10.3 Basics......................................................................................................................................1840
9.10.3.1 Work area of the "Scheduler" editor........................................................................................1840
9.10.3.2 Function list.............................................................................................................................1842
9.10.3.3 Function list.............................................................................................................................1842
9.10.3.4 Triggers...................................................................................................................................1843
9.10.4 Planning jobs...........................................................................................................................1845
9.10.4.1 Planning tasks with acyclic triggers.........................................................................................1845
9.10.4.2 Planning tasks with cyclic triggers ..........................................................................................1846
9.10.4.3 Planning tasks with event triggers ..........................................................................................1847
9.10.4.4 Administer task........................................................................................................................1848
Table of contents
WinCC Advanced V11.0 SP1
14 System Manual, 08/2011,
9.10.5 Examples.................................................................................................................................1849
9.10.5.1 Example: Terminating Runtime every day...............................................................................1849
9.10.5.2 Example: Update user following change of user.....................................................................1850
9.10.5.3 Example: Changing the starting point of a job in Runtime......................................................1851
9.11 Communicating with PLCs......................................................................................................1856
9.11.1 Basics of communication.........................................................................................................1856
9.11.1.1 Communication between devices............................................................................................1856
9.11.1.2 Devices and networks in the automation system....................................................................1857
9.11.1.3 Data exchange using tags.......................................................................................................1862
9.11.1.4 Data exchange using area pointers.........................................................................................1863
9.11.1.5 Communication drivers............................................................................................................1863
9.11.2 Networks and connections......................................................................................................1864
9.11.2.1 SIMATIC communication networks.........................................................................................1864
9.11.2.2 Configuring networks and connections....................................................................................1868
9.11.3 Data exchange........................................................................................................................1876
9.11.3.1 Data exchange using tags.......................................................................................................1876
9.11.3.2 Data exchange using area pointers.........................................................................................1882
9.11.4 Device dependency.................................................................................................................1888
9.11.4.1 Basic Panel..............................................................................................................................1888
9.11.4.2 Panel.......................................................................................................................................1892
9.11.4.3 Comfort Panel..........................................................................................................................1895
9.11.4.4 Multi Panel...............................................................................................................................1898
9.11.4.5 Mobile Panel............................................................................................................................1901
9.11.4.6 PC systems.............................................................................................................................1904
9.11.4.7 Parallel communication ..........................................................................................................1906
9.11.5 Communicating with SIMATIC S7 1200..................................................................................1907
9.11.5.1 Communication with SIMATIC S7 1200..................................................................................1907
9.11.5.2 Communication via PROFINET...............................................................................................1908
9.11.5.3 Communication via PROFIBUS...............................................................................................1927
9.11.5.4 Data exchange........................................................................................................................1941
9.11.5.5 Performance features of communication.................................................................................1963
9.11.5.6 Creating connections in the "Connections" editor...................................................................1964
9.11.5.7 Time synchronization...............................................................................................................1972
9.11.6 Communicating with SIMATIC S7 300/400.............................................................................1976
9.11.6.1 Communication with SIMATIC S7 300/400.............................................................................1976
9.11.6.2 Communication via PROFINET...............................................................................................1977
9.11.6.3 Communication via PROFIBUS...............................................................................................1997
9.11.6.4 Communication via MPI...........................................................................................................2011
9.11.6.5 Data exchange........................................................................................................................2023
9.11.6.6 Performance features of communication.................................................................................2043
9.11.6.7 Creating connections in the "Connections" editor...................................................................2043
9.11.7 Communicating with SIMATIC S7 200....................................................................................2056
9.11.7.1 Communication with SIMATIC S7 200....................................................................................2056
9.11.7.2 Creating a connection to SIMATIC S7 200..............................................................................2056
9.11.7.3 Parameters for the connection................................................................................................2058
9.11.7.4 Data exchange........................................................................................................................2066
9.11.7.5 Performance features of communication.................................................................................2085
9.11.8 Configuring direct keys............................................................................................................2086
9.11.8.1 Direct keys...............................................................................................................................2086
9.11.8.2 Changing the operating mode of the HMI device....................................................................2086
9.11.8.3 Configuring direct keys............................................................................................................2088
9.11.8.4 PROFINET IO direct keys.......................................................................................................2092
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 15
9.11.8.5 PROFIBUS DP direct keys......................................................................................................2108
9.11.9 Communication via SIMATIC HMI HTTP................................................................................2124
9.11.9.1 Basic information on SIMATIC HMI HTTP..............................................................................2124
9.11.9.2 Configuring a connection via SIMATIC HMI HTTP..................................................................2126
9.11.9.3 Performance features of communication.................................................................................2139
9.11.10 Communication via OPC.........................................................................................................2140
9.11.10.1 Communication via OPC....................................................................................................2140
9.11.10.2 Configuring a connection via OPC.....................................................................................2140
9.11.10.3 Performance features of communication............................................................................2142
9.11.11 Communication via routing......................................................................................................2144
9.11.11.1 Communication via routing.................................................................................................2144
9.11.11.2 Example for communication via routing.............................................................................2145
9.11.11.3 Configuring communication via routing..............................................................................2147
9.11.12 Communication with other PLCs.............................................................................................2148
9.11.12.1 Communication with other PLCs........................................................................................2148
9.11.12.2 Distinctive features when configuring.................................................................................2149
9.11.12.3 Parallel communication .....................................................................................................2150
9.11.12.4 Communication drivers.......................................................................................................2151
9.11.12.5 Data exchange using area pointers....................................................................................2267
9.11.13 Special features of WinAC MP................................................................................................2282
9.11.13.1 WinAC MP basics...............................................................................................................2282
9.11.13.2 Communication options with WinAC MP............................................................................2283
9.11.13.3 Standard procedure for communication with WinAC MP...................................................2288
9.11.13.4 Configuring the WinAC MP communications driver...........................................................2289
9.11.13.5 Transferring WinAC MP to the HMI device........................................................................2298
9.11.13.6 Transferring authorization to the HMI device.....................................................................2303
9.11.13.7 WinAC MP system library...................................................................................................2304
9.12 Using global functions.............................................................................................................2305
9.12.1 HMI device wizard basics........................................................................................................2305
9.12.2 HMI device wizard basics........................................................................................................2306
9.12.3 Importing and exporting project data.......................................................................................2307
9.12.3.1 Importing and exporting project data.......................................................................................2307
9.12.3.2 Importing and exporting recipes..............................................................................................2308
9.12.3.3 Importing and exporting alarms...............................................................................................2312
9.12.3.4 Importing and exporting tags...................................................................................................2319
9.12.3.5 Importing and exporting text lists.............................................................................................2324
9.12.4 Using cross-references............................................................................................................2328
9.12.4.1 General information about cross references...........................................................................2328
9.12.4.2 Displaying the cross-reference list...........................................................................................2329
9.12.4.3 Structure of the cross-reference list.........................................................................................2330
9.12.4.4 Displaying cross-references in the Inspector window..............................................................2331
9.12.5 Managing languages...............................................................................................................2332
9.12.5.1 Languages in WinCC...............................................................................................................2332
9.12.5.2 Language settings in the operating system.............................................................................2334
9.12.5.3 Operating system settings for Asian languages......................................................................2334
9.12.5.4 Setting project languages........................................................................................................2335
9.12.5.5 Creating one project in multiple languages.............................................................................2338
9.12.5.6 Using language-specific graphics............................................................................................2346
9.12.5.7 Languages in runtime..............................................................................................................2350
9.12.5.8 Example of multilingual configuration......................................................................................2357
9.12.6 Replacing devices...................................................................................................................2360
9.12.6.1 Basics......................................................................................................................................2360
Table of contents
WinCC Advanced V11.0 SP1
16 System Manual, 08/2011,
9.12.6.2 Device-specific functions.........................................................................................................2361
9.12.6.3 Adjust screens to the new device............................................................................................2366
9.12.6.4 Example: Replacing devices...................................................................................................2370
9.12.7 Copying between devices and editors.....................................................................................2373
9.12.7.1 Basics......................................................................................................................................2373
9.12.7.2 Copy and paste.......................................................................................................................2376
9.12.8 Configuring system diagnostics...............................................................................................2380
9.12.8.1 System diagnostics basics......................................................................................................2380
9.12.8.2 System diagnostics views........................................................................................................2381
9.12.8.3 Configuring system diagnostics objects..................................................................................2383
9.13 Compiling and loading.............................................................................................................2391
9.13.1 Compiling and loading projects...............................................................................................2391
9.13.1.1 Overview of compiling and loading projects............................................................................2391
9.13.1.2 Compiling a project..................................................................................................................2393
9.13.1.3 Loading projects......................................................................................................................2394
9.13.1.4 Runtime start...........................................................................................................................2402
9.13.2 Simulating projects..................................................................................................................2404
9.13.2.1 Simulation basics.....................................................................................................................2404
9.13.2.2 WinCC Runtime Advanced simulation.....................................................................................2405
9.13.2.3 Simulating a project.................................................................................................................2406
9.13.2.4 Simulating a screen.................................................................................................................2408
9.13.2.5 Working with the tag simulator................................................................................................2408
9.13.2.6 Start debugger.........................................................................................................................2410
9.13.3 Servicing the HMI device.........................................................................................................2411
9.13.3.1 ProSave...................................................................................................................................2411
9.13.3.2 Backup of HMI data.................................................................................................................2411
9.13.3.3 Backing up and restoring data of the HMI device....................................................................2413
9.13.3.4 Updating the operating system................................................................................................2414
9.13.3.5 Updating the operating system on the HMI device..................................................................2415
9.13.3.6 Transferring license keys.........................................................................................................2417
9.13.3.7 Managing licenses...................................................................................................................2417
9.13.3.8 Installing and uninstalling an option.........................................................................................2419
9.13.4 Reference................................................................................................................................2420
9.13.4.1 Error messages during the download of projects....................................................................2420
9.13.4.2 Adapting the project for another HMI device...........................................................................2421
9.13.4.3 Establishing a connection to the HMI device...........................................................................2423
9.14 Operating in Runtime...............................................................................................................2424
9.14.1 Basics......................................................................................................................................2424
9.14.1.1 Overview..................................................................................................................................2424
9.14.1.2 System behavior......................................................................................................................2425
9.14.2 Commissioning projects..........................................................................................................2429
9.14.2.1 Runtime Advanced and Panels...............................................................................................2429
9.14.2.2 Settings for Runtime Advanced and Panels............................................................................2429
9.14.2.3 Loading a project.....................................................................................................................2432
9.14.2.4 Testing a project......................................................................................................................2433
9.14.2.5 Backup and restoring projects.................................................................................................2434
9.14.2.6 Starting the project..................................................................................................................2436
9.14.3 Operating projects...................................................................................................................2436
9.14.3.1 Setting the project language....................................................................................................2436
9.14.3.2 Operating recipes....................................................................................................................2437
9.14.3.3 Operating alarms.....................................................................................................................2466
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 17
9.14.3.4 Basics......................................................................................................................................2476
9.14.3.5 Project security........................................................................................................................2493
9.15 Performance features..............................................................................................................2512
9.15.1 Engineering system.................................................................................................................2512
9.15.2 Basic Panel..............................................................................................................................2514
9.15.3 Panel.......................................................................................................................................2517
9.15.4 Mobile Panel............................................................................................................................2521
9.15.5 Multi Panel...............................................................................................................................2525
9.15.6 Comfort Panel..........................................................................................................................2529
9.15.7 WinCC Runtime Advanced......................................................................................................2532
9.15.8 General technical specifications..............................................................................................2536
9.15.8.1 Recommended printers...........................................................................................................2536
9.15.8.2 Memory requirement of recipes...............................................................................................2536
9.15.8.3 Memory requirements of recipes for Basic Panels, OP 77A, and TP 177A............................2537
9.16 Options....................................................................................................................................2539
9.16.1 Following GMP with Audit........................................................................................................2539
9.16.1.1 Basics......................................................................................................................................2539
9.16.1.2 Enabling GMP compliant configuration...................................................................................2543
9.16.1.3 Using the Audit trail.................................................................................................................2545
9.16.1.4 Configuring audit functions......................................................................................................2566
9.16.1.5 Performance features of GMP relevant configuration.............................................................2580
9.16.2 Sm@rt Options........................................................................................................................2582
9.16.2.1 Basics......................................................................................................................................2582
9.16.2.2 Remote control via Sm@rtServer............................................................................................2611
9.16.2.3 E-mail notification from runtime...............................................................................................2622
9.16.2.4 Display integrated Service-Pages...........................................................................................2626
9.16.2.5 Access via SIMATIC HMI HTTP Protocol................................................................................2638
9.16.2.6 Connection to the Office-world................................................................................................2646
9.17 Interfaces.................................................................................................................................2651
9.17.1 OPC.........................................................................................................................................2651
9.17.1.1 Basics......................................................................................................................................2651
9.17.1.2 Configuring an OPC server.....................................................................................................2654
9.17.1.3 Configuring an OPC client.......................................................................................................2656
9.17.1.4 Reference................................................................................................................................2661
9.18 Migration to WinCC V11..........................................................................................................2664
9.18.1 Overview of migration to WinCC V11......................................................................................2664
9.18.2 WinCC flexible.........................................................................................................................2664
9.18.2.1 Libraries...................................................................................................................................2664
9.18.2.2 Screens and templates............................................................................................................2666
9.18.2.3 Scripts in faceplates................................................................................................................2668
9.18.2.4 Synchronization of recipes......................................................................................................2669
10 Using online and diagnostics functions..................................................................................................2671
10.1 General information about online mode..................................................................................2671
10.2 View in online mode................................................................................................................2673
10.3 Online access..........................................................................................................................2675
10.4 Displaying accessible devices.................................................................................................2677
10.5 Opening the properties of an interface....................................................................................2679
Table of contents
WinCC Advanced V11.0 SP1
18 System Manual, 08/2011,
10.6 Establishing and canceling an online connection....................................................................2680
10.7 Connecting online with several devices...................................................................................2682
10.8 Basics of assigning parameters for the PG/PC interface........................................................2683
10.9 Adding interfaces.....................................................................................................................2684
10.10 Setting parameters for the Ethernet interface..........................................................................2685
10.10.1 Setting parameters for the Industrial Ethernet interface..........................................................2685
10.10.2 Displaying operating system parameters................................................................................2686
10.10.3 Connecting the PG/PC interface to a subnet...........................................................................2687
10.10.4 Setting parameters for the Ethernet interface..........................................................................2687
10.10.5 Assigning a temporary IP address...........................................................................................2688
10.10.6 Managing temporary IP addresses..........................................................................................2688
10.10.7 Resetting the TCP/IP configuration.........................................................................................2689
10.11 Setting parameters for the MPI and PROFIBUS interfaces.....................................................2690
10.11.1 Setting parameters for the MPI and PROFIBUS interfaces.....................................................2690
10.11.2 Setting MPI or PROFIBUS interface parameters automatically..............................................2691
10.11.3 Setting parameters for the MPI interface.................................................................................2691
10.11.4 Setting parameters for the PROFIBUS interface.....................................................................2693
10.11.5 Overview of the bus parameters for PROFIBUS.....................................................................2696
10.11.6 Resetting the MPI or PROFIBUS configuration.......................................................................2697
10.12 Establishing a remote connection with TeleService................................................................2698
10.12.1 Basics of working with TeleService.........................................................................................2698
10.12.1.1 Introduction to TeleService.................................................................................................2698
10.12.1.2 TeleService functionality....................................................................................................2699
10.12.1.3 Telephone book at TeleService..........................................................................................2699
10.12.2 Telephone networks and modems..........................................................................................2700
10.12.2.1 Supported telephone networks and modems.....................................................................2700
10.12.2.2 Installing the local modem..................................................................................................2701
10.12.2.3 Connecting and configuring the remote modem................................................................2702
10.12.2.4 Initialization string requirements.........................................................................................2703
10.12.3 Using a TS adapter to establish a remote connection.............................................................2703
10.12.3.1 Basics of using a TS adapter.............................................................................................2703
10.12.3.2 Installing TS adapter software............................................................................................2705
10.12.3.3 TS adapter MPI..................................................................................................................2705
10.12.3.4 TS adapter IE.....................................................................................................................2712
10.12.4 Access protection for TeleService and the TS Adapter...........................................................2717
10.12.4.1 Access protection information............................................................................................2717
10.12.4.2 TeleService callback options..............................................................................................2718
10.12.4.3 Levels of protection............................................................................................................2718
10.12.4.4 Setting up access protection and callback number for the TS adapter..............................2719
10.12.4.5 Complete a callback in TeleService...................................................................................2720
10.12.5 Establishing a remote connection to a remote plant................................................................2722
10.12.5.1 Establishing a remote connection......................................................................................2722
10.12.5.2 Terminating a remote connection.......................................................................................2723
10.12.5.3 Checklist for troubleshooting the modem...........................................................................2723
10.12.6 Working with the phone book..................................................................................................2724
10.12.6.1 Basics on working with the phone book.............................................................................2724
10.12.6.2 Structure of the phone book...............................................................................................2725
10.12.6.3 Symbols in the phone book................................................................................................2726
10.12.6.4 Manage phone book...........................................................................................................2726
Table of contents
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 19
10.12.7 CPU controlled TeleService remote connections ...................................................................2728
10.12.7.1 Overview of CPU controlled remote connections...............................................................2728
10.12.7.2 Establishing a connection from and to remote systens (PG-AS-remote coupling).............2729
10.12.7.3 Data exchange between remote systems (AS-AS-remote coupling).................................2731
10.12.7.4 Send SMS from a system...................................................................................................2733
10.12.7.5 Send an email from a system.............................................................................................2734
10.12.8 Troubleshooting.......................................................................................................................2736
10.12.8.1 General information on troubleshooting.............................................................................2736
10.12.8.2 Recording a log file for the modem....................................................................................2736
10.12.8.3 Remote connection to the TS adapter is not established...................................................2737
10.12.8.4 Remote connection from the TS adapter is not established...............................................2738
10.12.8.5 Modem connection is interrupted.......................................................................................2739
10.12.8.6 Modem alarms....................................................................................................................2740
11 Glossary.................................................................................................................................................2741
Index.......................................................................................................................................................2743
Table of contents
WinCC Advanced V11.0 SP1
20 System Manual, 08/2011,
System overview of STEP 7 and WinCC
1
1.1 Scaling of STEP 7 and WinCC
Scope of performance of the products
The following graphic shows the scope of performance of the individual products of STEP 7
and WinCC:
Programming languages
LAD, FBD, SCL, STL*, S7-GRAPH*
STEP 7 Safety option
Machine-level operator control
and monitoring
SCADA applications
WinAC (incl. fail-safe)
S7-400 (incl. fail-safe)
S7-300 (incl. fail-safe)
S7-1200
PC single-station
Comfort Panels and x77
(no Micro), Mobile
Basic Panels
Communication
PROFlBUS, PROFlNET, AS-i, lO-Link, ET 200, Network Topology
P
r
o
f
e
s
s
i
o
n
a
l
B
a
s
i
c
B
a
s
i
c
C
o
m
f
o
r
t
A
d
v
a
n
c
e
d
P
r
o
f
e
s
s
i
o
n
a
l
* Only with Professional for S7-300/400/WinAC
Common functions
System diagnostics, Excel import/export, Undo actions, and many more
SCADA
SlMATlC STEP 7 SlMATlC WinCC
STEP 7
STEP 7 (TIA Portal) is the engineering software for configuring the SIMATIC S7-1200,
S7-300/400, and WinAC controller families. STEP 7 (TIA Portal) is available in 2 editions,
depending on the configurable controller families:
STEP 7 Basic for configuring the S7-1200
STEP 7 Professional for configuring S7-1200, S7-300/400, and WinAC
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 21
WinCC
WinCC (TIA Portal) is an engineering software for configuring SIMATIC Panels, SIMATIC
Industrial PCs, and Standard PCs with the WinCC Runtime Advanced or the SCADA System
WinCC Runtime Professional visualization software.
WinCC (TIA Portal) is available in 4 editions, depending on the configurable operator control
systems:
WinCC Basic for configuring Basic Panels
WinCC Basic is included with every STEP 7 Basic and STEP 7 Professional product.
WinCC Comfort for configuring all panels (including Comfort Panels, Mobile Panels)
WinCC Advanced for configuring all panels and PCs with the WinCC Runtime Advanced
visualization software
WinCC Runtime Advanced is a visualization software for PC-based single-station systems.
WinCC Runtime Advanced can be purchased with licenses for 128, 512, 2k, 4k as well as
8k PowerTags (tags with a process interface).
WinCC Professional for configuring panels and PCs with WinCC Runtime Advanced or
SCADA System WinCC Runtime Professional
WinCC Runtime Professional is a SCADA system for structuring a configuration ranging
from single-station systems to multi-station systems including standard clients or web
clients. WinCC Runtime Professional can be purchased with licenses for 128, 512, 2k, 4k,
8k, 64k, 102400, 153600 as well as 262144 PowerTags (tags with a process interface).
With WinCC (TIA Portal), it is also possible to configure a SINUMERIK PC with WinCC Runtime
Advanced or WinCC Runtime Professional and HMI devices with SINUMERIK HMI Pro sl RT
or SINUMERIK Operate WinCC RT Basic.
System overview of STEP 7 and WinCC
1.1 Scaling of STEP 7 and WinCC
WinCC Advanced V11.0 SP1
22 System Manual, 08/2011,
1.2 Options for STEP 7 Engineering System
Additional STEP 7 products
For applications with increased safety requirements, STEP 7 Professional can be extended
with the STEP 7 Safety option.
The STEP 7 Safety option allows you to configure fail-safe PLC programs for F-CPUs.
System overview of STEP 7 and WinCC
1.2 Options for STEP 7 Engineering System
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 23
1.3 Options for WinCC Engineering and Runtime systems
SIMATIC Panels as well as WinCC Runtime Advanced and WinCC Runtime Professional
contain all essential functions for operator control and monitoring of machines or plants.
Additional options allow you to extend the functionality in some cases to increase the range
of available tasks.
Options for Comfort Panels, Mobile Panels, Multi Panels
The following possible extensions are available for Comfort Panels, Mobile Panels, and Multi
Panels:
WinCC SmartServer (remote operation)
WinCC Audit (audit trail and electronic signature for regulated applications)
Note
In contrast to WinCC flexible 2008, functions from the WinCC flexible /Sm@rtService,
WinCC flexible /Sm@rtAccess options as well as the WinCC flexible /OPC Server option
are incorporated into the basic functionality.
Options for WinCC Runtime Advanced
The following possible extensions are available for WinCC Runtime Advanced:
WinCC SmartServer (remote operation)
WinCC Recipes (recipe system)
WinCC Logging (logging of process values and alarms)
WinCC Audit (audit trail for regulated applications)
Note
In contrast to WinCC flexible 2008, functions from the WinCC flexible /Sm@rtService,
WinCC flexible /Sm@rtAccess options as well as the WinCC flexible /OPC Server option
are incorporated into the basic functionality.
Options for WinCC Runtime Professional
The following possible extensions are available for WinCC Runtime Professional:
WinCC Client (standard client for structuring multi-station systems)
WinCC Server (supplements WinCC Runtime to include server functionality)
WinCC Recipes (recipe system, formerly WinCC /UserArchives)
System overview of STEP 7 and WinCC
1.3 Options for WinCC Engineering and Runtime systems
WinCC Advanced V11.0 SP1
24 System Manual, 08/2011,
WinCC WebNavigator (Web-based operator control and monitoring)
WinCC DataMonitor (display and evaluation of process states and historical data)
Note
In contrast to WinCC V7, functions from the WinCC /OPC-Server and WinCC /
ConnectivityPack options are incorporated into the basic functionality. Likewise, the basic
functionality includes the Runtime API from WinCC /ODK.
Beyond the Runtime options, WinCC Runtime Advanced and WinCC Runtime Professional
can be extended through customer-specific controls. To develop controls, the WinCC
ControlDevelopment option is required.
System overview of STEP 7 and WinCC
1.3 Options for WinCC Engineering and Runtime systems
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 25
Readme
2
2.1 General notes
2.1.1 General notes
The information in this readme file supersedes statements made in other documents.
Read the following notes carefully because they include important information for installation
and use. Read these notes prior to installation.
Security settings
In order to operate the software packages in the TIA Portal, port 4410 for TCP must be entered
as an exception in the Windows firewall during installation.
Installing new .Net versions or .Net service packs
Close the TIA portal before installing a new .Net version or a new .Net service pack on your
programming device/PC.
Restart the TIA portal only after successful installation of the new .Net version or the
new .Net service pack.
Notes on handling
If a project in the list of projects last used is located on a network drive that is not connected,
you may experience delays when opening the "Project" menu.
When you insert a CPU, you may need to wait for some time if the project editor is open at
the same time. This generally takes longer when you insert the first CPU in a newly created
project. To be able to continue working more quickly, you should close the project editor
before inserting a CPU.
The message "Application is not responding" may appear in Windows 7 with functions that
take a long time to run (loading the CPU for example). If this occurs, wait until the function
has correctly finished.
If you have installed a Microsoft mouse with IntelliPoint, you may find that it superimposes
components over the buttons of the title bar. If this is the case, uninstall the IntelliPoint
software from Microsoft.
Enabling the "Virtual Desktop" options with NVIDIA graphics cards can cause problems. In
this case, disable the "nView virtual desktop manager" of your NVIDIA graphics driver.
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 27
Using the TIA Portal via a remote desktop
In principle, it is possible to use the TIA Portal via a remote desktop connection. During
configuration, you should, however, avoid disconnecting the connection to the desktop client.
In rare cases, this can lead to the software user interface being blocked.
If you experience this blockage, follow these steps on the desktop client.
1. Open the Windows Task-Manager and close the "rdpclip.exe" process.
2. Type in "rdpclip.exe" in the command prompt to restart the process.
Note that the current content of the clipboard will be lost. You can, however, then continue
configuration as usual. To be on the safe side, you should restart the TIA Portal at the next
opportunity.
Opening the TIA portal multiple times
If you are running several applications of the TIA portal and they continually become active in
turn, you can briefly switch to another application or use the key combination <ALT+Tab> to
solve the problem.
Note on SD cards
The SD cards have been formatted and initialized by Siemens for use with S7-1200 modules.
This format must not be overwritten otherwise the card will no longer be accepted by the
S7-1200 modules. Formatting with Windows tools is therefore not permitted.
Behavior in case of open force job
Note that active force jobs will be retained even after you have loaded a new project to the SD
card. This means you should first delete the active force job before you remove an SD card
from the CPU and before you overwrite the card in the PC with a new project. If you use an
SD card with unknown content, you should format the SD card before the next download.
Issues when shutting down Windows XP or when activating a screen saver
Windows XP uses the ACPI (Advanced Configuration and Power Interface) to shut down the
computer or to go to standby mode. It can happen that while the system is processing a newly
installed tool that the screen saver is not activated by the ACPI or that after exiting the tool
that Windows XP cannot be shut down properly.
If the TIA Portal is running, the Standby function of the computer is deactivated. To put the
computer into Standby, you have to first exit the TIA Portal.
The following description shows several optional settings in the "Power Options Properties"
you can use to set the Standby mode of the computer with the function "Hibernate":
1. In Windows XP, open the "Power Options Properties" by pointing at "Start > Settings >
Control Panel > Power Options" and select the tab "Hibernate". Select the "Enable
hibernation" check box.
2. Switch to the "Advanced" tab. In the "Power buttons" dialog, click the drop down list box
under "When I close the lid of my portable computer:" and select the option "Hibernate".
3. Then click the drop-down list box under"When I press the power button on my computer:"
and select the option "Shut down".
Readme
2.1 General notes
WinCC Advanced V11.0 SP1
28 System Manual, 08/2011,
4. Click "Apply" and confirm the settings with "OK".
5. Afterwards, restart the PC.
If you experience problems shutting down the computer, make sure that the TIA Portal has
closed completely.
1. In the shortcut menu, select the Task Manager from the shortcut menu on the Taskbar.
2. If you see the process "Siemens.Automation.ObjectFrame.FileStorage.Server.exe" in the
"Processes" tab, wait until this process has closed.
3. Then you can shut down the computer.
Subnet addressing for CP 1613 and CP 1623
CP 1613 and CP 1623 are communication modules with microprocessor. To ensure secure
management of communication links, these are processed on the module. The protocol stack
in your PC is used for diagnostic purposes (SNMP, DCP). To allow both protocol stacks (i.e.
CP 1613/23 Firmware and CP 1613/23 NDIS access) access to the same partners, is
recommended to place both stacks of a module in the same subnet.
Editing a device IP address
Do not use the address range from 192.168.x.241 to 192.168.x.250 when editing a device IP
address. If necessary, this address range is automatically assigned by the system to a
programming device. Depending on the subnet mask, this applies also for all network classes.
"TM_MAIL" instruction for TeleService
The "TM_MAIL" instruction is not included in the scope of delivery for TIA portal V11.0. The
information on the use and functionality of the "TM_MAIL" instruction contained in the
information system does not apply.
Migrating projects with the TIA Portal
After the migration of hardware configurations and program blocks from earlier automation
solutions, first check the functionality of the migrated project before you use it in productive
operation.
Screen display
After long periods of work, it can happen in the case of certain computer configurations with
Windows XP that parts of the TIA Portal interface are no longer updated. Reducing the graphic
hardware acceleration can correct this problem. You can find the setting for this by clicking on
the desktop and selecting "Properties > Settings > Advanced > Troubleshoot > Slider Hardware
acceleration" by means of the right mouse button. In this dialog, move the slider "Hardware
acceleration" gradually to the left and apply this setting until the contents of the screen are
displayed correctly again.
Readme
2.1 General notes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 29
Tablet PCs
For the TIA Portal V11, tablet PCs are only released with the operating system Windows 7,
not with Windows XP.
SQL Server
During the installation of the SQL Server 2005 or the SQL Server 2005 Express, an error can
occur if the product SQL Server 2008 is already installed on your system.
In order to be able to use both varieties of the SQL Server in parallel, the SQL Server 2005
must be installed before the SQL Server 2008. To do this, follow these steps:
1. Remove the SQL Server 2008 version, without deleting the databases.
2. Install WinCC. The SQL Server 2005 is hereby installed and set up on your system.
3. Install the SQL Server 2008 again. Now you can continue to use the databases already
created in the SQL Server 2008.
Working with automatically synchronized network drives
Automatic synchronization after a network interruption can result in current (local) project data
being stored as a "backup" on the network drive through user interactions. This could cause
outdated project data to be loaded from the network drive when opening the project. For this
reason, we do not recommend that you store TIA Portal projects on synchronized network
drives.
If, however, you do work on synchronized drives, you can continue working locally in the event
of a network interruption. In this case, you must always ensure that the TIA Portal application
is closed while data is synchronized. The synchronization itself must be implemented in such
a way that the current (local) project data replaces the project data on the network drive.
Entry of decimal places
With certain Windows language settings, it may occur that the entry of values with a comma
is not recognised (entering "1,23" leads to an error). Instead, use the international format
("1.23").
FAQs on the TIA Portal
FAQs on the TIA Portal are available at http://support.automation.siemens.com (http://
support.automation.siemens.com/WW/view/en/28919804/133000).
2.1.2 Notes on the installation
Contents
Information that could not be included in the online help.
Readme
2.1 General notes
WinCC Advanced V11.0 SP1
30 System Manual, 08/2011,
Target directory of the installation
Do not use any UNICODE characters (for example, Chinese characters) in the installation path.
Installation of STEP 7 Basic V11 and STEP 7 Professional V11 under Windows XP with Turkish
Regional and Language Options
Installation of STEP 7 Basic V11 and STEP 7 Professional V11 under Windows XP may be
cancelled, if the regional and language options are set to Turkish. In this case change the
regional and language options from Turkish to English or German.
1. Open the Control Panel under Windows with one of the following commands:
"Start > Control Panel" (Start menu under Windows XP)
"Start > Settings > Control Panel" (classic start menu)
2. Open the "Regional and Language Options".
3. Select the "Regional Options" tab.
4. Under "Standards and formats" select "German" or "English" in the drop-down list.
5. Click "Apply" and confirm with OK.
6. Restart your PC for the setting to become active. Now you can continue with the installation
of STEP 7 Basic V11 and STEP 7 Professional V11.
7. After installation, you can revert the regional and language settings (as described in steps
1 to 4) to Turkish.
Removing
In rare cases removal of the program can cause the computer to freeze, even when a full
version of SQL Server 2005 is installed. In this occurs, disconnect the computer from the
network to continue the removal process.
Installation of the SIMATIC USB driver under Windows server 2003 R2 StdE SP2
An operating system message relating to the SIMATIC USB driver is issued on the operating
system Windows Server 2003 R2 StdE SP2. This message must be acknowledged with "Yes"
as soon as possible after the message has been issued. The message may be in the
background and therefore may not be immediately visible. After a certain period of time, the
setup continues with the next component. The SIMATIC USB drivers are then not installed
and cannot be used.
Display of the desktop icon
If you do not select the standard installation path during the installation of the TIA portal, the
desktop icon may not be displayed correctly. This does not affect the functionality of the product.
Readme
2.1 General notes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 31
2.1.3 Use of communications processors
Contents
Information that could not be included in the online help.
Necessary hotfixes for the use of certain communications processors
For the following communication processors, hotfixes are required for the use of certain
products:
CP 1613
CP 1613 A2
CP 1623
CP 5613
CP 5614
CP 5613 A2
CP 5614 A2
CP 5623
CP 5624
Install the following hotfixes and service packs:
SIMATIC NET CD V8.0 SP1 for Windows 7: Hotfix 1 for SIMATIC NET CD V8.0 SP1
SIMATIC NET CD 2008 SP3 for Windows XP, Windows Server 2003 or Windows Server
2008
You can find the hotfixes in the Service & Support area (http://
support.automation.siemens.com/WW/view/en/12660737) of the Siemens website under the
entry ID 12660737
Operation of communications processors
If both STEP7 V5.5 and STEP7 V11 are installed on a computer and STEP7 V5.5 is removed,
the setup repair function of STEP7 V11 must be executed before the following communications
processors can be used:
CP 561x
CP 5613 A2
CP 5614 A2
CP 5623
CP 5624
CP 5711
Readme
2.1 General notes
WinCC Advanced V11.0 SP1
32 System Manual, 08/2011,
2.2 WinCC Readme
2.2.1 Functional Constraints
Functional Constraints
The following functions are already described in the information system, but are not available
in WinCC V11.0 Advanced:
1. Mobile Panel 277 IWLAN V2; Mobile Panel 277F IWLAN V2; Mobile Panel 277F IWLAN
(RFID tag)
These devices cannot be configured with WinCC V11.
2.2.2 Notes on use
Contents
Information that could not be included in the online help.
Parallel installation in the TIA portal
You will be prevented from starting the TIA portal if you set up a non-permitted parallel
installation of STEP 7 and WinCC.
The following parallel installations are not permitted in the TIA portal:
STEP 7 V11 and WinCC V11 SP1
STEP 7 V11 SP1 and WinCC V11
Both Engineering Systems must always have the same version after an installation.
A dialog opens during installation to inform you of any inconsistencies in your parallel
installation.
The following parallel installations are also not permitted:
WinCC V11 and RT Advanced V11 SP1
WinCC V11 SP1 and RT Advanced V11
The Engineering System and Runtime must always be of the same version after an installation.
Parallel use
If the term "Combo" appears in the name or license key of the software after installation, the
use of the following products/versions is permitted in accordance with paragraph 1.6 of the
General Terms and Conditions (see also setup text):
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 33
WinCC flexible 2008 Standard
Copying HMI devices with HMI connections
If you copy an HMI device with HMI connections to a PLC, the HMI connection in the new HMI
device will not automatically be connected to an existing PLC with the same name. This
statement applies to copying within a project as well as copying across projects.
To access the PLC tag via HMI tag in the new HMI device, you will have to complete the HMI
configuration immediately after the copying step. Proceed as follows:
1. Open the "Devices & Networks" editor.
2. Connect the new HMI device with the desired network.
3. Open the connection table.
4. Select the HMI connection of the new HMI device.
5. Select the desired PLC under "Partner".
If you compile the new HMI device or connect additional PLC tags in between copying the HMI
device and completing the connection, there may be some instances in which you create an
additional HMI connection to the same PLC. This is especially true if you connect HMI tags
with DB array elements.
Device replacement
After an HMI device has been replaced, you should check the appearance of the configured
screens. Changing the size of the display may result in changes to the position and appearance
of screen objects, e.g. recipe view and alarm view.
Device replacement - communication
If an HMI device is replaced, error messages of the type "... will not be supported in the new
configuration. It will be removed" will be issued. These alarms refer to configured connections
of the device and are triggered, for example, if the HMI devices have a different number of
interfaces. These connections are marked red after a device replacement. If you would like to
continue to use these connections, you have change the configuration of the connection.
Proceed as follows:
1. Open the "Devices and Networks" editor.
2. Click "Network" in the toolbar of the network view.
3. Network the interface of the HMI device with the interface of the CPU.
4. Click in the tabular area of the network view on the "Connections" table.
5. Select the connection marked red.
6. Enter the new interface under "Properties > Properties > General > Interface" in the
Inspector window.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
34 System Manual, 08/2011,
Specifying the time of modification in the overview window
The times of modification displayed in the overview window only refer to changes to the object
itself. Changes to subordinate objects, e.g. screen objects in a screen, do not cause the time
of the last change to the screen to change in the overview window.
HMI device wizard
When you create a device with a color display using the HMI device wizard, the graphics of
the navigation buttons may be displayed in black and white. This error only occurs, however,
if the new device is created with the same name as a device with a monochrome display which
has been deleted in the meantime.
You can avoid this error by always deleting the associated graphics in the Graphics collection
whenever you delete a device from the project.
Objects with object references in the project library
Two copying methods can be used in WinCC flexible.
With "simple copy" a WinCC flexible screen including an IO field, for example is copied.
Only the object name of a tag configured on the IO field is copied, as this is a reference.
With "copy", a screen, an IO field contained there and a tag configured on the IO field
together with its properties are copied.
These two methods can also be used for storing an object in a library. Project libraries and the
objects contained there are migrated during migration and can be used in WinCC.
In WinCC, however, only one copying method is available. With regard to tags, it functions like
"simple copy" in WinCC flexible. With regard to graphics, graphics lists and text lists, it functions
like "copy" in WinCC flexible.
If you stored objects with references to tags in a library in WinCC flexible, you must reconfigure
the referenced objects when using them in WinCC.
Reports with Asian character sets on Windows CE devices
If Asian characters sets are displayed in an illegible manner in a report on a Windows CE
device, you must change the character sets for the objects in the report. it is sufficient to change
to a different character set and then reset the original character set.
Windows 7 and Windows 7 SP1
WinCC V11 SP1 is released for:
Windows 7
Windows 7 SP1
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 35
2.2.3 Migration
Contents
Information that could not be included in the online help.
Changing the names of alarm classes
In contrast to WinCC flexible, the names of the predefined alarm classes are not dependent
on the user interface language currently in use. During migration, the names of the alarm
classes are assigned as follows:
WinCC flexible WinCC
Error Errors
System System
Warnings Warnings
The display names of the alarm classes can be changed as necessary after migration.
Project languages in WinCC
WinCC V11 does not support all project languages that were available in WinCC flexible, such
as Arabic. If you receive an empty project as the result of your migration, you may want to
check the set editing language. Do not set the project languages that are not supported as
editing language in the source project. Proceed as follows:
1. Open the project with WinCC flexible.
2. Change the editing language to English, for example.
3. Save the project.
4. Restart the migration.
Objects with object references in the project library
Two copying methods can be used in WinCC flexible.
With "simple copy", a WinCC flexible screen including an IO field, for example, is copied.
Only the object name of a tag configured on the IO field is copied, as this is a reference.
With "copy", a screen, an IO field contained there and a tag configured on the IO field
together with its properties are copied.
These two methods can also be used for storing an object in a library. Project libraries and the
objects contained there are migrated during migration and can be used in WinCC.
In WinCC, however, only one copying method is available. It functions like "simple copy" in
WinCC flexible.
If you have stored objects with references to other objects in a library in WinCC flexible, you
must reconfigure the referenced objects when using them in WinCC.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
36 System Manual, 08/2011,
Structures with data type "Stringchar"
In WinCC V11, the data type "StringChar" is not supported in HMI user data types.
If you have used this data type in a structure in a WinCC flexible project, an invalid element is
created by the migration in the HMI user data type.
You have to rework this user data type in WinCC. You can only remove the invalid element if
you assign a valid data type and release the user data type. You can then delete the element.
However, doing this causes any interconnections present between a faceplate and the
elements of the user data type to be lost.
Also check the offsets of the subsequent elements and change them, if required.
Tag logging archives from WinCC V7
It is not possible to use the tag logging archives from WinCC V7 after migration to WinCC V11.
See also
Object support during migration
2.2.4 Special considerations for Windows 7
Contents
Information that could not be included in the online help.
Permission for the starting Runtime
To start WinCC Runtime Professional or WinCC Runtime Advanced, a user must be a member
of the automatically created group, "Siemens TIA Engineer".
Working with standard user rights
If you are working with standard user rights in Windows 7, "User Account Control (UAC)" cannot
be disabled.
The "User Account Control" is enabled in Windows 7 by default.
For more information on the "User Account Control, refer to the online help for Windows 7.
Slow response from the screen keyboard and SmartServer
The following programs may start and respond very slowly under Windows 7 and Windows
2008 servers:
Microsoft OSK screen keyboard and HMI TouchInputPC
SmartServer: <Ctrl+Alt+Del> shortcut in the logon dialog
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 37
The delay is caused by the callback for the Internet certificate validation.
Remedy:
Locate the following files on the product DVD under:
Support\Windows7\CRL_Check or CD_RT\ Support\Windows7\CRL_Check\
:
DisableCRLCheck_LocalSystem.cmd
DisableCRLCheck_CurrentUser.cmd
1. Run the "DisableCRLCheck_LocalSystem.cmd" file with administrator rights. Select the
command "Run as administrator" from the shortcut menu of the file.
2. Reboot the PC.
If the problem persists, follow these steps:
1. Double-click the file and run the "DisableCRLCheck_CurrentUser.cmd" file with user rights.
2. Reboot the PC.
NOTICE
The callback for the certificate validation is disabled for all users or PCs. To restore the
original state, perform the following files:
RestoreDefaults_LocalSystem.cmd
RestoreDefaults_CurrentUser.cmd
You can find the files in the following directory of product DVD:
Support\Windows7\CRL_Check bzw. CD_RT\Support\Windows7\CRL_Check\
2.2.5 Engineering System
2.2.5.1 Screens and Screen Objects
Contents
Information that could not be included in the online help.
Text format of output fields in alarm text
It is not possible to underline tags and text list entries.
Copying display objects between two projects or two devices
In Project_1 configure an alarm window in the Global Screen, for example. You copy the alarm
window and paste it in the Global Screen in Project_2.
The enabled alarm classes are partly not enabled in the alarm window after pasting.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
38 System Manual, 08/2011,
This behavior applies to the following display objects:
Alarm window
Alarm indicator
Alarm view
Representation of the cross-references in the Inspector window
The Inspector window displays objects used by a screen object in the "About > Cross-
reference" tab.
A screen is open and an object selected. You are using an HMI tag at the object as process
tag.
The object and the linked HMI tag are displayed in the cross-references. All locations of use
of the object and the HMI tags are listed.
If the HMI tag is interconnected with a PLC tag or a DB tag, then the locations of use of the
interconnected PLC tag or DB tag will be displayed.
Event names in case of alarms in the "Info" tab of the Inspector window
In some alarms of the Inspector window the event names in the "Info" tab will deviate from the
names in the "Properties" tab.
Name in the "Properties" tab of the Inspector
window
Name in the "Info" tab of the Inspector window
Cleared ClearScreen
Loaded GenerateScreen
Enable Activate
Change Change
When a dialog is opened ONMODALBEGIN
When a dialog is closed ONMODALEND
User change PASSWORD
Screen change SCREEN
Disable Deactivate
Press Press
Outgoing Going
Incoming Coming
Limit "high limit error" violated AboveUpperLimit
Limit "low limit error" violated BelowLowerLimit
Click Click
Loop-In-Alarm LoopInAlarm
Release Release
Alarm buffer overflow OVERFLOW
Acknowledge Acknowledgement
Runtime stop Shutdown
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 39
Name in the "Properties" tab of the Inspector
window
Name in the "Info" tab of the Inspector window
Press key KeyDown
Release key KeyUp
Switch ON SwitchOn
Switch OFF SwitchOff
Value change Change value
Dynamization of object properties in a group
The dynamization of properties for all objects of the group which have these properties is not
possible in a group. In WinCC V11, the properties of the objects beloning to a group can only
be dynamized for each object itself.
Illegible characters in Runtime Professional
With Runtime Professional, only characters belonging to the language area which is defined
with the operating system setting "Language for non-Unicode programs" can be displayed on
the target system. Texts with characters from other language areas can, however, also be
configured in the project.
Illegible characters may occur in the Engineering System with the objects text field, symbolic
I/O field, gauge and slider if the settings in the operating system relating to "Language for non-
Unicode programs" do not match the selected editing language and the objects are displayed
in a different design than "WinCC Classic". The characters are displayed correctly in the
Inspector window and the "Project texts" editor.
Therefore, first check in the Control Panel under "Regional and Language Options > Advanced"
whether the setting for "Language for non-Unicode programs" is the same as the editing
language. Otherwise, you can check or change the correct texts in the Inspector window or
the "Project texts" editor.
Faceplates
Faceplates cannot be rotated or mirrored.
Persistence with display objects in WinCC Runtime Professional
The objects f(t)-trend view, f(x)-trend view, alarm view, recipe view, table view and value table
have settings for the persistence of online configurations. If you have configured "Persistence"
for "Online configuration" and "Keep changes" for "Reaction to screen change", you can make
changes to the configuration dialogs in runtime which will be retained after a screen change
and after runtime is exited.
However, online configurations for the settings mentioned cause changes to the configuration
of the objects in the Engineering System to only be applied in Runtime if you recompile the
device with the command "Compile > Software (rebuild all)".
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
40 System Manual, 08/2011,
Basic Panels, OP73, OP77A and TP177A: Displaying texts in runtime
The default font selected in the "Runtime settings > Languages & font" editor has an effect on
the display of texts in runtime.
Text entries may be truncated if you selected an unfavorable font size or style.
This setting possibly has an effect on the following text entries:
Tooltips
long alarm text
text in the dialogs
2.2.5.2 Tags
Contents
Information that could not be included in the online help.
Tag names
HMI tag names may not start with the character @.
Display of deleted array elements at location of use of HMI tags
The locations of use of HMI tags, such as the process value of IO fields, are usually indicated
by the tag name. If the element of an array tag is used, then the tag name will be extended by
the index of the array element indicated in brackets.
If a used tag is no longer included in the project, then the tag name will still be displayed at the
location of use. The field will be displayed with a red background to indicate the missing tag.
If a used array element or the array tag is no longer present, then only the index of the array
element will be displayed in brackets. The tag name will not be displayed. The field is
highlighted in red. You can no longer identify the name of the associated array tag based on
the location of use in this instance.
If you do not know which array tag was linked to this location of use, then it may be necessary
to link the array element once again.
If a tag or array tag was created based on a reference, then the selected reference will be
closed automatically.
If an HMI tag is connected with an array element of a PLC tag and the PLC tag does no longer
exist in the project, then the same behavior will take place in the "HMI tags" editor.
Array tags as list entry of multiplex tags
You can use the array tags of the Char data type just like the tags of the String data type.
The use of an array tag of the Char data type as list entry of a multiplex tag in the "HMI
tags" editor is not supported.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 41
2.2.5.3 Alarm system and alarm displays
Contents
Information that could not be included in the online help.
Displaying special characters in alarm texts
When configuring alarm texts, a fixed character set is used in the Engineering System. This
character set allows you to use numerous special characters in alarm texts.
Language-dependent fonts are used in runtime to display the texts, for example MS PGothic,
SimSun. The fonts used in runtime do not support all special characters. As a result, some
special characters are not displayed in runtime.
Use of multiplex tags in output boxes with alarm texts
In the engineering system, it is also possible to use multiplex tags in the output boxes of alarm
texts. During runtime, this leads to an incorrect display of the alarm, because the use of
multiplex tags is not supported by the basic panels.
2.2.5.4 System functions and scripts
Contents
Information that could not be included in the online help.
Debugging using the Microsoft Script Debugger
If you want to use the Microsoft Script Debugger for debugging, the English version
"scd10en.exe" must be used. The German version "scd10de.exe" cannot be installed.
Runtime error on startup on TP 277 and OP 277
At the start of the runtime on a TP 277 or OP 277, the error "Global unknown error with VBScript:
'Expected statement' in script ..". can be reported.
This error is triggered on devices with the Windows CE 3.0 operating system by user functions
of the following type:
Sub VBFunction_1()
With HmiRuntime.Screens("Screen_1").ScreenItems("Button_1")
.backcolor = vbred
.visible = not .visible
End With
End Sub
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
42 System Manual, 08/2011,
If the error occurs, you need to re-program the user function as follows:
Sub VBFunction_1()
HmiRuntime.Screens("Screen_1").ScreenItems("Button_1").backcolor = vbred
HmiRuntime.Screens("Screen_1").ScreenItems("Button_1").visible = not .visible
End Sub
2.2.5.5 Recipes
Contents
Information that could not be included in the online help.
2.2.5.6 User administration
Contents
Information that could not be included in the online help.
2.2.5.7 Communication
Contents
Information that could not be included in the online help.
Connection interruptions with Mitsubishi PLCs
After multiple connection interruptions, a situation may arise where all the connection
resources of the Mitsubishi PLC are in use and the connection can no longer be established.
It is recommended to check these connection resources in the PLC program of the PLC and
also enable them again.
Using "DTL" data type for area pointers
Use the "DTL" data type for configuration of area pointers "Date/time" and "Date/time PLC".
The "DTL" data type supports time information down to the nanosecond range. Because Basic
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 43
Panels support time information only down to the millisecond range, you will encounter the
following restrictions in the case of use on the area pointers:
Area pointer "Date/time"
For transmission of time information from a Basic Panel to the PLC, the smallest unit of
time is 1 millisecond. The value range from microseconds to nanoseconds of the "DTL"
data type will be filled with zeros.
Area pointer "Date/time PLC"
For transmission of time information from a PLC to a Basic Panel, the area from
microseconds to nanoseconds will be ignored. The time information will be processed on
the panel down to milliseconds.
Limited number of possible HMI connections
An error message is displayed during compilation of a device indicating that the configuration
of the HMI connection in the "Devices & Networks" editor is invalid. The reason may be that
the maximum number of possible connections of the HMI device or PLC has been exceeded.
Check the maximum number of available connections. Consult the device manuals of the
devices you are using.
Routed communication with S7 300/400
The communication of connection partners in various subnets can be routed via the following
links: PROFINET, PROFIBUS, MPI.
Using PROFINET IO with panel HMI devices
When using PROFINET IO to connect the direct keys and LEDs of HMI devices to the PLC,
you can define an offset for the address area of the inputs and outputs during configuration in
HW Config.
The following restriction applies when you use a PROFINET IO-capable CPU of the 400 series
with one of the HMI devices listed below:
The offset for the start of the address area of the inputs must not be bigger than the offset for
the start of the address area of the outputs.
The restriction applies to the following HMI devices:
OP 177B
OP 277
Mobile Panel 177
For the configuration of the address parameters, open the PLC with the CPU of the 400 series
in HW Config. Select the HMI device connected via PROFINET IO in the station window of
HW Config. A table with the properties of the HMI device is displayed at the bottom of the
station window in the detail view. Select the line containing the addresses of the HMI device
in the table and open the object properties using the shortcut menu.
Select the "Addresses" tab in the "Object properties" dialog. Configure the offset for the inputs
under "Inputs > Start". Configure the offset for the outputs under "Outputs > Start".
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
44 System Manual, 08/2011,
Exceeding value ranges with Mitsubishi MC and Mitsubishi FX
With some data types, the communication drivers Mitsubishi MC and Mitsubishi FX do not
check whether the value of a recipe tag exceeds the value range of the PLC tags. The data
types affected are:
4-bit block
12-bit block
20-bit block
24-bit block
28-bit block
Area pointer Coordination in an OPC connection
In principle, the area pointer Coordination can be used eight times in an OPC connection. If
you have configured an OPC connection and automatically create another OPC connection
using "Add", the area pointer Coordination is only displayed once in the newly created
connection. In this case, you should change the communication driver of the connection. If you
then set OPC again as the communication driver, the area pointer Coordination can again be
used eight times.
Communication resources: SIMATIC S7 1200
The SIMATIC S7 1200 controller provides six communication resources for HMI
communication.
The number of HMI connections that you can actually configure depends on the HMI devices
that you connect with the SIMATIC S7 1200.
One HMI Panel occupies one communication resource per connection.
One RT Advanced occupies one communication resource per connection.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 45
RT Advanced communication via Station Manager (SIMATIC NET) with a SIMATIC S7 1200
For routed communication of a SIMATIC S7 1200 with a PC with WinCC RT Advanced, the
following restrictions apply for the PC:
Windows 7: Only with installed SIMATIC NET 8.1
Windows XP: Communication via Station Manager (SIMATIC NET) is not supported
These restrictions also apply if you are using WinAC MP or Station Manager. Connections with
the help of the Station Manager of Runtime Advanced are always treated as routed
connections.
Valid operand types for communication with Mitsubishi MC TCP/IP
Operand type "W" is not available for the "String" data type.
Communication between S7-1200 and a multi panel
Communication between an S7-1200 and a multi panel with the "WinAC MP" option installed
via ProSave is not possible. The data types affected are:
SIMATIC MP 177 6" Touch
SIMATIC MP 277 8" Touch
SIMATIC MP 277 8" Key
SIMATIC MP 277 10" Touch
SIMATIC MP 277 10" Key
SIMATIC MP 377 12" Touch
SIMATIC MP 377 12" Key
SIMATIC MP 377 15" Touch
SIMATIC MP 377 19" Touch
2.2.6 Compiling and loading
Contents
Information that could not be included in the online help.
Compiling and loading
If internal errors or warnings occur during compiling, compile the complete project using the
command "Compile > Software (rebuild all)" in the shortcut menu of the HMI device.
Before you start productive operation with your project, compile the entire project using the
"Compile > Software (rebuild all)" command from the shortcut menu of the HMI device.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
46 System Manual, 08/2011,
If you are using HMI tags that are connected to the control tags in your project, compile all
modified blocks with the command "Compile > Software" in the shortcut menu before you
compile the HMI device.
Saving the WinCC project
If you save a project in WinCC using the "Save As" command, this has no effect on the name
of the Runtime projects generated for the devices. If you do not adapt the target path of the
devices in the "Extended download to device" dialog, the Runtime projects on the target
devices will be overwritten.
Settings for update of operating system
If you select the command "Online > HMI device maintenance > Update operating system"
from WinCC, you cannot change the settings such as the type of PG/PC interface or baud
rate. The settings used during the last download are always used.
To make changes to the settings, open the "Extended download" dialog using the "Online >
Extended download to device" command and change the settings. When you click the "Load"
button the changed settings are saved.
Alternatively, you can perform an update of the operating system with changed settings with
ProSave. You start ProSave via the Windows Start menu "Siemens Automation > Options and
Tools > HMI Tools > SIMATIC ProSave".
Incorrect installation of ProSave
If you receive an error message during installation of ProSave when loading data to a target
device or maintenance of an HMI device, then you cannot remedy this error using the repair
function of setup. Remove ProSave via the Control Panel. Then start setup and install the
"ProSave" component again.
Checking the address parameters
During compilation of an HMI device in the project tree with the command "Compile > Software"
in the shortcut menu, the address parameters of the HMI device, such as the IP address, will
not be checked. If you want to ensure that the address parameters are checked as well, you
will have to compile the HMI device in the "Devices & Networks" editor of the toolbar.
Error message when downloading data to the PLC
A panel and a PLC are connected and communicating with other.
If a tag is accessed while downloading data from the panel to the PLC, an error message is
displayed on the panel.
Delayed reaction in the "Extended download to device" dialog
If the settings in the "Extended download to device" dialog for "Type of the PG/PC interface"
and "PG/PC interface" do not match the settings on the HMI device, this can result in the
application not responding for up to a minute.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 47
Extended download with an S7-1200 and a Comfort Panel
An S7-1200 PLC and a Comfort Panel are located in the same physical network as the PG/
PC. You open the "Extended download to device" dialog for the Comfort Panel.
If you activate the option "Show all accessible devices", it may occur that the application stops
responding.
OP77A, OP73, TP177A: Loading projects
When loading a project to an HMI device, it can happen that Runtime is not automatically
ended, even though "Remote Transfers" is activated in the Panel.
If this happens, stop Runtime and manually set the transfer mode on the HMI device.
Loading a SIMATIC HMI application to a PC station
The following circumstances can lead to an error message during the first load of a SIMATIC
PC station:
A SIMATIC HMI application is configured in a PC station in the project
WinCC Runtime Advanced
WinCC Runtime Professional
WinCC Standby
or WinCC Client
The property "S7RTM is installed" is activated.
Before you load a SIMATIC PC station for the first time, select the configured device HMI_RT
(WinCC...) in the project navigation. Open the "Extended download to device" dialog and select
the appropriate interface and parameter settings. Click "Load".
You then load the PC station as normal.
Unpacking a distributed "Pack&Go" file
To unpack a "Pack&Go" file which is distributed over several files, you need an unpack
program. The unpack program integrated in the operating system is not adequate to unpack
distributed files.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
48 System Manual, 08/2011,
2.2.7 Runtime
2.2.7.1 Notes on operation in Runtime
Contents
Information that could not be included in the online help.
CAUTION
Ethernet communication
In Ethernet-based communication, the end user is responsible for the security of his data
network. The proper functioning of the device cannot be guaranteed in all circumstances;
targeted attacks, for example, can lead to overload of the device.
Special characters in the user view
Special characters, such as / " $ % & ' ?, are not permitted when entering a name or the
password in the user view.
Language behavior - Layout of screen keyboard
The layout of the screen keyboard is not switched when the runtime language changes.
Tag values overwrite the maximum length
You enter a character string in a string tag via an I/O field. If the character string exceeds the
number of configured tags, the character string will be shortened to the configured length.
2.2.7.2 Notes on operation of panels in Runtime
Contents
Information that could not be included in the online help.
Using the mouse wheel in Runtime
The use of the mouse wheel in Runtime is not supported on all panels.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 49
2.2.7.3 Notes on operation of Runtime Advanced
Contents
Information that could not be included in the online help.
.Net-Controls in Runtime
If you have incorporated a .Net Control in your project as "Specific .Net-Control", you have to
copy the files belonging to these controls to the installation directory of WinCC Runtime, e.g.
"C:\ProgramFiles\Siemens\Automation\WinCC RT Advanced". Otherwise, the control cannot
be loaded in Runtime.
2.2.8 HMI devices
2.2.8.1 General notes
Contents
Information that could not be included in the online help.
If the PC goes into standby or hibernate mode while the transfer is in progress, the panel status
after interruption of the transfer is not defined.
TS Adapter with Ethernet interface
If an HMI device is connected via Ethernet and a TS adapter, it can not be reset to factory
settings.
Simulation of the Basic Panels
Use an output field in an alarm text to output an external tag. The content of the output field
will always be displayed with "0" during simulation.
Simulation with real PLC connection
The access point used by the simulation is independent from the settings of the Engineering
System and can only be altered in the Control Panel with the "Setting PG/PC Interface" tool.
If the PLC connection is terminated right after the start of the simulation with alarm 140001,
you should check the access point used by the simulation with "Setting PG/PC Interface".
1. Double-click "Setting PG/PC Interface" in the Control Panel. A dialog opens.
2. Select" "S7ONLINE" in the "Access point of application" field as standard for HMI.
3. Select the interface in the "Interface Parameter Assignment Used" area.
4. Exit the dialog "Setting PG/PC Interface" with OK
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
50 System Manual, 08/2011,
Loading of projects without recipe data records
You are using recipes in a project. You transfer the project to a Basic Panel without recipe
data records.
You may encounter inconsistencies if you have altered the structure of the recipe in the
Engineering System and the device already held recipe data records.
Check the consistency of the data records in this case. The device will not issue a note for all
structural changes.
Floating point numbers on MP 277, MP 377, TP 177B 4'' and CP4
Only floating point numbers in the range from 10
-293
... 10
+307
are displayed correctly on the
HMI devices MP 277, MP 377, TP 177B 4'' and CP4. If the tag value is outside this range, it
is displayed as 0.
USB device driver under Windows XP
If a configuration PC with Windows XP and a Comfort Panel are connected via USB, the S7-
USB driver may be reinstalled when the HMI device is restarted. The device settings may in
this case not be restored.
2.2.8.2 Printing via print server
Introduction
Print servers enable access to network printers. Print jobs are routed to a corresponding printer
via the print server.
Note
Printing takes place via the print server for the following HMI devices:
xP 177, Mobile Panel 177
xP 277, Mobile Panel 277, Mobile Panel 277 IWLAN, Mobile Panel 277F IWLAN
Mobile Panel 277 IWLAN V2, Mobile Panel 277F IWLAN V2, Mobile Panel 277F IWLAN
(RFID Tag)
MP 377
PC with WinCC Runtime Advanced
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 51
Requirements
The print server deploys the "RAW" mode.
Note
For additional information on settings, refer to the relevant print server documentation.
The device is interconnected via Ethernet with the print server or with a printer featuring an
integrated print server.
External print servers are interconnected with a printer via USB port.
The IP address and port used are identical in the "Printer Properties" of the HMI device and
on the print server.
Procedure
1. Open the "Control Panel" on your HMI device.
2. Select "Printer". The "Printer Properties" dialog box opens.
3. Select a printer from the "Printer Language" selection list.
4. Select the "PrintServer" entry from the "Port" selection list.
5. Enter the IP address and the port used for communication with the printer in the "IP:Port"
input field.
Note
Use the ":" character as delimiter between the IP address and the port number. For
example: "192.168.56.23:9100".
6. Select any additional printer settings.
Readme
2.2 WinCC Readme
WinCC Advanced V11.0 SP1
52 System Manual, 08/2011,
Installation
3
3.1 System requirements for installation
3.1.1 Notes on the system requirements
System requirements for individual products
The system requirements may differ depending on the products you want to install. You should
therefore check the individual system requirements of your products.
If you want to install several products, make sure that your system meets the demands of the
product with the highest requirements.
Displaying PDF files
To be able to read the supplied PDF files, you require a PDF reader that is compatible with
PDF 1.7 e.g. Adobe (R) Reader version 9.
Displaying the Welcome Tour
You require the Adobe (R) Reader as of version 9 to start the Welcome Tour for the TIA portal.
See also
Licenses (Page 67)
Starting installation (Page 69)
Displaying the installed software (Page 72)
Modifying or updating installed products (Page 73)
Repairing installed products (Page 75)
Starting to uninstall (Page 77)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 53
3.1.2 System requirement for WinCC Advanced
3.1.2.1 Software and hardware requirements
Introduction
Specific requirements for the operating system and software configuration must be met for the
installation.
Note
WinCC is generally authorized for use in a domain or workgroup.
However, be aware that domain group policies and restrictions of the domain may hinder the
installation. In this happens, remove the computer from the from the domain prior to installing
Microsoft Message Queuing, Microsoft SQL Server and WinCC. Log onto the computer in
question locally with administrative rights. Then perform the installation. After successful
installation, you can enter the WinCC computer back into the domain. If the domain group
policies and restrictions of the domain do not impede the installation, the computer need not
be removed from the domain during the installation.
Be aware that domain group policies and restrictions of the domain may also hinder operation.
If you cannot avoid these restrictions, run the WinCC computer in a workgroup.
Consult with the domain administrator if needed.
Installation requirements
The following table shows the minimum software and hardware requirements that have to be
met for installation of the "SIMATIC WinCC Professional" software package:
Hardware/software Requirement
Processor type Pentium M, 1.6 GHz or similar
RAM 2 GB
Free hard disk space 2 GB on system drive "C:"
Operating systems * Windows XP Professional SP3
Windows 7 (Professional, Enterprise, Ultimate)
Windows 7 SP1 (Professional, Enterprise, Ultimate)
Windows Server 2003 R2 Standard Edition SP2
Windows Server 2008 Standard Edition SP2
Graphics card 32 MB RAM
24-bit color depth
Screen resolution 1024x768
Network Ethernet 10 Mbps or faster
Optical drive DVD-ROM
Software Microsoft .Net Framework 3.5 SP1
Microsoft Windows Message Queuing
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
54 System Manual, 08/2011,
* For more detailed information on operating systems, refer to the help on Microsoft Windows
or the Microsoft homepage.
Simultaneously opening multiple instances of WinCC on a configuration PC can also increase
the hardware capacity required.
Note
"Aero Glass Style" of Microsoft Windows 7
A powerful graphics card is required for "Aero Glass Style". It requires DirectX9 capabilities
and 128 MB of dedicated graphics memory.
The performance of the architecture of the graphics system can significantly influence the
performance of WinCC.
Recommended hardware
The following table shows the recommended hardware for the operation of SIMATIC WinCC.
Hardware Requirement
Computer SIMATIC FIELD PG M2 PREMIUM
Processor 2.2 GHZ CORE 2 DUO (T7500)
RAM 1X2GB DDR2 RAM
Hard disk 250GB S-ATA HDD
Monitor 15" SXGA+ DISPLAY (1400 X 1050)
Optical drive DL MULTISTANDARD DVD RW
Parallel installation of WinCC V11 and other SIMATIC products
The parallel installation of WinCC V11 is permitted with the following other SIMATIC
products
WinCC Basic V11, WinCC Comfort V11 or WinCC Advanced V11 can be installed on a
computer parallel to STEP 7 V5.4 or V5.5, STEP 7 Micro/WIN, STEP 7 10.5, WinCC flexible
(as of 2008) and WinCC (as of V7.0 SP2).
When WinCC V7 is removed, the Setup for WinCC V11 should be run and a repair
performed for the installation.
WinCC Professional V11 can be installed on a computer parallel to STEP 7 V5.4 or V5.5,
STEP 7 Micro/WIN, STEP 7 10.5 and WinCC flexible (as of 2008).
Installing Microsoft .Net Framework
.Net Framework 3.5 SP1 is included on the installation medium. The installation routine
determines if .Net Framework is already installed at the beginning of the installation. If .Net
Framework is not installed, you will be prompted with a dialog to perform the installation. When
you confirm the prompt for installation, .Net Framework is installed. You need to reboot the
computer after installing .Net Framework. If you do not install .Net Framework, the installation
of WinCC Runtime Professional is aborted.
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 55
Installing Microsoft Windows Message Queuing in Windows XP
You can install the Windows Message Queuing component from the Windows Control Panel.
Click Start > Control Panel. Double-click "Add or remove software", the "Add or remove
software" dialog opens. In the "Add or Remove Programs" dialog, click "Add or Remove
Windows Components". The Windows Components Wizard opens. Select the "Message
Queuing" component in the Windows Components Wizard. Click "Next", the "Message
Queuing" component is installed.
Installing Microsoft Windows Message Queuing in Windows 7
You can install the Windows Message Queuing component from the Windows Control Panel.
Click Start > Control Panel. Click "Programs" and the "Programs" dialog opens. Under the
"Programs and Features" section, click "Turn Windows features on or off". The "Windows
Features" dialog opens. In the "Windows Features" dialog, select the "Microsoft Message
Queue Server" feature. Click "OK" to enable the "Microsoft Message Queue Server".
Online help for Windows 7 / Windows Server 2008
Windows 7 and Windows Server 2008 no longer support all online help formats by default.
With WinCC, these online help formats are used in the following cases:
Calling WinCC Direct Help
Calling the WinCC Information System from the WinCC editors or via the Direct Help links
To be able to continue calling WinCC Direct Help, the following components are installed during
the installation of WinCC:
Microsoft Help Engine
You can also call the WinCC Information System under Windows 7 and Windows Server 2008
from the Windows Start menu or from the installation folder.
To call the WinCC Information System from the WinCC editors or via the Direct Help links,
some changes have to be made to the operating system. You can find more information on
this in the section "More information for advanced users" of Microsoft Support article "917607":
http://support.microsoft.com/kb/917607 (http://support.microsoft.com/kb/917607)
See also
Options for WinCC Engineering and Runtime systems (Page 56)
Licensing of WinCC Engineering System (Page 59)
3.1.2.2 Add-ons
Options for WinCC Engineering and Runtime systems
SIMATIC Panels as well as WinCC Runtime Advanced and WinCC Runtime Professional
contain all essential functions for operator control and monitoring of machines or plants.
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
56 System Manual, 08/2011,
Additional add-ons allow you to extend the functionality in some cases to increase the range
of available tasks.
Add-ons for Comfort Panels, Mobile Panels, Multi Panels
The following add-ons are available for Comfort Panels, Mobile Panels, and Multi Panels:
WinCC SmartServer (remote operation)
WinCC Audit (audit trail and electronic signature for regulated applications)
Note
In contrast to WinCC flexible 2008, functions from the WinCC flexible /Sm@rtService,
WinCC flexible /Sm@rtAccess add-ons as well as the WinCC flexible /OPC Server add-
on are incorporated into the basic functionality.
Add-ons for WinCC Runtime Advanced
The following add-ons are available for WinCC Runtime Advanced:
WinCC SmartServer (remote operation)
WinCC Recipes (recipe system)
WinCC Logging (logging of process values and alarms)
WinCC Audit (audit trail for regulated applications)
Note
In contrast to WinCC flexible 2008, functions from the WinCC flexible /Sm@rtService,
WinCC flexible /Sm@rtAccess add-ons as well as the WinCC flexible /OPC Server add-
on are incorporated into the basic functionality.
Add-ons for WinCC Runtime Professional
WinCC Runtime Professional contains the following components, which you can activate with
the appropriate license:
WinCC Server (supplements WinCC Runtime to include server functionality)
WinCC Recipes (recipe system, formerly WinCC /UserArchives)
WinCC Logging (logging system, previously WinCC/TagLogging)
You can select and install the following add-ons in the installation dialog:
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 57
WinCC Client (standard client for building multiple-station systems)
WinCC WebNavigator (Web-based operator control and monitoring)
WinCC DataMonitor (display and evaluation of process states and historical data)
Note
In contrast to WinCC V7, functions from the WinCC / OPC Server add-ons have been
incorporated into the basic functionality. Likewise, the basic functionality includes the
Runtime API from WinCC /ODK.
In addition to the Runtime add-ons, you can also expand WinCC Runtime Professional with
custom controls. The WinCC ControlDevelopment add-on is required to develop controls.
See also
Software and hardware requirements (Page 54)
Installing and uninstalling options (Page 58)
Installing and uninstalling options
Introduction
Some add-ons are included in standard WinCC installation and are installed automatically.
During the installation of WinCC Engineering System, the following add-ons are available for
you to select for installation:
Simulation for WinCC Runtime Advanced
During the installation of WinCC Runtime Advanced, the following add-ons are available for
you to select for installation:
OPC XML Gateway
WinCC Audit Viewer
You must enable all the necessary add-ons for use.
Note
Each add-on requires a license. You activate an add-on by installing the appropriate license
key.
Add-ons for non-PC-based HMI devices
The required Runtime add-ons are installed on the HMI device as follows:
During the transfer of the project to the HMI device
Add-ons that are no longer required are removed automatically.
With ProSave
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
58 System Manual, 08/2011,
Procedure - activating add-ons
To activate an add-on for use, install the appropriate license key using the Automation License
Manager.
In order to backup the license key of an add-on or use it on a different configuration PC or HMI
device, you must uninstall this license key using the Automation License Manager.
NOTICE
When no valid license key is installed on a PC with WinCC Runtime, Runtime runs in Demo
mode.
See also
Options for WinCC Engineering and Runtime systems (Page 56)
3.1.2.3 Licenses and Powerpacks
Licensing of WinCC Engineering System
You require a license key for the following:
WinCC Engineering System, for example, WinCC Professional
Add-ons for WinCC Engineering System
You can install the license key during the installation of WinCC. You transfer the licenses for
WinCC add-ons after installation with the Automation License Manager.
Starting without a valid license key
If you start WinCC without a valid license, the system alerts you that you are working in non-
licensed mode. You have the option of activating a one-time trial license. Trial licenses for
Engineering editions WinCC Basic, Comfort, Advanced und Professional expire after 21 days.
When the trial license expires, the following scenarios can occur:
WinCC was never licensed on the PC in question.
Operations requiring a license can no longer be performed in WinCC.
WinCC was already licensed on the PC in question.
An alert for non-licensed mode is presented every 10 minutes and for every action
requiring a license by a window requiring acknowledgment.
License requirements for simulation
When you want to start simulation in WinCC using the menu command "Online > Simulation>
With tag simulator", you do not need licenses for WinCC Runtime or licensed-based add-ons.
If the following conditions are met, you also need the appropriate licenses for the simulation
of WinCC Runtime and license-based add-ons:
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 59
The engineering station is connected to a PLC.
The connection to the PLC is configured and active.
You start the simulation with the "Online > Simulation > Start" menu command.
See also
Software and hardware requirements (Page 54)
Licensing WinCC Runtime on PC-based HMI devices (Page 60)
Licensing of HMI devices (Page 61)
Working with license keys (Page 62)
Powerpack (Page 65)
Installing a Powerpack (Page 65)
Licensing WinCC Runtime on PC-based HMI devices
With PC-based HMI devices, you require a license key for the following:
WinCC Runtime with 128 tags, for example.
WinCC add-ons
You can install the license key for WinCC Runtime during the installation of WinCC. You
transfer the licenses for WinCC add-ons after installation with the Automation License Manager.
Note
Only the Certificate of License for WinCC Runtime V11 authorizes operation of WinCC
Runtime V11.
The appropriate new license is required to license WinCC Runtime.
You can upgrade the runtime licenses of WinCC flexible 2008 and WinCC V7 with an upgrade
to WinCC Runtime V11.
Productive operation of the software is only allowed with a valid Certificate of License that
matches the version listed on it.
Non-licensed mode
WinCC Runtime and the Runtime add-ons can be used freely without license. An alert for non-
licensed mode is presented every 10 minutes by a window requiring acknowledgment.
See also
Licensing of WinCC Engineering System (Page 59)
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
60 System Manual, 08/2011,
Licensing of HMI devices
Non-PC-based HMI devices are always equipped to maximum capacity. A license key is not
required for runtime operation.
A license is required for each add-on for non-PC-based HMI devices. The license key of the
respective license always activates one instance for use.
License key
To be able to license non-PC-based HMI devices with license keys, you require the "SIMATIC
HMI License Manager Panel Plug-in" add-on.
WinCC Setup installs this add-on by default. You can open the License Manager Panel plug-
in in the Automation License Manager with the menu command "Edit > Connect Target System
> Connect HMI Device".
If WinCC is not installed, an installation of ProSave 7.2 or higher is required.
Note
Further information about handling the licenses can be found in the Automation License
Manager help.
Note
Verify that the current release of the operating system is installed on the HMI device before
you start licensing. If necessary, update the operating system using ProSave.
Data backup
CAUTION
Destruction of license keys on non-PC-based HMI devices
Installed license keys and authorizations are destroyed by the backup/restore processes on
the HMI devices listed below.
270 series
370 series
Carry out the following before beginning restoring:
Use the Automation License Manager and ProSave to check whether license keys are
installed on the HMI device.
Remove any license keys present on the HMI device.
After restoring has been carried out, re-install the license keys on the HMI device.
Non-licensed mode
Runtime add-ons can also be used without a license without restriction. An alert for non-
licensed mode is presented every 10 minutes by a window requiring acknowledgment.
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 61
See also
Licensing of WinCC Engineering System (Page 59)
Working with license keys
Introduction
Install a license key in the following situations:
To use the WinCC Engineering System
To use add-ons for the WinCC Engineering System
To operate WinCC Runtime
To use add-ons for WinCC Runtime on PC-based HMI devices
To use add-ons on non-PC-based HMI Devices
To uninstall a license key in the following cases:
When backing up data
If you no longer require the license
You can then use this license on another PC or HMI device.
When you install a license, the associated license key is removed from the license key storage
location.
Note
A license key cannot be copied. The copy protection employed prevents the license keys
from being copied.
Data backup
Remove the license keys on the HMI device when backing up data on the HMI device and
when creating a backup during device replacement.
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
62 System Manual, 08/2011,
You use the Automation License Manager to back up license keys of a HMI device to the
storage area of the license key.
CAUTION
Destruction of license keys on non-PC-based HMI devices
Installed license keys are destroyed by backup/restore processes on the HMI devices listed
below.
270 series
370 series
Carry out the following before beginning restoring:
Use the Automation License Manager and ProSave to check whether license keys are on
the HMI device.
Remove any license keys present on the HMI device.
After restoring has been carried out, re-install the license keys on the HMI device.
CAUTION
Destruction of license keys on PCs
Start by removing all license keys in the following situations:
Before you format the hard disk
Before you compress the hard disk
Before you restore the hard disk
Starting an optimization program that moves fixed blocks
Installing a new operating system
Read the description of Automation License Manager ("Start > Simatic Automation >
Documentation"). Observe all warnings and notices.
The license key storage location on PC-based HMI devices and on non-PC-based HMI devices
where Automation License Manager is used may contain multiple license keys. This capability
means you can store multiple licenses of the same type at one location. Save all license keys
of the HMI device to the same storage location.
CAUTION
Always keep the original storage location of the license keys.
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 63
Invalid license after time zone change
The installed license no longer functions in the following case.
If you change the time zone on a WinCC PC as follows:
From a time based on a complete hour to a time not based on a complete hour.
Example: You change the time zone from GMT +3:00 to GMT +3:30.
To avoid this inconvenience, uninstall the license key under the time zone setting that was set
when the license key was installed.
Example:
You have installed the license key with a time zone setting based on a full hour. Then also
uninstall the license key with a time zone setting based on a full hour.
This behavior does not apply to the trial license.
Defective license
A license is defective in the following cases:
If the license key is no longer accessible at the storage area.
If the license key disappears during its transfer to the destination drive.
You can use the Automation License Manager to repair the defective license. Use the "Restore"
function or the "Restore Wizard" of the Automation License Manager for this purpose. Contact
Customer Support in order to restore the license. For additional information see: http://
support.automation.siemens.com (http://support.automation.siemens.com)
Note
The runtime software can also be operated without errors if the license is missing or defective.
The system alerts you at brief intervals that you are working in non-licensed mode.
CAUTION
If you start WinCC Engineering System without a valid license key, the system alerts you that
you are working in non-licensed mode. You have the one-time option of activating a trial
license. The trial license expires after 21 days.
When the trial license expires, the following scenarios can occur:
WinCC was never licensed on the PC in question.
WinCC can no longer be started.
WinCC was already licensed on the PC in question.
WinCC cannot be started. An alert for non-licensed mode is presented every 10 minutes
by a window requiring acknowledgment.
See also
Licensing of WinCC Engineering System (Page 59)
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
64 System Manual, 08/2011,
Powerpack
Introduction
The following upgrades are possible with a Powerpack:
From a smaller to a larger edition of WinCC Engineering System
On a runtime system with greater quantity structure
A Powerpack also includes a special license using which you can at any time activate a higher
level of WinCC for use.
Engineering system
You have WinCC Comfort, for example. You can use the "SIMATIC WinCC Advanced
Powerpack WinCC Comfort -> WinCC Advanced V11" Powerpack to activate
WinCC Advanced for use.
Runtime
You own WinCC Runtime Advanced with 128 tags, for example. You can use the "SIMATIC
WinCC Runtime Advanced Powerpack 128 PowerTags -> 512 PowerTags V11" Powerpack
to increase the capacity from 128 to 512 tags.
You own WinCC Runtime Advanced with 128 tags, for example. You can use the "SIMATIC
WinCC Runtime Professional Powerpack Runtime Advanced 128 PowerTags -> Runtime
Professional 128 PowerTags V11" Powerpack to activate WinCC Runtime Professional with
128 tags for use.
See also
Licensing of WinCC Engineering System (Page 59)
Installing a Powerpack
Introduction
Install a Powerpack by transferring the corresponding license key. The Powerpack license key
replaces the license key of an existing installation.
Requirement
The conditions described in the "System requirements" chapter must be fulfilled.
WinCC has been installed.
The license key for the license for which you have purchased a Powerpack is available on
the PC.
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 65
Installing a Powerpack
1. Transfer the purchased Powerpack license key using the Automation License Manager.
Result
The Powerpack license key replaces the former license key. You cannot reverse this process.
See also
Licensing of WinCC Engineering System (Page 59)
Installation
3.1 System requirements for installation
WinCC Advanced V11.0 SP1
66 System Manual, 08/2011,
3.2 Licenses
Availability of licenses
The licenses for the products of the TIA Portal are usually supplied on the installation data
medium and installed automatically by the Automation Licence Manager during the installation
process of the TIA Portal.
If you remove the TIA Portal, the corresponding licenses are also removed automatically.
Licenses still required should be secured.
Provision of the Automation License Manager
The Automation License Manager is supplied on the installation data medium and is
transferred automatically during the installation process.
If you remove the TIA Portal, the Automation License Manager remains installed on your
system.
Working with the Automation License Manager
The Automation License Manager is a product of Siemens AG, which is used for handling
license keys (technical representatives of licenses).
Software products that require license keys for operation, such as the TIA-Portal, register the
required license key automatically with the Automation License Manager . If the Automation
License Manager finds a valid license key for this software, the software can be used according
to the license usage terms associated with this license key.
Note
For additional information on how to manage your licenses with the Automation License
Manager , refer to the documentation supplied with the Automation License Manager .
See also
Notes on the system requirements (Page 53)
Starting installation (Page 69)
Displaying the installed software (Page 72)
Modifying or updating installed products (Page 73)
Repairing installed products (Page 75)
Starting to uninstall (Page 77)
Installation log (Page 68)
Installation
3.2 Licenses
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 67
3.3 Installation log
Function of the installation log
The progress during the following installation processes is logged in a file:
Installing products
Modifying or updating already installed products
Repairing an existing installation
Uninstalling products
If errors occur during the installation process or warnings are issued, these can be evaluated
with the help of the log file. You can do this yourself or contact product support.
Installation logs storage location
The log file is the most recent file with the file extension ".log" and whose name begins with
"SIA", e.g. "SIA_STEP7_PRO_V11.log".
The location of the log file is stored in the environment variable "%autinstlog%". You can enter
this environment variable in the address bar of Windows Explorer to open the folder with the
log files. Alternatively, you can navigate to the corresponding directory by entering "CD
%autinstlog%" in the command line.
The location depends on the operating system, e.g. "C:\Documents and Settings\All Users
\Application Data\Siemens\Automation\Logfiles\Setup" in the English version of Windows XP.
Setup_Report (CAB file)
To make it easier to provide Product Support with all necessary files, an archive file that
contains the installation log and all other required files is saved in CAB format. This archive
can be found at "%autinstlog%\Reports\Setup_report.cab". Send this CAB file to Product
Support if you need assistance with installation. With this information, Product Support can
determine whether the installation was executed properly. CAB files that were generated
during earlier installation processes are saved with a date ID in the "Reports" directory.
See also
Licenses (Page 67)
Starting installation (Page 69)
Installing Support Packages (Page 71)
Displaying the installed software (Page 72)
Modifying or updating installed products (Page 73)
Repairing installed products (Page 75)
Starting to uninstall (Page 77)
Installation
3.3 Installation log
WinCC Advanced V11.0 SP1
68 System Manual, 08/2011,
3.4 Starting installation
Introduction
Software packages are installed automatically by the setup program. The setup program starts
once the installation medium has been inserted in the drive.
Requirement
Hardware and software of the programming device or PC meet the system requirements.
You have administrator privileges on your computer.
All running programs are closed.
Procedure
To install the software packages, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking
the "Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the product languages opens.
6. Select the languages for the product user interface, and click the "Next" button.
Note
"English" is always installed as the basic product language.
The dialog for selecting the product configuration opens.
7. Select the products you want to install:
If you wish to install the program in a minimal configuration, click on the "Minimal" button.
If you wish to install the program in a typical configuration, click on the "Typical" button.
If you wish to personally select the products to be installed, click on the "User-defined"
button. Then select the check boxes for the products you wish to install.
8. If you want to create a shortcut on the desktop, select the "Create desktop shortcut" check
box.
9. Click the "Browse" button if you want to change the target directory for the installation. Note
that the length of the installation path must not exceed 89 characters.
Installation
3.4 Starting installation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 69
10.Click the "Next" button.
The dialog for the license terms opens.
11.To continue the installation, read and accept all license agreements and click "Next".
If changes to the security and permissions settings are required in order to install the TIA
Portal, the security settings dialog opens.
12.To continue the installation, accept the changes to the security and permissions settings,
and click the "Next" button.
The next dialog displays an overview of the installation settings.
13.Check the selected installation settings. If you want to make any changes, click the "Back"
button until you reach the point in the dialog where you want to make changes. Once you
have completed the desired changes, return to the overview by clicking on "Next".
14.Click the "Install" button.
Installation is started.
Note
If no license key is found during installation, you have the chance to transfer it to your PC.
If you skip the license transfer, you can register it later with the Automation License
Manager.
If the installation was successful, a message to this effect is displayed on the screen. If
errors occurred during installation, an error message is displayed informing you of the
type of errors.
15.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
16.If the computer does not reboot, click "Exit".
Result
The TIA Portal along with the products and licenses you have ordered and the Automation
License Manager have been installed on your computer.
See also
Installation log (Page 68)
Notes on the system requirements (Page 53)
Licenses (Page 67)
Displaying the installed software (Page 72)
Modifying or updating installed products (Page 73)
Repairing installed products (Page 75)
Starting to uninstall (Page 77)
Installation
3.4 Starting installation
WinCC Advanced V11.0 SP1
70 System Manual, 08/2011,
3.5 Installing Support Packages
You can install subsequent support packages, for example, hardware support packages, in
the TIA Portal.
Note
Support packages for STEP7 V5.4 or V5.5 cannot be used.
Procedure
To install a Support Package, follow these steps:
1. Click "Support packages" in the "Options" menu.
The "Detailed information" dialog opens. A table lists all support packages from the directory
that you selected as the storage location for support packages in the settings.
2. If you want to install a support package that is not in the list, you have the following options:
If the support package is already on your computer, you can add it to the list by selecting
"Add from the file system".
If you add a support package from the "Service & Support" page on the Internet, first
you download it by selecting "Download from the Internet". Then you can add it from
the file system.
3. Select the support package that you want to install.
4. Click "Install."
5. Close and then restart the TIA Portal.
See also
Installation log (Page 68)
Installation
3.5 Installing Support Packages
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 71
3.6 Displaying the installed software
You can find out which software is installed at any time. In addition, you can request additional
information on the installed automation software to be displayed.
Procedure
To display an overview of the software installed, follow these steps:
1. Click "Installed software" in the "Help" menu.
The "Installed software" dialog opens. You will see the installed software products in the
dialog. Expand the entries to see which version is installed in each case.
2. If you would like to display additional information on the installed automation software, click
the link on the "Detailed information about installed software" dialog.
The "Detailed information" dialog opens.
3. Chose the topic you want more information about in the area navigation.
See also
Notes on the system requirements (Page 53)
Licenses (Page 67)
Starting installation (Page 69)
Modifying or updating installed products (Page 73)
Repairing installed products (Page 75)
Starting to uninstall (Page 77)
Installation log (Page 68)
Installation
3.6 Displaying the installed software
WinCC Advanced V11.0 SP1
72 System Manual, 08/2011,
3.7 Modifying or updating installed products
You have the option to modify installed products using the setup program or to update to a
new version.
Requirement
Hardware and software of the programming device or PC meet the system requirements.
You have administrator privileges on your computer.
All running programs are closed.
Procedure
To modify or update installed products, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking
the "Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the installation variant opens.
6. Select the "Modify/Upgrade" option button and click the "Next" button.
The dialog for selecting the product languages opens.
7. Select the check boxes of the product languages that you want to install. You can remove
previously installed product languages by clearing the corresponding check boxes.
Note
Note that the product language "English" cannot be removed.
8. Click the "Next" button.
The dialog for selecting the product configuration opens.
9. Select the check boxes of the components that you want to install. You can remove
previously installed components by clearing the corresponding check boxes.
Installation
3.7 Modifying or updating installed products
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 73
10.Click the "Next" button.
Note
Note that you cannot change the target directory because the existing installation is being
modified.
If changes to the security and permissions settings are required in order to install the TIA
Portal, the security settings dialog opens.
11.To continue the installation, accept the changes to the security and permissions settings,
and click the "Next" button.
The next dialog displays an overview of the installation settings.
12.Click the "Modify" button.
This starts the installation of the additional components.
Note
If the installation was successful, a message to this effect is displayed on the screen. If
errors occurred during installation, an error message is displayed informing you of the
type of errors.
13.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
14.If the computer does not reboot, click "Exit".
Result
The existing installation has been modified on your computer.
See also
Notes on the system requirements (Page 53)
Licenses (Page 67)
Starting installation (Page 69)
Displaying the installed software (Page 72)
Repairing installed products (Page 75)
Starting to uninstall (Page 77)
Installation log (Page 68)
Installation
3.7 Modifying or updating installed products
WinCC Advanced V11.0 SP1
74 System Manual, 08/2011,
3.8 Repairing installed products
You have the option to repair installed products by completely reinstalling them using the setup
program.
Requirement
Hardware and software of the programming device or PC meet the system requirements.
You have administrator privileges on your computer.
All running programs are closed.
Procedure
To repair installed products, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking
the "Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the installation variant opens.
6. Select the "Repair" option button, and click the "Next" button.
The next dialog displays an overview of the installation settings.
7. Click the "Repair" button.
This starts the repair of the existing installation.
Note
If the installation was successful, a message to this effect is displayed on the screen. If
errors occurred during installation, an error message is displayed informing you of the
type of errors.
8. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
9. If the computer does not reboot, click "Exit".
Result
The installed products have been reinstalled.
Installation
3.8 Repairing installed products
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 75
See also
Notes on the system requirements (Page 53)
Licenses (Page 67)
Starting installation (Page 69)
Displaying the installed software (Page 72)
Modifying or updating installed products (Page 73)
Starting to uninstall (Page 77)
Installation log (Page 68)
Installation
3.8 Repairing installed products
WinCC Advanced V11.0 SP1
76 System Manual, 08/2011,
3.9 Starting to uninstall
Introduction
Software packages are removed automatically by the setup program. Once started, the setup
program guides you step-by-step through the entire removal procedure.
You have two options for removing:
Removing selected components via the Control Panel
Removing a product using the installation medium
Note
The Automation License Manager will not be removed automatically when you remove the
software packages, because it is used for the administration of several license keys for
products supplied by Siemens AG.
Removing selected components via the Control Panel
To remove selected software packages, follow these steps:
1. Open the Control Panel with "Start > Settings > Control Panel".
2. Double click on "Add or Remove Programs" in the control panel.
The "Add or Remove Programs" dialog opens.
3. Select the software package to be removed in the dialog "Add or Remove Programs", and
click "Remove".
The dialog for selecting the setup language opens.
4. Select the language in which you want the setup program dialogs to be displayed and click
the "Next" button.
The dialog for selecting the products you want to remove opens.
5. Select the check boxes for the products that you want to remove and click the "Next" button.
The next dialog displays an overview of the installation settings.
6. Check the list with the products to be removed. If you want to make any changes, click the
"Back" button.
7. Click the "Uninstall" button.
Removal begins.
8. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
9. If the computer does not reboot, click "Exit".
Installation
3.9 Starting to uninstall
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 77
Removing a product using the installation medium
To remove all software packages, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking
the "Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the installation variant opens.
6. Select the "Uninstall" option button and click the "Next" button.
The next dialog displays an overview of the installation settings.
7. Click the "Uninstall" button.
Removal begins.
8. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
9. If the computer does not reboot, click "Exit".
See also
Installation log (Page 68)
Notes on the system requirements (Page 53)
Licenses (Page 67)
Starting installation (Page 69)
Displaying the installed software (Page 72)
Modifying or updating installed products (Page 73)
Repairing installed products (Page 75)
Installation
3.9 Starting to uninstall
WinCC Advanced V11.0 SP1
78 System Manual, 08/2011,
3.10 Installing and uninstalling the migration tool
3.10.1 System requirements
System requirements for the migration tool
The following system requirements apply to the use of the migration tool:
All products used to create the source project must be installed. The following products are
supported:
SIMATIC STEP 7 V5.4 SP5 and STEP 7 V5.5
WinCC V7 SP1 or V7 SP2
WinCC flexible V1.3 SP2
All optional packages needed to process the STEP 7 project are installed. For example, all
HSPs for the devices used in the source project are required.
3.10.2 Installing the migration tool
Distribution of the migration tool
The migration tool is available for download from the Service & Support area of the Siemens
website.
Normally, the migration tool is installed without the TIA Portal. Because the TIA Portal has its
own integrated migration function, a separate installation of the migration tool is not necessary.
Procedure
To install the migration tool, proceed as follows:
1. Download the installation file from the Service & Support area on the Siemens website.
2. Run the downloaded file.
The setup program for the migration tool will open.
3. First, select the language in which the setup should be displayed and click the "Next" button.
The page for selecting the software language is displayed.
4. Since the migration tool is provided exclusively in English, you cannot choose any other
language for the installation. Therefore, click "Next" to proceed to the next step.
The page for selecting the product is displayed.
5. The migration tool consists solely of a software component. Therefore, the migration tool
is already selected.
To create a Desktop icon for starting the migration tool, select the check box "Create
Desktop icon". Then click the "Next" button.
The page for confirming the licensing terms is shown.
Installation
3.10 Installing and uninstalling the migration tool
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 79
6. Click on an entry in the list of license terms to read the selected license term. If you agree
with all license terms, select the check box "I accept the terms of the displayed license
agreement". Then click the "Next" button.
An overview of the installation is displayed.
7. Click the "Install" button.
The installation is performed with the displayed settings.
3.10.3 Uninstalling the migration tool
The migration tool can be removed using the Control Panel.
Procedure
To remove the migration tool, follow these steps:
1. Open the Control Panel.
2. Double click on "Add or Remove Programs" in the Control Panel.
The "Add or Remove Programs" dialog opens.
3. Select the "TIA Portal Migration Tool V11" entry in the "Add or Remove Programs" dialog,
and click the "Remove" button.
A confirmation prompt appears.
4. Click the "Uninstall" button to confirm this prompt.
The migration tool will be removed.
Installation
3.10 Installing and uninstalling the migration tool
WinCC Advanced V11.0 SP1
80 System Manual, 08/2011,
Migrating projects
4
4.1 Migrating projects
Migration of existing projects
You can migrate projects from earlier automation solutions to the TIA Portal. Each time you
migrate, a new project is created for the migrated data with which you can then work. Any
projects already open are closed first.
The migration is then displayed in the table of the project history. From here, you have access
to a log file that is created automatically for the migration.
Supported products for migration
The chapter "System overview STEP 7 and WinCC" includes information on the products that
are available for the TIA Portal. In principle, all products listed there are supported by the TIA
Portal during migration.
Any additional requirements that must be met depend on the initial products that were used
and the currently installed products. For more information on the migration options for your
products, you can, for example, refer to the Service & Support Internet pages and the
documentation of your software products.
See also: Scaling of STEP 7 and WinCC (Page 21)
Procedure during migration
The migration process is divided into the following basic steps:
1. Preparing the initial project
If the software that was used to create the initial project is not installed or is only partly
installed on the programming device/PC together with the TIA Portal installation, you first
need to convert the project to a special migration format with the file extension "AM11". To
do this, install the migration tool on a PG/PC on which the required software is installed.
Then, use the migration tool to convert the initial project, and copy the file to the
programming device/PC on which the TIA Portal is installed.
You can omit this step if the initial project and its associated software are on the same
programming device/PC as the TIA Portal. In this case, you can directly migrate the source
project.
2. Performing migration
You perform the actual migration within the TIA Portal.
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 81
3. Checking the migration log
A log is created for each migration, in which the result of the migration is stored. In this log,
you can find information on project components that have been lost or modified, or, when
applicable, the reasons why the migration of a project could not be performed. Check this
log after migration. Immediately after completion of the migration, the log is displayed in
the Inspector window. You can also open the log from the project history. If a migration is
not possible, you can decide where the log will be saved.
4. Correcting the migrated project
Because the configurations of the initial project may not always be completely compatible
with the TIA Portal, not all configurations are transferred in identical form in the migrated
project. You should therefore work through the points in the migration log systematically.
Excluding the hardware configuration from the migration
If you know at the outset that hardware used in the initial project is not supported by the TIA
Portal, you can exclude the hardware configuration from the migration. In this case, only the
software is migrated.
An unspecified device is then generated in the migrated project for the devices contained in
the initial project. The hardware and network configurations and the connection are not
migrated. You can convert the unspecified devices into suitable devices after the migration
and create any network configurations and connections manually.
See also
Displaying the log file of the migration (Page 89)
Scaling of STEP 7 and WinCC (Page 21)
Migrating projects
4.1 Migrating projects
WinCC Advanced V11.0 SP1
82 System Manual, 08/2011,
4.2 Preparing projects with the migration tool
4.2.1 Migrating projects with the migration tool
Preparation for migration
In many cases, a project you want to migrate is not located on the same programming device/
PC on which the TIA Portal V11 is installed. Therefore, the initial project must first be converted
to a compatible format for the migration. You then copy the migration file to the programming
device or PC on which the current version of the TIA Portal is installed. There you can then
read the file into the TIA Portal and create a project in the current file format of the TIA Portal.
Procedure for migration with the migration tool
To perform a migration without the initial software, the following preparatory steps are
necessary:
1. Install the migration tool on the programming device/PC where the source project is located.
To do this, download the installation file from the Service & Support area on the Siemens
website.
2. Start the migration tool and use it to convert the source project to the migration file format
with file extension ".ap11".
For this step, make sure that all software needed to process the source project is installed
on the programming device/PC. This also includes all necessary service packs, hardware
support packages and all expansion software that is needed to process the initial project.
If individual products are not installed it may not be possible to perform the migration or the
migration may be incomplete.
3. Copy the migration file to the target system on which a current version of the TIA Portal is
installed.
Note that the target system must have been installed with all software needed to configure
the complete set of devices contained in the migration.
4. Perform the migration within the TIA Portal, and specify the migration file as the source.
5. Following the migration, check the log file and work through the information provided there
for the newly created project in a systematic manner. Read the information in the Inspector
window with special care after the first compilation of the configuration.
Excluding the hardware configuration from the migration
If you know at the outset that hardware used in the initial project is not supported by the TIA
Portal, you can exclude the hardware configuration from the migration. In this case, only the
software is migrated.
An unspecified device is then generated in the migrated project for the devices contained in
the initial project. The hardware and network configurations and the connection are not
migrated. You can convert the unspecified devices into suitable devices after the migration
and create any network configurations and connections manually.
Migrating projects
4.2 Preparing projects with the migration tool
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 83
See also
Migrating projects (Page 81)
Migrating projects (Page 86)
Calling the migration tool (Page 84)
Creating a migration file (Page 84)
4.2.2 Calling the migration tool
Starting the migration tool
A "Migration to TIA Portal V11" shortcut is always created during the installation in Start menu
under "Siemens Automation > Migration Tool". Click this shortcut.
Alternatively, you can call the migration tool directly in Windows Explorer. The migration tool
is saved to the following default folder during installation: "C:\Program Files\Siemens
\Automation\Portal V11\Mig\bin". To start the migration tool, click the
"Siemens.Automation.MigrationApplication.exe" file in this directory.
See also
Creating a migration file (Page 84)
4.2.3 Creating a migration file
The section below describes how you can use the migration tool to convert the initial project
into a migration file that can be read by the TIA Portal. Following conversion, this file is
transferred to the target system and migrated there.
You can specify whether the migration file should contain the entire project, including the
complete hardware configuration and the associated software, or whether you want to migrate
the software only.
Requirement
The suitable, original software with a valid license is installed for all configurations used in
the initial project.
The initial project is not provided with access protection.
The initial project must be consistent, otherwise problem-free migration cannot be assured.
Migrating projects
4.2 Preparing projects with the migration tool
WinCC Advanced V11.0 SP1
84 System Manual, 08/2011,
Procedure
To create the migration file, follow these steps:
1. Choose the path of the source file for the migration in the "Storage Location (Path)" field.
2. Select the check box "Exclude hardware configuration" to migrate the software only.
3. Choose the path and the file name for the migration file in the "Intermediate file".
4. Click the "Migrate" button.
Result:
A migration file is created. Finally, copy this file to the target system and migrate this file in the
TIA Portal.
See also
Migrating projects (Page 86)
Calling the migration tool (Page 84)
Migrating projects with the migration tool (Page 83)
Migrating projects
4.2 Preparing projects with the migration tool
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 85
4.3 Migrating projects
Requirement
There is already a converted file in the format AM11 available or the original software with
a valid license is installed for all the configurations in the initial project.
The initial project is not provided with access protection.
The initial project must be consistent, otherwise problem-free migration cannot be assured.
Read the additional information on the requirements in the help for the respective products
installed.
Note
System hibernation during the migration
While a migration is running, the system should not be changed to the standby or hibernate
mode. Otherwise the migration will be aborted.
Procedure
To migrate a project, follow these steps:
1. Select the "Migrate project" command in the "Project" menu.
The "Migrate project" dialog opens.
2. Specify the path and the file name for the project to be migrated in the "Source path" field.
Choose either a project in the AM11 migration format or in the format of the initial project.
3. Select the check box "Exclude hardware configuration" to migrate the software only.
If you have selected a migration file that was created using the migration tool, the check
box is disabled. In this case, you must specify if you wish to exclude the hardware
configuration of the migration before the conversion with the migration tool .
4. Choose a name for the new project in the "Project name" box.
5. Choose a path in the "Target path" box where the new project will be created.
6. Enter your name or the name of another person responsible for the project in the "Author"
field.
7. Enter a comment in the "Comment" box, if you require one.
8. Click "Migrate".
Result
The initial project is converted. The system outputs a message when the migration is complete.
From here, you can directly open a log for the migration. The newly created project then opens
in the project view. The migration log is also displayed in the Inspector window.
Migrating projects
4.3 Migrating projects
WinCC Advanced V11.0 SP1
86 System Manual, 08/2011,
See also
Post-editing integrated projects (Page 138)
Migrating projects with the migration tool (Page 83)
Creating a migration file (Page 84)
Migrating projects
4.3 Migrating projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 87
4.4 Displaying the history of the migration
If a project was created by migration, the migration will be listed in the table of the project
history. You can open the migration log in the table. The time of the migration is also shown.
Procedure
To display the migration in an overview table, follow these steps:
1. Select the open project in the project tree.
2. Select "Properties" in the shortcut menu of the project.
The dialog with the properties of the project opens.
3. Select the "Project history" group in the area navigation.
The overview table is displayed.
See also
Displaying properties of the project (Page 191)
Migrating projects
4.4 Displaying the history of the migration
WinCC Advanced V11.0 SP1
88 System Manual, 08/2011,
4.5 Displaying the log file of the migration
A log file is created for each migration. The log file contains the following information:
Migrated objects
Modifications to objects made during migration
Errors that occurred during migration
Procedure
To display the log file of the migration, follow these steps:
1. Select the open project in the project tree.
2. Select "Properties" in the shortcut menu of the project.
The dialog with the properties of the project opens.
3. Select the "Project history" group in the area navigation.
The overview table is displayed.
4. Click on the link to the log file in the "Log file" column.
The log file is displayed in the Microsoft Internet Explorer.
See also
Migrating projects (Page 81)
Migrating projects
4.5 Displaying the log file of the migration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 89
4.6 Migrating WinCC flexible projects (Advanced)
4.6.1 Principles (WinCC flexible)
4.6.1.1 Migration (WinCC flexible)
Introduction
You can continue to use projects in WinCC from WinCC flexible. The following version of
WinCC flexible is supported:
WinCC flexible 2008 SP2
The following sections describe the HMI devices that are supported and the required basic
conditions for a successful migration.
Projects from ProTool Pro and earlier WinCC flexible versions cannot be migrated directly to
WinCC. If you want to continue using such projects in WinCC, you have to migrate these to a
supported version of WinCC flexible first and change the HMI device type.
If the project to be migrated contains components of a supported option package, the option
package must be installed for successful migration to WinCC. If the option package is not
installed, migration is canceled. This concerns the following option packages:
SINUMERIK
The following option packages are not supported by the migration:
ProAgent
Open Platform Program - OPP
See also
Migrating projects from WinCC flexible (WinCC flexible) (Page 92)
Compiling and loading a migrated project (WinCC flexible) (Page 94)
Supported HMI devices (WinCC flexible) (Page 95)
Migration of connections (WinCC flexible) (Page 103)
Migration of tags (WinCC flexible) (Page 106)
Migration of runtime data (WinCC flexible) (Page 115)
Migration of integrated projects (WinCC flexible) (Page 118)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
90 System Manual, 08/2011,
4.6.1.2 Migration principles (WinCC flexible)
Introduction
In the migration the project data are converted from a WinCC flexible project into the new data
format of WinCC. The data will not be evaluated to see if they are consistent in the project you
want to migrate. If errors or warnings are output in a source project during compilation, these
will not be resolved as part of the migration. This means you should be able to compile the
project without errors prior to migration. Note the scope of a project during migration. The
features of WinCC apply for migration. See Engineering system (Page 2512) for additional
information.
Unique object names
The objects are clearly identified by the folders in which they are contained in WinCC flexible.
Screen objects in groups are clearly identified by the group name.
In WinCC, an object name must be unique within an HMI device. The name of screen objects
must be unique within a screen.
The uniqueness of the name is verified during migration. If a name is not unique according to
the new rule, the object in question will be renamed. A renamed object will receive the suffix
"#Mign", where "n" stands for a sequential number.
Points to note when renaming tags
If you have structured tags in folders in WinCC flexible, the name of the tag will be formed
during migration from the folder name and the tag name. The names of the folders and tags
are separated by the character \. The name of the tag after migration is then, for example:
Plant1\Line3\Tag17.
If the name would otherwise be longer than 128 characters after migration, the name is formed
by the character string #mig, a consecutive number, the character # and the tag name from
WinCC flexible, for example #mig2#Tag17.
If you dynamically compose tag names in scripts, you must check the tags whose names were
changed during migration with "#mig".
Affected objects
The following objects are renamed if necessary:
Screens
Faceplates
Screen objects
Graphics
Recipes
Structures
Structural elements
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 91
Alarm logs
Tags
Data logs
Connections
Cancelling migration
The migration is cancelled in the following cases:
If the project to be migrated is opened in the engineering system or in Runtime.
If not enough memory space is available on the hard disk to create a a copy for migration
of the project.
If the migration cannot address the project database due to problems with the installed SQL-
Server.
If the migration cannot address the project database due to missing user authorization.
If you select the "*.hmi" file for the migration in an integrated project. You must select the
"*.s7" file for the migration in an integrated project.
If the project was created with a version not supported by the migration.
Saving the project in the migration format
You do not have to execute the migration of a WinCC flexible project completely on the PC on
which the project is available. You can prepare the migration by saving the project in the
migration format. The migration tool is available for saving a WinCC flexible project in the
migration format. The migration tool exports the engineering data from the WinCC flexible
project and saves the data in the migration format "*.AM11".
For the actual migration, copy the data in the migration format to a PC on which the TIA-Portal
is installed.
For more detailed information, please refer to the migration tool documentation.
See also
Engineering system (Page 2512)
4.6.1.3 Migrating projects from WinCC flexible (WinCC flexible)
Introduction
When you migrate a project, data from a WinCC flexible project is loaded into a new project
for WinCC. A new project is therefore created automatically for project migration. You cannot
migrate to an existing project.
The migration can be started in both the Portal view and the Project view.
You should only migrate a project in a newly started TIA portal.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
92 System Manual, 08/2011,
Information on the migration of integrated project can be found in the Chapter Migration of
integrated projects (WinCC flexible) (Page 118).
If you only want to save the project in migration format, you can use the migration tool. See
Migration principles (WinCC flexible) (Page 91) for additional information.
Requirement
A project from WinCC flexible is available.
The project is not open in WinCC flexible.
The TIA portal is newly started.
Procedure
Migrate a project in the Portal view as follows:
1. Select the action "Start > Migrate Project".
2. In the "Source path" box, navigate to the project you want to migrate.
3. Select the WinCC flexible project file "*.hmi".
4. Change the information for the project to be created, if necessary. For example, change
the project name or project path. The data to be migrated is created in the new project.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 93
5. Click "Migrate".
A new project is created and migration of the data is started:
The Project view opens.
The progress of the migration is shown in a migration window.
Warnings and errors about the migration process are displayed in the Inspector window
under "Info > General".
All information about the migration is saved in a log file.
A message is displayed upon completion of the migration. The message contains a link
that you can use to open the log.
6. Once migration is completed, save the project.
When migration is complete, you will find a newly created device for each migrated HMI device
in the project tree. These devices contain the migrated data, such as screens, alarms and tags.
Opening the migration log at a later point in time
The migration log is saved together with the migrated project. You can view the log at a later
point in time. Open the log as follows:
1. Select the project in the project tree.
2. Select the "Properties" command in the shortcut menu.
3. Click "Project History" in the "Properties" dialog.
4. Click on the log file.
The migration log opens.
See also
Migration (WinCC flexible) (Page 90)
Migration of integrated projects (WinCC flexible) (Page 118)
Migration principles (WinCC flexible) (Page 91)
4.6.1.4 Compiling and loading a migrated project (WinCC flexible)
Compiling a migrated project
Once you have successfully migrated a WinCC flexible project, you need to recompile it before
loading it to the HMI device. The project will only compile successfully if it was capable of error-
free compiling prior to migration.
If errors occur during compilation of the migrated project, they have to be eliminated.
Once compiling is successfully completed, load the project to the HMI device.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
94 System Manual, 08/2011,
Settings for download to the HMI device
The settings for loading the HMI device are not included in the migration. Once you have
migrated the project, you must configure the settings for loading.
Select the HMI device in the project tree and select "Loading in device > Software (complete
loading)" from the shortcut menu.The dialog "Advanced Loading" is opened. Configure the
required settings for the interface. Click the "Load" button. The project is recompiled and the
dialog "Load preview" is opened.
Expand the "Overwrite" entry and verify the settings for the following options:
Would you like to overwrite the existing user administration data from this device
Would you like to overwrite the existing recipe data on HMI system
Configure the options as you want to use them in the project in the future. Subsequently, load
the project to the HMI device.
See also
Migration (WinCC flexible) (Page 90)
4.6.2 Migrating engineering data (WinCC flexible)
4.6.2.1 HMI devices (WinCC flexible)
Supported HMI devices (WinCC flexible)
Introduction
When migrating projects from WinCC flexible you must bear in mind that WinCC does not
support all HMI devices. You have to distinguish between the following cases:
HMI device is supported by WinCC.
The project is migrated 1:1 and gets the same HMI device after migration as before
migration.
The HMI device is replaced by a compatible successor model.
The project is migrated. The migration replaces the HMI device with a compatible successor
model. See HMI device change as a result of migration (WinCC flexible) (Page 98) for
additional information.
HMI device is not supported.
If your WinCC flexible project contains an HMI device that is not supported by WinCC, the
migration process is cancelled. To migrate the project, you must change the HMI device in
WinCC flexible to a HMI device type supported by WinCC.
The following HMI device types are supported both by WinCC flexible and WinCC:
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 95
Basic Panels
KTP400 Basic mono PN
KTP400 Basic mono PN Portrait
KTP600 Basic DP
KTP600 Basic DP Portrait
KTP600 Basic PN
KTP600 Basic PN Portrait
KTP600 Basic mono PN
KTP600 Basic mono PN Portrait
KTP1000 Basic DP
KTP1000 Basic PN
TP1500 Basic PN
Mobile Panels
Mobile Panel 177 6'' DP
Mobile Panel 177 6'' PN
Mobile Panel 277 8''
Mobile Panel 277 8'' IWLAN V2
Mobile Panel 277F 8'' IWLAN V2
Mobile Panel 277F 8'' IWLAN (RFID Tag)
Mobile Panel 277 10''
Panels
OP 73
OP 77A
OP 77B
OP 177B 6'' mono
OP 177B 6'' color PN/DP
TP 177B 4'' color PN/DP
TP 177A
TP 177A Portrait
TP 177B 6'' mono DP
TP 177B 6'' color PN/DP
OP 277 6''
TP 277 6''
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
96 System Manual, 08/2011,
Multi Panels
MP 177 6'' Touch
MP 277 8'' Key
MP 277 8'' Touch
MP 277 10'' Key
MP 277 10'' Touch
MP 377 12'' Key
MP 377 12'' Touch
MP 377 15'' Touch
MP 377 19'' Touch
Sinumerik PC
OP 010 Key
OP 012 Key
OP 015 Key
OP 015A Key
TP 015A Touch+Key
HMI applications
WinCC flexible Runtime
WinCC only supports the functions provided by these HMI device types.
Other functions which are not migrated because of the restricted device selection are
documented in the following sections.
Adaptations before migration
If the HMI device was changed to an HMI device with a different screen size in the project to
be migrated, you must recompile and save the project in WinCC flexible before the migration.
The compilation process will adjust the size of the screens and screen elements.
See also
Migration (WinCC flexible) (Page 90)
HMI device change as a result of migration (WinCC flexible) (Page 98)
Configuration change after HMI device change (WinCC flexible) (Page 99)
Migration of connections (WinCC flexible) (Page 103)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 97
HMI device change as a result of migration (WinCC flexible)
Introduction
WinCC flexible supports some HMI devices which are discontinued in the future. These HMI
devices are no longer supported by WinCC. When migrating a WinCC flexible project, an HMI
device that is not supported is replaced by a compatible successor device.
Only the HMI device type is changed during the migration. HMI device-specific data are not
changed by the migration.
Inconsistencies in the project may occur due to a change in the HMI device. In a project which
was compilable before the migration, errors may occur in the project compilation after changing
the HMI device. E.g. because the changed HMI device supports different memory media to
the previous HMI device.
HMI device change by the migration
The following table provides information about which successors replace the HMI devices that
are not supported.
Unsupported HMI devices Successors
Mobile Panel 170 6'' Mobile Panel 177 6'' DP
Mobile Panel 277 8'' IWLAN Mobile Panel 277 8'' IWLAN V2
Mobile Panel 277F 8'' IWLAN Mobile Panel 277F 8'' IWLAN V2
OP 170B 6'' mono OP 177B 6'' color PN/DP
TP 170A 6'' TP 177A 6''
TP 170B 6'' mono TP 177B 6'' color PN/DP
TP 170B 6'' color TP 177B 6'' color PN/DP
OP 270 6'' OP 277 6''
OP270 10'' MP 277 10'' Key
TP 270 6'' TP 277 6''
TP 270 10'' MP 277 10'' Touch
MP 270 6'' Touch TP 277 6''
MP 270 10'' Key MP 277 10'' Key
MP 270 10'' Touch MP 277 10'' Touch
MP 370 12'' Key MP 377 12'' Key
MP 370 12'' Touch MP 377 12'' Touch
MP 370 15'' Touch MP 377 15'' Touch
PC 477 12'' Key PC 477B 12'' Key PB
PC 477 12'' Touch PC 477B 12'' Touch PB
PC 477 15'' Key PC 477B 15'' Key PB
PC 477 15'' Touch PC 477B 15'' Touch PB
PC 477 19'' Touch PC 477B 19'' Touch PB
PC 577 12'' Key IPC 577C 12'' Key PB
PC 577 12'' Touch IPC 577C 12'' Touch PB
PC 577 15'' Key IPC 577C 15'' Key PB
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
98 System Manual, 08/2011,
Unsupported HMI devices Successors
PC 577 15'' Touch IPC 577C 15'' Touch PB
PC 577 19'' Touch IPC 577C 19'' Touch PB
PC 670 12'' Key PC 677B 12'' Key PB
PC 670 12'' Touch PC 677B 12'' Touch PB
PC 670 15'' Key PC 677B 15'' Key PB
PC 670 15'' Touch PC 677B 15'' Touch PB
PC 677 12'' Key PC 677B 12'' Key PB
PC 677 12'' Touch PC 677B 12'' Touch PB
PC 677 15'' Key PC 677B 15'' Key PB
PC 677 15'' Touch PC 677B 15'' Touch PB
PC 677 17'' Touch PC 677B 17'' Touch PB
PC 677 19'' Touch PC 677B 19'' Touch PB
HMI device change by the user
If a project contains an HMI device that is not supported by WinCC and no compatible
successor model exists, the migration is cancelled. If you want to migrate the project, you must
change the HMI device to WinCC yourself before the migration. Use an HMI device which is
supported both by WinCC flexible and WinCC for this.
See also
Supported HMI devices (WinCC flexible) (Page 95)
Configuration change after HMI device change (WinCC flexible)
HMI device change by the migration
If the migration makes an HMI device change, it replaces the existing HMI device with a
compatible successor model. The successor models are further developed and therefore more
efficient than their predecessors. The new models therefore support all the properties of their
predecessors. Therefore only a little rework is to be expected on the project due to the HMI
device change.
HMI device change by the user
if you change an HMI device yourself before the migration, you must ensure that the HMI
device used supports all properties which are used in the project. Compile the project after the
HMI device change in WinCC flexible. The project must be perfectly compilable before the
migration. Then migrate the project to WinCC.
See also
Supported HMI devices (WinCC flexible) (Page 95)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 99
4.6.2.2 Object support during migration (WinCC flexible)
Introduction
When migrating projects from WinCC flexible, all configuration data involving an HMI device
supported by WinCC will be migrated. Basically, all object types and functions that are available
and can be mapped to the new project environment will be fully migrated.
Some global object types are not migrated, for example, dictionaries and global libraries.
Supported object types
The following object types are supported for migration:
Animations
Audit settings
Audit reports
Scheduler
User administration
Area pointer
Faceplates
Screens
Screen template
Data types
Function lists
Graphics lists
Display and operating elements
Migration supports all display and operating elements available on the supported HMI
devices.
Alarms
Alarm classes
Alarm groups
Project library
Project languages
Reports
Recipes
Runtime languages
Runtime scripting
Sm@rtAccess/Sm@rtService
Structures
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
100 System Manual, 08/2011,
System events
System functions
Texts
Text lists
Tags
Connections
Effective ranges
Zones
Cycles
Unsupported object types
The following object types are not supported by migration:
Global libraries
Dictionaries
Project versions
Change log
Mapping of the screen navigation
WinCC does not support the screen navigation from WinCC flexible. The data of the screen
hierarchy from WinCC flexible are not migrated. To map the functionality of a screen navigation
from WinCC flexible, the naivigation buttons are migrated to the button available in WinCC.
The system functions migrated to the "ActivateScreen" system function are migrated to the
"Click" event of the respective button. The following system functions used in WinCC flexible
are not available for the screen navigation in WinCC:
ActivateRootScreen
ActivateLeftScreen
ActivateRightScreen
ActivateParentScreen
ActivateFirstChildScreen
These system functions are migrated to the "ActivateScreen" system function. The "Screen
name" parameter is taken from the data of the screen hierarchy. If one of the named system
functions is called from a screen which is not contained in the screen hierarchy, the
"ActivateScreen" function is created without parameters. You must configure the desired
screen to this system function after the migration.
Migration of the screen template
WinCC offers an extended concept for working with screen templates. WinCC offers a global
screen and several templates for each device. During migration of a template from
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 101
WinCC flexible, the objects contained there and the properties configured in the template are
migrated to the extended concept of the screen templates of WinCC.
The following objects are migrated to the "global screen" of WinCC:
Alarm window
Alarm indicator
Help indicator
Function keys of HMI devices with function keys
All other objects and properties are migrated to a template of WinCC.
The connection of the objects and properties to the respective template is automatically
adapted.
See also
Changes of values of object properties by the migration (WinCC flexible) (Page 102)
4.6.2.3 Changes of values of object properties by the migration (WinCC flexible)
Introduction
The standardization of object properties from WinCC V7 and WinCC flexible requires changes
to the object properties during the migration process. The migration calculates the changes in
such a way that the representation of the objects after migration is the same as prior to
migration. Changes made during migration result in different units of measurements and values
in the configuration for some object properties.
Migrating the font settings of an object
In WinCC V7 and WinCC flexible, the unit of measurement "point" is used to denote the size
of the fonts used for an object. In WinCC, the unit of measurement "pixel" is used to denote
the size of the fonts used for an object. During migration, the font size is converted accordingly
to ensure that the representation of the font is the same size at zoom level 100%. The different
units of measurement result in changes to the numerical values for the font sizes after
migration.
Example:
Font style before migration Font style after migration
Arial 10 points Arial 13 pixels
Arial 16 points Arial 21 pixels
Tahoma 10 points Tahoma 13 pixels
Tahoma 16 points Tahoma 21 pixels
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
102 System Manual, 08/2011,
Migration of object margins
In WinCC flexible, some objects permit the entry of values <0 and >127 for setup of the object
margins for the configuration of the representation. In WinCC, the range of values for object
margins is limited to values between 0 and 127. The migration changes values <0 to the value
"0" and values >127 to the value "127".
See also
Object support during migration (WinCC flexible) (Page 100)
4.6.2.4 Connections (WinCC flexible)
Migration of connections (WinCC flexible)
Introduction
If you migrate a project in which a supported communication driver is used, this driver is used
further in WinCC. Objects which communicate via this driver are migrated 1:1. No rework is
necessary.
Not all communication drivers which are available in WinCC flexible are supported in WinCC.
If an unsupported driver is used in the project to be migrated, there are two possible scenarios:
1. A compatible spare driver is available for the used driver.
2. No compatible spare driver is available for the used driver.
Compatible spare driver is available
If a driver is available in WinCC which addresses the used PLC or a comptaible PLC, the driver
is automatically replaced during the migration.
You get an appropriate warning if the used driver is replaced.
In this case, check whether all the external tags and area pointers are valid after the migration
by means of the migration report.
If the used driver is replaced, all the connection parameters are reset to the standard values.
The CPU type is adapted to the appropriate PLC. The properties of the connected tags and
area pointers are not changed.
Compatible spare driver is not available
If no driver is available in WinCC which addresses the used PLC or a compatible PLC, the
configured connection is not migrated. All external tags which were connected to the PLC by
this driver are converted into internal tags. External tag properties are lost in the conversion,
e.g. the address in the PLC. All changes to the tags are recorded in the migration report.
You must reconnect the tags with the PLC after the migration and configuring of a connection.
You get an appropriate warning if the driver is not migrated.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 103
Converting the communication driver
The following tables show the mapping of communication drivers from WinCC flexible to
WinCC.
Supported communication drivers
WinCC flexible WinCC
Allen Bradley DF1 Allen Bradley DF1
Mitsubishi FX Mitsubishi FX
Modicon MODBUS Modicon MODBUS RTU
Modicon MODBUS TCP/IP Modicon MODBUS TCP/IP
Omron Hostlink/Multilink Omron HostLink
OPC OPC
SIMATIC HMI HTTP Protocol SIMATIC HMI HTTP Protocol
SIMATIC S7 200 SIMATIC S7 200
SIMATIC S7 300/400 SIMATIC S7 300/400
Compatible communication drivers
WinCC flexible WinCC
Allen Bradley DH485 Allen Bradley DF1
Allen Bradley E/IP C.Logix Allen Bradley EtherNet/IP
Mitsubishi Protocol 4 Mitsubishi MC TCP/IP
Not supported communication drivers
WinCC flexible WinCC
GE Fanuc SNP not supported
ISAC not supported
LG GLOFA-GM not supported
SIMATIC 500/505 DP not supported
SIMATIC 500/505 serial not supported
SIMATIC S5 AS511 not supported
SIMATIC S5 DP not supported
SIMOTION not supported
Telemecanique Uni-Telway not supported
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
104 System Manual, 08/2011,
See also
Migration (WinCC flexible) (Page 90)
Supported HMI devices (WinCC flexible) (Page 95)
Adapting configuration for non-migrated connection (WinCC flexible) (Page 105)
Migration of area pointers (WinCC flexible) (Page 106)
Migration of tags (WinCC flexible) (Page 106)
Adapting configuration for non-migrated connection (WinCC flexible)
Introduction
If a connection cannot be migrated you have the following options:
Change the configuration in WinCC flexible before the migration
Change the configuration after the migration
Change a connection before the migration
If the communication driver selected for the connection is not supported by the migration, you
must select a driver which is supported by the migration. The HMI device must also support
the selected communication driver.
If no suitable driver is available for the used HMI device, you must use a suitable HMI device.
Then adapt the configuration in WinCC flexible and recompile the project. Migrate the project
after successful adaptation and compiling. The connection is then also migrated.
Changing a connection before the migration
If you migrate a WinCC flexible project in which the connection is not migrated, all external
tags of this connection are mapped to internal tags. You receive an appropriate entry in the
migration protocol for every tag concerned.
You must configure a new connection after the migration. For this connection you select a
communication driver which supports the used HMI device. If no suitable driver is available for
the used HMI device, you must use a suitable HMI device.
If you have configured the new connection, you must reconnect all tags which were mapped
to internal tags before the migration. Open the migration report to make reconfiguration easier.
Reconfigure the tags according to the log entry.
If the project contained area pointers, you must also reconfigure these. You will also find
corresponding entries for the area pointers in the migration log.
See the section Migrating projects from WinCC flexible (WinCC flexible) (Page 92) for further
information about the migration log.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 105
See also
Migrating projects from WinCC flexible (WinCC flexible) (Page 92)
Migration of connections (WinCC flexible) (Page 103)
Migration of area pointers (WinCC flexible)
Introduction
The migration of area pointers depends on the used communication driver.
If the used communication driver is supported by the migration, area pointers from WinCC
flexible are taken over unchanged in the migration.
if the used communication driver is not supported by the migration, area pointers are not
migrated.
Migration of the area pointers
If the connection used by the area pointers is fully migrated, the area pointers are also fully
migrated. The parameters of the area pointers are taken over unchanged.
If you replace the communication driver of the connection before the migration, check whether
all the parameters of the area pointers are still valid after the migration.
If the connection used by the area pointer is not migrated, the area pointers are not migrated
either. See Adapting configuration for non-migrated connection (WinCC flexible) (Page 105)
for additional information.
See also
Adapting configuration for non-migrated connection (WinCC flexible) (Page 105)
Migration of connections (WinCC flexible) (Page 103)
4.6.2.5 Migration of tags (WinCC flexible)
Introduction
You need to make some special considerations when migrating tags. The following aspects
should be distinguished:
Migrating data types of tags
Migrating internal tags
Migrating external tags
Tag names
Tag limits
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
106 System Manual, 08/2011,
Migrating data types
WinCC features some other data types and uses different data type names than
WinCC flexible. When migrating a relevant tag, the data type from WinCC flexible is mapped
to the corresponding data type in WinCC. See Migration of data types (WinCC flexible)
(Page 121) for additional information.
Migrating internal tags
Internal tags are always migrated completely. Only the data type names and tag names may
change due to migration.
Migrating external tags
If the connection used by the external tags is migrated, the external tags are also fully migrated.
The migration of external tags depends on whether the used communication driver is supported
by the migration. See Migration of connections (WinCC flexible) (Page 103) for additional
information.
If the connection used by the external tags is not migrated, the external tags are not migrated
either. The external tags are then mapped to internal tags. You must configure a new
connection and reconnect the tags with the tags of the PLC after the migration.
Migrating names of tags
In WinCC flexible, tags located in different folders can have the same name. In WinCC, the
tag name must be unique on the configured HMI device. This means that tags with the same
name from different folders will be renamed during migration. See Migration principles (WinCC
flexible) (Page 91) for additional information.
See also
Migration of data types (WinCC flexible) (Page 121)
Migration of connections (WinCC flexible) (Page 103)
Migration principles (WinCC flexible) (Page 91)
Migration (WinCC flexible) (Page 90)
Migration of alarm classes and alarm groups (WinCC flexible) (Page 108)
Migration of scripts (WinCC flexible) (Page 111)
Migration of language-specific content (WinCC flexible) (Page 112)
Migration of libraries (WinCC flexible) (Page 114)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 107
4.6.2.6 Migration of logs
Storage location of logs
WinCC flexible allowed you to store logs in a database which was automatically set up upon
WinCC flexible installation ("System-defined data source" setting). This option is not available
in WinCC.
If you have used this setting in your WinCC flexible project, it will be changed to "User-defined
name of data source" during migration. Before you can store logs in a database, you must
configure an ODBC data source in the Windows control panel and configure the name of the
user data source specified there as the "name of the data source" in the log in WinCC.
4.6.2.7 Migration of alarm classes and alarm groups (WinCC flexible)
Changing the names of alarm classes
In contrast to WinCC flexible, the names of the predefined alarm classes are not dependent
on the user interface language currently in use. During migration, the names of the alarm
classes are assigned as follows:
WinCC flexible WinCC
Error Alarms
System System
Warnings Events
The names of the alarm classes can be changed as necessary after migration.
Migrating alarm groups
Migration will migrate only those alarm groups actually in use.
Alarm groups with an ID from 1-31 will be migrated 1:1.
A corresponding alarm group is created in WinCC for each alarm class in the system. These
alarm groups created by the system are assigned IDs beginning with the number 32 and
consecutively incremented. The 4 pre-defined message classes in every WinCC project are
automatically given IDs 32-35 by their alarm groups. Additionally created alarm group and an
additional ID is assigned to each user-defined alarm class. Therefore, the IDs for alarms groups
with IDs > 31 may be changed after migration. This step also changes the assignment of the
alarm group names to the IDs.
Example:
In the example, you can see the assignment of the IDs in WinCC for the migration.
Alarm groups ID in WinCC flexible ID in WinCC
Alarm group 1-16 1-16 1-16 Default for alarm groups from system
alarms
Alarm group 17-31 17-31 17-31 Custom alarm groups
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
108 System Manual, 08/2011,
Alarm groups ID in WinCC flexible ID in WinCC
32-35 Default in WinCC for alarm groups of
predefined alarm classes.
Alarm group 32 32 36 Changed assignment of ID to alarm group
in WinCC
Alarm group 33 33 37 Changed assignment of ID to alarm group
in WinCC
Also note:
When migrating alarm groups that supposedly have the same group name, the migration
adapts the name. This occurs, for example, when a group name contains a space at the end
of the name. The migration deletes all existing spaces at the end of names. If two groups
obtained the same group names due to this deletion, the migration adds the suffix "# Mign" to
the group name of the following alarm groups, where "n" stands for a sequential number.
Example:
The following alarm groups exist in WinCC flexible:
"AlarmGroup_18"
"AlarmGroup_18 " - group name contains one space
"AlarmGroup_18 " - group name contains two spaces
"AlarmGroup_18" is the alarm group with the highest number.
Result after migration:
"AlarmGroup_18"
"AlarmGroup_18#Mig1"
"AlarmGroup_18#Mig1.1"
Changing the names of alarm classes
In contrast to WinCC flexible, the names of the predefined alarm classes are not dependent
on the user interface language currently in use. During migration, the names of the alarm
classes are assigned as follows:
WinCC flexible WinCC
Error Errors
System System
Warnings Warnings
The names of the alarm classes can be changed as necessary after migration.
Display of ALARM_S messages and SIMATIC SFM messages
In WinCC flexible you can activate the display classes for ALARM_S messages in integrated
projects. In WinCC flexible, you activate the display of SIMATIC SFM messages via a separate
setting. The separate setting for activating the display of SIMATIC SFM messages is not
required in WinCC. You control the display of SIMATIC SFM messages, and also the display
of ALARM_S messages in WinCC only by activating the corresponding display class.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 109
The changed concept may cause the display of messages to change following migration.
If all the display classes for ALARM_S messages are activated and the display of
SIMATIC SFM messages is deactivated in the WinCC flexible project , ALARM_S messages
and SIMATIC SFM messages are displayed following migration.
To ensure that only ALARM_S messages are displayed following migration, you have to assign
the SIMATIC SFM messages to an unused display class after migration to STEP 7. You then
have to deactivate this display class in WinCC.
If all the display classes for ALARM_S messages are deactivated and the display of
SIMATIC SFM messages is activated in the WinCC flexible project , ALARM_S messages and
SIMATIC SFM messages are not displayed following migration.
To ensure that only SIMATIC SFM messages are displayed following migration, you have to
assign the SIMATIC SFM messages to an unused display class after migration to STEP 7.
You then have to activate this display class in WinCC.
The display class is dependent on the settings in STEP 7. The default setting for SIMATIC SFM
messages in Step 7 is the display class "0". To activate the display in WinCC, the display class
"0" must be activated.
You activate the display class in WinCC in the Runtime settings of the respective HMI device
in the "Messages" category.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
110 System Manual, 08/2011,
See also
Migration of tags (WinCC flexible) (Page 106)
4.6.2.8 Migration of scripts (WinCC flexible)
Introduction
The migration supports VB-scripts which were created in WinCC flexible. For a VB-script to
be migrated successfully it must be functionable in WinCC flexible first.
Migration of a VB script
A script is analyzed in the migration and adapted to the system behavior of WinCC if necessary.
The following is adapted:
System functions which have changed their names are renamed.
This concerns the following system functions:
Function name in WinCC flexible Function name in WinCC
IncreaseValue IncreaseTag
DecreaseValue DecreaseTag
SetValue SetTag
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 111
The access to tags as parameters of system functions is adapted to the system behavior
of WinCC. In WinCC scripts are no longer transfromed as in WinCC flexible. The scripts
are executed directly as a source code. Therefore the stricter rules for the VBS syntax
apply. A tag call is always migrated with inverted commas. If several parameter types are
allowed for a system function, these are migrated with the keyword "SmartTags".
Example 1:
The value of the "temperature" tag should be incremented by the value "1".
Valid expressions in WinCC flexible:
IncreaseValue temperature, 1
IncreaseValue "temperature", 1
IncreaseValue SmartTags("temperature"), 1
Valid expression in WinCC:
IncreaseTag "temperature", 1
Example 2:
You use a system function on which several parameters are allowed. The value of the
"temperature" tag should be incremented by the value of the "heatcontrol" tag.
Valid expression for WinCC flexible:
IncreaseValue "temperature", "heatcontrol"
Valid expression for WinCC:
IncreaseTag "temperature", SmartTags("heatcontrol")
Objects renamed by the migration are also renamed in the script when using in a script.
See the section Migration principles (WinCC flexible) for further information about the
renaming objects. You only have to observe the following rules when renaming objects:
If you address objects whose names are dynamically generated by the script with the help
of a script, the object names in the script can not be automatically changed by the migration.
In such a case, you have to correct the generation of the object names in the script after
migration.
See also
Migration of tags (WinCC flexible) (Page 106)
4.6.2.9 Migration of language-specific content (WinCC flexible)
Introduction
WinCC offers the same options for configuring projects in different languages as those
available in WinCC flexible. All languages supported by WinCC are included in the migration
of a project.
Migrating language-dependent content
The following language-dependent content is migrated:
Project languages
Project texts
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
112 System Manual, 08/2011,
Fonts for display in runtime
Language-dependent graphics
You need to consider the following when migrating language-dependent content:
The operating system on the PC performing the migration must support the project
languages used in the project.
The fonts used for runtime display must be installed on the PC performing the migration.
Dictionaries are not supported by the migration.
Editiing language of integrated projects following migration
During migration of an integrated project, the project components to be migrated from STEP 7
and WinCC flexible also bring their respective settings for the editing language. In WinCC there
is only one editing language for all project components. Migration activates for the mgrated
project the editing language which was set in STEP 7 prior to migration. If this setting is not
the same as the setting from WinCC flexible, the configured texts are no longer visible in
WinCC. No text is displayed at the usage locations, or only the entry "Text" can be seen. To
make the texts visible, you must change the editing language. Click the "Tasks" taskcard at
the right-hand edge of the TIA portal and select the correct editing language in the "Language
& Resources" area.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 113
Unsupported languages
The migration of language-dependent content depends on whether or not WinCC supports the
respective language.
If a project only contains project languages not supported by WinCC, the project will not be
migrated.
If a project contains supported and unsupported project languages, only the supported
languages will be migrated. The editing language and reference language are set to a
supported language.
The following languages are not supported by WinCC:
Arabic
Hebrew
Dhivehi
Gujarati
Kannada
Tamil
Telugu
Urdu
Punjabi
Persian
Syrian
See also
Migration of tags (WinCC flexible) (Page 106)
4.6.2.10 Migration of libraries (WinCC flexible)
Introduction
You need to consider two different cases when migrating from libraries:
1. Migrating a project library
2. Migrating a global library
Migrating a project library
A project library is stored together with the project data in the project file. For this reason, a
project library is migrated with the same restrictions as the project data.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
114 System Manual, 08/2011,
Migrating a global library
Global libraries are not supported by the migration. The library objects used in the project will
be migrated, however. The library objects are copied when used in the project and then no
longer have a connection to the library.
To migrate a global library, you must copy or move the objects contained in the library to the
project library. The objects are then included in the migration. In WinCC, you move the migrated
objects to a new global library that is created. You can copy or move both individual objects
or entire library categories.
See also
Migration of tags (WinCC flexible) (Page 106)
4.6.3 Migrating runtime data (WinCC flexible)
4.6.3.1 Migration of runtime data (WinCC flexible)
Introduction
Only the configuration data are migrated by the migration when migrating a project. The runtime
data are not affected. You need to update the runtime data following migration.
The runtime data consists of the following:
Runtime project
The runtime project contains the compiled project data.
Recipe data and user administration
The recipe data and user administration are data that can be changed in runtime.
Log data
The data of tag logs and alarm logs are acquired and logged in runtime.
Migrating recipe data and user administration
If the recipe data and user administration were changed in runtime, you need to back up this
information from the HMI device before you load the migrated project.
Depending on the used HMI device, you have different options for saving the above data.
If the HMI device supports external memory media and the recipe data are saved there, the
data remain on the memory medium. External memory media are for example StorageCard
or a network drive. You use the data again after the migration. The user adminsitration is not
saved on an external memory medium so you have to save these data, e.g. with ProSave.
If the recipe data are saved in the internal memory of the HMI device, save these data on an
external memory medium. Use ProSave to save the recipe data. If you have already configured
appropriate system functions in your project, use the system functions. The following system
functions are available for the recipe data:
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 115
"ExportDataRecords" for the backup
"ImportDataRecords" for the restore
You update the runtime project by compiling the project in WinCC again and loading it to the
HMI device.
After you have loaded the migrated project on the HMI device, restore the recipe data and the
user administration to the HMI device.
See also
Migration (WinCC flexible) (Page 90)
Backing up recipe data and user administration (WinCC flexible) (Page 116)
Restoring recipe data and user administration (WinCC flexible) (Page 117)
4.6.3.2 Backing up recipe data and user administration (WinCC flexible)
Introduction
To continue using the recipe data and user administration in a migrated project, you first need
to back up this data from the HMI device. Then load the data into the migrated WinCC project.
Use ProSave to back up the data.
Requirement
The WinCC flexible project is running on the HMI device in Runtime.
The HMI device is connected to a PC on which ProSave is installed.
Procedure
Proceed as follows to back up the recipe data and user administration:
1. Start ProSave.
2. Select the device type and the connection parameters in the "General" tab.
3. Open the "Backup" tab.
4. Select the "Recipes from the device memory" entry in the "Data type" box.
Do not select "Complete backup" because otherwise you will not be able to select separately
when restoring the recipe data.
5. Navigate to the desired location in the "Save as" box and click "Start Backup".
The recipe data are saved.
6. Select "User administration" in the "Data type" box and click "Start Backup".
The user administration is saved.
For additional information refer to the online help for ProSave.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
116 System Manual, 08/2011,
Alternative procedure
ProSave is automatically installed with WinCC flexible. The entire functional range of ProSave
is available on the configuration PC within WinCC flexible via the menu command "Project >
Transfer".
Alternatively, you can back up the recipe data and user administration via the ProSave
integrated in WinCC flexible. Start WinCC flexible and select the menu command "Project >
Transfer > Backup". Back up the recipe data and user administration as described in steps 4-6.
See also
Migration of runtime data (WinCC flexible) (Page 115)
4.6.3.3 Restoring recipe data and user administration (WinCC flexible)
Introduction
To continue using saved recipe data and user administration after the migration, you first need
to compile the migrated project and load it to the HMI device. You can then transfer the saved
data to the HMI device. Use ProSave to restore the data.
Requirement
The migrated project has been transferred to the HMI device and is running in runtime.
The HMI device is connected to a PC on which ProSave is installed.
Procedure
Proceed as follows to load the saved recipe data and user administration to the HMI device:
1. Start ProSave.
2. Select the device type and the connection parameters in the "General" tab.
3. Open the "Restore" tab.
4. Navigate to the location of the saved recipe data in the "Opening..." box and select the file.
5. Click "Start Restore".
The recipe data will be transferred to the HMI device..
6. Repeat steps 4-5 to restore the user administration.
The user administration will be transferred to the HMI device.
For additional information refer to the online help for ProSave.
Alternative procedure
ProSave is automatically installed with WinCC. The entire functional range of ProSave is
available on the configuration PC within WinCC flexible via the menu command "Project >
Transfer".
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 117
You can also restore the recipe data and user administration via the ProSave integrated in
WinCC. Start WinCC and select the menu command "Online > Device maintenance >
Restore". Restore the recipe data and user administration as described in steps 4-6.
See also
Migration of runtime data (WinCC flexible) (Page 115)
4.6.3.4 Backing up log data (WinCC flexible)
Introduction
If an HMI device supports external memory media and the log data are saved there, the data
remain on the memory medium. External memory media are for example StorageCard or a
network drive. If a log is saved on an external memory medium, the migrated project accesses
this storage location again after the migration. In this case the log data must not be backed up.
Backing up log data
If you want to back up the log data externally before the migration, you have the following
options:
Backup with the "ArchiveLogFile".
If you have already configured the "ArchiveLogFile" function in the WinCC flexible project,
use this function to back up the data.
Copy the log files by Copy&Paste with the Windows Explorer to an external memory
medium or network drive.
See also
Migration of runtime data (WinCC flexible) (Page 115)
4.6.4 Migrating integrated projects (WinCC flexible)
4.6.4.1 Migration of integrated projects (WinCC flexible)
Introduction
The controllers and HMI devices contained in a project integrated in STEP 7 are linked together
by the configuration. The configuration data of WinCC flexible and STEP 7 are also connected.
When an integrated project is migrated, the complete project will be migrated with components
from WinCC flexible and STEP 7. The connections remain intact.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
118 System Manual, 08/2011,
Migrating an integrated project
When migrating an integrated project, the same requirements apply for the WinCC flexible
component as those for the migration of a non-integrated WinCC flexible project. The objects
and properties contained in the WinCC flexible component must be supported by WinCC, for
example, the HMI device or the communication driver. The "Online" property must be activated
on the configured connection. A connection with deactivated "Online" property is not migrated.
In addition to the requirements for the WinCC flexible component, there are also requirements
for the STEP 7 component of the integrated project. The objects and properties contained in
the STEP 7 V5.4 SP5 or V5.5 component must be supported in STEP 7. For detailed
information, refer to the documentation for STEP 7.
To fully migrate an integrated project and then edit it, the following components must be
installed on the PC performing the migration:
STEP 7 V5.4 SP5 or STEP 7 V5.5
WinCC
STEP 7
If you only want to save the project in migration format, you can use the migration tool. See
Migration principles (WinCC flexible) (Page 91) for additional information.
An integrated project is always fully migrated. If you only want to migrate the WinCC flexible
project it contains, you need to separate it from the STEP 7 project before the migration. To
separate the project from the integrated form, open the project in STEP 7 V5.4 SP5 or V5.5.
Open the WinCC flexible project in the SIMATIC Manager. The project is opened with
WinCC flexible. In WinCC flexible, select the menu command "Project > Copy project from
STEP 7". WinCC flexible saves a non-integrated copy of the project.
See also
Migration (WinCC flexible) (Page 90)
Migrating integrated project (WinCC flexible) (Page 119)
Migration principles (WinCC flexible) (Page 91)
4.6.4.2 Migrating integrated project (WinCC flexible)
Introduction
When migrating an integrated project, the components from both the WinCC flexible project
and the STEP 7 project will be migrated. This means you need to select the project file with
the file extension "*.s7p" for migration. During migration, the data is copied from the existing
project and migrated to a new project. You cannot migrate to an existing project.
The migration can be started in both the Portal view and the Project view.
You should only migrate a project in a newly started TIA portal.
If you only want to save the project in migration format, you can use the migration tool. See
Migration principles (WinCC flexible) (Page 91) for additional information.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 119
Requirement
STEP 7 V5.4 SP5 or STEP 7 V5.5 and all add-on packages used are installed.
STEP 7 and all add-on packages used are installed.
The TIA portal is newly started.
No project is open in WinCC.
An integrated project is available.
The integrated project is not open.
Procedure
Proceed as follows to migrate an integrated project in the Portal view:
1. Select the action "Start > Migrate Project".
2. In the "Source path" box, navigate to the project you want to migrate.
3. Select the "*.s7p" project file.
4. Change the information for the project to be created, if necessary. For example, change
the project name or project path. The data to be migrated is created in the new project.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
120 System Manual, 08/2011,
5. Click "Migrate".
A new project is created and migration of the data is started:
The Project view opens.
The progress of the migration is shown in a migration window.
Warnings and errors about the migration process are displayed in the Inspector window
under "Info > General".
All information about the migration is saved in a log file.
A message is displayed upon completion of the migration. The message contains a link
that you can use to open the log.
6. Once migration is completed, save the project.
Once the migration is complete, you will find a newly created device for each migrated HMI
device and controller in the project tree. These devices include the migrated data.
Opening the migration log at a later point in time
The migration log is saved together with the migrated project. You can view the log at a later
point in time. Open the log as follows:
1. Select the project in the project tree.
2. Select the "Properties" command in the shortcut menu.
3. Click "Project History" in the "Properties" dialog.
4. Click on the log file.
The migration log opens.
See also
Migration of integrated projects (WinCC flexible) (Page 118)
Migration principles (WinCC flexible) (Page 91)
4.6.5 Reference (WinCC flexible)
4.6.5.1 Migration of data types (WinCC flexible)
Introduction
To harmonize the data types used by PLCs and HMI systems, some data types of the internal
HMI tags are renamed. The naming takes place in accordance with IEC conventions. Because
only the names change, there are no changes to the internal tags for the configuration.
The following table describes the mapping of the internal data types from WinCC flexible to
the data types in WinCC.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 121
Migrating internal data types
The internal data types are mapped as follows during migration:
Internal data types WinCC flexible Internal data types WinCC
Bool Bool
Char SInt
Byte USInt
Int Int
UInt UInt
Long DInt
ULong UDInt
Float Real
Double LReal
String WString
DateTime DateTime
Migrating external data types
See the following pages for how to map the available communication drivers.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
122 System Manual, 08/2011,
See also
Migrating data types of Allen-Bradley DF1 (WinCC flexible) (Page 123)
Migrating data types of Allen-Bradley DF485 (WinCC flexible) (Page 124)
Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible) (Page 124)
Migrating data types of GE Fanuc SNP (WinCC flexible) (Page 125)
Migrating data types of LG GLOFA GM (WinCC flexible) (Page 125)
Migrating data types of Mitsubishi FX (WinCC flexible) (Page 126)
Migrating data types of Mitsubishi Protocol 4 (WinCC flexible) (Page 127)
Migrating data types of Modicon Modbus (WinCC flexible) (Page 127)
Migrating data types of Modicon Modbus TCP/IP (WinCC flexible) (Page 128)
Migrating data types of Omron Hostlink/Multilink (WinCC flexible) (Page 128)
Migrating data types of OPC (WinCC flexible) (Page 129)
Migrating data types of SIMATIC 500/505 DP (WinCC flexible) (Page 130)
Migrating data types of SIMATIC 500/505 serial (WinCC flexible) (Page 130)
Migrating data types of SIMATIC HMI HTTP Protocol (WinCC flexible) (Page 131)
Migrating data types of SIMATIC S5 AS511 (WinCC flexible) (Page 131)
Migrating data types of SIMATIC S5 DP (WinCC flexible) (Page 132)
Migrating data types of SIMATIC S7 200 (WinCC flexible) (Page 133)
Migrating data types of SIMATIC S7 300/400 (WinCC flexible) (Page 133)
Migrating data types of Telemecanique Uni-Telway (WinCC flexible) (Page 136)
4.6.5.2 Migrating data types of Allen-Bradley DF1 (WinCC flexible)
Migrating data types Allen-Bradley DF1
The data types of the Allen-Bradley DF1 communication driver are mapped as follows in the
migration to WinCC:
Data type in WinCC flexible Data type in WinCC
ASCII ASCII
BCD4 UInt
BCD8 UDInt
Bit Bool
Int Int
Long DInt
Real Real
UInt UInt
ULong UDInt
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 123
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.3 Migrating data types of Allen-Bradley DF485 (WinCC flexible)
Migrating data types Allen-Bradley DH485
The Allen-Bradley DH485 communication driver is not supported by WinCC, it is replaced by
the Allen-Bradley DF1 driver. The data types of the Allen-Bradley DH485 communication driver
are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
ASCII ASCII
Bit Bool
Int Int
Long DInt
Real Real
UInt UInt
ULong UDInt
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.4 Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible)
Migrating data types Allen-Bradley Ethernet IP
The data types of the Allen-Bradley Ethernet IP communication driver are mapped as follows
in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bool Bool
DInt DInt
Int Int
Real Real
SInt SInt
String String
UDInt UDInt
UInt UInt
USInt USInt
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
124 System Manual, 08/2011,
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.5 Migrating data types of GE Fanuc SNP (WinCC flexible)
Migrating data types GE Fanuc SNP
The GE Fanuc SNP communication driver is not supported by WinCC, the data types are
mapped to the internal data types of WinCC. The data types of the GE Fanuc SNP
communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
BCD4 UInt
BCD8 UDInt
Bit Bool
Byte USInt
DInt DInt
Word UInt
Int Int
Real Real
UInt UInt
DWord UDInt
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.6 Migrating data types of LG GLOFA GM (WinCC flexible)
Migrating data types LG GLOFA GM
The LG GLOFA GM communication driver is not supported by WinCC, the data types are
mapped to the internal data types of WinCC. The data types of the LG GLOFA GM
communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bool Bool
Byte USInt
DInt DInt
DWord UDInt
Int Int
SInt SInt
String WString
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 125
Data type in WinCC flexible Data type in WinCC
Time UDInt
UDInt UDInt
UInt UInt
USInt USInt
Word UInt
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.7 Migrating data types of Mitsubishi FX (WinCC flexible)
Migrating data types Mitsubishi FX
The data types of the Mitsubishi FX communication driver are mapped as follows in the
migration to WinCC:
Data type in WinCC flexible Data type in WinCC
12 Bit Block 12-Bit Block
16 Bit Block 16-Bit Block
20 Bit Block 20-Bit Block
24 Bit Block 24-Bit Block
28 Bit Block 28-Bit Block
32 Bit Block 32-Bit Block
4 Bit Block 4-Bit Block
8 Bit Block 8-Bit Block
Bit Bool
Double DWord
IEEE-Float Real
String String
Word Word
See also
Migration of data types (WinCC flexible) (Page 121)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
126 System Manual, 08/2011,
4.6.5.8 Migrating data types of Mitsubishi Protocol 4 (WinCC flexible)
Migrating data types Mitsubishi Protocol 4
The Mitsubishi Protocol 4 communication driver is not supported by WinCC, it is replaced by
the Mitsubishi MC TCP/IP driver. The data types of the Mitsubishi Protocol 4 communication
driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
4 Bit Block 4-Bit Block
8 Bit Block 8-Bit Block
12 Bit Block 12-Bit Block
16 Bit Block 16-Bit Block
20 Bit Block 20-Bit Block
24 Bit Block 24-Bit Block
28 Bit Block 28-Bit Block
32 Bit Block 32-Bit Block
Bit Bool
DInt DInt
DWord DWord
Int Int
Real Real
String String
Word Word
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.9 Migrating data types of Modicon Modbus (WinCC flexible)
Migrating data types Modicon Modbus
The Modicon Modbus communication driver is not supported by WinCC, it is replaced by the
Modicon Modbus RTU driver. The data types of the Modicon Modbus communication driver
are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
+/-Double +/- Double
+/-Int +/- Int
16 Bit Group 16 Bit Group
ASCII ASCII
Bit Bit
Double Double
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 127
Data type in WinCC flexible Data type in WinCC
Float Float
Int Int
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.10 Migrating data types of Modicon Modbus TCP/IP (WinCC flexible)
Migrating data types Modicon Modbus TCP/IP
The data types of the Modicon Modbus TCP/IP communication driver are mapped as follows
in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
+/-Double +/- Double
+/-Int +/- Int
16 Bit Group 16 Bit Group
ASCII ASCII
Bit Bit
Double Double
Float Float
Int Int
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.11 Migrating data types of Omron Hostlink/Multilink (WinCC flexible)
Migrating data types Omron Hostlink/Multilink
The Omron Hostlink/Multilink communication driver is not supported by WinCC, it is replaced
by the Omron Host Link driver. The data types of the Omron Hostlink/Multilink communication
driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
+/-DEC Int
+/-LDEC DInt
ASCII String
BIN Bool
BYTE Byte
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
128 System Manual, 08/2011,
Data type in WinCC flexible Data type in WinCC
DEC UInt
IEEE Real
LDEC UDInt
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.12 Migrating data types of OPC (WinCC flexible)
Migrating data types OPC
The data types of the OPC communication driver are mapped as follows in the migration to
WinCC:
Data type in WinCC flexible Data type in WinCC
Bool VT_BOOL
Byte VT_UI1
Char VT_I1
Date VT_DATE
Double VT_R8
DWord VT_UI4
Float VT_R4
Long VT_I4
Short VT_I2
String VT_BSTR
Word VT_UI2
See also
Migration of data types (WinCC flexible) (Page 121)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 129
4.6.5.13 Migrating data types of SIMATIC 500/505 DP (WinCC flexible)
Migrating data types SIMATIC 500/505 DP
The SIMATIC 500/505 DP communication driver is not supported by WinCC, the data types
are mapped to the internal data types of WinCC. The data types of the SIMATIC 500/505 DP
communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
+/-Double DInt
+/-Int Int
ASCII WString
Bit Bool
Double UDInt
Int UInt
Real Real
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.14 Migrating data types of SIMATIC 500/505 serial (WinCC flexible)
Migrating data types SIMATIC 500/505 seriell
The SIMATIC 500/505 seriell communication driver is not supported by WinCC, the data types
are mapped to the internal data types of WinCC. The data types of the SIMATIC 500/505 seriell
communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
+/-Double DInt
+/-Int Int
ASCII WString
Bit Bool
Double UDInt
Int UInt
Real Real
See also
Migration of data types (WinCC flexible) (Page 121)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
130 System Manual, 08/2011,
4.6.5.15 Migrating data types of SIMATIC HMI HTTP Protocol (WinCC flexible)
Migrating data types SIMATIC HMI HTTP Protocol
The data types of the SIMATIC HMI HTTP Protocol communication driver are mapped as
follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bool Bool
Byte USInt
Char SInt
DateTime DateTime
Double LReal
Float Real
Int Int
Long DInt
String WString
UInt UInt
ULong UDInt
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.16 Migrating data types of SIMATIC S5 AS511 (WinCC flexible)
Migrating data types SIMATIC S5 AS511
The SIMATIC S5 AS511 communication driver is not supported by WinCC, the data types are
mapped to the internal data types of WinCC. The data types of the SIMATIC S5 AS511
communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bit in D Bool
Bit in W Bool
DF DInt
DH UDInt
KC WString
KF Int
KG Real
KH UInt
KM UInt
KT UDInt
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 131
Data type in WinCC flexible Data type in WinCC
KY UInt
KZ UInt
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.17 Migrating data types of SIMATIC S5 DP (WinCC flexible)
Migrating data types SIMATIC S5 DP
The SIMATIC S5 DP communication driver is not supported by WinCC, the data types are
mapped to the internal data types of WinCC. The data types of the SIMATIC S5 DP
communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bit in D Bool
Bit in W Bool
DF DInt
DH UDInt
KC WString
KF Int
KG Real
KH UInt
KM UInt
KT UDInt
KY UInt
KZ UInt
See also
Migration of data types (WinCC flexible) (Page 121)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
132 System Manual, 08/2011,
4.6.5.18 Migrating data types of SIMATIC S7 200 (WinCC flexible)
Migrating data types SIMATIC S7 200
The data types of the SIMATIC S7 200 communication driver are mapped as follows in the
migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bool Bool
Byte Byte
Char (Range of values: -128...127) Char (Range of values: 0...255)
DInt DInt
DWord DWord
Int Int
Real Real
StringChar StringChar
Timer Timer
Word Word
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.19 Migrating data types of SIMATIC S7 300/400 (WinCC flexible)
Migrating data types SIMATIC S7 300/400
The data types of the SIMATIC S7 300/400 communication driver are mapped as follows in
the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
Bool Bool
Byte Byte
Char see below
Counter see below
Date Date
Date and Time Date_And_Time
DInt DInt
DWord DWord
Int Int
Real Real
String String
StringChar see below
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 133
Data type in WinCC flexible Data type in WinCC
Time Time
Time of Day Time_Of_Day
Timer see below
Word Word
Special considerations for some data types
There are special considerations to be made when migrating external tags that contain data
types of a SIMATIC S7-300/400 PLC.
Mapping of the S7 data type "Char"
The S7 data type "Char" is a data type for mapping characters according to the specification.
However, since this data type is often used for reading and writing numerical values, it is
mapped in WinCC to the S7 data type "Byte". If this should be the case during migration, an
alarm will appear in the output window.
If the S7 data type "Char" is used for numerical values and negative numbers were configured
at the point of use, the result is an error in mapping to the S7 data type "Byte". The S7 data
type "Byte" cannot map any negative numbers. You have to adapt the configuration accordingly
to correct the error. Use a signed data type, such as the data type "Int", for processing positive
and negative numerical values.
If the S7 data type "Char" is used for mapping characters, you must change the configuration
after migration. To represent characters, use the data type "String".
When an integrated project is migrated, the data type "Char" in WinCC is also migrated to the
data type "Byte". With a connected PLC tag, the data type "Char" remains "Char". As a result
of changing the data type of the HMI tag, symbolic addressing of the tags in question is not
migrated. After migration. the tags are interconnected by absolute addresses and continue to
work. If you want to restore symbolic addressing, you have to change the configuration
accordingly after the migration.
Mapping an array of the S7 data type "Char"
An array of the S7 data type "Char" is mapped to an array of the data type "Byte" during
migration.
If an array of the S7 data type "Char" is used for numerical values and negative numbers were
configured at the point of use, the result is an error in mapping to an array of the S7 data type
"Byte". The S7 data type "Byte" cannot map any negative numbers. You have to adapt the
configuration accordingly to correct the error. Use a signed data type, such as the data type
"Int", for processing positive and negative numerical values.
Mapping of the S7 data type "Counter"
An external tag with the S7 data type "Counter" with counter address is mapped to the S7 data
type "Counter". The address will be retained.
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
134 System Manual, 08/2011,
If an external tag with the S7 data type "Counter" addresses a data block or a bit memory
address, it is is mapped to the S7 data type "Word". The address will be retained. The migration
sets the coding to "SimaticBCDCounter".
The S7 data type "Counter" has a value range of 0-999. When supplied by the S7 data type
"Word" the value range may be exceeded on the PLC side. Ensure that you are observing the
value range.
Example:
WinCC flexible
Tag S7 data type Address Comment
Counter_Actual_Value Counter C10 BCD coded counter value
Counter_Setpoint_Value Counter DB10.DBW200 BCD coded counter value
Counter_Setpoint_Value#2 Counter MW20 BCD coded counter value
WinCC
Tag S7 data
type
Address Coding Comment
Counter_Actual_Value Counter %C10 <Standard> BCD coded counter
value
Counter_Setpoint_Value Word %DB10.%DB
W200
SimaticBCDCounter BCD coded counter
value
Counter_Setpoint_Value#2 Word %MW20 SimaticBCDCounter BCD coded counter
value
Mapping of the data type "StringChar"
In WinCC there is no corresponding data type to which the "StringChar" data type can be
mapped. Mapping in WinCC depends on the property "Length" of the S7 data type.
A tag of the "StringChar" data type with the "Length" property > 1 is migrated to an array of
the S7 data type "Char". The length of the array corresponds to the length of the originally
configured data type "StringChar".
If the property "Length" = 1, the data type in WinCC is migrated to an array of the S7 data type
"Char" with length = 1. The expression for an array with an element is "Array[0 ..0] of Char".
Mapping of the S7 data type "Timer"
An external tag with the S7 data type "Timer" with timer address is mapped to the S7 data type
"Timer". The address will be retained.
If an external tag with the S7 data type "Timer" addresses a data block or a bit memory address,
it is is mapped to the S7 data type "S5 Time". The address will be retained.
Example:
WinCC flexible
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 135
Tag S7 data type Address Comment
Timer_Actual_Value Timer T10 BCD coded timer value
Timer_Setpoint_Value Timer DB10.DBW200 BCD coded timer value
Timer_Setpoint_Value#2 Timer MW20 BCD coded timer value
WinCC
Tag S7 data type Address Comment
Timer_Actual_Value Timer %T10 BCD coded timer value
Timer_Setpoint_Value S5Time %DB10.%DBW200 BCD coded timer value
Timer_Setpoint_Value#2 S5Time %MW20 BCD coded timer value
See also
Migration of data types (WinCC flexible) (Page 121)
4.6.5.20 Migrating data types of Telemecanique Uni-Telway (WinCC flexible)
Migrating data types Telemecanique Uni-Telway
The Telemecanique Uni-Telway communication driver is not supported by WinCC, the data
types are mapped to the internal data types of WinCC. The data types of the Telemecanique
Uni-Telway communication driver are mapped as follows in the migration to WinCC:
Data type in WinCC flexible Data type in WinCC
+/-Int Int
+/-Long DInt
ASCII WString
Bool Bool
Float Real
Int UInt
Long UDInt
See also
Migration of data types (WinCC flexible) (Page 121)
Migrating projects
4.6 Migrating WinCC flexible projects (Advanced)
WinCC Advanced V11.0 SP1
136 System Manual, 08/2011,
4.7 Post-editing integrated projects
4.7.1 Migrating an integrated project
Introduction
When an integrated project is migrated, the complete project will be migrated with components
from Wind and STEP 7. Configured connections between control and visualization remain
intact.
Migrating an integrated project
When migrating an integrated project, the same requirements apply for the STEP 7 component
as those for migration of a non-integrated STEP 7 project. The objects and properties contained
in the Wind component must also be supported in Wind (IA Portal). For detailed information,
refer to the documentation for Wind.
To fully migrate an integrated project, the following components must be installed on the PH/
PC performing the migration:
STEP 7 V5.4 SP5 or STEP 7 V5.5
WinCC V7 SP1 or SP2 or Wind Flexible 2008 SP2
To be able to fully post-edit an integrated project, the following components must be installed
on the PC for post-editing:
STEP 7 Professional V11 (IA Portal)
Wind Basic, Wind Comfort/Advanced oder Wind Professional, depending on the
components used
If the initial project is not located on the same PH/PC on which the IA Portal is installed, first
use the migration tool to prepare migration. This enables you to convert the initial project to a
format that can be read for the IA Portal.
Migration of the STEP 7 part of an integrated project
An integrated project is always fully migrated. Individual components cannot be migrated on
their own. You can only migrate the included STEP 7 project alone, if you have previously
deleted all HMI stations in the SIMATIC stations in the SIMATIC manager and then recompiled
the project in NetPro.
Alternatively, you can open the project in an installation of STEP 7 V5.4 S or V5.5 without an
installation of Wind. Then, save the project again and select the "Reorganize" function during
saving. The Wind parts are then automatically removed during the saving of the copy.
You can then migrate the STEP 7 project without the Wind project.
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 137
Migration of an integrated project without the hardware configuration
You can migrate an integrated project just like any other project without the hardware
configuration. In this case, only the software of the initial project is migrated. The STEP 7
devices, network configurations, connections and interrupts used in the initial project are not
migrated. However, HMI devices are always retained even if you migrate without hardware
configuration.
HMI modules that are plugged into a PC station are converted to a separate Station during the
migration. Thus, the migrated project contains a non-specified SIMATIC PC Station and a
SIMATIC PC Station with the HMI devices. References to HMI devices are not imported during
migration.
The following chapters describe, by way of example, how you post-edit an integrated project
after the migration, in order to restore the full functionality of source project.
Storage location of an integrated Wind project
If you migrate an integrated project, the HMI portion of it must be on the same PH/PC as the
STEP 7 portion of the project. If the HMI portion is on a different PH, then only the STEP 7
portion will be migrated.
Unsupported objects
The following components are not supported for migration:
STEP 7 multiproject
A STEP 7 multiproject cannot be migrated. Migration will be canceled.
Central Archive Server - CAS
If a CAS is part of an integrated project, then the migration will be carried out but the CAS
data will not be migrated.
See also
Post-editing integrated projects (Page 138)
4.7.2 Post-editing integrated projects
If you have migrated an integrated project without hardware configuration, unspecified CPUs
are used instead of the CPUs of the original project. Since no connection can exist between
an unspecified CPU and an HMI device, connections from the source project are also imported
only unspecified.
The following figure shows the state after a Migration without hardware configuration in an
example project:
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
138 System Manual, 08/2011,
1
2
The original CPU 317-2 PN/DP was replaced with an unspecified CPU during migration.
The link between the CPU and HMI device is also unspecified and must be renewed.
Procedure
To continue to use an integrated project after the migration, follow these steps:
1. Convert the unspecified devices into suitable devices again.
2. Restore the integrated HMI connection between the HMI device and the PLC.
3. Connect all HMI tags to the newly created integrated connection.
4. Restore the connection between HMI tags and PLC tags.
5. Delete the non-integrated HMI connection.
In the following chapters a sample project is used to describe the individual steps in more detail.
See also
Converting unspecified CPUs into specified CPUs (Page 140)
Creating an integrated HMI connection (Page 141)
Re-linking HMI tags (Page 143)
Deleting an unspecified connection (Page 144)
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 139
4.7.3 Converting unspecified CPUs into specified CPUs
The first step after the migration without hardware configuration is the conversion of the
unspecified CPUs into specified CPUs. Unspecified CPUs are placeholders for certain CPUs
from the hardware catalog that are not currently known. You can define general parameters
and home the CPUs already in the user program. However, the project is not fully functional
until the unspecified CPU has been specified.
Specifying a CPU using module replacement
To use module replacement to specify an unspecified CPU, follow these steps:
1. Select the unspecified CPU in the network or device view.
2. Select the "Replace device" command in the shortcut menu.
The "Replace device" dialog opens.
1
2
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
140 System Manual, 08/2011,
3. Under "New device" in the tree structure, select the module with which you want to replace
the unspecified CPU. (Area 1)
"Compatibility information" provides you with information on the extent to which the selected
CPU is compatible with the configuration in source project. (Area 2)
4. Click "OK".
5. Perform the above-described steps for all unspecified CPUs.
See also
Creating an integrated HMI connection (Page 141)
4.7.4 Creating an integrated HMI connection
After you have specified the unspecified CPU, establish the connection to the HMI-device.
Procedure
To create a connection graphically, follow these steps:
1. On the toolbar, click the "Connections" icon. This activates connection mode.
2. Select the connection type "HMI connection" in the adjacent drop-down list.
The network view highlights in color all CPUs and HMI devices that can be used for an HMI
connection.
3. You can now have the connection path automatically determined, or explicitly select a
connection path via specific interfaces:
Allow connection path to be automatically determined
Select the source CPU for a connection. Drag the mouse to the target components.
Confirm the connection endpoint with another mouse click.
Alternatively: While holding down the shift button, select the target components and with
the right mouse button select the "Add new connection" command.
Selecting an explicit connection path from interface to interface
Click on the subnet interface in the device for which you want to create a connection.
Hold down the mouse button, drag the cursor to the relevant interface in the target device
and then release the mouse button.
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 141
Result
The following figure shows the state after the integrated connection has been created:
1
2
3
An integrated HMI connection is created and highlighted in the network view.
The connection is shown in the connection table of the components.
The connection can be edited in the connection properties.
See also
Re-linking HMI tags (Page 143)
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
142 System Manual, 08/2011,
4.7.5 Re-linking HMI tags
When you have created a new HMI connection between the CPU and HMI device, you have
to assign the existing HMI tags to the new connection. Perform the following steps for each
line in the relevant tag table.
Procedure
To re-link HMI tags, follow these steps:
1. In the project tree, navigate to the HMI tags and double-click the relevant tag table to show
this in the work area.
The tag table opens.
2. Click the " ... " button in the "Connection" column.
A dialog box for selecting the connection opens.
3. Select the newly established HMI connection.
4. Click the "" button to apply the selected connection.
5. On the toolbar, click the "Re-connect PLC tag" button.
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 143
See also
Deleting an unspecified connection (Page 144)
4.7.6 Deleting an unspecified connection
Finally, you can remove unspecified connections that still remain from the source project.
Procedure
To delete unspecified connections, follow these steps:
1. In the project tree, open the HMI device and double-click the "Connections" entry.
The connection table opens.
2. Select the row with the old connection in the table.
3. Select the "Delete" command in the shortcut menu of the connection line.
4. Perform the above-described steps for all unspecified connections of the source project.
Migrating projects
4.7 Post-editing integrated projects
WinCC Advanced V11.0 SP1
144 System Manual, 08/2011,
First steps
5
5.1 Getting Started Documentation
Getting started with the TIA Portal
The Getting Started documentation is available to help you begin using the TIA portal.
The Getting Started documentation contains instructions which show you, step-by-step how
to create a project in the TIA portal and give you the chance to get a quick overview of all the
possibilities the TIA portal offers you.
Contents
The Getting Started documents describe the creation of a single, continuous project that is
extended with each chapter. You start with simple basic functions, and use more complex ones
as you continue with the creation of the project.
In addition to the step-by-step instructions, the Getting Started documents also give you
background information that explains the functions used and illustrate how they relate to each
other.
Target audience
The Getting Started documents are intended for beginners, but are also useful for users
migrating from a previous version of SIMATIC STEP 7 and WinCC.
Download
The documentation is available, free of charge at the Service&Support (https://
support.automation.siemens.com) portal in PDF form.
You can download the documents here:
STEP 7 Basic (http://support.automation.siemens.com/WW/view/en/40263542/0/en)
STEP 7 Professional (http://support.automation.siemens.com/WW/view/en/
28919804/133300)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 145
Introduction to the TIA Portal
6
6.1 User interface and operation
6.1.1 Starting, setting and exiting the TIA Portal
6.1.1.1 Starting and exiting the TIA Portal
Starting the TIA Portal
Follow the steps below to start the TIA Portal:
1. In Windows, select "Start > Programs > Siemens Automation > TIA Portal V11".
The TIA Portal opens with the last settings used.
Exiting the TIA Portal
Follow the steps below to exit the TIA Portal:
1. In the "Project" menu, select the "Exit" command.
If the project contains any changes that have not been saved, you will be asked if you wish
to save them.
Select "Yes" to save the changes in the current project and close the TIA Portal.
Select "No" to close the TIA Portal without saving the most recent changes in the project.
Select "Cancel" to cancel the closing procedure. The TIA Portal will remain open if you
select this option.
6.1.1.2 Overview of the program settings
Overview
The following table shows the application settings that you can make:
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 147
Group Setting Description
General settings User name The user name of the user. The user name is stored in the project
properties when a new project is created.
User interface language Language for the program interface
Mnemonic Specifies the mnemonics for programming:
"German" uses the German mnemonics, for example, "E1.0".
"International" uses international mnemonics, for example, "I1.0".
For information on the differences in the mnemonics of the
individual commands, refer to the description of the relevant
programming language.
Show list of recently used
projects
Number of entries in the list of recently used projects in the
"Project" menu
Show all message
windows
All message windows whose appearance was manually
suppressed are displayed again.
Open cascade
automatically in tooltips
After a brief time, the tooltips automatically expand to display a
cascade containing additional help. If this option is cleared, the
tooltips must be manually expanded.
Layout Load most recent project
during startup
The last opened project is opened automatically after the TIA
Portal starts.
Reset layout Resets the complete layout of the application to factory settings.
Start view Most recent view Starts the program in the last view that was used. This can be be
either the portal view or the project view.
Portal view The TIA Portal will always be started in the portal view,
irrespective of the last view you worked in.
Project view The TIA Portal will always be started in the project view,
irrespective of the last view you worked in.
View for objects in overview Details When several views are available, the detail view opens by
default, for example, in the overview window.
List When several views are available, the list view opens by default,
for example, in the overview window.
Thumbnails When several views are available, the symbol view opens by
default, for example, in the overview window.
Storage settings Recently used storage
location
When a project is saved the first time, the most recently used file
path is set by default.
Default storage location Enables the specification of file paths for:
Projects
Libraries
Data exchange Storage location for data
import
Imported files are searched for at this storage path by default.
Storage location for data
export
This is the default storage path for the data export.
Storage location for
support packages
When support packages are downloaded, they are stored in the
specified storage path and can be installed from there.
Storage location for log
files
Log files are stored at the location specified here.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
148 System Manual, 08/2011,
See also
Starting and exiting the TIA Portal (Page 147)
Resetting the user interface layout (Page 175)
Changing the settings (Page 151)
6.1.1.3 Overview of the script and text editor settings
Overview
The following table shows the available settings for script and text editors:
Group Setting Description
Font Font type and size Sets the font type and size for the text in text editors.
Font colors Color settings You can choose the colors for individual text elements from the
respective drop-down lists in the text editors. Optional settings
are available for the following text elements:
Text
Keywords
Comments
Translatable comments
Instructions
Scripts
Standard functions
System functions
Constant strings
Constant tags
Tags
Object models
Formal parameters
Reset to default Resets all font colors in editors to their factory settings.
Tabs Tab width Sets the width of tabs.
Use tabs Enables the use of tabs.
Use spaces Specifies use of space characters instead of tabs.
Indent Indention at start of
paragraph
Specifies whether the start of a new paragraph is to be indented.
The following selection options are available:
None
No indentation is used at the beginning of a paragraph in
editors.
Block
The first line of a paragraph in the editors is automatically
indented.
Smart
The program code is detected and the paragraphs are
automatically indented to improve readability of the syntax.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 149
Group Setting Description
View Show line numbers Displays the line numbers on the left side of the text.
Show white spaces Shows control characters within a text.
STL (statement list) Font type and size Sets the font type and size for STL program code.
SCL (Structured Control
Language)
Font type and size Sets the font type and size for SCL.
Indentation Creates SCL programs automatically with syntactically correct
indentation.
Show line numbers Shows the row numbers in SCL programs.
See also
Changing the settings (Page 151)
6.1.1.4 Overview of the print settings
Overview
The following table shows the available settings for printing:
Group Setting Description
General Always print table data as
pairs of values
Tables are printed as a list and not in tabular form. The corresponding
values are listed for each column.
Enable this option, for example, if you want to print a table that is too
large for the print area.
Always print data in tables All parameters of technology objects are printed in tabular format.
Print mask graphics if
possible
If the utilized editor supports this function, the contents of the editor
are printed not only as a table but rather as a complete graphic as it
appears on the screen.
Hardware
configuration
Active graphic view The graphics of network and device view are included in the printout.
Active table A table associated with an editor is included when printing with the
editor.
PLC Programming Zoom factor Specifies the size in which blocks are to be printed out.
With interface The interfaces of blocks are included in the printout.
With comments Comments on blocks are included in the printout.
With line numbers The line numbers of the program code are printed for text-based
programming languages.
HMI screens Show tab order In the printout you can specify the order in which the runtime objects
can be selected with the TAB key.
See also
Changing the settings (Page 151)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
150 System Manual, 08/2011,
6.1.1.5 Changing the settings
Procedure
To change the settings, proceed as follows:
1. Select the "Settings" command in the "Options" menu.
The "Settings" window is displayed in the work area.
2. Select the "General" group in the area navigation to change the settings described in the
previous sections. Or click on one of the other entries in area navigation to make settings
for your installed products.
3. Change the settings.
Result
The change will be adopted immediately, there is no need to save it explicitly.
See also
Overview of the program settings (Page 147)
Overview of the script and text editor settings (Page 149)
Overview of the print settings (Page 150)
6.1.2 Layout of the user interface
6.1.2.1 Views
Views
Two different views are available for your automation project:
The portal view is a task-oriented view of the project tasks.
The project view is a view of the components of the project, as well as the relevant work
areas and editors.
You can change over between the two views using a link.
6.1.2.2 Portal view
Purpose of the portal view
The portal view provides you with a task-oriented view of the tools. Here, you can quickly
decide what you want to do and call up the tool for the task in hand. If necessary, the view
changes automatically to the project view (Page 153) for the selected task.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 151
Layout of the portal view
The following figure shows an example of the components in the portal view:
Portals for different tasks
Actions for the selected portal
Selection panel for the selected action
Change to the project view
Display of the project that is currently open
Portals
The portals provide the basic functions for the individual task areas. The portals that are
provided in the portal view depends on the products that have been installed.
Actions for the selected portal
Here, you will find the actions available to you in the portal you have selected. You can call up
the help function in every portal on a context-sensitive basis.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
152 System Manual, 08/2011,
Selection panel for the selected action
The selection panel is available in all portals. The content of the panel adapts to your current
selection.
Change to the project view
You can use the "Project view" link to change to the project view.
Display of the project that is currently open
Here, you can obtain information about which project is currently open.
See also
Project navigation (Page 155)
Basics of the work area (Page 158)
Inspector window (Page 167)
Basics on task cards (Page 169)
Details view (Page 170)
6.1.2.3 Project view
Purpose of the project view
The project view is a structured view of all components of the project.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 153
Layout of the project view
The following figure shows an example of the components of the project view:
1
2
3
4
5
7
6
8
9 10 11
Title bar
Menu bar
Toolbar
Project tree (Page 155)
Work area (Page 158)
Task cards (Page 169)
Details view (Page 170)
Inspector window (Page 167)
Changing to the Portal view (Page 151)
Editor bar
Status bar with progress display
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
154 System Manual, 08/2011,
Title bar
The name of the project is displayed in the title bar.
Menu bar
The menu bar contains all the commands that you require for your work.
Toolbar
The toolbar provides you with buttons for commands you will use frequently. This gives you
faster access to these commands.
Changing to the portal view
You can use the "Portal view" link to change to the portal view.
Editor bar
The Editor bar displays the open editors. If you have opened a lot of editors, they are shown
grouped together. You can use the Editor bar to change quickly between the open elements.
Status bar with progress display
In the status bar, you will find the progress display for processes that are currently running in
the background. This also includes a progress bar that shows the progress graphically. Hover
the mouse pointer over the progress bar to display a tooltip providing additional information
on the active background process. You can cancel the background processes by clicking the
button next to the progress bar.
If no background processes are currently running, the status bar displays the last generated
alarm.
6.1.2.4 Project navigation
Function of the project tree
Using the project tree features gives you access to all components and project data. You can
perform the following tasks in the project tree:
Add new components
Edit existing components
Scan and modify the properties of existing components
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 155
Layout of project tree
The following figure shows an example of the project tree components:
1
2
3
4
5
6
7
8
9
Title bar
Toolbar
Project
Devices
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
156 System Manual, 08/2011,
Common data
Document information
Languages & resources
Online access
SIMATIC Card Reader
Title bar
The title bar of the project tree has a button for automatically and manually collapsing the
project tree. Once it is collapsed manually, the button is "Reduced" to the left-hand margin. It
changes from an arrow pointing left to one that is pointing right, and can now be used to reopen
the project tree. You can use the "Reduce automatically" button collapse to project tree
automatically when you do not need it.
See also: Maximizing and minimizing the work area (Page 160)
Toolbar
You can do the following tasks in the toolbar of the project tree:
Create a new user folder; for example, in order to group blocks in the "Program blocks"
folder.
Navigate forward to the source of a link and back to the link itself.
There are two buttons for links in the project tree. You can use these to navigate from the
link to the source and back.
Show an overview of the selected object in the work area.
When the overview is displayed, the lower-level objects and actions of the elements in the
project tree are hidden.
Project
You will find all the objects and actions related to the project in the "Project" folder, e.g.:
Devices
Languages & resources
Online access
Device
There is a separate folder for each device in the project, which has an internal project name.
Objects and actions belonging to the device are arranged inside this folder.
Common data
This folder contains data that you can use across more than one device, such as common
message classes, scripts and text lists.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 157
Document information
In this folder, you can specify the layout for project documentation to be printed at a later point.
Languages & resources
You can determine the project languages and texts in this folder.
Online access
This folder contains all the interfaces of the programming device / PC, even if they are not
used for communication with a module.
SIMATIC Card Reader
This folder is used to manage all card readers connected to the programming device / PC.
See also
Portal view (Page 151)
Project view (Page 153)
Basics of the work area (Page 158)
Inspector window (Page 167)
Basics on task cards (Page 169)
Details view (Page 170)
6.1.2.5 Work area
Basics of the work area
Function of the work area
The objects that you can open for editing purposes are displayed in the work area. These
objects include, for example:
Editors and views
Tables
You can open several objects. However, normally it is only possible to see one of these at a
time in the work area. All other objects are displayed as tabs in the Editor bar. If, you would
like to view two objects at the same time when performing certain tasks, you can tile the work
area either horizontally or vertically or undock elements of the work area. If no objects are
open, the work area will be empty.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
158 System Manual, 08/2011,
Layout of the work area
The following figure shows an example of a vertically split work area:
1 3
2 4
Title bar of left-hand editor
Work area of left-hand editor
Title bar of right-hand editor
Work area of right-hand editor
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 159
See also
Maximizing and minimizing the work area (Page 160)
Splitting the work area (Page 162)
Floating the work area elements (Page 162)
Using grouped elements of the work area (Page 163)
Minimizing and maximizing elements of the work area (Page 165)
Switching between the elements in the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Maximizing and minimizing the work area
You have the option to adapt the work area to make it as large as possible. You can use the
following function for this:
Maximizing the work area
You can close the task cards, project tree and inspector window with a single click. This
increases the size of the work area. You can minimize the work area again at any time in
order to return to the previous view.
Collapsing task cards, project tree, and Inspector window automatically
You can use the "Collapse automatically" option for the task cards, project tree, and
Inspector window. This function causes these items to collapse automatically when you
don't need them.
Maximizing and minimizing the work area
To maximize the work area, follow these steps:
1. Open an element such as an editor or a table.
The element appears in the work area.
2. Click the "Maximize" button in the title bar of the element.
The task cards, project tree and inspector window collapse, and the work area is shown
with its maximum dimensions.
To minimize the work area again, follow these steps:
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
160 System Manual, 08/2011,
1. Click the "Embed" button in the title bar of the displayed element.
This restores the view that existed before the work area was maximized. That is, if the task
cards, project tree, or Inspector window were expanded before, they will be expanded
again.
Collapsing task cards, project tree, and Inspector window automatically
To collapse the task cards automatically, follow these steps:
1. Click "Collapse automatically" in the title bar of the task cards.
The task cards collapse when you click anywhere outside the task cards.
2. To use the task cards, click the collapsed task cards.
3. The task cards expand and are available for use. The "Collapse automatically" option
remains enabled.
To collapse the project tree automatically, follow these steps:
1. Click "Collapse automatically" in the title bar of the project tree.
The project tree collapses when you click anywhere outside the project tree.
2. To use the project tree, click the collapsed project tree.
The project tree expands and is available for use. The "Collapse automatically" option
remains enabled.
To collapse the Inspector window automatically, follow these steps:
1. Click "Collapse automatically" in the title bar of the Inspector window.
The Inspector window collapses when you click anywhere outside the Inspector window.
2. To use the Inspector window, click the collapsed Inspector window.
The Inspector window expands and is available for use. The "Collapse automatically" option
remains enabled.
To disable the automatic collapse option, follow these steps:
1. Click "Expand permanently" again in the relevant window.
The Collapse automatically" option is disabled, and the window remains expanded.
See also
Basics of the work area (Page 158)
Splitting the work area (Page 162)
Floating the work area elements (Page 162)
Using grouped elements of the work area (Page 163)
Minimizing and maximizing elements of the work area (Page 165)
Switching between the elements in the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 161
Splitting the work area
You can split the work area vertically or horizontally.
Procedure
To split the work area vertically or horizontally, follow these steps:
1. In the "Window" menu, select the "Split editor space vertically" or "Split editor space
horizontally" command.
The element you have clicked and the next element in the Editor bar will be displayed either
next to one another or one above the other.
Note
If no elements are open in the work area, the "Split editor space vertically" and "Split editor
space horizontally" functions will not be available.
See also
Basics of the work area (Page 158)
Maximizing and minimizing the work area (Page 160)
Floating the work area elements (Page 162)
Using grouped elements of the work area (Page 163)
Minimizing and maximizing elements of the work area (Page 165)
Switching between the elements in the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Floating the work area elements
You can float work area elements in their own separate window:
Editors
Tables
Setting windows
Task cards
Inspector window
You can embed floating elements again in the work area at any time.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
162 System Manual, 08/2011,
Floating the work area elements
To float work area elements, follow these steps:
1. Click the "Float" button in the title bar of the element.
The element will be released from the work area and displayed in its own window. You can
now place the window wherever you wish. If you have minimized the window, you can
restore it via the editor bar.
Embedding elements in the work area
To embed elements in the work area again, follow these steps:
1. Click the "Embed" button in the title bar of the element.
The element will appear in the work area again.
See also
Basics of the work area (Page 158)
Maximizing and minimizing the work area (Page 160)
Splitting the work area (Page 162)
Using grouped elements of the work area (Page 163)
Minimizing and maximizing elements of the work area (Page 165)
Switching between the elements in the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Using grouped elements of the work area
If you open more than five elements of the same type, e.g., editors or tables, they are grouped
in the editor bar. You can use these groups as follows:
Displaying individual elements of a group
Displaying all elements of a group in separate windows
Embedding all displayed elements of a group in the work area
Minimizing all displayed elements
Closing all elements of a group
Displaying individual elements of a group
To display individual elements of a group, follow these steps:
1. In the editor bar, click the group containing the element you want to display.
All list of all available elements of the group is displayed.
2. Click the element that you want to display.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 163
Displaying all elements of a group in separate windows
To display all elements of a group in separate windows, follow these steps:
1. In the editor bar, right-click the group whose elements you want to display.
2. Select "Restore group" in the shortcut menu.
All elements of the group are displayed in separate, overlapping windows. Move the
windows in order to see the individual element, or choose an element via the group in the
editor bar.
Embedding all displayed elements of a group in the work area
To embed all elements of a group displayed in separate windows in the work area again, follow
these steps:
1. In the editor bar, right-click the group whose elements you want to embed.
2. Select "Embed group" in the shortcut menu.
All elements of the group are embedded in the work area again.
Minimizing all displayed elements
To minimize all elements of a group, follow these steps:
1. In the editor bar, right-click the group whose elements you want to minimize.
2. Select "Minimize group" in the shortcut menu.
All elements of the group are minimized. However, the minimized elements remain open
and can be quickly maximized again via the group in the editor bar.
Closing all elements of a group
To close all elements of a group, follow these steps:
1. In the editor bar, right-click the group whose elements you want to close.
2. Select "Close group" in the shortcut menu.
All elements of the group are closed. The group is removed.
See also
Basics of the work area (Page 158)
Maximizing and minimizing the work area (Page 160)
Splitting the work area (Page 162)
Floating the work area elements (Page 162)
Minimizing and maximizing elements of the work area (Page 165)
Switching between the elements in the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
164 System Manual, 08/2011,
Minimizing and maximizing elements of the work area
You can minimize the elements that are open in the work area, such as editors or tables, as
needed. However, an element remains open even if it has been minimized, and can quickly
be maximized again using the editor bar.
Minimizing elements in the work area
To minimize elements in the work area, follow these steps:
1. Click the "Minimize" button in the title bar of the element.
The element is minimized, but can still be accessed via the editor bar.
To minimize all elements at the same time, follow these steps:
1. In the "Window" menu, select the "Minimize all" command.
Maximizing elements in the work area
To maximize elements in the work area again, follow these steps:
1. Click the required element in the editor bar.
The element is maximized and appears in the work area.
See also
Basics of the work area (Page 158)
Maximizing and minimizing the work area (Page 160)
Splitting the work area (Page 162)
Floating the work area elements (Page 162)
Using grouped elements of the work area (Page 163)
Switching between the elements in the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Switching between the elements in the work area
You can switch between the elements in the work area at any time.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 165
Switching between the elements in the work area
To switch to the previous or next editor, follow these steps:
1. In the "Window" menu, select the "Next editor" or "Previous editor" command.
The next or previous editor will be displayed.
See also
Basics of the work area (Page 158)
Maximizing and minimizing the work area (Page 160)
Splitting the work area (Page 162)
Floating the work area elements (Page 162)
Using grouped elements of the work area (Page 163)
Minimizing and maximizing elements of the work area (Page 165)
Saving a layout of editors and tables (Page 166)
Saving a layout of editors and tables
You have the option of adapting editors and tables to meet your requirements. For example,
you can hide columns in tables that you don't need. You can then save your customized view.
Procedure
To save the layout of editors and tables in the work area, follow these steps:
1. Adapt the editor or table according to your requirements.
2. Click the "Remember Layout" button in the editor or table.
Result
The layout is saved. When you reopen the editor or table, this layout will be used.
See also
Basics of the work area (Page 158)
Maximizing and minimizing the work area (Page 160)
Splitting the work area (Page 162)
Floating the work area elements (Page 162)
Using grouped elements of the work area (Page 163)
Minimizing and maximizing elements of the work area (Page 165)
Switching between the elements in the work area (Page 165)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
166 System Manual, 08/2011,
6.1.2.6 Inspector window
Function of the Inspector window
Additional information on an object selected or on actions executed are displayed in the
inspector window.
Layout of the Inspector window
The following figures show the components of the Inspector window:
4
5
3
"Properties" tab
"Info" tab
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 167
"Diagnostics" tab
Navigation within the tabs:
Area navigation within the "Properties" tab
Lower-level tabs in the "Info" and "Diagnostics" tabs
"Properties" tab
This tab displays the properties of the object selected. You can change editable properties
here.
"Info" tab
This tab displays additional information on the object selected, as well as alarms on the actions
executed (such as compiling).
"Diagnostics" tab
This tab provides information on system diagnostics events, configured alarm events, and
connection diagnostics.
Navigation within the tabs
You can use area navigation and the lower-level tabs to display the information you require
within the tabs.
See also
Project navigation (Page 155)
Basics of the work area (Page 158)
Portal view (Page 151)
Project view (Page 153)
Basics on task cards (Page 169)
Details view (Page 170)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
168 System Manual, 08/2011,
6.1.2.7 Task cards
Basics on task cards
Function of task cards
Depending on the edited or selected object, task cards that allow you perform additional actions
are available. These actions include:
Selecting objects from a library or from the hardware catalog
Searching for and replacing objects in the project
Dragging predefined objects to the work area
The task cards available can be found in a bar on the right-hand side of the screen. You can
collapse and reopen them at any time. Which task cards are available depends on the products
installed. More complex task cards are divided into panes that you can also collapse and
reopen.
Layout of task cards
The following figure shows an example of the bar with the task cards:
Title bar
Content of the selected object
Title bar
The arrow for closing the details view is located in the title bar of the details view. After it has
closed, the direction in which the arrow is pointing changes from left to right. It can now be
used to reopen the details view.
Objects
The displayed content varies depending on the selected object. You can move the content of
objects from the details view to the required location using drag-and-drop.
See also
Project navigation (Page 155)
Basics of the work area (Page 158)
Inspector window (Page 167)
Basics on task cards (Page 169)
Portal view (Page 151)
Project view (Page 153)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 171
6.1.2.9 Overview window
Overview window
Functions of the Overview window
The Overview window supplements the project tree. The Overview window shows the contents
of the folder currently selected in the project tree.
In addition, you can perform the following actions in the Overview window:
Open objects
Display and edit the properties of objects in the Inspector window
Rename objects
Call object-specific actions from the shortcut menu
Compare objects side by side
Perform various object operations, such as inserting objects from the library via drag-and-
drop and moving, copying, pasting, and deleting objects
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
172 System Manual, 08/2011,
Layout of the Overview window
The following figure shows the components of the Overview window:
Overview window
Switch to the Details view
Switch to the List view
Switch to the Icon view
Move to higher level
Split the overview window in two. Either the right or left half of the overview window is synchronized. Clicking again
cancels the split.
Contents of the object selected in the project tree.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 173
Display forms of the Overview window
The content of the Overview window can be displayed as follows:
Details view
The objects are displayed in a list with additional information, such as the date of the last
change.
List view
The objects are displayed in a simple list.
Icon view
The objects are displayed as icons.
See also
Comparing objects (Page 174)
Showing or hiding additional columns (Page 174)
Comparing objects
You can display the contents of two folders or objects side by side in the Overview window.
The Overview window is split in half and you can display different contents on the left and right
sides.
In addition, you can use a drag-and-drop operation to move objects between the split windows.
Thus, for example, you can move contents from one window to the other.
Procedure
To split the Overview window in half or cancel the split, follow these steps:
1. In the toolbar, click on the "Synchronize left side" or "Synchronize right side" icon to split
the overview window. Either the left or the right side of the overview window synchronized
with the contents of the selected object in the project tree.
2. To cancel the split, click again on the previously selected icon.
See also
Overview window (Page 172)
Showing or hiding additional columns
In the details view of the Overview window, you can display more columns containing additional
information on an object and then hide them again. The columns available depend on the
selected object.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
174 System Manual, 08/2011,
Procedure
To show or hide additional table columns, follow these steps:
1. Right-click the title bar of the table.
2. Select the "Show/Hide" command in the shortcut menu, and select the columns you want
to display.
See also
Overview window (Page 172)
6.1.2.10 Resetting the user interface layout
Every change you make to the layout of the user interface is saved. The changes are thus
available even after a restart of the TIA Portal. For example, if you change the height and width
of a text editor or the division of a table, your changes are retained so that you don't have to
re-customize elements every time.
In some cases, however, it may be helpful to restore the original layout settings, for example,
to suit the preferences of another user or if a different user interface layout is desired.
Procedure
To reset the user interface settings to the factory settings, follow these steps:
1. Select the "Settings" command in the "Options" menu.
The "Settings" window is displayed in the work area.
2. Select the "General" group in the area navigation.
3. Click the "Reset to default" button under "Layout > Reset layout".
Result
The default settings for the user interface are restored.
See also
Overview of the program settings (Page 147)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 175
6.1.3 Keyboard shortcuts
6.1.3.1 Keyboard shortcuts for project editing
Editing a project
Function Key combination Menu command
Open a project <Ctrl+O> Project > Open
Close a project <Ctrl+W> Project > Close
Save a project <Ctrl+S> Project > Save
Save a project under a different name <Ctrl+Shift+S> Project > Save as
Print project <Ctrl+P> Project > Print
Compile a project <Ctrl+B> Edit > Compile
Undo last action <Ctrl+Z> Edit > Undo
Redo last action <Ctrl+Y> Edit > Redo
Editing objects within a project
Function Key combination Menu command
Rename a project <F2> Edit > Rename
Highlight all objects in an area <Ctrl+A> Edit > Select all
Copy an object <Ctrl+C> Edit > Copy
Cut an object <Ctrl+X> Edit > Cut
Paste an object <Ctrl+V> Edit > Paste
Delete an object <Del> Edit > Delete
Find an object <Ctrl+F> Edit > Find and replace
Replace an object <Ctrl+H> -
Calling up the help function
Function Key combination Menu command
Calling up the help function <F1> or <Shift+F1> Help > Show help
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
176 System Manual, 08/2011,
6.1.3.2 Keyboard shortcuts for windows
Opening and closing windows
Function Key combination Menu command
Open/close project tree <Ctrl+1> View > Project tree
Opening/closing the detailed view <Ctrl+4> View > Details view
Opening/closing the overview <Ctrl+2> View > Overview
Opening/closing a task card <Ctrl+3> View > Task card
Open/close inspector window <Ctrl+5> View > Inspector window
Close all editors <Ctrl+Shift+F4> Window > Close all
Open the shortcut menu <Shift+F10> -
6.1.3.3 Keyboard shortcuts in the project tree
Keyboard shortcuts in the project tree
Function Key combination
Jump to the start of the project tree <Home> or <Page Up>
Jump to the end of the project tree <End> or <Page Down>
Open folder <Arrow Right>
Close folder <Arrow Left>
6.1.3.4 Keyboard shortcuts in tables
General keyboard shortcuts in tables
Function Key combination
Place a cell in edit mode <F2> or <Return>
Open drop-down list in a cell <Return>
Close drop-down list in a cell <Esc>
Navigate in tables
Function Key combination
Go to the next cell <Arrow keys>
Go to the next editable cell on the right <Tab>
Go to the next editable cell on the left <Shift+Tab>
Move a screen upwards <PgUp>
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 177
Function Key combination
Move a screen downwards <PgDn>
Go to the first cell in the row <Home>
Go to the last cell in the row <End>
Go to the first cell in the table <Ctrl+Home>
Go to the last cell in the table <Ctrl+End>
Go to the top cell in the column <Ctrl+up arrow>
Go to the bottom cell in the column <Ctrl+down arrow>
Highlighting areas in tables
Function Key combination
Highlight a column <Ctrl+space bar>
Highlight a row <Shift+space bar>
Highlight all cells <Ctrl+A>
Highlight to expand a cell <Shift+arrow keys>
Extend highlighting to the first visible cell <Shift+PgUp>
Extend highlighting to the last visible cell <Shift+PgDn>
Extend highlighting to the first row <Ctrl+Shift+up arrow>
Extend highlighting to the last row <Ctrl+Shift+down arrow>
Extend highlighting to the first cell in the row <Ctrl+Shift+left arrow>
Extend highlighting to the last cell in the row <Ctrl+Shift+right arrow>
6.1.3.5 Keyboard shortcuts for text editing
Editing text
Function Key combination
Switch to insert or overwrite mode <Insert>
Exit edit mode <Esc>
Delete <Del>
Delete characters <Backspace>
6.1.3.6 Using the on-screen keyboard
Introduction
When working with the TIA portal, you also have the Microsoft on-screen keyboard available.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
178 System Manual, 08/2011,
Displaying the on-screen keyboard
To display the on-screen keyboard, follow these steps:
1. In the "View" menu, select the "Screen keyboard" command.
Exiting the on-screen keyboard
To exit the on-screen keyboard, follow these steps:
1. In the "File" menu of the on-screen keyboard, select the "Exit" command.
6.1.4 Special features specific to the operating system
6.1.4.1 Influence of user rights
Restrictions when user rights are limited
The software provides several functions that require direct access to the hardware of the
programming device / PC and therefore also to the installed operating system. To make full
use of the range of functions, the software must cooperate closely with the operating system.
To ensure problem-free interaction, you should therefore be logged on to the operating system
with adequate user rights.
In particular, you may not be able to use functions requiring an online connection or those that
change the settings of interface cards if you work with limited user rights.
Recognizing restricted functions
You can recognize functions requiring special rights as follows:
A shield icon is displayed beside the function.
The function can be used but is regulated by the user account control.
A box is grayed out and cannot be accessed.
You require administrator privileges to access the box. In some operating system
environments, you can obtain administrator privileges by entering an administrator
password.
Note
A box being grayed out does not necessarily mean a lack of rights. You should also check
the additional information in the tooltip cascades to find out the conditions for editing the box.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 179
6.1.4.2 Expanding user rights
Counteracting restrictions due to user rights
Certain functions may not be available if you are not logged on to the operating system with
adequate rights. You can counteract these restrictions in the following ways:
Enabling of extended rights using Windows user account control
Logging on to the operating system with administrator privileges
Using temporary administrator rights
Enabling extended rights using the Windows user account control
To be able to use a function indicated by the shield icon of the Windows user account control,
follow these steps:
1. Click on the box or button with the shield icon.
The security prompt of the Windows user account control opens.
2. Follow the instructions of the Windows user account control and, when prompted enter an
administrator password, if possible.
The function can now be used once without restrictions.
Logging on to the operating system with administrator privileges
To be able to use a function that is disabled due to lack of user rights, follow these steps:
1. Close the software.
2. Log off from the operating system.
3. Log on to the operating system with administrator privileges.
4. Restart the software.
Using temporary administrator rights
To obtain administrator privileges temporarily, follow these steps:
1. Click the "Change settings" button. You will find this button in dialogs that allow the
temporary assignment of administrator privileges.
An operating system dialog box for entering an administrator password opens.
2. Enter an administrator password.
The settings can be temporarily changed. When you call the dialog again, the procedure must
be repeated.
Note
This function is not supported by all operating systems. If no "Change settings" button is
present or the button is grayed out, you will need to log on to the operating system with
administrator privileges instead.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Advanced V11.0 SP1
180 System Manual, 08/2011,
6.2 Help on the information system
6.2.1 General remarks on the information system
Quick answers to your questions
A comprehensive Help system is available for solving your tasks. It describes basic concepts,
instructions and functions. While working with the program, you also receive the following
support:
Roll-out for correct inputs in dialog boxes
Tooltips for information on elements of the user interface, for example text boxes, buttons
and icons. Some of the tooltips are supplemented by cascades containing more precise
information.
Help on the current context, on menu commands for example when you click on the keys
<F1> or <Shift+F1>.
The following figure shows an example of a cascading tooltip (top) and a roll-out (bottom):
Help
The Help system describes concepts, instructions and functions. It also contains reference
information and examples. The help opens in a separate window.
A navigation pane appears on the left side of the help window. You can also hide the navigation
pane to make room on the screen. The navigation pane provides you with the following
functions:
Table of contents
Search in the index
Full text search of the entire Help
Favorites
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 181
Identification of the topics in the Help according to the type of information
The help topics are identified by different symbols depending on the type of information they
contain.
Symbol Information type Explanation
Operating instructions Describes the steps to follow in order to carry out a particular task.
Example Contains a concrete example to explain the task.
Factual information Contains background information that you need to know to carry
out a task.
Reference Contains comprehensive reference information to refer back to.
Identification of the topics in the Help according to the target system
Depending on the products that are installed, the help system may contain sections that apply
only to specific devices. To be able to recognize such sections at a glance, you will find a note
in brackets in the table of contents. The search results in the full text search and in the index
are marked in the same way if they only apply to a specific device.
Roll-out
Certain text boxes offer information that rolls out and helps you to enter valid parameters and
values. The roll-out informs you about permissible value ranges and data types of the text
boxes.
The following figure shows a roll-out (yellow) and a roll-out error message (red), which indicates
an invalid value:
Tooltip
Interface elements offer you a tooltip for easier identification.
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
182 System Manual, 08/2011,
Tooltips, which have an arrow icon on the left, contain additional information in tooltip
cascades. If you position the mouse pointer briefly over the tooltip or click the arrow icon, this
information is displayed. The automatic display of tooltip cascades can be disabled.
If additional information is contained in the Help system, a link appears to the corresponding
Help topic in the cascade. If you click on the link, the corresponding topic opens in Help.
The following figure shows a tooltip with opened cascade:
See also
Disabling the automatic display of tooltip cascades (Page 186)
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 183
6.2.2 Opening the Help system
Opening the Help system
You can open the Help system in the following ways:
1. In the "Help" menu, select the "Show help" command or press <F1> to display the
corresponding help for the current context.
Or
1. Click on the link in a tooltip cascade to go directly to an additional point in the Help system.
6.2.3 Searching the Help system for keywords
Searching for keywords in the help text
To search the help topics for predefined keywords, follow these steps:
1. Click the "Show/hide table of contents" button in the help toolbar to display the table of
contents.
The table of contents is displayed and the "Index", "Search" and "Favorites" tabs are visible.
2. Open the "Index" tab.
3. Enter the search term in the input box or select the search term from the list of key words.
4. Click "Display".
6.2.4 Full-text searches
Full-text searches
To search the entire text for specific words, follow these steps:
1. Click the "Show/hide table of contents" button in the help toolbar to display the table of
contents.
The table of contents is displayed and the "Index", "Search" and "Favorites" tabs are visible.
2. Open the "Search" tab.
3. Type in your search term in the text box.
4. Refine your search if necessary using additional criteria:
Select "Search previous results" to start an additional search operation of your last
search results only.
Select "Search for similar words" to find words that differ only slightly from your search
term.
Select "Search titles only" to obtain only results that contain your search term in the title.
The contents of the Help topics are ignored during the search.
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
184 System Manual, 08/2011,
5. Click on the arrow button to the right of the search field to use logic operations. The following
logic operations are available:
Combine two or more search terms using the "AND" operator to find only Help topics
that contain all the search terms in the text.
Combine two or more search terms using the "OR" operator to find only Help topics that
contain one or more of the search terms in the text.
Combine two or more search terms using the "NEAR" operator to find only Help topics
that contain terms in close proximity to each other (eight words).
Precede a word with the "NOT" operator to exclude Help topics from the search that
contain this word.
6. Click on "List topics" to start the search.
The results are now listed with title, position and ranking. The "Position" column shows the
section in which the Help topic found is located. Sorting according to ranking is based on
the position of the Help topics found in the table of contents and based on the number of
hits in the Help topics.
6.2.5 Using favorites
Using favorites
You can save individual help topics as favorites. This saves you searching for the help topic
a second time.
Saving favorites:
To save a page as a favorite, follow these steps:
1. Open the help topic or the chapter you want to save as a favorite.
2. Click the "Show/hide table of contents" button in the help toolbar to display the table of
contents.
The table of contents is displayed and the "Index", "Search" and "Favorites" tabs are visible.
3. Open the "Favorites" tab.
4. Click the "Add" button.
The help topic or chapter is saved as a favorite and is available the next time you open the
help system.
Calling up favorites:
To call up a page from the favorites, follow these steps:
1. Click the "Show/hide table of contents" button in the help toolbar to display the table of
contents.
The table of contents is displayed and the "Index", "Search" and "Favorites" tabs are visible.
2. Open the "Favorites" tab.
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 185
3. Select the topic you want to open from the list.
4. Click the "Display" button.
Deleting favorites
To delete an entry from the favorites, proceed as follows:
1. Click the "Show/hide table of contents" button in the help toolbar to display the table of
contents.
The table of contents is displayed and the "Index", "Search" and "Favorites" tabs are visible.
2. Open the "Favorites" tab.
3. Select the topic you want to remove from the list.
4. Click the "Remove" button.
6.2.6 Printing help topics
Printing information
You can either print all the contents of the Help system or individual topics only.
Procedure
To select the topics you would like to print, follow these steps:
1. Click the "Display printing dialog" button.
The table of contents opens in a separate window.
2. Select the check boxes for the folders and help topics to be printed in the "Print help topics"
dialog.
3. Click the "Print" button to print the selected information.
The "Print" dialog opens.
4. Select the printer on which you want print the help topics.
5. Click "Properties" if you want to make additional printer settings.
6. Confirm your entries with "OK".
The help topics are printed out on the selected printer.
6.2.7 Disabling the automatic display of tooltip cascades
You can suppress the automatic display of tooltip cascades. Manual display remains possible.
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
186 System Manual, 08/2011,
Procedure
To disable the automatic display of tooltip cascades, follow these steps:
1. In the "Options" menu, select the "Settings" command.
2. Select the "General" group in the area navigation.
3. Disable the "Open cascade automatically in tooltips" check box in the "General settings".
If you want to display a tooltip cascade manually, click on the arrow icon within the tooltip.
See also
General remarks on the information system (Page 181)
6.2.8 Safety Guidelines
Safety guidelines
This Help manual contains you have to observe in order to ensure your personal safety, as
well as to prevent damage to property. The notices referring to your personal safety are
highlighted in the manual by a safety alert symbol, notices referring only to property damage
have no safety alert symbol. These 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 a safety alert symbol, 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 unintended result or situation can occur if the corresponding information is
not taken into account.
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 187
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.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation.
Commissioning and operation of a device/system may only be performed by qualified
personnel. Within the context of the safety notes 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.
Prescribed Usage
Note the following:
WARNING
This device 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, reliable operation of the
product requires proper transport, storage, positioning and assembly as well as careful
operation 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.
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Advanced V11.0 SP1
188 System Manual, 08/2011,
Editing projects
7
7.1 The basics of projects
Introduction
Projects are used to organize the storage of data and programs resulting from the creation of
an automation solution. The data that makes up a project includes the following:
Configuration data on the hardware structure and parameter assignment data for modules
Project engineering data for communication over networks
Project engineering data for the devices
Project hierarchy
Data is stored in a project in the form of objects. Within the project, the objects are arranged
in a tree structure (project hierarchy).
The project hierarchy is based on the devices and stations along with the configuration data
and programs belonging to them.
Common data of the project and online access, for example, are also displayed in the project
tree.
See also
Creating a new project (Page 190)
Opening projects (Page 190)
Saving projects (Page 192)
Deleting projects (Page 193)
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 189
7.2 Creating and managing projects
7.2.1 Creating a new project
Procedure
To create a new project, follow these steps:
1. Select the "New" command in the "Project" menu.
The "Create a new project" dialog opens.
2. Enter your project name and path or accept the proposed settings.
3. Click the "Create" button.
Result
The new project is created and displayed in the project tree.
See also
The basics of projects (Page 189)
Opening projects (Page 190)
Saving projects (Page 192)
Deleting projects (Page 193)
7.2.2 Opening projects
Procedure
To open an existing project, follow these steps:
1. Select the "Open" command in the "Project" menu.
The "Open project" dialog opens and includes the list of most recently used projects.
2. Select a project from the list and click "Open".
3. If the project you require is not included in the list, click the "Browse" button. Navigate to
the desired project folder, and open the project file. Projects of the TIA Portal V11 have the
extension ".ap11", while older projects from the TIA Portal V10 have the extension "ap10".
Result
The project opens in the project view.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
190 System Manual, 08/2011,
Notes on compatibility
When you open a project that was created with an older version of the TIA Portal, the project
is converted automatically to the current file format and saved as a new project. The
designation "_V11" is added to the file name of the new project.
If you want to open a project from a newer version, this is possible if the following conditions
are met:
The project was created with a different version of the TIA Portal V11, for example, a version
with an installed service pack.
The project does not contain any data that is incompatible with the current installation.
If the project to be opened contains data that was created with optional software, but the
corresponding software product is not installed, the following cases can occur:
Software components are missing, but none of them are essential:
A dialog appears listing the missing software components. After the project is opened, its
properties are displayed. You now have the opportunity to install the missing products. All
the devices contained in the project are available even if you do not install the missing
products. However, you can only work with the devices that are supported by the currently
installed software.
If devices are not supported because software is missing, they are marked with the following
symbol in the project tree:
At least one software package is required in order to open the project:
A dialog appears listing the missing software components. The essential package(s) are
marked. The project can only be opened if you install the missing components.
See also
The basics of projects (Page 189)
Creating a new project (Page 190)
Saving projects (Page 192)
Deleting projects (Page 193)
7.2.3 Displaying properties of the project
You can display the properties of a project. Properties include the following:
Metadata for the project
This includes the following information: creation time, author, file path, project size,
copyright , project languages, etc. Many of the attributes can be changed.
Project history
The project history contains an overview with important events in the project life cycle. Here
you can also call the log file for a migration.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 191
Support packages in the project
You can display an overview of the additional software needed to work with all devices in
the project.
Software products in the project
You can display an overview of all installed software products needed for the project.
Procedure
To display the project properties, follow these steps:
1. Select the open project in the project tree.
2. Select "Properties" in the shortcut menu of the project.
The dialog with the properties of the project opens.
3. Select the project properties in the area navigation that you want to have displayed.
7.2.4 Saving projects
You can save the project at any time either under the same or a different name. You can even
save a project when it still contains elements with errors.
Saving a project
To save a project, follow these steps:
1. Select the "Save" command in the "Project" menu.
All changes to the project are saved under the current project name.
Project Save as
To save a project under another name, follow these steps:
1. Select the "Save as" command in the "Project" menu.
The "Save current project as" dialog opens.
2. Select the project folder in the "Save in" box.
3. Enter the new project name in the "File name" box.
4. Confirm your entry with "Save".
The project is saved under the new name and opened.
See also
The basics of projects (Page 189)
Creating a new project (Page 190)
Opening projects (Page 190)
Deleting projects (Page 193)
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
192 System Manual, 08/2011,
7.2.5 Closing projects
Procedure
To close a project, follow these steps:
1. Select the "Close" command in the "Project" menu.
If you have made changes to the project since the last time you saved it, a message is
displayed.
2. Decide whether or not you want to save the changes.
7.2.6 Deleting projects
NOTICE
When you delete a project, the entire project data is removed from the storage medium.
Requirements
The project you want to delete is not open.
Procedure
Follow the steps below to delete an existing project:
1. Select the "Delete project" command in the "Project" menu.
The "Delete project" dialog opens and includes the list of most recently used projects.
2. Select a project from the list.
If the project you require is not included in the list, click the "Browse" button. Navigate to
the required project folder, and open the project file with the extension ".ap11".
3. Click the "Delete" button.
4. Click "Yes" to confirm. This starts the deletion of the project.
Result
The entire project folder is deleted from the file system.
See also
The basics of projects (Page 189)
Creating a new project (Page 190)
Opening projects (Page 190)
Saving projects (Page 192)
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 193
7.2.7 Working with multi-language projects
7.2.7.1 Project text basics
Texts in different languages in the project
When you enter texts while working on a project, you would normally do this in your own
language. If you then pass on the project to someone else who does not know this language,
this person will require a translation of the relevant texts to a language they know. This is why
all texts can be translated. In this way, you can ensure that anyone who is subsequently
confronted with the texts sees the texts in his/her language of choice.
Project language
Project languages are all languages in which a project will later be used. Based on the editing
language, all the texts can be translated to the various project languages. You specify the
languages that will be available in the project tree under "Languages & Resources > Project
languages".
Editing language
Every project has an editing language. When you enter texts, these are always created in the
editing language. You should therefore make sure that the editing language set is the language
in which you enter the texts. This avoids problems if you translate the texts later.
The editing language does not depend on the language of the user interface. You could, for
example, set English as the user interface language, but use Italian as the editing language.
If you enter texts, these will be created in this case in the project language "Italian", although
the user interface of the TIA Portal displays English.
You set the editing language in the project tree under "Languages & Resources > Project
languages > Editing language".
User texts and system texts
For clarification purposes, a distinction is made between user texts and system texts:
User texts are texts that the user created.
System texts are texts that are created automatically according to the configuration in the
project.
You manage the project texts in the project tree under "Languages & Resources > Project
texts".
Examples of multilingual project texts
You can, for example, manage the following project texts in more than one language:
Block titles and block comments
Network titles and network comments
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
194 System Manual, 08/2011,
Statement comments from STL programs
Comments in tables
Alarm texts
Operator-relevant texts
Text lists
Labels of buttons
Display names of recipes
Translating texts
There are three ways of translating texts.
Translating texts directly
You can enter the translations for the individual project languages directly in the "Project
texts" table. You will find this in the project tree under "Languages & Resources > Project
texts".
Translating texts using reference texts
You can change the editing language for shorter texts. All the text cells are filled again with
the default values and can be filled in the current language. As orientation, you can display
what you last entered in the box in the reference language. To do this, select the "Tasks"
task card and open the "Languages & resources".
Exporting texts and translating them externally
With larger volumes of text, you can export the texts to an Office Open XML file and translate
them with a normal table calculation program. You then import the translated texts again
into the TIA Portal.
Note
Using Asian project languages
East Asian project languages are only displayed correctly in Windows XP, if the option "Install
files for East Asian languages" is selected on the Languages tab of Regional and Language
Options in the Control Panel of Windows XP Professional.
See also
Overview of the program settings (Page 147)
Changing the settings (Page 151)
Application examples for multilanguage projects (Page 200)
7.2.7.2 Select project languages
All the texts can be displayed within a project in the same language that you selected for your
software user interface. This means that all project texts must exist in the corresponding
language. You can select the available project languages yourself.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 195
Requirement
You are in the project view.
A project is open.
Procedure
To select the project languages, follow these steps:
1. Click on the arrow symbol to the left of "Languages & Resources" in the project tree.
The elements below this are displayed.
2. Double-click on "Project languages".
In the work area, you will see a list of languages that you can select.
3. Select the required languages.
Result
All texts can be displayed in the activated languages if there is already a translation for these
languages.
7.2.7.3 Setting the editing language
All the texts in the project are created in the editing language when they are entered. If you
change the editing language, all future text input will be stored in the new editing language.
Requirement
You are in the project view.
A project is open.
Procedure
To change the editing language, follow these steps:
1. Click on the arrow symbol to the left of "Languages & Resources" in the project tree.
The lower-level elements are displayed.
2. Double-click on "Project languages".
The possible settings for the project languages are displayed in the work area.
3. Select the editing language in "General > Editing language".
7.2.7.4 Translating texts directly
If you use more than one language in your project, you can enter translations of individual
project texts directly in the selected project languages. To allow this, there is a list for user
texts and one for system texts with a column for every project language.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
196 System Manual, 08/2011,
Requirement
You are in the project view.
A project is open.
You have selected at least one further project language.
Procedure
To translate individual texts, follow these steps:
1. Click on the arrow symbol to the left of "Languages & Resources" in the project tree.
The elements below this are displayed.
2. Double-click "Project texts".
A list with the user texts in the project is displayed in the work area.
3. Click on "System texts" if you you want to edit the list of system texts rather than the user
texts.
4. You can improve the clarity of the lists if you have a lot of texts.
To group identical texts and to translate them all at once, click the "Switch on/off
grouping" button in the toolbar.
To hide texts that do not have a translation, click the "Filter for empty texts on/off" button
in the toolbar.
To further limit the displayed project texts to certain devices, select the devices for which
you want to display project texts in the drop-down list.
5. Enter the translation of the project texts in the relevant column.
Note
If there is no translation for a text in a particular language, the English text is displayed.
7.2.7.5 Translating texts using reference texts
Introduction
After changing the editing language, all texts are shown in input boxes in the new editing
language. If there is not yet a translation available for the newly set language, the input boxes
are empty or filled with default values.
If you enter text in an input box, this is saved in the current editing language. Following this,
the texts exist in two project languages for this input field, in the previous editing language and
in the current editing language. This makes it possible to create texts in several project
languages.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 197
You can display existing translations for an input box in other project languages. These serve
as a comparison for text input in the current editing language and they are known as the
reference language.
Note
The display of reference texts depends on the installed products and is not supported by
every editor.
Requirement
There is at least one translation into a different project language for an input field.
Procedure
To display the translation of an input cell in a reference language, follow these steps:
1. In the "Tasks" task card, select the "Languages & Resources" pane.
2. Select a reference language from the "Reference language" drop-down list.
Result
The reference language is preset. If you click in a text box, translations that already exist in
other project languages are shown in the "Tasks > Languages & Resources" task card.
See also
Application examples for multilanguage projects (Page 200)
7.2.7.6 Exporting and importing project texts
You can export project texts for translation and then reimport them. The texts are exported to
an Office Open XML file with the extension ".xlsx". This can be edited in Microsoft Excel or a
number of other spreadsheet programs.
The following export options are available:
Exporting individual project texts
Exporting all user texts or system texts at once
In this case, the export can be additionally limited by categories.
Note
Row limit in Microsoft Excel
Note that Microsoft Excel 2003 supports a maximum of 65536 rows. Microsoft Excel 2007
supports up to 1048576 rows.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
198 System Manual, 08/2011,
Exporting individual project texts
To export individual project texts, follow these steps:
1. Open the "Languages & Resources" folder in the project tree.
The lower-level elements are displayed.
2. Double-click "Project texts".
The project texts editor opens.
3. Choose the "User texts" or "System texts" tab in the editor, depending on which texts you
want to export.
4. Select the project texts you want to export.
5. Click the "Export project texts" icon in the toolbar of the editor.
The "Export" dialog box opens.
6. Choose the language you want to translate from in the "Source language" drop-down list.
7. Choose the language you want to translate to in the "Target language" drop-down list. The
drop-down list contains the project languages you specified previously. If the required
language is missing, you must first specify it in the project languages editor.
8. Specify a file path and a file name for the export file in the "Select file for export" input box.
9. Click "Export".
Exporting all system or user texts
To export all project texts, follow these steps:
1. Select the "Export project texts" command in the "Tools" menu.
The "Export" dialog box opens.
2. Choose the language you want to translate from in the "Source language" drop-down list.
3. Choose the language you want to translate to in the "Target language" drop-down list. The
drop-down list contains the project languages you specified previously. If the required
language is missing, you must first specify it in the project languages editor.
4. In "Select content", select the check box "User texts" to export user texts. To export system
texts, select "System texts". To export both user texts and system texts, select both check
boxes.
5. In "Select content", select the required text categories for the user texts or the system texts.
6. In the "Export file" input field, specify a file name for the export file.
7. In the "Path" input field, select a path in the data system to which the export file is to be
saved.
8. Click "Export".
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 199
Importing project texts
To import a file containing project texts, follow these steps:
1. Select the "Import project texts" command in the "Tools" menu.
The "Import" dialog box opens.
2. Select the path and the file name of the import file from the "Select file for import" field.
3. Select the "Import base language" check box if you have made changes to the base
language in the export file and you want to overwrite the entries in the project with the
changes.
4. Click "Import".
See also
Application examples for multilanguage projects (Page 200)
7.2.7.7 Application examples for multilanguage projects
Introduction
Let us assume you are working in a team with colleagues some of whom speak English, some
French and some German. You have created a project with the TIA Portal and have already
created a functioning configuration.
To allow your other colleagues to be able to keep track of the project, you would like all devices
being used to have comments in English and German. First, you would like to enter the
comments in German. Following this, to save time and costs, you want to have the texts
translated into English in a spreadsheet program by an external translation office.
In addition to this, you also want a single comment for a particular device in French so that
your French-speaking colleague can continue working on this device.
The section below describes an example of how you can achieve this with the tools of the TIA
Portal.
Translating the project into English
To enter the comments in German and to have them translated into English later, follow these
steps:
1. Set the editing language to "German" and fill all the comment boxes with the relevant texts
in German.
On the device selected from the French-speaking colleague, enter, for example "Unser
neues Gert" in German first.
All the comments are now stored in German.
2. Export all user texts to an Office Open XML file with the extension ".xlsx".
3. Have the user texts contained in the file translated into English in a spreadsheet program
such as Microsoft Excel.
4. Import the file into the TIA Portal after it has been translated.
All texts are now available in German and English.
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
200 System Manual, 08/2011,
Translating a single comment field to French
To translate an individual comment field to French, follow these steps:
1. Open the comment box for the device on which the French-speaking colleague will be
working.
2. Open the "Languages & Resources" pane in the "Tasks" task card.
3. Set "French" as the editing language in the "Languages & Resources" pane. As the
reference language, set, for example, "English".
Since no translation has yet been installed in French, the comment box is empty. In the
"Languages & Resources" pane, the English translation "Our new device" is displayed as
a reference.
4. Orientating yourself on the English reference text enter "Notre nouvel appareil" in the
comment box.
The comment for this device is now available in the languages German, English and French.
See also
Project text basics (Page 194)
Exporting and importing project texts (Page 198)
Translating texts using reference texts (Page 197)
Editing projects
7.2 Creating and managing projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 201
7.3 Editing project data
7.3.1 Compiling and loading project data
7.3.1.1 Compiling project data
General information on compiling project data
Compiling project data
During compilation, project data is converted so that it can be read by the device. Hardware
configuration data and program data can be compiled separately or together. You can compile
the project data for one or more target systems at the same time.
The following project data must be compiled prior to loading:
Hardware project data, for example, configuration data of the devices or networks and
connections
Software project data, for example, program blocks or process screens
Scope of the compilation
When you compile project data, you have the following options depending on the device
involved:
All
Hardware configuration
Software
Software (rebuild all blocks)
See also
Compiling project data (Page 202)
Compiling project data
The following section describes the general procedure for compiling project data in the project
tree. You will find details of how certain objects are compiled and any special points to note in
the online help of the product.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
202 System Manual, 08/2011,
Procedure
To compile project data, follow these steps:
1. In the project tree, right-click on the device for which you want to compile the project data.
2. Select the option you require in "Compile" submenu of the shortcut menu.
Note
Note that the options available to you depend on the selected device.
The project data is compiled. You can check whether or not the compilation was successful
in the Inspector window with "Info > Compile".
Canceling compilation operation
You can cancel compilation at any time. Proceed as follows:
1. Click the "Cancel" button in the status bar next to the progress bar. If the TIA Portal is
currently processing multiple asynchronous processes, you can use the Up or Down arrow
to change to the progress display of the compilation operation you want to cancel.
2. Click "Yes" to confirm.
See also
General information on compiling project data (Page 202)
7.3.1.2 Downloading project data
General information on loading
Introduction
In order to set up your automation system, you must download the project data you generated
offline to the connected devices. This project data is generated, for example when configuring
hardware, networks, and connections or when programming the user program or when
creating recipes. The first time you download, the entire project data is downloaded. During
later loading operations, only changes are downloaded.
You can download the project data to the following destinations:
Devices
Accessible devices
Memory cards
Depending on the object you want to download, you have the following options:
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 203
All
Both hardware configuration as well as software are downloaded to the destination.
Hardware configuration
Only the hardware configuration is downloaded to the destination.
Software
Only the objects that differ online and offline are downloaded to the destination.
Software (all blocks)
All blocks are downloaded to the destination.
You can also upload project data already contained in a device back to your project. You have
the following options:
Uploading a complete device
All relevant data of the device is uploaded to the project.
Uploading blocks and parameters
Only the blocks and parameters from the device are uploaded to the project.
See also
Downloading project data to a device (Page 204)
Loading project data to an accessible device (Page 205)
Downloading project data to a memory card (Page 206)
Uploading project data from a device (Page 207)
Downloading project data to a device
The following section describes the general procedure for downloading project data to a device.
You will find details of how certain objects are downloaded and any special points to note in
the online help of the product.
Requirement
The project data is consistent.
Each device to which you want to download is accessible via an online access.
Procedure
To download the project data to the selected devices, follow these steps:
1. Select one or more devices systems in the project tree.
2. Right-click on a selected element.
The shortcut menu opens.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
204 System Manual, 08/2011,
3. Select the option you require in the shortcut menu of the "Download to device" submenu.
Note
Note that the options available to you depend on the selected device.
When necessary, the project data is compiled.
If you had previously established an online connection, the "Load preview" dialog opens.
This dialog displays messages and proposes actions necessary for downloading.
If you had not previously established an online connection, the "Extended download to
device" dialog opens, and you must first select the interfaces via which you want to
establish the online connection to the device.
See also: Establishing and canceling an online connection (Page 2680)
4. Check the messages in the "Load preview" dialog, and select the actions in the "Action"
column, if necessary.
NOTICE
Performing the proposed actions while the plant is in operation can cause serious bodily
injury and property damage in the event of malfunctions or program errors.
Make sure that no dangerous situations can arise before you start the actions!
As soon as loading becomes possible, the "Load" button is enabled.
5. Click the "Load" button.
6. The loading operation is performed. The "Load results" dialog then opens. In this dialog,
you can check whether or not the loading operation was successful and take any further
action that may be necessary.
7. Click the "Finish" button.
Result
The selected project data was downloaded to the devices.
See also
General information on loading (Page 203)
Loading project data to an accessible device (Page 205)
Downloading project data to a memory card (Page 206)
Uploading project data from a device (Page 207)
Loading project data to an accessible device
The following section describes the general procedure for downloading project data to an
accessible device in the project tree. You will find details of how certain objects are downloaded
and any special points to note in the online help of the product.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 205
Requirement
The accessible devices are displayed.
See also: Displaying accessible devices (Page 2677)
Procedure
To load project data to an accessible device, follow these steps:
1. In the project tree, drag the folder containing your device to the accessible device.
The "Load preview" dialog opens. This dialog displays messages and proposes actions
necessary for downloading.
2. Check the messages, and select the actions in the "Action" column, if necessary.
NOTICE
Performing the proposed actions while the plant is in operation can cause serious bodily
injury and property damage in the event of malfunctions or program errors.
Make sure that no dangerous situations can arise before you start the actions!
3. As soon as loading becomes possible, the "Load" button is enabled.
4. Click the "Load" button.
The loading operation is performed. The "Load results" dialog then opens. In this dialog,
you can check whether or not the loading operation was successful and take any further
action that may be necessary.
5. Click the "Finish" button.
See also
General information on loading (Page 203)
Downloading project data to a device (Page 204)
Downloading project data to a memory card (Page 206)
Uploading project data from a device (Page 207)
Downloading project data to a memory card
Requirement
The memory card is displayed.
See also: Accessing memory cards (Page 243)
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
206 System Manual, 08/2011,
Procedure
To download project data to a memory card, follow these steps:
1. Use a drag-and-drop operation in the project tree to take the project data you want to
download and move it to the memory card.
The "Load preview" dialog opens. This dialog displays messages and proposes actions
necessary for downloading.
2. Check the messages, and select the actions in the "Action" column, if necessary.
As soon as loading becomes possible, the "Load" button is enabled.
3. Click the "Load" button.
The loading operation is performed. The "Load results" dialog then opens. In this dialog,
you can check whether or not the loading operation was successful and take any further
action that may be necessary.
4. Click the "Finish" button.
See also
General information on loading (Page 203)
Downloading project data to a device (Page 204)
Loading project data to an accessible device (Page 205)
Uploading project data from a device (Page 207)
Uploading project data from a device
The following section describes the general procedure for uploading project data from a device.
Which project data you can upload from a device depends on the products installed.
You have the following basic options for uploading project data from a device to your project:
Uploading a device to a programming device or PC
You can use this option to start with an empty project and upload existing project data
directly from a device.
Uploading from device
Only certain project data are uploaded from the device to the project. You will find the project
data that can be downloaded in the online help of the product.
Requirement
A project is open.
The hardware configuration and software to be downloaded have to be compatible with the
TIA Portal. If the data on the device was created with a previous program version or with
a different configuration software, please make sure they are compatible.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 207
Uploading a device to a programming device or PC
To upload the complete device to your project, follow these steps:
1. Select the project name in the project tree.
The "Upload device to PG/PC" command in the "Online" menu is then enabled.
2. In the "Online" menu, select the "Upload device to PG/PC" command.
The "Upload device to PG/PC" dialog opens.
3. Select the type of interface you want to use for the load operation in the "Type of the PG/
PC interface" drop-down list.
4. Select the interface to be used from the "PG/PC interface" drop-down list.
5. Click the "Configure interface" button to the right of the "PG/PC interface" drop-down list to
adapt the settings for the selected interface.
See also: Establishing and canceling an online connection (Page 2680)
6. In the accessible devices table, select the device from which you want to upload project
data.
7. Click on "Load".
Depending on the selected device, a dialog appears in which you have to enter additional
information, such as the position of the module rack.
The project data of the device is uploaded to the project. You can edit it offline and then
download it to the device again.
Or:
1. Open the accessible devices in the project tree.
See also: Displaying accessible devices (Page 2677)
2. Use a drag-and-drop operation in the project tree to move the accessible devices to the
project.
Depending on the selected device, a dialog appears in which you have to enter additional
information, such as the position of the module rack.
The project data of the device is uploaded to the project. You can edit it offline and then
download it to the device again.
Uploading from device
To upload only certain project data from a device to your project, follow these steps:
1. Establish an online connection to the device from which you want to download the project
data.
See also: Establishing and canceling an online connection (Page 2680)
2. Select an element in the project tree that allows uploading of project data.
As a result, the "Upload from device" command in the "Online" menu becomes enabled.
3. Select the "Upload from device" command in the "Online" menu.
The "Upload preview" dialog box opens.
4. Check the messages in the "Upload preview" dialog, and select the necessary actions in
the "Action" column.
As soon as uploading becomes possible, the "Upload from device" button is enabled.
5. Click the "Upload from device" button.
The loading operation is performed.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
208 System Manual, 08/2011,
See also
General information on loading (Page 203)
Downloading project data to a device (Page 204)
Loading project data to an accessible device (Page 205)
Downloading project data to a memory card (Page 206)
7.3.2 Comparing project data
7.3.2.1 Basics of project data comparison
Function
You have the option of comparing project data of the same type in order to determine possible
discrepancies. For example, you can compare a hardware configuration with another hardware
configuration.
A simple online-online comparison is already performed when you establish an online
connection. During this process, comparable objects in the project tree are marked with icons
that represent the result of the comparison. Beyond this marking, you can use the comparison
editor to compare project data and have detailed information displayed. You can also select
actions for non-identical objects in the comparison editor.
In addition to the online-offline comparison, there is also an offline-offline comparison available.
This allows you to compare project data of two devices within one project or from different
projects.
Which project data you can compare depends on the products installed.
Comparison icons
The result of the comparison is indicated by means of icons. The following table shows the
relevant icons and their meaning:
Icon Meaning
Folder contains objects whose online and offline versions differ
Comparison result is not known
Online and offline versions of the object are identical
Online and offline versions of the object are different
Object only exists offline
Object only exists online
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 209
7.3.3 Protecting project data
7.3.3.1 Protection concept for project data
Introduction
You can protect your project data from unauthorized access. These include, for example:
Access protection for devices
Copy and display protection of objects
Restrictions for printouts of know-how-protected objects
Note that every protection mechanism is not available for all objects. How to protect specific
objects is described in the online help of the product.
Revoking access rights for devices
If you want to execute a function that is password-protected by means of the device protection
level, you are prompted to enter a password. When the password is entered correctly, you can
execute the required function. You continue to have access rights on the device until you close
the TIA Portal.
If you want to reactivate password protection while the TIA Portal is open, you can explicitly
revoke the access rights for a device. As a result, certain functions for the protected device
cannot be executed until the correct password is entered again. You specify the functions for
which a password must be entered when you assign the device protection level.
See also
Printing project data (Page 228)
7.3.3.2 Revoking access rights for devices
Requirement
A protection level has been set for the device.
A protected function for the device has been enabled by entering the password.
Procedure
To revoke the access rights for the device, follow these steps:
1. Select the device for which you want to revoke access rights in the project tree.
2. Select the "Delete access rights" command in the "Online" menu.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
210 System Manual, 08/2011,
Result
The access rights are revoked, and starting from now the user will be prompted to enter the
password again to execute a password-protected function on the device. The function can only
be executed if the correct password is entered.
If the device has an online connection, it will be disconnected.
See also
Protection concept for project data (Page 210)
7.3.4 Printing project contents
7.3.4.1 Documentation settings
Introduction
Once a project is created, the contents can be printed in an easy-to-read format. You may print
the entire project or individual objects within the project. A well-structured printout is helpful
when editing the project or performing service work. The printout can also be used for your
customer presentations or as full system documentation.
You can prepare the project in the form of standardized circuit manuals and print it in a uniform
layout. You can limit the scope of the printout. You have the option to print to the entire project,
individual objects along with their properties, or a compact overview of the project. In addition,
you can print the contents of an open editor.
Improving the printout with frames and cover pages.
You can design the appearance of the printed pages according to your own requirements, for
example, with your company logo or company layout. You can create your own printout
templates with frames that will surround the project data in the printout. You create the frames
in an external layout program or an image editing program and save the file in PDF or EMF
format. The file can then be imported as a background image. You can insert placeholders for
data from previously entered document information on the background. These will be filled
automatically with the appropriate metadata during printing.
If you want to avoid designing your own template, there are ready-made frames and covers
pages available. These include templates complying with the ISO standard for technical
documentation.
If you already have cover pages or frames from earlier versions of the TIA Portal or you have
templates and cover pages in EMF or PDF file format, you can import these.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 211
Modular structure of a printout
An printout generally consists of the following components:
Cover page (only when printing from the project tree)
Table of contents (only when printing from the project tree)
Name and path of an object within the project tree
Object data
Printout of the cover page or the table of contents can be deactivated in the "Print" dialog.
See also
Creating a frame (Page 217)
Creating a cover page (Page 217)
Editing cover pages and frames (Page 219)
Entering document information (Page 215)
7.3.4.2 Printout of project contents
Availability of print function
The following contents can be printed:
An entire project in the project tree
One or more project-related objects in the project tree
Contents of an editor
Tables
Libraries
Diagnostics view of the Inspector window
It is not possible to print in the following areas:
Portal view
Detailed view
All tabs of the Inspector window, except the diagnostics view
All task cards, except the libraries
Most of the dialogs
Scope of printout
To be able to print, at least one printable element has to be selected.
If a selected object is printed, all subordinate objects are also printed. For example, if a device
is selected in the project tree, all of its data is also printed.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
212 System Manual, 08/2011,
When table contents are printed, all lines in the table in which a cell is selected are printed. In
order to print one or more table columns, the desired columns must be selected. If no individual
cells or columns are selected, the entire table is printed.
Limitations when printing
In general, it is possible to print all objects that can be visualized on the user interface.
Conversely, this means that you cannot print objects that you do not have access to. If a printout
fails, possible reasons may include the following:
A valid license does not exist for displaying an object.
There is no device description for an object.
A software component needed to display an object is not installed.
See also
Printing project data (Page 228)
7.3.4.3 Changing the print settings
Changing the print settings
You can specify general print settings that are retained even after the TIA Portal is closed and
re-opened. Some settings are dependent on the products installed. The following settings are
possible in every case:
Always print table data as pairs of values
If this option is selected, tables are not printed in tabular format but rather as a pairs of key
and value.
Example:
Object name Property 1 Property 2
Object A Value A1 Value A2
Object B Value B1 Value B2
In this case, the printout has the following appearance:
Object A
Property 1: Value A1
Property 2: Value A2
Object B
Property 1: Value B1
Property 2: Value B2
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 213
Printing mask editors
Always print data in tables
All parameters of technology objects are printed in tabular format.
Print mask graphics if possible
If the utilized editor supports this function, the contents of the editor are not printed as a
table but rather as a complete graphic as it appears on the screen.
Procedure
To change the print settings, follow these steps:
1. Select the "Settings" command in the "Options" menu.
The "Settings" window is displayed in the work area.
2. Select the "General" group.
3. Select the desired default settings in the "Print settings" area.
The changes are applied immediately and are retained for all projects, even after the TIA
Portal is closed.
See also
Overview of the print settings (Page 150)
7.3.4.4 Specifying the print layout
Specifying the print layout
If you do not want to rely on ready-made print templates, you can specify your own cover page
or your own layout for the individual pages. Your designs are saved together with the respective
project.
Your designs for the cover page and your templates for the page layout can be found in the
project tree under the "Documentation information" group. You will also find metadata on the
project there under the entry "Document information". For subsequent print operations, you
can customize the appearance of the printout in the "Print" dialog using the saved cover pages
and page layout templates and the available metadata.
Designing the cover page
The cover page can be customized. You can insert a background graphic and provide
placeholders for text on the page. The placeholders are automatically filled with data from a
documentation information during printing.
Cover pages are located in the project tree under the "Documentation information > Cover
pages" group.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
214 System Manual, 08/2011,
Designing the content page
The regular pages of a printout can contain the following elements:
Frame with static content, such as a company logo
Place holders for text, such as the name of the project, the page number, and the time the
printout was started
Several different values for the individual placeholders can be specified in the document
information. Other values, such as the project name, are preassigned and are inserted
automatically during printing.
Footnote
The footnote is always output below the content area.
Content area
You can specify an area where the printed content is to be embedded.
The design of the content pages is saved in Frames. The individual frames are located in the
project tree under the "Documentation information > Frames" group.
7.3.4.5 Entering document information
You can enter metadata in the document information for every project. In addition, a print frame
and a cover page are specified in the document information. You can create different
information, if required, to enable you to quickly switch between different document information
containing different information, frames, cover pages, page sizes, and page orientations when
printing. For example, this is useful if you want to generate printouts in different languages and
different document information is provided for each language.
In the documentation editor, you can specify placeholders on the cover page or in the frame
of the regular pages. These placeholders can be automatically replaced with metadata from
the documentation information during printing.
The various document information are therefore part of the printing function and specify the
print layout and print content.
Procedure
To add metadata, follow these steps:
1. To create new document information, double-click "Add new document information" under
"Documentation information > Document information" in the project tree.
The new document information is created and opened immediately.
2. Enter a name for the set in the "Name" field.
3. Fill in the individual fields with the metadata for the project.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 215
7.3.4.6 Managing cover pages and frames
Using cover pages and frames
Uses for cover pages
You can give your plant documentation printouts a professional appearance by adding a cover
page. You can design your own cover page or use ready-made cover pages. Ready-made
cover pages can be adapted and stored again as a template.
Cover pages can be saved in global libraries where they are available for use across projects.
Cover pages are designed for use as a right printed page only.
Uses of frames
You can embed the regular pages of your plant documentation inside a consistently uniform
page frame. The frame can contain placeholders for project metadata, which is stored in the
document information. It can also contain graphic elements that you design yourself.
You can create your own frames or rely on ready-made page frames. You can adapt a ready-
made page frame and then store it again as a new frame.
Like cover pages, frames can be saved in global libraries where they are available for use
across projects.
Frames are designed for use on right printed pages only.
Cover pages and templates in the project tree
Cover pages and frames associated with the project are stored in the project tree under the
entry "Documentation information". There are separate folders here for frames and cover
pages.
The following actions are available in the project tree for cover pages and frames.
Creating your own subfolders
Copying and pasting
Inserting cover pages and frames from the "Documentation templates" system library
Copying cover pages and templates to a global library
Cover pages and templates in libraries
The "Documentation templates" system library contains a few cover pages and templates that
are available in every project. The cover pages and templates can be moved from there to the
project tree using a drag-and-drop operation. You can then adapt the cover pages and
templates in the project tree according to the requirements of your project.
Cover pages and templates can be moved from the project tree to a global library. Afterwards,
these are available in every project.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
216 System Manual, 08/2011,
See also
Library basics (Page 245)
"Libraries" task card (Page 246)
Global library basics (Page 257)
Using ready-made frames and cover pages (Page 218)
Creating a frame
You can create any number of frames for each project. The frames are stored in the project
tree below the "Documentation information > Frames" group. You can assign a frame to all
document information. When you select document information for printing, its associated frame
is used.
Procedure
To create a new frame, follow these steps:
1. Double-click the entry "Add new frame" below the "Documentation information > Frames"
group in the project tree.
The "Add new frame" dialog opens.
2. Enter a name for the frame in the "Name" field.
3. Choose the paper size from the "Paper type" drop-down list.
4. Choose whether the page is to be created in portrait or landscape format in the "Orientation"
drop-down list.
Click the "Add" button.
Result
A new frame is created. The frame is then opened automatically in the documentation editor
where it can be edited.
See also
Editing cover pages and frames (Page 219)
Creating a cover page (Page 217)
Creating a cover page
You can create any number of cover pages for the printout for each project. The cover pages
are stored in the project tree below the the "Documentation information > Cover pages" group.
You can assign a cover page to all document information. When you select specific document
information for printing, its associated cover page is used.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 217
Procedure
To create a new cover page, follow these steps:
1. Double-click the entry "Add new cover page" below the "Documentation information > Cover
pages" group in the project tree.
The "Add new cover page" dialog box opens.
2. Enter a name for the cover page in the "Name" field.
3. Choose the paper size from the "Paper type" drop-down list.
4. Choose whether the page is to be created in portrait or landscape format in the "Orientation"
drop-down list.
Click the "Add" button.
Result
A new cover page is created. The cover page is then opened automatically in the
documentation editor where it can be edited.
See also
Editing cover pages and frames (Page 219)
Creating a frame (Page 217)
Using ready-made frames and cover pages
The TIA Portal comes with some ready-made frames and cover pages. These can change
according to your wishes.
Procedure
To create and edit the ready-made frames and cover pages, follow these steps:
1. Open the "Global libraries" pane in the "Libraries" task card.
2. In the "Templates" folder, open the "Cover Pages" or "Frames" folder.
3. Drag a cover page or a frame from one of the folders into the project tree and drop it into
one of the following folders:
For frames: "Document information > Frames"
For cover pages: "Document information > Cover pages".
The ready-made frame or cover page can now be used in the project.
4. Double-click on the new entry in the project tree click to edit the frame or the cover page.
See also
Using cover pages and frames (Page 216)
Editing cover pages and frames (Page 219)
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
218 System Manual, 08/2011,
7.3.4.7 Designing cover pages and frames
Editing cover pages and frames
The documentation editor is a graphical editor which allows you to design frames and cover
pages for your plant documentation. You can place images or text elements on the frame and
the cover pages in the document editor. The text elements are either static or they are
automatically filled during printing with the data from the document information that you have
selected in the print dialog.
Procedure
To edit a cover page or a frame in the documentation editor, follow these steps:
1. In the project tree, double-click on the entry for an existing cover page or frame under the
"Documentation information > Frames " or "Documentation information > Cover pages"
group.
The documentation editor opens.
2. Design the cover page or frame as desired.
3. Close the documentation editor.
The changes to the cover page or frame are applied automatically.
See also
Creating a cover page (Page 217)
Creating a frame (Page 217)
General operation of the documentation editor (Page 220)
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 219
General operation of the documentation editor
Components of the documentation editor
The following figure provides an overview of the components of the documentation editor:
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
220 System Manual, 08/2011,
Toolbar
The toolbar provides the following tools (from left to right):
Insert background image
Inserts a background image into the template or cover page.
Arrow tool
Enables object selection.
Navigation tool
Allows shifting of the partial page.
Zoom-in button
Magnifies the page display incrementally.
Zoom-out button
Reduces the page display incrementally.
Selecting a zoom factor
Adapts the page size to the area selected with the lasso zoom tool.
Dynamic zoom
Adapts the page width to the work area.
Work area
You can design the cover page or frame in the work area.
"Toolbox" task card
The "Toolbox" task card contains various types of placeholders that you can use on
the cover sheet or frame. The placeholders can be placed in the work place using
a drag-and-drop operation.
Properties in the Inspector window
You can display and modify the properties of the currently selected object in the
"Properties" tab of the Inspector window. For example, you can modify the properties
of the page, format text, specify the position of objects on the page, etc.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 221
Operation in the documentation editor
The following basic functions are available in the documentation editor:
Drag-and-drop functionality
The documentation editor is a graphic editor, which means you can place objects anywhere
with the mouse. An image of the page is displayed in the work area. This image corresponds
to the ultimate print layout.
If you want to select objects on the page in order to move them or modify their properties,
the arrow tool must be activated in the toolbar.
Zoom function
You can use the zoom function to change the size of the page display. You have two options
for changing the page size:
Via the buttons in the toolbar
Select the "Zoom in" or "Zoom out" magnifying glass button in the toolbar of the
documentation editor. Then click on the page in order to magnify (zoom in) or reduce
(zoom out) the page incrementally.
To zoom in on a particular area, select the "Select zoom factor" tool and use the mouse
to drag an outline around the area you want to focus on.
To continuously zoom in or zoom out of the work area, use the "Dynamic zoom" tool.
To magnify the page display, click anywhere on the work area, and then hold down the
mouse button while dragging the mouse toward the top of the page. To reduce the page
display, drag the mouse toward the bottom of the page.
Via the zoom bar
You can also use the zoom bar (located in the bottom right corner of the work area) to
change the display size. Choose a percentage value from the drop-down list or enter a
percentage value. Alternatively, you control the display size using the slider.
Navigation over the page
In addition to scrolling, you the option of changing the partial page with the navigation tool.
To change the partial page with the navigation tool, select the Hand button in the toolbar.
Then, click anywhere on the page and hold the mouse button down while moving the page
to the desired position.
Using and adapting the positioning aids
You have various aids at your disposal to help you position elements on the page:
Rulers
Rulers are affixed to the page margins in the work area.
Page grid
A grid is placed underneath the page in the work area.
You can display, hide or adapt the positioning aids in the Inspector window under "Properties
> Rulers and grid". You can make the following settings:
Units:
Specify the unit of measurement for the grid and the rulers.
Grid steps:
Specify the width of the grid.
Show grid:
Specify whether the grid is to be displayed or hidden.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
222 System Manual, 08/2011,
Snap to grid:
Specify whether objects are to be aligned automatically to the grid. If the option is selected,
the grid lines function like a "magnet".
Show rulers:
Specify whether the rulers are to be displayed.
See also
Editing cover pages and frames (Page 219)
Inserting a background image (Page 223)
Specifying the print area (Page 223)
Inserting placeholders for metadata (Page 224)
Inserting a background image
You can specify a background image for a cover page or frame. You can design the
background image in another program and then insert it.
The background image is inserted in its original size. To keep it from extending beyond the
margins, make sure that the background image is already correctly sized when you save it.
Requirement
The background image must be in EMF or PDF format.
A cover page is open in the documentation editor.
Procedure
To insert a background image, follow these steps:
1. Click the "Add background image" button.
The "Open" dialog box opens.
2. Select the background image in the file system.
3. Click the "Open" button.
The background image is inserted in its original size at the top left page margin.
See also
Creating a cover page (Page 217)
General operation of the documentation editor (Page 220)
Specifying the print area
An area within the frame is provided for the actual printed contents. The project data is then
always inserted inside this defined and uniformly consistent area within the frame. You can
adjust the size of the print area.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 223
Requirement
A frame is open in the documentation editor.
Procedure
To define an area for the printed contents, follow these steps:
1. Click on the slightly darker area within the page display in the documentation editor to select
the area for the print content.
This opens the properties of the area to be printed in the Inspector window.
2. Enter the position of the print area on the X and Y axes in the Inspector window.
3. Specify the width and height of the print area in cm in the Inspector window.
Alternatively, you can change the width and position of the print area in the graphic display of
the page. To do so, use the mouse to drag the margins of the print area until the desired size
and position are achieved.
See also
Creating a frame (Page 217)
General operation of the documentation editor (Page 220)
Inserting placeholders for metadata
You can provide placeholders on the cover page and in a frame. The placeholders are
automatically filled with metadata from documentation information during printing, if they are
placeholders for text. Alternatively, you can add non-modifiable data, such as free text or an
image.
All elements are arranged in numbered Z-Orders. If objects overlap, you can determine in
which sequence these are to be arranged.
Types of placeholders
The following types of placeholders are available to you:
Text field
The text field stands as a placeholder for a text element from a document information. In
the properties of the text field, you set which text from a document information should be
automatically inserted during printing.
Field for date and time
A date and time is inserted instead of the placeholder when printing. This can be the date
of creation or the point in time when the last change was made to the project. In the
properties of the Inspector window, you specify which date or time is printed.
Page number
The correct page number is automatically applied when printing.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
224 System Manual, 08/2011,
Free text
You can enter freely selectable text in the properties of the text field. The text is static and
is not influenced by the document information selected at the time of printing.
Image
Select the image file in the properties of the placeholder in the Inspector window. Images
in the formats BMP, JPEG, PNG, EMF or GIF are possible.
Requirement
An cover page or frame is open in the documentation editor.
Procedure
To insert placeholders for metadata on the cover sheet or in a frame, follow these steps:
1. Drag a field from the "Toolbox > Elements" task card to the work area of the documentation
editor.
The placeholder is inserted. The placeholder properties are shown in the Inspector window
and can be edited there.
2. Select the metadata to be inserted during printing from the "Text" drop-down list in the
Inspector window under "Properties > General > Text box". Alternatively, you have the
option of entering free text or selecting an image depending on the type of placeholder.
3. In the Inspector window under "Properties > General > Position and size", specify the
position of the placeholder on the X and Y axis and enter the width and height of the text
box in cm. You specify the sequence of the objects in the "Z-Order" field, if these overlap.
The smaller the value, the further down an object is located.
4. In the Inspector window, go to "Properties > View" and select the font formatting and the
orientation of the text as well as the alignment of the text. You cannot make this setting for
images.
See also
General operation of the documentation editor (Page 220)
7.3.4.8 Displaying print preview
Creating a print preview
Creating a print preview
You can create a preview of the printout. Document information can be chosen for this, in the
same way as as for the actual printout. In this way, you preview the selected frame and, if
applicable, the cover sheet. The settings are retained for later printing.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 225
Procedure
To create a print preview and to set the scope of the later printout, follow these steps:
1. Select the "Print preview" command in the "Project" menu.
The "Print preview" dialog opens.
2. Select the frame layout you want to use for the printout.
In the "Document information" drop-down list, select the documentation information you
want to use later for the printout.
Select the "Print cover page" check box to print the cover page, which is specified in the
selected document information.
Select the "Print table of contents" check box to add a table of contents to the printout.
The check boxes for printing the cover page and the table of contents can only be selected
if you have started the printout in the project tree.
3. Under "Print objects/area", select what is to be printed. The selection is only possible if you
have started the printout from an editor that supports this function.
Choose "All" to print out the entire content of the editor.
Choose "Selection" to print only the objects currently selected in the editor.
4. Select the print scope under "Properties".
Choose "All" to print all configuration data of the selected objects.
Choose "Visible" to print the information of an editor that is currently visible on the
screen. This option can only be chosen if you have started the printout from an editor
that supports this function.
Choose "Compact" to print out an abbreviated version of the project data.
5. Click "Preview" to generate the preview.
A print preview is created in the work area.
Note
Wait time for extensive documents
It can take several minutes to generate the print preview in the case of very extensive
projects. You can continue working normally in the meantime on systems with adequate
resources. The progress of the print preview is shown in the status bar.
See also
Operation within the print preview (Page 227)
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
226 System Manual, 08/2011,
Operation within the print preview
Functions within the print preview
The print preview shows an exact image of the subsequent printout. You can use the buttons
in the toolbar to modify the print preview display. The following functions are available (from
left to right):
Navigation mode
Allows shifting of the partial page.
To change the partial page with the navigation tool, select the arrow button in the toolbar.
Then, click anywhere on the page and hold the mouse button down while moving the page
to the desired position.
Zoom function
"Zoom in" and "Zoom out"
Magnifies or reduces the page display.
To zoom in or zoom out the display incrementally, select the corresponding button. Then
click on the page in order to magnify (zoom in) or reduce (zoom out) the page
incrementally.
To zoom in on a particular area, select the "Lasso zoom" button and use the mouse to
drag an outline around the area you want to focus on.
To select an area to focus on, select the button "Zoom in / zoom out with rectangle".
With the mouse, drag a border around the area to focus on it.
To zoom dynamically through the page, select the button "Zoom in / zoom out
dynamically". With pressed mouse button, scroll down over the page to zoom in. Scroll
up to zoom out.
Percentage value in the drop-down list
Specifies the display size of the page in percent.
Enter a percentage value or select a percentage value from the drop-down list.
Alternatively, choose the the "Fit to page" option from the drop-down list to adapt the
page size to the work area. Or, choose "Fit to width" to adapt the page width to the work
area.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 227
"Forward" and "Backward":
Each change in the partial page, the page count, or the display size is saved in a history in
the background. You can use the "Forward" or "Backward" button to return to the previous
view or the next view.
Page navigation
"First page"
Jumps back to the first page.
"Previous page"
Goes one page back.
"Page number" input field
Shows the current page. To jump directly to a page, enter the page number of the page
you want to view.
"Next page"
Goes to the next page.
"Last page"
Jumps to the last page.
See also
Creating a print preview (Page 225)
7.3.4.9 Printing project data
You have two options for printing out project data:
Print immediately using default settings by means of the "Print" button in the toolbar.
The button is only active if a printable object is selected.
Printout with additional setting options with the "Project > Print" menu command.
For example, you can choose a different printer or specific documentation information or
you can specify whether a cover page and table of contents are to be printed. In addition,
you can specify the print scope or display a print preview prior to printing.
Requirement
At least one printer is configured.
The objects to be printed are not protected.
If printing is restricted by access protection, you must temporarily cancel the password
protection in order to release the objects for printing. Otherwise, protected objects will not
be included in the printout.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
228 System Manual, 08/2011,
Printing project data
To print out data from the current project or the entire project with additional setting options,
follow these steps:
1. Select the entire project in the project tree in order to print out the entire project. To print
only individual elements within a project, select them in the project tree.
2. Select the "Print" command in the "Project" menu.
The "Print" dialog opens.
3. Select the printer in the "Name" box.
4. Click "Advanced" to modify the Windows printer settings.
5. Select the frame layout you want to use for the printout.
Select the documentation information in the "Document information" drop-down list.
The frame stored in the document information is used for the printout. All placeholders
within the chosen frame are filled with the metadata from the selected document
information.
Select the "Print cover page" check box to print the cover page, which is stored in the
selected document information.
Select the "Print table of contents" check box to add a table of contents to the printout.
The check boxes for printing the cover page and the table of contents can only be selected
if you have started the printout in the project tree.
6. Under "Print objects/area", select what is to be printed. The selection is only possible if you
have started the printout from an editor that supports this function.
Choose "All" to print out the entire content of the editor.
Choose "Selection" to print only the objects currently selected in the editor.
7. Select the print scope under "Properties".
Choose "All" to print all configuration data of the selected objects.
Choose "Visible" to print the information of an editor that is currently visible on the
screen. This option can only be chosen if you have started the printout from an editor.
Choose "Compact" to print out an abbreviated version of the project data.
8. Click "Preview" to generate a print preview in advance.
A print preview is created in the work area.
9. Click "Print" to start the printout.
Note
Scope of the "Print" dialog
The options available in the "Print" dialog vary depending on the elements to be printed.
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 229
Result
The project data is prepared in the background for printing and then printed on the selected
printer. The status bar shows the progress of the print operation. You can continue working
normally while data is being prepared for printing.
The print results and any errors or warnings are listed in the Inspector window under "Info" at
the conclusion of the print job.
Canceling a print job
To cancel an active print job, follow these steps:
1. Click the red "X" in the status bar next to the progress display for the printout.
The printout is cancelled promptly.
See also
Protection concept for project data (Page 210)
Revoking access rights for devices (Page 210)
Printout of project contents (Page 212)
Editing projects
7.3 Editing project data
WinCC Advanced V11.0 SP1
230 System Manual, 08/2011,
7.4 Undoing and redoing actions
7.4.1 Basics of undoing and redoing actions
Function
You can undo performed actions at any time. For this purpose, every action you perform is
saved in an action stack. When undoing actions, the stack is processed from top to bottom. In
other words, if you undo an action that lies further down in the stack, all actions located above
it in the stack will also be undone automatically.
You can redo previously undone actions until you execute a new action. Once you execute a
new action, it is no longer possible to redo previously undone actions.
Particularities for undoing
There are a few actions that empty the action stack. You cannot undo these actions or the
actions performed before these actions. The following actions empty the action stack:
Saving
Project management (creating a new project, opening project, closing a project, deleting a
project)
Compiling
Restoring blocks
Establishing an online connection
Loading
Writing to memory cards
Displaying the action stack
The "Undo" button in the toolbar is enabled as soon as you perform an action that can be
undone. This button is split; you can use the arrow down portion to open a drop-down list
containing all actions of the action stack that you can undo. If you had performed actions in
an editor other than the currently displayed editor, the corresponding editor is also displayed
as a subheading. This allows you to always identify the point at which the undo operation will
be applied. The subheadings are removed from the list when the editor responsible can no
longer undo actions.
Actions you have undone are entered in the action stack from where they can be redone. Here,
you can redo actions you have undone. The display of actions you can redo it is analogous to
the display of the actions that you can undo.
Editing projects
7.4 Undoing and redoing actions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 231
Example of undoing actions
The figure below shows how actions performed in various editors and tables are undone:
Hardware and
network editor
Programming editor
Messages
Task planner
"Save project"
Action stack
"Undo" sequence
1
2
3
4
5
6
7
8
9
10
In this example, you cannot undo actions 1 to 3 because the project was saved. You can undo
actions 4 to 10 in the order indicated by the direction of the arrow. In other words, you must
undo action 10 first. Once you have undone action 8, you cannot then undo action 5. You must
first undo actions 7 and 6. As the final step in the sequence, you can then undo action 4. You
also have the option of undoing several actions in a single step by undoing an action located
further down in the action stack. All actions located above it in the stack will be undone
automatically.
The same principle also applies to redoing of actions.
See also
Undoing an action (Page 232)
Redoing an action (Page 233)
7.4.2 Undoing an action
The following options are available for undoing actions:
Undoing the last action only
Only the last action performed is undone.
Undoing as many actions as required
Multiple actions in the action stack are undone in a single step.
Editing projects
7.4 Undoing and redoing actions
WinCC Advanced V11.0 SP1
232 System Manual, 08/2011,
Undoing the last action only
To undo the last action performed, follow the steps below:
1. Click the "Undo" button in the toolbar.
If the action was not performed in the currently displayed editor, a confirmation prompt
appears.
If the undo operation requires an editor containing a protected object to be opened, you
must enter the password for the object.
2. Click "Yes" to confirm.
3. Enter the password, if necessary.
The editor in which the action was performed is displayed and the action is undone.
Undoing as many actions as required
To undo multiple actions in the action stack in a single step, follow these steps:
1. Click the Down arrow next to the "Undo" button in the toolbar.
This opens a drop-down list containing all actions you can undo. Actions performed in other
editors are identified by the editor name in the subheading.
2. Click the action you want to undo.
The chosen action and all actions in the stack located above the chosen action are undone.
If the undo operation requires an editor containing a protected object to be opened, you
must enter the password for the object.
3. Enter the required passwords, if necessary.
The editors in which the actions were performed are displayed and the actions are undone.
See also
Basics of undoing and redoing actions (Page 231)
Redoing an action (Page 233)
7.4.3 Redoing an action
You have the option of redoing an action that has been undone, so that you can return to the
status present before "Undo" was performed. However, this is only possible until you perform
a new action. The following options are available for redoing actions:
Redoing the last undone action only
Only the last undone action is redone.
Redoing as many undone actions as required
Multiple undone actions in the action stack are redone in a single step.
Editing projects
7.4 Undoing and redoing actions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 233
Redoing the last undone action only
To redo the last undone action, follow the steps below:
1. Click the "Redo" button in the toolbar.
If the action is not being redone in the currently displayed editor, a confirmation prompt
appears.
If the redo operation requires an editor containing a protected object to be opened, you
must enter the password for the object.
2. Click "Yes" to confirm.
3. Enter the password, if necessary.
The editor in which the action was undone is displayed and the action is redone.
Redoing as many undone actions as required
To redo multiple undone actions in the action stack in a single step, follow these steps:
1. Click the Down arrow next to the "Redo" button in the toolbar.
This opens a drop-down list containing all actions you can redo. Actions performed in other
editors are identified by the editor name in the subheading.
2. Click the action you want to redo.
The chosen action and all actions in the stack located above the chosen action are redone.
If the redo operation requires an editor containing a protected object to be opened, you
must enter the password for the object.
3. Enter the required passwords, if necessary.
The editors in which the actions were undone are displayed and the actions are redone.
See also
Basics of undoing and redoing actions (Page 231)
Undoing an action (Page 232)
Editing projects
7.4 Undoing and redoing actions
WinCC Advanced V11.0 SP1
234 System Manual, 08/2011,
7.5 Finding and replacing in projects
7.5.1 Information on the search function
Find and replace
You can search for texts in the editors. The search function finds all texts containing the search
key in the currently opened editor. The results are selected in sequence in the opened editor.
You also have the following options:
Narrowing down the search with additional options
Replacing found texts
The additional options and the type of texts for which you can search depend on the installed
products and the currently open editor.
See also
Search and replace (Page 235)
7.5.2 Search and replace
Using Find
The "Find and replace" function enables you to search for or replace texts in an editor.
Additional options for searching
You can narrow down your search by selecting one of the following additional options:
Whole words only
Only whole words are found. Words that contain the search key as part of the word are
ignored.
Match case
Upper- and lowercase letters are taken into account in the search.
Find in substructures
The search also includes texts contained in another object.
Editing projects
7.5 Finding and replacing in projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 235
Find in hidden texts
Texts that are assigned to another text but that are currently hidden are also included in
the search.
Use wildcards
Enter an asterisk as the wildcard for any number of characters. Example: You want to
search for all words starting with "Device". Type in "Device*" in the search key box.
Enter a question mark as the wildcard, however, if you only want to leave out a single
character.
Use regular expressions (for searching in scripts only)
A regular expression is a character string used to describe sets of values and for filtering.
This allows you to create complex search patterns.
The additional options available depend on the installed products and the editor opened.
Start search
Follow these steps to start the "Find and replace" function:
1. Select the "Find and replace" command in the "Edit" menu or open the "Find and replace"
pane in the "Tasks" task card.
The "Find and replace" pane opens.
2. Enter a term in the "Find" drop-down list.
As an alternative, you can select the most recent search key from the drop-down list.
3. Select the options desired for the search.
4. Using the option buttons, select the starting point for the search and the search direction.
Select "Whole document" if you want to search through the entire editor regardless of
the current selection,
Select "From current position" if you want to start the search at the current selection.
Select "Selection" if you only want to search within the current selection.
Select "Down" to search through the editor from top to bottom or from left to right.
Select "Up" to search through the editor from bottom to top or from right to left.
5. Click "Find".
The first hit is marked in the editor.
6. Click "Find" again to display the next hit.
The next hit is marked in the editor. Repeat this process, as necessary, until you reach the
last hit.
Replacing the search key
You have the option of replacing hits individually or automatically replacing all the found texts,
if the respective editor supports this function. Follow these steps to replace terms:
1. Enter a term in the "Find" drop-down list.
As an alternative, you can select the most recent search key from the drop-down list.
2. Select the options desired for the search.
Editing projects
7.5 Finding and replacing in projects
WinCC Advanced V11.0 SP1
236 System Manual, 08/2011,
3. Click the "Find" button to start a search for the specified search key.
The first hit is displayed in the editor.
4. In the "Replace" drop-down list, enter the text you wish to use to replace the search key.
As an alternative, you can select the most recently text specified from the drop-down list.
5. Click the "Replace" button to replace the selected hit with the specified text.
The found text is replaced and the next hit is marked in the editor.
Repeat this process until you have replaced all the hits as wanted. To skip to the next hit
without replacing the marked word, click the "Find" button instead of "Replace".
6. Click "Replace all" to automatically replace all hits at once.
See also
Information on the search function (Page 235)
Editing projects
7.5 Finding and replacing in projects
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 237
7.6 Working with text lists
7.6.1 Text lists
Introduction
You can manage texts to be referenced in alarms centrally. All the texts are stored in text lists.
Each text list has a unique name with which you can call up its content. A range of values is
assigned to each text in a text list. If a value from a range of values occurs, the corresponding
text is called up.
All the texts can be translated to all project languages. Here, you have two options available:
You can enter the translation of the texts in a list. You will find the list in the project tree
under "Languages & Resources > Project texts".
You can export all texts to a file in Office Open XML format and enter the translation in a
spreadsheet program. The translations can then be imported again.
The texts are translated into the other project languages within the framework of the project
texts. In the text lists editor, you only have to manage the assignment of individual texts to a
text list.
Each device in the project has its own text lists. For this reason, these lists are arranged under
the devices in the project tree. In addition, there are text lists that apply to all devices. These
can be found in the project tree under "Common data > Text lists".
User-defined and system-defined text lists
There are two types of text lists:
User-defined text lists
You can create user-defined text lists yourself and fill them with texts; in other words, you
can specify value ranges and the corresponding texts yourself. With user-defined text lists,
the name of the text list begins with "USER" as default. You can change this name to any
suitable name.
System-defined text lists
System-defined text lists are created by the system. These always involve texts relating to
devices. They are automatically created as soon as you insert a device in the project. With
system alarms, the name of the text list begins with "SYSTEM". The name of the text list
and the ranges of values it contains cannot be modified. You can only edit texts assigned
to individual value ranges.
User-defined text lists System-defined text lists
A user-defined text list can only be assigned to one
device.
System-defined text lists can be assigned both to
a device as well as to the entire project.
You can create new text lists and delete existing
text lists.
You cannot create new text lists or delete text lists.
Editing projects
7.6 Working with text lists
WinCC Advanced V11.0 SP1
238 System Manual, 08/2011,
User-defined text lists System-defined text lists
You can add and delete value ranges in the text
lists.
You cannot add or delete value ranges in the text
lists.
You can specify both the value ranges as well as
the associated texts.
You can only edit the text associated with one
value range.
Device-specific and cross-device text lists
Device-specific text lists relate to only one device in the project and are therefore only valid
for this device. For this reason, they are arranged under a device in the project tree. Device-
specific text lists can be used-defined or created by the system.
If system-defined text lists are generally valid for several devices or not intended uniquely for
one device, these are grouped together in the project tree under "Common data". These text
lists are available for all devices. Cross-device text lists are always created by the system and
are used solely for system diagnostics alarms. For this reason, you cannot store any user-
defined text lists under "Common data".
See also
Exporting and importing project texts (Page 198)
7.6.2 Creating user-defined text lists
Creating text lists
You can create user-defined text lists for individual devices.
Requirement
You are in the project view.
A project is open.
The project includes a least one device.
Procedure
To create user-defined text lists, follow these steps:
1. Click on the arrow to the left of a device in the project tree.
The elements arranged below the device are displayed.
2. Double-click on "Text lists".
All the text lists assigned to the device are displayed in the work area listed in a table.
3. Double-click on the first free row in the table.
A new user-defined text list is created.
4. Enter a name for your new text list in the "Name" column.
Editing projects
7.6 Working with text lists
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 239
5. From the drop-down list in the "Selection" column, select whether you want to specify the
value ranges in decimal, binary or in bits. Depending on the device, there may be further
options available at this point.
6. Enter a comment in the "Comment" column.
A new user-defined text list has been created and you can now enter the value ranges and
texts.
7.6.3 Editing user-defined text lists
Editing user-defined text lists
You can enter value ranges and the corresponding texts in user-defined text lists. User-defined
text lists are always located below a device in the project tree.
Requirement
You are in the project view.
A project is open.
The project includes a least one device.
Adding to user-defined text lists with value ranges and texts
To add to user-defined text lists with value ranges and texts, follow these steps:
1. Click on the arrow to the left of a device in the project tree.
The elements arranged below are displayed.
2. Double-click on "Text lists".
All the text lists assigned to the device are displayed in the work area listed in a table.
3. Select a text list in the table.
The contents of the selected text list are displayed in the work area. There, you can enter
a value range and assign texts to the individual value ranges.
4. Enter the value ranges you require in the "Range from" and " Range to" columns. The entry
must be made in the numeric format selected for the text list.
5. Enter a text for each value range in the "Entry" column.
7.6.4 Editing system-defined text lists
Editing system-defined text lists
In system-defined text lists, you can only modify the individual texts assigned to a value range.
System-defined text lists are located in the project tree either below a device or under
"Common data".
Editing projects
7.6 Working with text lists
WinCC Advanced V11.0 SP1
240 System Manual, 08/2011,
Requirement
You are in the project view.
A project is open.
The project includes a least one device.
Modifying texts in system-defined text lists
To edit texts in system-defined text lists that are assigned to a value range, follow these steps:
1. Click on the arrow to the left of a device in the project tree or the "Common data" element.
The elements arranged below are displayed.
2. Double-click on "Text lists".
All the text lists assigned to the device or used in common are displayed in the work area
listed in a table.
3. Select a text list in the table.
The contents of the selected text list are displayed in the work area. Here, you can add to
or edit the texts assigned to a value range.
4. Enter a text for each value range in the "Entry" column.
Editing projects
7.6 Working with text lists
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 241
7.7 Using memory cards
7.7.1 Basics about memory cards
Introduction
Memory cards are plug-in cards that come in a variety of types and can be used for a variety
of purposes. Depending on the device type or device family, memory cards can be used for
purposes, such as:
Load memory of a CPU
Storage medium for projects, firmware backups, or any other files
Storage medium for performing a firmware update
Storage medium for the PROFINET device name
For information regarding the technical variants of the respective memory cards and general
information on their handling, refer to the respective documentation for the device. For
information on handling memory cards in the TIA Portal, refer to the online help under keyword
"Memory Card".
CAUTION
Do not use memory cards for non-SIMATIC-related purposes, and do not use third-party
devices or Windows tools to format them. This will irrevocably overwrite the internal structure
of the memory card, rendering it unusable for SIMATIC devices!
See also
Adding a user-defined card reader (Page 242)
Accessing memory cards (Page 243)
Displaying properties of memory cards (Page 243)
7.7.2 Adding a user-defined card reader
Introduction
If your card reader is not detected automatically, you can add it manually.
Requirement
The project view is open.
Editing projects
7.7 Using memory cards
WinCC Advanced V11.0 SP1
242 System Manual, 08/2011,
Procedure
To add a card reader, follow these steps:
1. Open the project tree.
2. Select "SIMATIC Card Reader > Add user-defined Card Reader" in the "Project" menu.
The "Add user-defined Card Reader" dialog opens.
3. In the drop-down list box, select the path for the card reader.
4. Confirm your entries with "OK".
See also
Basics about memory cards (Page 242)
Accessing memory cards (Page 243)
Displaying properties of memory cards (Page 243)
7.7.3 Accessing memory cards
Requirement
A memory card is inserted in the card reader.
The project view is open.
Procedure
To access memory cards, follow these steps:
1. Open the project tree.
2. Select "SIMATIC Card Reader > Show SIMATIC Card Reader" in the "Project" menu.
The "SIMATIC Card Reader" folder is displayed in the project tree.
3. Open the "SIMATIC Card Reader" folder.
You can now access the memory card.
See also
Basics about memory cards (Page 242)
Adding a user-defined card reader (Page 242)
Displaying properties of memory cards (Page 243)
7.7.4 Displaying properties of memory cards
You can display the properties for the utilized memory cards. Note that different memory cards
with different properties must be used, depending on the device.
Editing projects
7.7 Using memory cards
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 243
Requirement
A memory card is inserted in the card reader.
The project view is open.
Procedure
To display the properties of a memory card, follow these steps:
1. Right-click on the memory card for which you want to display the properties.
2. Select the "Properties" command in the shortcut menu.
The "Memory Card <name of the memory card>" dialog opens. The properties are displayed
in this dialog.
See also
Basics about memory cards (Page 242)
Adding a user-defined card reader (Page 242)
Accessing memory cards (Page 243)
Editing projects
7.7 Using memory cards
WinCC Advanced V11.0 SP1
244 System Manual, 08/2011,
7.8 Using libraries
7.8.1 Library basics
Introduction
You can store objects you want to use more than once in libraries. It is possible to reuse the
stored objects throughout a project or across projects. This means you can, for example, create
block templates for use in different projects and adapt them to the particular requirements of
your automation task.
Library types
Depending on the task, you can use one of the following library types:
Project library
Each project has its own library. Here, you store the objects you want to use more than
once in the project. This project library is always opened, saved, and closed together with
the current project.
Global libraries
You can also create other libraries in addition to the project library. Here, you store the
objects you want to use in more than one project. You can create, change, save, and
transfer these global libraries independent of projects.
In the global libraries area, you will also find libraries that ship with the software. These
include off-the-peg functions and function blocks that you can use within your project. You
cannot modify the supplied libraries.
Library objects
Libraries can accommodate a large number of objects. These include, for example:
Functions (FCs)
Function blocks (FBs)
Data blocks (DBs)
Devices
PLC data types
Watch and force tables
Process screens
Faceplates
For objects with know-how protection, this protection is also retained after the object is inserted
into a library.
Editing projects
7.8 Using libraries
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 245
Use types
You can use the library elements as either a copy template or a type. You can use copy
templates to generate copies of the library element that are independent of one another. Copy
templates are marked with a black triangle in the "Libraries" task card. You can derive and use
instances from types. These instances are tied to their respective type, and changes to one
instance also change all other instances. Types are marked with a green triangle in the
"Libraries" task card.
Note
Please note the following:
The use as a type is not available for every object.
You can only create types in the project library.
See also
Project library basics (Page 249)
Global library basics (Page 257)
"Libraries" task card (Page 246)
7.8.2 "Libraries" task card
Function of the "Libraries" task card
The "Libraries" task card enables you to work efficiently with the project library and the global
libraries.
You can show or hide the task card as needed.
Editing projects
7.8 Using libraries
WinCC Advanced V11.0 SP1
246 System Manual, 08/2011,
Structure of the "Libraries" task card
The "Libraries" task card consists of the following components:
Device view (Page 279), network view (Page 277), topology view (Page 282)
Inspector window (Page 286)
Hardware catalog (Page 287)
The hardware and network editor provides you with three views of your project. You can switch
between these three views at any time depending on whether you want to produce and edit
individual devices and modules, entire networks and device configurations or the topological
structure of your project.
The inspector window contains information on the object currently marked. Here you can
change the settings for the object marked.
Drag the devices and modules you need for your automation system from the hardware catalog
to the network, device ot topology view.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
276 System Manual, 08/2011,
8.1.1.2 Network view
Introduction
The network view is one of three working areas of the hardware and network editor. You
undertake the following tasks here:
Configuring and assign device parameters
Networking devices with one another
Structure
The following diagram shows the components of the network view:
Selection of a module
Editing option for addresses in the device overview
Selection options in the inspector window
Editing option for addresses in the inspector window
See also
Inspector window (Page 286)
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
312 System Manual, 08/2011,
Update module version
Explanation of terms
The terms "Module version" and "Firmware version" are explained in more detail in the
following section.
Module version: The specific version of the configuration software from which the module
description stems.
Exp.: V11.0.0.0
Firmware version: The version of the firmware of the offline configured module
Exp.: V2.0
Requirements
You have created a device configuration.
You have installed an update or an optional package at a later date. As a result of this
installation, the module version of at least one module type was updated in the hardware
catalog, whereby the new version is incompatible with the previous version.
You have used such modules in your device configuration and want to use the modified or
added properties.
Procedure
Perform the following step for each affected module type.
1. Select the affected module in the device view.
2. In the Inspector window, go to "Properties > General > Catalog Information". Click the
"Update module version" button there.
3. In the query that then appears, specify whether you want to update the module version only
for the selected module or for all modules of this type in the current project.
Result
The selected modules are replaced by the same modules with updated module version in the
the current project.
In which cases is it unnecessary to update the module version?
An updating of the module version is not necessary in the following cases:
You do not want to used the modified or added properties of the modules.
You open an existing project with a version of the configuration software that is more recent
than the version with which you created the project and the system automatically performs
a project conversion, for example from V10.5 to V11.0. In this case, all older module
versions are automatically adapted.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 313
8.1.3 Configure networks
8.1.3.1 Networking devices
Communication and networks
Communication between devices
The basis of all types of communication is always a previously configured network. The network
configuration provides the necessary requirements for communication:
All the devices in a network are provided with a unique address
Communication of the devices with consistent transmission properties
Network configuration
The following steps are necessary when configuring networks:
Connect devices to subnet
Specify the properties/parameters for each subnet
Specify the device properties for every networked module
Download configuration data to the devices to supply interfaces with the settings resulting
from the network configuration
Document the network configuration
For Open User Communication, creating and configuring a subnet is supported by the
assignment of connection parameters.
Relation between network configuration and project
Within a project, subnets and their properties are managed. Properties result mainly from
adjustable network parameters and the quantity and communication properties of the
connected devices.
The devices to be networked must be in the same project.
Subnet name and subnet ID
Within the project, subnets are clearly identified by a subnet name and ID. The subnet ID is
saved in all components along with interconnectable interfaces. Components can then be
clearly assigned to a subnet even after uploading into a project.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
314 System Manual, 08/2011,
Networking options
In the project, you can create and network devices with components capable of
communication. The following basic options are available for networking the devices:
You link the interfaces of the components capable of communication with one another. A
new subnet is created suitable for the type of interface.
You connect the interface of the devices capable of communication with a new or existing
subnet.
You create an Open User Communication connection. When you assign parameters to the
connection for Open User Communication, a subnet is created automatically between the
communication partners.
You use the graphic connection configuration to configure connections; missing networks
are hereby recognized and are created either automatically or via dialog.
Due to the different tasks of the devices or the span of the plant, you may need to use several
subnets. These subnets are managed in a project.
Networking devices in the network view
Options
In the graphic network view, you have an overview of the subnets of the entire system in the
project. You can use the tabular network overview for additional support.
Depending on the starting situation, there are various ways of undertaking configuration to
network the interface for a component capable of communication. The procedures are
described in the following section:
Creating an individual subnet
Creating several subnets at one time
Connecting two target devices via a new subnet
Connecting devices to existing subnet
Selecting an existing subnet from a list
Automatic networking during the configuration of the connection;
See also: Auto-Hotspot
Possible starting situations are:
A suitable subnet is not yet available.
The subnet with which you want to connect the component already exists.
Procedure - creating a single subnet
To create a subnet and to connect it to an interface, proceed as follows:
1. Select the interface of a CPU / a CP.
2. Select the "Create subnet" command in the shortcut menu of the interface.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 315
The selected interface is connected to a new subnet. Consistent address parameters are set
automatically for the interface.
The following schematic shows an interface with outgoing line connecting to a subnet:
Procedure - creating several subnets at one time
To create several subnets at one time, proceed as follows:
1. Select several interfaces by clicking on them while pressing the <Ctrl> button.
2. Select the "Create subnet" command in the shortcut menu of the interface.
Each selected interface is connected to a new subnet. Consistent address parameters are set
automatically for the interface.
The following figure shows multiple subnets created by selecting multiple interfaces:
Procedure Connecting two target devices via a new subnet
To connect an interface with another device via a subnet that does not yet exist, proceed as
follows:
1. Position the mouse pointer over the interface for a component capable of communication
requiring networking.
2. Click with the left mouse button and hold the button down.
3. Move the mouse pointer.
The pointer now uses the networking symbol to indicate "Networking" mode. At the same
time, the mouse pointer shows the lock symbol that will only disappear when the pointer is
on a valid target.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
316 System Manual, 08/2011,
4. Now move the pointer onto the interface of the target device. You can either keep the mouse
button pressed or release it.
5. Now release the left mouse button or press it again (depending on previous action).
A new subnet is created. The interfaces are now connected via the new subnet. Consistent
address parameters are set automatically for the interface.
The following schematic shows two networked devices:
Procedure - Connecting devices to existing subnet
To connect an interface to an existing subnet, proceed as follows:
1. Position the mouse pointer on the interface of a communications-compliant component you
want to network or on the existing subnet.
2. Click with the left mouse button and hold the button down.
3. Move the mouse pointer.
The pointer now uses the networking symbol to indicate "Networking" mode. At the same
time, the mouse pointer shows the lock symbol that will only disappear once the pointer is
moved to a valid target.
4. Now move the mouse pointer to the existing subnet or to the interface to be networked.
You can either keep the mouse button pressed or release it.
5. Now release the left mouse button or press it again (depending on previous action).
Result:
The interface and selected subnet are now connected. Consistent address parameters are set
automatically for the interface.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 317
Procedure - selecting an existing subnet from a list
To link an interface with a subnet that has already been created, proceed as follows:
1. Select the interface of a CPU.
2. Select the "Assign to new subnet" command in the shortcut menu of the interface.
A list box containing the available subnets appears.
3. Select a subnet from the list.
The interface and selected subnet are now connected. Consistent address parameters are set
automatically for the interface.
Tabular network overview
Meaning
The tabular network overview adds the following functions to the graphic network view:
You obtain detailed information on the structure and parameter settings of the devices.
Using the "Subnet" column, you can connect components capable of communication with
created subnets.
Basic functions for tables
The network overview supports the following basic functions for editing a table:
Displaying and hiding table columns
Note: The columns of relevance to configuration cannot be hidden.
Optimizing column width
Sorting table
Displaying the meaning of a column, a row or cell using tooltips.
Networking devices in the device view
Networking in the device view
In the device view, you can check and set all the parameters of the components belonging to
a device and the interfaces in detail. Here you can also assign the interfaces to the subnets
created in the project.
Requirements
The subnet with which you want to connect an interface has already been created.
If the subnet has not yet been created, change to the network view and make the settings
required for networking.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
318 System Manual, 08/2011,
Procedure - connecting to an existing subnet
To connect an interface to an existing subnet, proceed in the device view as follows:
1. Select the entire communications-compliant component or the interface to be networked.
The properties of the selected interface or component are displayed in the Inspector window.
2. In the Inspector window, select the parameter group for the selected interface; for example,
the "Ethernet addresses" parameter group for a PROFINET interface.
3. Select the subnet to be connected from the "Interface connected with" drop-down list.
The interface and selected subnet are now connected. Consistent address parameters are set
automatically for the interface.
Procedure - creating a new subnet
To create a subnet and to connect it to the interface, proceed as follows in the device view:
1. Select the entire communications-compliant component or the interface to be networked.
The properties of the selected interface or component are displayed in the Inspector window.
2. In the Inspector window, select the parameter group for the selected interface; for example,
the "Ethernet addresses" parameter group for a PROFINET interface.
3. In "Interface connected with", click the "Add new subnet" button.
The interface is connected to a new subnet of the appropriate subnet type. Consistent address
parameters are set automatically for the interface.
Checking or changing network parameters and interface parameters
Introduction
Communication between networked devices requires the following parameters to be
configured:
Network parameters
Network parameters identify the network within the system configuration, for example, using
a name.
Interface parameters
Interface parameters define specific properties of a component capable of communication.
Addresses and transmission characteristics are set automatically and are consistent with
the network parameters.
Note
Network parameters and interface parameters are usually set during networking such that
communication can take place for numerous applications without the parameters having
to be changed.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 319
Procedure - checking or changing network parameters
Proceed as follows to check or change network parameters:
1. Enter the network view.
2. Select the subnet from the network view.
You can see the network parameters in the "Properties" tab in the inspector window.
3. If necessary, check or modify the network parameters in the relevant group of parameters.
Procedure - checking or changing interface parameters
You can check and modify interface parameters in the network and device view.
Proceed as follows to check or change interface parameters:
1. Enter the network view or device view.
2. Select the interface.
You can see the interface parameters in the "Properties" tab in the inspector window.
3. If necessary, check or modify the interface parameters in the relevant group of parameters.
Changing networkings
Introduction
You can cancel an interface's network connection or assign it to another subnet of the same
subnet type.
Consequences
Depending on the version, a distinction should be made between:
Canceling a network connection for an interface
The configured parameters for the interface remain unchanged.
Assigning a network connection to another subnet
If the addresses in the assigned subnet are not unique, in other words, they already exist,
they will be changed automatically to make them unique.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
320 System Manual, 08/2011,
Procedure - disconnecting from a network
Proceed as follows to cancel the network connection for an interface:
1. Select the networked interface.
2. Select the "Disconnect from subnet" command in the shortcut menu of the interface.
The network connection is deleted, the interface addresses are, however, not changed.
Configured connections are retained; however these connections are marked red in the
connection table because they are not networked. Specified connections remain specified.
See also
Networking devices in the network view (Page 315)
Copying, cutting or deleting subnets
Introduction
You can copy subnets as individual objects or copy them along with networked devices or
other networks.
For example, you can create complex configurations to be used more than once in different
variants within the project with no additional effort.
Effects on the copied subnet
Properties that have to be assigned explicitly within a project are re-assigned appropriately
when the copied objects are copied.
For subnets, this means: The subnet ID and name are re-assigned to the copied subnet.
The configured properties are adopted in the copied subnet.
Procedure - copying a subnet
Proceed as follows to copy one or more subnets:
1. Select one or more subnets.
2. In the shortcut menu, select the "Copy" command.
3. Select the "Paste" command in the shortcut menu.
The copied subnets are shown as "orphaned" subnets in the top part of the network view.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 321
Procedure - copying a subnet with connected devices
To copy one or more subnets with networked devices, proceed as follows:
1. Select one or more subnets with the connected devices, for example by drawing a lasso
around them.
2. In the shortcut menu, select the "Copy" command.
3. Select the "Paste" command in the shortcut menu.
Complete copies of the subnets and connected devices are created.
Configured connections are adopted and remain within the copied devices. Connections to
devices that have not been copied are interrupted and become unspecified.
MPI network configuration
Allocating MPI addresses
Note the following for devices with an MPI interface: All devices of a subnet must have different
device addresses.
CPUs with MPI address ship with the default MPI address 2. Since you can only use this
address once in the MPI subnet, you will have to change the default address in all other CPUs.
The following applies to devices with the order no. 6ES7 3xx-xxxxx-0AB0:
When planning the MPI addresses for several CPUs, you have to fill "MPI address gaps" for
FMs and CPs with separate MPI addresses to prevent addresses being assigned twice.
Only when all the modules in a subnet have different addresses and your actual structure
matches that of the network configuration produced, should you load the settings across the
network.
Rules for assigning the MPI address
Allocate the MPI addresses in ascending order.
Reserve MPI address 0 for a programming device.
You can link up to 126 (addressable) devices with one another in an MPI subnet; up to 8
devices at a transfer speed of 19.2 KB/s.
All MPI addresses in an MPI subnet must be different.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
322 System Manual, 08/2011,
You will find other rules relating to the structure of a network in the manuals for setting up
automation systems.
PROFIBUS network configuration
PROFIBUS addresses
Rules for the network configuration
All the devices in a subnet must have a different PROFIBUS address.
Only when all the modules in a subnet have different addresses and your actual structure
matches that of the network configuration produced, should you load the settings across the
network.
You can connect devices to the PROFIBUS subnet that communicate via configured
connections or that belong to a PROFIBUS DP master system.
You can find more information on configuring a DP master system in the following sections.
Requirements
The 121xC CPU is PROFIBUS compatible as of firmware version 2.0.
Rules for assigning PROFIBUS addresses
Allocate the PROFIBUS addresses in ascending order.
Reserve the PROFIBUS address "0" for a programming device.
Allocate a unique PROFIBUS address between 0 and 126 for each device on the
PROFIBUS network and/or for each DP master and each DP slave in the PROFIBUS
network.
There are modules with which the smallest address that can be set has to be greater than
1.
All PROFIBUS addresses of a PROFIBUS subnet must be different.
You will find additional rules relating to the structure of a network in the manuals for setting up
automation systems, for example SIMATIC S7-1200.
Note
PROFIBUS address "0"
Reserve PROFIBUS address "0" for a programming device that you will briefly connect up
to the PROFIBUS network at a later date for servicing.
See also
What you need to know about PROFIBUS bus parameters (Page 324)
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 323
What you need to know about PROFIBUS bus parameters
Matching parameters to one another
The PROFIBUS subnet will only function without problem if the parameters for the bus profile
are matched to one another. You should therefore only change the default values if you are
familiar with how to configure the bus profile for PROFIBUS.
Note
It may be possible for the bus parameters to be adjusted depending on the bus profile. If the
bus parameters cannot be adjusted, they are grayed out. The offline values of the bus
parameters are always shown even if you are online and linked to the target system.
The parameters shown apply to the entire PROFIBUS subnet and are briefly explained below.
Activating cyclic distribution of the bus parameters
If the "Enable cyclic distribution of the bus parameters" check box is selected under "Bus
parameters" while PROFIBUS subnet is selected in the Inspector window, the bus parameters
are transferred cyclically during operation by the modules that support this function. This allows
a programming device, for example, to be easily connected to the PROFIBUS in runtime.
You should deactivate this function:
For a heterogeneous PROFIBUS subnet (or more accurately: when external devices are
connected whose protocol uses the DSAP 63 for Multicast)
When in constant bus cycle time mode (minimize bus cycle)
Bus parameters for the bus profile of PROFIBUS subnets
Bus parameter Adjustable? Limit values
Tslot_Init Yes Max. Tsdr + 15 <= Tslot_init <= 16.383 t_bit
Max. Tsdr Yes 35 + 2*Tset + Tqui <= Max. Tsdr <= 1.023 t_bit
Min. Tsdr Yes 11 t_bit <= Min. Tsdr <= MIN(255 t_bit, ...
... Max. Tsdr - 1, 34 + 2*Tset + Tqui)
Tset Yes 1 t_bit <= Tset <= 494 t_bit
Tqui Yes 0 t_bit <= Tqui <= MIN(31 t_bit, Min. Tsdr - 1)
GAP factor Yes 1 <= GAP factor <= 100
Retry limit Yes 1 <= Retry limit <= 15
Tslot No ---
Tid2 No Tid2 = Max. Tsdr
Trdy No Trdy = Min. Tsdr
Tid1 No Tid1 = 35 + 2*Tset + Tqui
Ttr Yes 256 t_bit <= Ttr <= 16.777.960 t_bit
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
324 System Manual, 08/2011,
Bus parameter Adjustable? Limit values
Ttr typical No This time is provided for information only and is not transferred to the
nodes.
Response monitoring 10 ms <= response monitoring (watchdog) <= 650 s
If you want to create a customized bus profile, we recommend the following settings:
Minimum target rotation time (Ttr) = 5000 x HSA (highest PROFIBUS address)
Minimum response monitoring (watchdog) = 6250 x HSA
Recalculating
You can use the "Recalculate" button to recalculate the parameters.
See also
PROFIBUS addresses (Page 323)
Description of the bus parameters (Page 325)
Description of the bus parameters
Detailed description of PROFIBUS bus parameters
Bus parameter Meaning
Tslot_Init The wait-for-reception (slot time) defines the maximum time the sender will wait
to receive a response from the addressed partner. If the influence of the line
components on message frame run times is entered in the "Cable Configuration"
parameter group, these components must also be taken into account. The
component is added to the specified Tslot_Init and the total used as Tslot.
Max. Tsdr The maximum protocol processing time defines the latest time by which the
responding node should have replied.
Min. Tsdr The minimum protocol processing time defines the earliest time by which the
responding node may reply.
Tset The trigger time is the time which may lapse between the reception of a data
message frame and the response to it in the node.
Tqui The modulator quiet time is the time which a sending node needs after the end
of the message frame to switch from sending to receiving.
GAP factor The GAP update factor defines the number of token rotations after which a newly
added, active node can be added to the logical token ring.
Retry limit This parameter defines the maximum number of attempts (message frame
repeats) made to reach a node.
Tslot The wait-for-reception time (slot time) defines the maximum time the sender will
wait to receive a response from the addressed partner.
If the influence of the bus design components on message frame run times is
entered in the "Cable Configuration" parameter group, these components must
also be taken into account. The component is added to the specified Tslot_Init
and the total used as Tslot.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 325
Bus parameter Meaning
Tid2 Idle time 2 defines the earliest time by which a sending node may send the next
message frame after sending a message frame that has not been acknowledged.
Trdy The ready time specifies the earliest time by which a sending node may receive
a response message frame.
Tid1 Idle time 1 defines the earliest time by which a sending node may send the next
message frame after receiving a response.
Ttr The target rotation time is the maximum time made available for a token rotation.
During this time, all active nodes (DP masters etc.) have the right to send (token)
once. The difference between the target rotation time and the actual token holding
time of a node determines how much time is left over for the other active nodes
(programming device, other DP masters etc.) to send message frames.
Ttr typical The typical data cycle time is the average response time on the bus if all
configured slaves are exchanging data with the DP master. None of the slaves
report diagnostics and there is no extra message frame traffic with programming
devices or other active nodes etc. on the bus.
Response monitoring The response monitoring time is only needed for PROFIBUS-DP bus systems. It
defines the latest time by which a DP slave has to be addressed by its DP master
with a new data message frame. If this does not happen, the DP slave assumes
that the DP master has failed and resets its outputs to a secure mode.
See also
What you need to know about PROFIBUS bus parameters (Page 324)
Bus profiles with PROFIBUS
Introduction
Depending on the device types connected and protocols used on the PROFIBUS, different
profiles are available. The profiles differ in terms of the setting options and calculation of bus
parameters. The profiles are explained below.
Devices with different profiles on the same PROFIBUS subnet
The PROFIBUS subnet only functions without problem if the bus parameters of all devices
have the same values. For example, if both DP and FMS services are being used on a subnet,
the "slower" sets of bus parameters must always be set for all devices, i.e. even the "Universal
(DP/FMS)" profile for DP devices.
Profiles and transmission rates
Profiles Supported transmission speeds in Kbits/s
DP 9.6 19.2 45.45 93.75 187.5 500 1500 3000 6000 12000
Standard 9.6 19.2 45.45 93.75 187.5 500 1500 3000 6000 12000
Universal (DP-FMS) 9.6 19.2 93.75 187.5 500 1500
Customized 9.6 19.2 45.45 93.75 187.5 500 1500 3000 6000 12000
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
326 System Manual, 08/2011,
Meaning of profiles
Profile Meaning
DP Select the "DP" bus profile when the only devices connected to the PROFIBUS
subnet are those which satisfy the requirements of standard EN 50170 Volume
2/3, Part 8-2 PROFIBUS. The bus parameter setting is optimized on these
devices.
This includes devices with DP master and DP slave interfaces of the SIMATIC
S7 and distributed I/Os of other manufacturers.
Standard Compared to the "DP" profile, the "Standard" profile also offers scope for
devices of another project or devices which have not been configured here to
be taken into account when calculating the bus parameters. The bus
parameters are then calculated following a simple, non-optimized algorithm.
Universal (DP/FMS) Select the "Universal (DP/FMS)" bus profile when individual devices on the
PROFIBUS subnet use the PROFIBUS-FMS service.
This includes the following devices for example:
CP 343-5 (SIMATIC S7)
PROFIBUS-FMS devices of other manufacturers
As with the "Standard" profile, this profile allows you to take other devices into
account when calculating the bus parameters.
Customized The PROFIBUS subnet will only function without problem if the parameters for
the bus profile are matched to one another. Select the "Customized" profile
when none of the usual profiles "match" a PROFIBUS device and you need to
adapt the bus parameters to your special structure. Information on this can be
found in the documentation for the PROFIBUS device.
You should only change the default values if you are familiar with how to
configure the bus profile for PROFIBUS.
Not all combinations that can be theoretically set can be used even with this
bus profile. The PROFIBUS standard specifies several parameter limits that
depend on other parameters. For example, a responder must not respond (Min
Tsdr) before the initiator can receive the message frame (Trdy). These standard
specifications are also checked in the "Customized" profile.
Tip: The bus parameters last valid on the PROFIBUS subnet are always
automatically set as customized. For example, if the "DP" bus profile was valid
for the subnet, then the bus parameters for "DP" are set in the "Customized"
bus profile. The parameters can be modified on this basis.
The monitoring times are not automatically recalculated so that you do not put
at risk the consistency of set values, for example with configurations in other
configuration tools without realizing that you have done so.
You can also have the Ttr monitoring times and target rotation time calculated
on the basis of parameters you have set: Click here on the "Recalculate" button.
Note
Both mono-master mode and multi-master mode are possible with all PROFIBUS profiles.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 327
What you need to know about PROFIBUS line configuration
Cable configuration and bus parameters
Information regarding the cable configuration can be taken into consideration when calculating
the bus parameters. For this purpose, you must select the "Consider cable configuration" check
box in the properties for the PROFIBUS subnet.
The remaining information then depends on the type of cable used; the following settings are
available:
Copper cable
Fiber-optic cable/optical ring
PROFIBUS line configuration, optical ring
The calculation depends on the OLM types used. The selection is made by activating the check
box (multiple activation is possible, at least one OLM type must be selected):
OLM/P12
OLM/G12
OLM/G12-EEC
OLM/G12-1300
The following bus parameter adjustments are made:
Configuration of a node not present
Note
The following restrictions apply to optical rings, even for passive nodes (DP slaves for
example):
A maximum of HSA-1 nodes may be connected to the PROFIBUS network. With an HSA
of 126, addresses 126 and 125 must not be used. A maximum of 125 nodes are possible
on the bus (No. 0 to 124).
If an HSA is less than or equal to 125, the addresses HSA and greater may not be used.
The address HSA-1 may not be used.
Increase the retry value to 3
Setting of minimum slot time needed for ring mode
Note
Short slot time values are needed for OLM/P12, average ones for OLM/G12 and OLM/
G12-EEC and long ones for OLM/G12-1300. This results in high performance for small
network lengths and average to low performance for average to large network lengths.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
328 System Manual, 08/2011,
PROFIBUS communication load
Communication load - allowing for additional network stations
The bus parameters depend on the volume of communication between the active network
nodes. There are differences between cyclic communication (DP) and connection-based,
acyclic communication (S7 communication, Send/Receive (FDL), FMS). Unlike DP, the volume
and size of communication tasks (communication load) depends on the user program. For this
reason, the communication load cannot always be calculated automatically.
To calculate the bus times you can define a network configuration in the "Additional network
stations" parameter group that differs from the network configuration.
Taking the profile into account
The network configuration can be defined for the "Standard", "Universal (DP/FMS)", and "User-
defined" profiles. Parameters cannot be entered in the "Additional network stations" parameter
group for the "DP" profile.
Quantification of the communication load
The following settings are available in order to make allowance for the communication load.
Information regarding the number of unconfigured network stations;
Information on the communication load resulting from the user programs for FDL or S7
communication. Here you can selected from the following settings:
Low
Typically used for DP, no great data communication apart from DP.
Medium
Typically used for mixed operations featuring DP and other communication services
(such as for S7 communication), when DP has strict time requirements and for average
acyclic volumes of communication.
High
For mixed operations featuring DP and other communication services (such as for S7
communication), when DP has loose time requirements and for high acyclic volumes of
communication.
Configuring Industrial Ethernet
Rules for the network configuration
The Ethernet interfaces of the devices have a default IP address that you can change.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 329
IP address
The IP parameters are visible if the module capable of communication supports the TCP/IP
protocol. This is usually the case for all Ethernet modules.
The IP address consists of 4 decimal figures in the range of 0 to 255. The decimal figures are
separated from one another by a dot.
Example: 140.80.0.2
The IP address consists of:
Address of the (sub) net
Address of the node (generally also called host or network node)
Subnet mask
The subnet mask splits these two addresses. It determines which part of the IP address
addresses the network and which part of the IP address addresses the node.
The set bits of the subnet mask determine the network part of the IP address.
Example:
Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000
In the example given for the above IP address, the subnet mask shown here has the following
meaning:
The first 2 bytes of the IP address identify the subnet - i.e. 140.80. The last two bytes address
the node, thus 0.2.
It is generally true that:
The network address results from AND linking the IP address and subnet mask.
The device address results from AND NOT linking the IP address and subnet mask.
Relation between IP address and default subnet mask
An agreement exists relating to the assignment of IP address ranges and so-called "Default
subnet masks". The first decimal number (from the left) in the IP address determines the
structure of the default subnet mask. It determines the number of "1" values (binary) as follows:
IP address (decimal) IP address (binary) Address class Default subnet mask
0 to 126 0xxxxxxx.xxxxxxxx.... A 255.0.0.0
128 to 191 10xxxxxx.xxxxxxxx... B 255.255.0.0
192 to 223 110xxxxx.xxxxxxxx... C 255.255.255.0
Note
Range of values for the first decimal point
A value of between 224 and 255 is also possible for the first decimal number of the IP address
(address class D etc). This is, however, not recommended because there is no address check
for these values.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
330 System Manual, 08/2011,
Masking other subnets
You can use the subnet mask to add further structures and form "private" subnets for a subnet
that is assigned one of the address classes A, B or C. This is done by setting other lower points
of the subnet mask to "1". For each bit set to "1", the number of "private" networks doubles
and the number of nodes they contain is halved. Externally, the network functions like an
individual network as it did previously.
Example:
You have a subnet of address class B (for example IP address 129.80.xxx.xxx) and change
the default subnet mask as follows:
Masks Decimal Binary
Default subnet mask 255.255.0.0 11111111.11111111.00000000.
00000000
Subnet mask 255.255.128.0 11111111.11111111.10000000.
00000000
Result:
All nodes with addresses between 129.80.001.xxx and 129.80.127.xxx are on one subnet, all
nodes with addresses between 129.80.128.xxx and 129.80.255.xxx are on another subnet.
Router
The task of the routers is to connect the subnets. If an IP datagram is to be sent to another
network, it first has to be conveyed to a router. To make this possible, you have to enter the
address of the router for each node in the subnet.
The IP address of a node in the subnet and the address of the router may only differ at the
points at which there is a "0" in the subnet mask.
Network configuration of AS interface
AS-Interface consists of an AS-i master and AS-i slaves connected to each other over an AS-
i subnet.
Rules for AS interface network configuration
All the nodes in an AS-i subnet must have a different AS-i node address.
You should only load the settings over the network when all the modules in a subnet have
different addresses and when the actual structure matches that of the network configuration
you have created.
One AS-i master and up to 31 AS-i slaves can be operated on one AS-i subnet.
For more information on configuring an AS-Interface with an AS-i master and AS-i slaves, refer
to the section on AS-Interface and the documentation of the AS-i master modules.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 331
8.1.3.2 Communication via connections
Working with connections
S7 connection
Introduction to configuring connections
Definition
A connection defines a logical assignment of two communication partners in order to undertake
communication services. A connection defines the following:
Communication partner involved
Type of connection (for example, S7 connection)
Special properties (e.g., whether a connection is established permanently or whether it is
established and terminated dynamically in the user program, and whether status messages
are to be sent)
Connection path
What you need to know about connection configuration
During connection configuration, a local connection name is assigned for an S7 connection as
a unique local identification.
In the network view, a "Connections" tab is displayed in addition to the "Network overview"
tab. This tab contains the connection table. A row in this connection table represents a
configured connection from the viewpoint of the local communication partner with its properties,
for example, between two S7-1200 CPUs.
What you need to know about using connection resources
Introduction
Each connection requires connection resources for the end point and/or transition point on the
devices involved. The number of connection resources is device-specific.
If all the connection resources of a communication partner are assigned, no new connections
can be established. This situation is apparent when a newly created connection in the
connection table has a red background. The configuration is then inconsistent and cannot be
compiled.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
332 System Manual, 08/2011,
S7 connections
In the case of S7 connections via the PN interface, one connection resource per S7 connection
is assigned for the endpoint for the S7-1200 CPU. One connection resource is also required
for the connection partner.
You can find an overview of available and assigned connection resources for selected S7-1200
CPU in the Inspector window at "Properties > Connection Resources"
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 333
Views containing information about the configured connections
The views described below will provide you with comprehensive access to all the information
and functions regarding configuring and checking communication connections.
Connection display in the network view
Connection table
"Properties" tab for a connection in the inspector window
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
334 System Manual, 08/2011,
Benefits
The information shown in these views are always up-to-date in terms of the current user
actions. This means:
The connection table displays all connections created.
If you have selected a connection in the connection table:
When connection mode is enabled, the connection path is highlighted in the network
view.
The "Properties" tab in the Inspector window displays the parameters of this connection.
The connection table
The connection table offers the following functions:
List of all connections in the project
Selection of a connection and display of connections associated with it in the network view
(when connection mode is enabled)
Changing of connection partners
Display showing status information
"Properties" tab for a connection in the inspector window
The properties dialog has the following meaning:
Display for connection parameters
Display of connection path
Subsequent specification of connections using the "Find connection path" button
Creating a new connection
Creating a connection - alternatives
You have the following options for creating a connection in the network view:
Graphic connection configuration
Interactive connection configuration
You'll find the individual steps for this in the following chapters.
Requirement and result
In the network view, you have add devices between which the connections should be
configured.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 335
Specifying a connection
If both partners for the connection type selected are networked on the same network, use the
graphic or interactive selection of both communication partners to create a fully specified
connection.
This connection is entered automatically in the connection table of the S7-1200 CPU. A local
connection name is assigned for this connection.
The following schematic shows a configured connection with a networked device:
Creating a new connection graphically
Graphically configuring connections
In the case of graphic connection configuration, the connection path is automatically specified
provided interfaces and resources are available. Select the devices to be connected in the
current configuration.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
336 System Manual, 08/2011,
Automatically determining connection path
To create a connection graphically, follow these steps:
1. Click the "Connections" button.
This step activates the connection mode: You can now select the connection type you want.
You will see this from the following:
The devices that can be used for the connection type selected in your project are color-
highlighted in the network view.
2. Hold down the mouse button and drag the mouse pointer from the device from which the
connection will originate to the device at which the connection ends.
3. Release the mouse button over the destination device to create the connection between
the two devices.
Result
A specified connection is created.
The connection path is highlighted.
The connection is entered in the connection table.
Configuring a connection when there is no or no clear network assignment
Any networking not in place will if possible be created automatically when a connection is
created. A query will be made upon completion of connection configuration if unique network
assignment is not possible. You will be able to choose from the existing subnets.
Example below: A query is made upon creation of a connection between stations PLC_1 and
PLC_2, which are not yet networked.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 337
Interactively creating a new connection
Interactively configuring connections
Define the local device and its connection partners.
Procedure
Proceed as follows to interactively create a connection:
1. Select the "Add new connection" command in the shortcut menu of a connection partner
for which you want to create a connection.
The "Create new connection" dialog appears.
2. Select the partner endpoint.
In the right pane of the dialog, a possible connection path fitting the selected endpoint is
displayed, if available. Incomplete paths, for example, for a non-specified CPU, are marked
by an exclamation mark on a red background.
3. To accept the configured connection and to configure additional connections to other
endpoints, click "Add".
To close the dialog, click "OK".
Working in the network view
Highlighting connection path and partner in the network view
To display the connection partners for all or certain connection types in the network view,
proceed as follows:
1. Click the "Connections" button.
2. Select the S7-CPU for which you want to display the connection partners in the network
view and then select the "Highlight connection partners" command in the shortcut menu.
3. Select "All connection partners" in the following menu.
The local device and the CPUs of the target devices are selected. The local connection
partner shows an arrow pointing right and the remote connection partners show an arrow
pointing left.
4. To open a list with information on the target devices, click the arrow of the local device.
This additional function is useful in complex network configurations in which some devices
are not visible.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
338 System Manual, 08/2011,
Note
You can display one of the connection partners which cannot be seen in the current display
range of the network view. Click on the communication partner in the list that appears. Result:
The display is moved such that the connection partner becomes visible.
Working with the connection table
Basic functions for tables
The connection table supports the following basic functions for editing a table:
Changing column width
Displaying the meaning of a column, a row or cell using tooltips.
Changing column width
To adjust the width of a column to the content so that all texts in the lines are legible, follow
these steps:
1. Position the cursor in the header of the connection table to the right of the column that you
want to optimize until the cursor changes its shape to two parallel lines (as if you wanted
to change the width of the column by dragging it with the cursor).
2. Double click on this point.
or
1. Open the shortcut menu on the header of the table.
2. Click on
"Optimize column width" or
"Optimize width of all columns".
For columns that are too narrow, the complete content of specific fields is shown when you
pause with the cursor on the respective field.
Show / hide columns
You can use the shortcut menu of the header of the connection table to control the display of
the various table columns. The shortcut menu entry "Show/hide columns" provides you with
an overview of the available columns. Use the check box to control whether columns are shown
or hidden.
If you want to store the layout, width and visibility of the table columns, click on the "Remember
layout" function in the top right-hand of the network view.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 339
Symbol Meaning
Remember layout
Saves the current table view. The layout, width and visibility of columns in the table view is
stored.
Using cursor keys to move within the connection table
You can use the UP and DOWN cursor keys to select a connection from the connection table;
the selected connection is marked and is shown highlighted in the network view.
Changing properties of connection
You can directly edit some of the parameters displayed in the connection table. The name of
the connection can, for example, only be changed in the connection table.
Changing connection partners
You can change the connection partner of a connection as follows:
1. Select the connection.
2. Select the new connection partner from the open drop-down list in the "Partner" column.
Deleting connections
You can delete configured connections via the network view or the connection table.
In the network view you can delete a highlighted connection. In the connection table you can
delete one or more connections.
Procedure
To delete a connection, proceed as follows:
1. Select the connection to be deleted:
In the network view: Select the connection to be deleted.
In the connection table: Select the rows of the connections to be deleted (multiple
selection possible).
2. Open the shortcut menu with a right mouse click.
3. Select the "Delete" command.
The selected connection will be completely deleted.
Copying connections
Introduction
Connections are not copied singly but always in context along with the project or the device.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
340 System Manual, 08/2011,
You can copy:
Entire projects
One or more devices within a project or from one project to another
Copying a project
When you copy a project all configured connections will also be copied. No settings whatsoever
are required for the copied connections because the connections remain consistent.
Copying devices
If you copy devices for which connections have been configured, the connections are copied
as well. To complete the connection path, you must still finalize the networking.
An S7-1200 CPU with a V.10 firmware is merely a server for connections and has no
connection configuration itself. Consequently, no connections are copied along with it when
an S7-1200 CPU with a V1.0 firmware is copied.
Inconsistent connections - connections without assignment
With an inconsistent connection the structure of the connection data is destroyed or the
connection is not functional in the project context.
Inconsistent connections cannot be compiled and loaded - operation is not possible with such
a connection.
In the connection table inconsistent connections are marked in red.
Possible causes for inconsistent connections
Deletion or change of the hardware configuration.
Missing interface network links in the project, which are necessary for a connection.
Connection resources are exceeded
Connections to an unspecified connection partner without partner address information.
Detailed information regarding the reasons for the inconsistency can be found in the "Compile"
tab following compilation (Edit > Compile).
Remedies
To assign a closed connection path to an existing open connection path, expand the device
configuration in such a way that the interfaces required for the connection type are available
for both partners. At "Properties > General > Interface" in the Inspector window, you can use
the "Find connection path" button to create a connection to an existing partner.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 341
S7 connection - general settings
General connection parameters
General connection parameters are displayed in the "General" parameter group under the
properties of the connection; these connection parameters identify the local connection end
point.
Here, you can assign the connection path and specify all aspects of the connection partner.
Local ID
The local ID of the module from which the connection is viewed is displayed here (local partner).
You can change the local ID. You may need to do this if you have already programmed
communication function blocks, and you want to use the local ID specified in those function
blocks for the connection.
Special connection properties
Display of connection properties (can be modified depending on the components used):
One-way
One-way means that the connection partner functions as a server on this connection and
cannot send or receive actively.
Active connection establishment
In the case of one-way connection, for example with a S7-1200 CPU (firmware version
V1.0), a connection partner can only be provided for the active connection establishment.
In the case of a two-way connection you can set which connection partner will assume the
active role.
Sending operating mode messages
Indicates whether or not the local partner sends operating mode messages to the
connection partner.
Address details
Displaying address details of the S7 connection. With an unspecified partner, the values for
the rack and slot can be changed. All other values are obtained from the current configuration
and cannot be changed.
S7 connection - address details
Meaning
The address details show the end points of the connection and can localize these via the
specification of rack and slot.
When a connection is established, the connection-specific resources of a module are assigned
specifically to this connection. This assignment requires that the connection resource can be
addressed. The TSAP (Transport Service Access Point) is, as it were, the address of the
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
342 System Manual, 08/2011,
resource that is formed with the help of the connection resource or, in the case of S7-1200
CPUs (firmware V2.0 or higher) with the SIMATIC-ACC (SIMATIC Application Controlled
Communication).
Configuration of TSAP for S7-1200
For S7-1200 CPU (firmare V2.0 or higher):
"SIMATIC-ACC"<nnn><mm>
nnn = Local ID
mm = any value
For S7-1200 CPU (firmare V1.0):
<xx>.<yz>
xx = Number of the connection resource
y = Rack number
z = Slot number
TSAP structure, dependent on partner
The configuration of the TSAP for S7-1200 CPUs is dependent on the respective firmware and
on the remote connection partner. When a S7-1200 CPU is connected with a S7-300/400 CPU,
a S7-1200 CPU also uses a TSAP configuration that includes the connection resource.
See the following examples for TSAPs of various connection configurations
Connection between two S7-1200 CPUs (both with firmware V2.0):
S7-1200 CPU "A" with firmware V2.0 and local ID 100:
TSAP: SIMATIC-ACC10001
S7-1200 CPU "B" with firmware V2.0 and local ID 5AE:
TSAP: SIMATIC-ACC5AE01
Connection between two S7-1200 CPUs (firmware V2.0 and V1.0):
S7-1200 CPU with firmware V2.0 and local ID 1FF:
TSAP: SIMATIC-ACC1FF01
S7-1200 CPU with firmware V1.0 (rack 0, slot 1, connection resource 03):
TSAP: 03.01
Connection between S7-1200 CPUs (firmware V2.0) and S7-300/400 CPU:
S7-1200 CPU with firmware V2.0 (rack 0, slot 1, connection resource 12):
TSAP: 12.01
S7-300/400 CPU (rack 0, slot 2, connection resource 11):
TSAP: 11.02
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 343
HMI connection
Introduction to configuring connections
Definition
A connection defines a logical assignment of two communication partners in order to undertake
communication services. A connection defines the following:
Communication partner involved
Type of connection (e.g., HMI connection)
Special properties (e.g., whether a connection is established permanently or whether it is
established and terminated dynamically in the user program, and whether status messages
are to be sent)
Connection path
What you need to know about connection configuration
During connection configuration, a local connection name is assigned for an HMI connection
as a unique local identification.
In the network view, a "Connections" tab is displayed in addition to the "Network overview"
tab. This tab contains the connection table. A line in this connection table represents a
configured connection, e.g., between an HMI device and PLC, along with its properties.
What you need to know about using connection resources
Introduction
Each connection requires connection resources for the end point and/or transition point on the
devices involved. The number of connection resources is device-specific.
If all the connection resources of a communication partner are assigned, no new connections
can be established. This situation is apparent when a newly created connection in the
connection table has a red background. The configuration is then inconsistent and cannot be
compiled.
HMI connections
For HMI connections via the integrated PN interface, one connection resource for the endpoint
per HMI connection is occupied for the HMI device.
One connection resource is also required for the connection partner (PLC).
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
344 System Manual, 08/2011,
Views containing information about the configured connections
The views described below will provide you with comprehensive access to all the information
and functions regarding configuring and checking communication connections.
Connection display in the network view
Connection table
"Properties" tab for a connection in the inspector window
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 345
Benefits
The information shown in these views are always up-to-date in terms of the current user
actions. This means:
The connection table displays all connections created.
If you have selected a connection in the connection table:
You will graphically see the connection path in the network view.
The "Properties" tab in the Inspector window displays the parameters of this connection.
The connection table
The connection table offers the following functions:
List of all connections in the project
Selection of a connection and display of connections associated with it in the network view
Changing of connection partners
Display showing status information
"Properties" tab for a connection in the inspector window
The properties dialog has the following meaning:
Display for connection parameters
Display of connection path
Subsequent specification of connections using the "Find connection path" button
Creating a new connection
Creating a connection - alternatives
You have the following options for creating a connection in the network view:
Graphic connection configuration
Interactive connection configuration
You'll find the individual steps for this in the following chapters.
Requirement and result
You have created the devices with CPUs and HMI devices between which you want to
configure connections in the network view.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
346 System Manual, 08/2011,
Specifying a connection
If both partners for the connection type selected are networked on the same network, use the
graphic or interactive selection of both communication partners to create a fully specified
connection.
This connection is entered automatically into the connection table of the HMI device. A local
connection name is assigned for this connection.
The following schematic shows a configured connection with a networked device:
Creating a new connection graphically
Graphically configuring connections
When using the graphic connection configuration, if necessary the system asks you to define
the connection path. Select the devices to be connected in the current configuration.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 347
Automatically determining connection path
To create a connection graphically, follow these steps:
1. Click the "Connections" button.
The connection mode for the connection type you have selected is then activated.
You will see this from the following:
The devices that can be used for the connection type selected in your project are color-
highlighted in the network view.
2. Hold down the mouse button and drag the mouse pointer from the device from which the
connection will originate to the device at which the connection ends.
3. Release the mouse button over the destination device to create the connection between
the two devices.
Result
A specified connection is created.
The connection path is highlighted.
The connection is entered in the connection table.
Interactively creating a new connection
Interactively configuring connections
Define the local device and its connection partners.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
348 System Manual, 08/2011,
Procedure
Proceed as follows to interactively create a connection:
1. Select the "Create new connection" command in the shortcut menu of a connection partner
for which you want to create a connection.
The "Create new connection" dialog is opened.
2. Select the partner endpoint.
In the right pane of the dialog, a possible connection path fitting the selected endpoint is
displayed, if available. Incomplete paths, for example, for a non-specified CPU, are marked
by an exclamation mark on a red background.
3. To close the dialog, click "OK".
To accept the configured connection and to configure additional connections to other
endpoints, click "Apply".
Working in the network view
Highlighting connection path and partner in the network view
To display the connection partners for all or certain connection types in the network view,
proceed as follows:
1. Click the "Connections" button.
2. Select the "Highlight connection partners" command in the shortcut menu for the HMI device
whose connection partners you want to display in the network view.
3. Select "All connection partners" in the following menu.
The local device and the CPUs of the target devices are selected. The local connection
partner shows an arrow pointing right and the remote connection partners show an arrow
pointing left.
4. To open a list with information on the target devices, click the arrow of the local device.
This additional function is useful in complex network configurations in which some devices
are not visible.
Note
You can display one of the connection partners which cannot be seen in the current display
range of the network view. Click on the communication partner in the list that appears. Result:
The display is moved such that the connection partner becomes visible.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 349
See also
Creating a new connection graphically (Page 347)
Working with the connection table
Basic functions for tables
The connection table supports the following basic functions for editing a table:
Changing column width
Displaying the meaning of a column, a row or cell using tooltips.
Changing column width
To adjust the width of a column to the content so that all texts in the lines are legible, follow
these steps:
1. Position the cursor in the header of the connection table to the right of the column that you
want to optimize until the cursor changes its shape to two parallel lines (as if you wanted
to change the width of the column by dragging it with the cursor).
2. Double click on this point.
or
1. Open the shortcut menu on the header of the table.
2. Click on
"Optimize column width" or
"Optimize width of all columns".
For columns that are too narrow, the complete content of specific fields is shown when you
pause with the cursor on the respective field.
Show / hide columns
You can use the shortcut menu of the header of the connection table to control the display of
the various table columns. The shortcut menu entry "Show/hide columns" provides you with
an overview of the available columns. Use the check box to control whether columns are shown
or hidden.
Using cursor keys to move within the connection table
You can use the UP and DOWN cursor keys to select a connection from the connection table;
the selected connection is marked and is shown highlighted in the network view.
Changing properties of connection
You can directly edit the parameters displayed in the connection table in some cases. To
change the name of a connection, you do not have to navigate to the Inspector window.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
350 System Manual, 08/2011,
Changing connection partners
You can change the connection partner of a connection as follows:
1. Select the connection.
2. Select the new connection partner from the open drop-down list in the "Partner" column.
Deleting connections
You can delete configured connections via the network view or the connection table.
In the network view you can delete a highlighted connection. In the connection table you can
delete one or more connections.
Procedure
To delete a connection, proceed as follows:
1. Select the connection to be deleted:
In the network view: Select the connection to be deleted.
In the connection table: Select the rows of the connections to be deleted (multiple
selection possible).
2. Open the shortcut menu with a right mouse click.
3. Select the "Delete" command.
The selected connection will be completely deleted.
Copying connections
Introduction
Connections are not copied singly but always in context along with the project or the device.
You can copy:
Entire projects
One or more devices within a project or from one project to another
Copying a project
When you copy a project all configured connections will also be copied. No settings whatsoever
are required for the copied connections because the connections remain consistent.
Copying devices
If you copy devices for which connections have been configured (HMI devices), the
connections are copied as well. To complete the connection path, you must still finalize the
networking.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 351
An S7-1200 CPU with a V.10 firmware is only a server for connections and has no connection
configuration itself. Consequently, no connections are copied along with it when an S7-1200
CPU with a V1.0 firmware is copied.
Inconsistent connections - connections without assignment
With an inconsistent connection the structure of the connection data is destroyed or the
connection is not functional in the project context.
Inconsistent connections cannot be compiled and loaded - operation is not possible with such
a connection.
In the connection table inconsistent connections are marked in red.
Possible causes for inconsistent connections
Deletion or change of the hardware configuration.
Missing interface network links in the project, which are necessary for a connection.
Connection resources are exceeded
Errors when backing up data due to insufficient memory
Connections to an unspecified connection partner without partner address information.
Detailed information regarding the reasons for the inconsistency can be found in the "Compile"
tab following compilation (Edit > Compile).
Remedies
If the connection cannot be repaired by opening the connection properties, changing them or
undoing them in the configuration, then it may be necessary to delete the connection and re-
create it.
HMI connection general settings
General connection parameters
General connection parameters are displayed in the "General" parameter group under the
properties of the connection; these connection parameters identify the local connection end
point.
Here, you can also assign the connection path and specify all aspects of the connection
partner.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
352 System Manual, 08/2011,
Special connection properties
Display of the connection properties (cannot be changed):
Active connection establishment
The connection establishment always starts from the HMI device. This option is selected
by default if the address of the partner is specified.
One-way
One-way means that the connection partner functions as a server on this connection and
cannot send or receive actively.
Sending operating mode messages
Not relevant for HMI devices.
Address details
Displaying address details of the HMI connection. With an unspecified partner, the values for
the rack and slot can be changed. All other values are obtained from the current configuration
and cannot be changed.
Miscellaneous
Display of the access points for the online connection between HMI device and connection
partner.
Using Open User Communication
Basics of Open User Communication
Introduction
Open User Communication is the name of a program-controlled communications technique
for communication via the integrated PN/IE interface of the CPU. Various connection types
are available for this communications technique.
The main feature of Open User Communication is its high degree of flexibility in terms of the
data structures transferred. This allows open data exchange with any communicating devices
providing they support the connection types available here. Since this communication is
controlled solely by instructions in the user program, event-driven connection establishment
and termination is possible. Connections can also be modified by the user program during
runtime.
For S7-1200 CPUs with an integrated PN/IE interface, the TCP, UDP and ISO-on-TCP
connection types are available for Open User Communication. The communications partners
can be two SIMATIC PLCs or a SIMATIC PLC and a suitable third-party device.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 353
Instructions for Open User Communication
To create the connections, you have various instructions available after opening the program
editor in the "Instructions > Extended instructions > Communication" task card:
Compact instructions for sending or receiving data via integrated functions for establishing
and terminating the connection:
TSEND_C (connection establishment/termination, sending)
TRCV_C (connection establishment/termination, receiving)
Individual instructions for sending and receiving data or for establishing or terminating
connections:
TCON (connection establishment)
TDISCON (connection termination)
TSEND (TCP or ISO-on-TCP: Sending)
TRCV (TCP or ISO-on-TCP: Receiving)
TUSEND (UDP: Sending)
TURCV (UDP: Receiving)
Connection establishment
For Open User Communication, instructions for establishing and terminating the connection
must exist for both communications partners. One communications partner sends its data
using TSEND, TUSEND or TSEND_C while the other communications partner receives the
data using TRCV, TURCV or TRCV_C.
One of the communications partners starts the connection establishment as the active partner.
The other communications partner reacts by starting its connection establishment as the
passive partner. If both communication partners have initiated their connection establishment,
the communication connection is fully established.
Connection parameter assignment
You can assign parameters to establish the connection using a connection description DB with
the TCON_Param structure as follows:
Manually create, assign parameters and write directly to the instruction.
Supported by connection parameter assignment.
Connection parameter assignment supports the establishment of the connection and should,
therefore, be given preference over the other methods.
You specify the following in the connection parameter assignment:
Connection partner
Connection type
Connection ID
Connection description DB
Address details according to selected connection type
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
354 System Manual, 08/2011,
In addition, you specify here which communication partner activates the connection
establishment and which partner establishes a connection passively in response to a request
from its communications partner.
See also
Principle of operation of connection-oriented protocols (Page 364)
Overview of connection parameter assignment
Introduction
You will find the connection configuration in the Inspector window of the program editor if you
want to program Open User Communication with the communication instructions TSEND_C,
TRCV_C or TCON.
Connection parameter assignment supports the flexible functionality of communications
programming: The parameters entered for the connection configuration are stored in an
automatically created global DB derived from the structure of the TCON_Param type. You can
modify the connection parameters in this connection description DB.
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 355
Structure of the connection parameter assignment
The connection parameter assignment is made up of the following components:
Editing devices and networks
8.1 Configuring devices and networks
WinCC Advanced V11.0 SP1
356 System Manual, 08/2011,
Alarm class
Alarm classes, such as "Warnings" or "Errors". The alarm class defines the following for an
alarm:
Acknowledgment model
Appearance in Runtime (e.g. color)
Logging
Note
Device dependency
Logging is not available for all HMI devices.
Alarm number
An alarm is identified by a unique alarm number. The alarm number is assigned by the system.
You can change the alarm number to a sequential alarm number, if necessary, to identify
alarms associated in your project.
Time and date
Every alarm has a time stamp that shows the time and date at which the alarm was triggered.
Alarm status
An alarm has the events "Incoming," "Outgoing," "Acknowledge." For each event, a new alarm
is output with the current status of the alarm.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 963
Alarm text
The alarm text describes the cause of the alarm.
The alarm text can contain output fields for current values. The values you can insert depend
on the Runtime in use. The value is retained at the time at which the alarm status changes.
Alarm group
The alarm group bundles individual alarms.
Tooltip
You can configure a separate tooltip for each alarm; the user can display this tooltip in Runtime.
Trigger tag
Each alarm is assigned a tag as trigger. The alarm is output when this trigger tag meets the
defined condition, e.g. when its state changes or it exceeds a limit.
Limit value
Analog alarms indicate limit violations. Depending on the configuration, WinCC outputs the
analog alarm as soon as the trigger tag exceeds or undershoots the limit value.
See also
Output of a tag value in the alarm text (Page 977)
Alarm states (Page 955)
Basics on alarm classes (Page 957)
Alarm groups (Page 961)
9.3.2.2 Configuring Alarms
Overview of alarm configuration tasks
Steps to configure alarms
Configuring alarms in WinCC involves the following steps:
1. Edit and create alarm classes
You use the alarm class to define how an alarm will be displayed in runtime and to define
the acknowledgment model for it.
2. Creating tags in the "HMI tags" editor
Configure the tags for your project.
You create range values for the tags.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
964 System Manual, 08/2011,
1. Creating tags in the "HMI alarms " editor
Create custom alarms and assign these the tag to be monitored, alarm classes, alarm
groups, and other properties.
You can also assign system functions or scripts to the alarm events.
2. Output of configured alarms
To output configured alarms, configure an alarm view or an alarm window in the "Screens"
editor.
Additional configuration tasks
Additional tasks may be necessary for configuring alarms, depending on the requirements of
your project:
1. Creating alarm groups
You assign the alarms of your project to alarm groups according to their association, such
as by the cause of the problem (power failure) or source of the error (Motor 1).
2. Configuring Loop-In-Alarm
A Loop-In-Alarm is configured in order to change to a screen containing relevant information
on an alarm received.
Overview of alarm configuration tasks
Steps to configure alarms
Configuring alarms in WinCC involves the following steps:
1. Edit and create alarm classes
You use the alarm class to define how an alarm will be displayed in runtime and to define
the acknowledgment model for it.
2. Creating tags in the "HMI tags" editor
Configure the tags for your project.
You create range values for the tags.
1. Creating tags in the "HMI alarms " editor
Create custom alarms and assign these the tag to be monitored, alarm classes, alarm
groups, and other properties.
You can also assign system functions or scripts to the alarm events.
2. Output of configured alarms
To output configured alarms, configure an alarm view or an alarm window in the "Screens"
editor.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 965
Additional configuration tasks
Additional tasks may be necessary for configuring alarms, depending on the requirements of
your project:
Activating and editing system events
You can import system events when you initially open the "System events" tab in the "HMI
alarms" editor. On completion of the import, you can edit the system events.
Activating and editing controller alarms
For integrated operation of a project in STEP 7, specify the controller alarms to be displayed
on your HMI device in the alarm settings.
Creating alarm groups
Assign the alarms of your project to alarm groups based on their relation, e.g. by error cause
(e.g. "power failure"), or by error source (e.g. "Motor 1").
Configuring Loop-In-Alarm
Configure a Loop-In-Alarm in order to change to a screen that contains information about
an incoming alarm.
Configuring Alarm Classes
Creating alarm classes
Introduction
Create alarm classes in the "Alarm classes" tab of the "HMI alarms" editor. Some default alarm
classes are already created for every project. You can create additional custom alarm classes.
You can create up to 32 alarm classes.
Requirement
The "HMI alarms" editor is open.
The Inspector window is open.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
966 System Manual, 08/2011,
Procedure
To create an alarm class, proceed as follows:
1. Click the "Alarm Classes" tab.
The predefined and existing custom alarm classes are displayed. The following table lists
the predefined alarm classes:
1. Double-click "<Add>" in the table.
A new alarm class is created. Each new alarm is automatically assigned a static ID.
The properties of the new alarm class are shown in the Inspector window.
2. Configure the alarm class under "Properties > Properties >General" in the Inspector window.
Enter a "Name" and the "Display name".
Depending on the HMI device, you can also activate logging, or automatic sending of e-
mails.
3. Define the acknowledgment model for the alarm class under "Properties > Properties >
Acknowledgment" in the Inspector window.
4. Change the default text under "Properties > Properties > Status" in the Inspector window.
This text indicates the status of an alarm in Runtime.
5. Change the default colors under "Properties > Properties > Colors" in the Inspector window.
Depending on the HMI device, also change the flashing characteristics.
These settings define how alarms from this alarm class are displayed in Runtime.
Note
To display the alarm classes in color in Runtime, the "Use alarm class colors" option must
be activated. In the project navigation, enable "Runtime settings > Alarms > General > Use
alarm class colors" accordingly. This option is selected in a new project in WinCC.
See also
Predefined alarm classes (Page 958)
Basics on alarm classes (Page 957)
Using project-wide alarm classes
Introduction
Project-wide alarm classes are displayed under "Shared data > Alarm classes" in the project
navigation. Create additional common alarm classes in WinCC.
Controller alarms are assigned to common alarm classes. If you work with controller alarms,
common alarm classes are automatically loaded in WinCC.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 967
Requirements
You have created a project.
Creating project-wide alarm class
To create a project-wide alarm class, proceed as follows:
1. Double-click "Shared data > Alarm classes" in the project navigation.
The "Project-wide message classes" editor opens in the work area.
2. To create a project-wide message class, double-click in the first empty line of the table
editor.
3. Specify the name and display name of the alarm class.
4. Select "With acknowledgment" if the alarm class requires acknowledgment.
Assign alarms to a common alarm class
Proceed as follows to assign an analog or discrete alarm to a common alarm class:
1. In the "HMI alarms" editor, select the alarm that you want to assign to the common alarm
class.
2. Click "General" in the Inspector window.
3. Click "Shared data > Alarm classes" in the project navigation.
4. Select the common alarm class in the detail view.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
968 System Manual, 08/2011,
5. Drag-and-drop the alarm class to the "Alarm class" selection box or "Alarm class" column
in the work area of the Inspector window of the alarm.
The system creates a new alarm class that is linked to the common alarm class. The new
name of the common alarm class is displayed in the "Alarm class" area of the Inspector
window of the alarm. The display name of the common alarm class is activated for the alarm
class in your project.
6. Click the "Alarm Class" tab.
7. Check to see whether the display name of the common alarm class is displayed in WinCC.
8. You can change the object name of the alarm class.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 969
Alternative procedure
To assign an alarm to a common alarm class, proceed as follows:
1. Click the "Alarm Classes" tab.
The alarm classes are displayed.
2. Click "Shared data > Alarm classes" in the project navigation. The following table shows
the common alarm classes:
3. Select the common alarm class in the detail view.
4. Drag-and-drop the alarm class to the "Alarm classes" tab of the "HMI alarms" editor
The system creates a new alarm class that is linked to the common alarm class. The new
name of the new alarm class in your project is displayed in the "Alarm class" tab.
5. Open the tab with the alarm procedure for the required alarm.
6. Under "General" in the Inspector window, select the alarm and the alarm class linked to the
common alarm class.
Note
Deleting a common alarm class
If you delete a common alarm class, the linked alarm class is maintained. If necessary, link
the alarm class with another common alarm class or use it as WinCC alarm class.
See also
Predefined alarm classes (Page 958)
Basics on alarm classes (Page 957)
Configuring Alarm Groups
Introduction
Create alarm groups on the "Alarm Groups" tab in the "HMI alarms" editor. An alarm group is
a compilation of single alarms. You assign alarms in an alarm group by association, such as
cause of the problem or source of the error. If you acknowledge an alarm from this alarm group
in Runtime, all other alarms in the alarm group are acknowledged automatically.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
970 System Manual, 08/2011,
Requirement
You have created a project.
The "HMI alarms" editor is open.
The Inspector window is open.
Creating a new alarm group
1. Click the "Alarm Groups" tab.
The existing alarm groups are displayed.
2. In the work area of the table, double-click "<Add>" in the first free row.
A new alarm group is created.
3. You can overwrite the proposed "Name".
Result
An alarm group is created. For the group acknowledgment of alarms in Runtime, assign the
associated alarms that require acknowledgment to an alarm group.
Configuring discrete alarms
Introduction
Discrete alarms triggered by the PLC indicate status changes in a plant. They indicate the
opened or closed state of a valve, for example.
The following sections describes the configuration procedures in the "HMI alarms" editor. You
can also configure discrete alarms in the "HMI tags" editor.
Requirements
The "HMI alarms" editor is open.
The Inspector window is open.
You have created the required alarm classes and alarm groups.
Procedure
To configure a discrete alarm, proceed as follows:
1. Open the "Discrete alarms" tab.
2. To create a new discrete alarm, double-click in the work area on "<Add>".
A new discrete alarm is created.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 971
3. To configure the alarm, select "Properties > Properties >General" in the Inspector window:
Enter an alarm text as event text.
Use the functions of the shortcut menu to format the text on a character-by-character
basis, or to insert output fields for HMI tags, or texts from the text lists.
You can renumber the alarm.
Select the alarm class and the alarm group, if necessary.
4. In the Inspector window, select the tag and the bit that triggers the alarm under "Properties
> Properties > Trigger". Note the following information:
Use the data types "Int" or "UInt" to select an HMI tag.
Use the data types "Int" or "Word" to select a PLC tag.
Use trigger tag bits only for alarms.
Do not use trigger tags for anything else.
If you want to acknowledge the alarm via the PLC, use this tag also as PLC
acknowledgment tag.
NOTICE
Note the method used to count bits in the utilized PLC when specifying the bit. For more
information, refer to the "Communication" section in the PLC Online Help.
Note
If the object does not yet exist in the selection list, create it directly in the object list and change
its properties later.
Status-dependent alarm texts
To display a different text independent of the alarm status, link a text list to the alarm text. You
control the text list with a tag.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
972 System Manual, 08/2011,
Additional settings for discrete alarms
Creating a tooltip
To configure a tooltip for the alarm, follow these steps:
Enter your text under "Properties > Properties > Tooltip".
Configuring event-driven tasks
To configure event-driven tasks, such as a loop-in alarm, follow these steps:
1. Select the discrete alarm.
2. Select "Properties > Events" in the Inspector window and configure a new function list for
the relevant event.
See also
Configuring trigger for alarm acknowledgment (Page 1003)
Output of a tag value in the alarm text (Page 977)
Formatting alarm text (Page 976)
Configuring loop-in alarm (Page 982)
Configuring analog alarms
Introduction
Analog alarms indicate limit violations. For example, if the speed of a motor drops below a
certain value, an analog alarm is triggered.
Requirements
The "HMI alarms" editor is open.
The Inspector window is open.
You have created the required alarm classes and alarm groups.
Procedure
To configure an analog alarm, proceed as follows:
1. Click the "Analog alarms" tab.
2. To create a new analog alarm, double-click in the table on "<Add>".
A new analog alarm is created.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 973
3. To configure the alarm, select "Properties > Properties >General" in the Inspector window:
Enter an alarm text as event text.
Format the text character-for-character using the shortcut menu.
Using the shortcut menu, you can insert output fields for HMI tags, or text from text lists.
You can renumber the alarm.
Select the alarm class and the alarm group, if necessary.
4. Configure the tag that triggers the alarm under "Properties > Properties > Trigger >
Settings".
Do not use trigger tags for anything else.
Configure limit values for an analog alarm
1. In the Inspector window, click the button under "Properties > Properties > Trigger >
Limit > Value".
To use a constant as limit value, select "Constant".
Enter the required limit value.
To use a tag as limit value, select "HMI tag".
The button is shown. Use this button to select the tag you want to use.
Note
If the required tag does not exist in the selection list yet, create it in the object list and
change its properties later.
2. Select the mode:
"High limit violation": The alarm is triggered when the limit is exceeded.
"Low limit violation": The alarm is triggered when the limit is undershot.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
974 System Manual, 08/2011,
Optional settings for analog alarms
Setting the delay time
To set the delay time, proceed as follows:
Enter a time period in the Inspector window under "Properties > Properties> Trigger >
Settings > Delay".
The alarm is only triggered when the trigger condition is still present after the delay time
has elapsed.
Setting the deadband
Note
If a process value fluctuates around the limit, the alarm associated with this fault may be
triggered multiple times. To prevent this from happening, configure a deadband or delay
time.
To enter the deadband, follow these steps:
1. Under "Properties > Properties> Trigger > Deadband > Mode", select the change in alarm
status for which the deadband is to be taken into account.
2. Enter a constant value under "Value".
3. To define the deadband value as a percentage of the limit, set the "in %" check box.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 975
Automatic reporting
To print the alarms continuously:
Select the "Activate" option under "Properties > Properties > Miscellaneous > Report."
Note
Device dependency
Reporting is not available for all HMI devices.
Creating a tooltip
To configure a tooltip for the alarm, follow these steps:
Select "Properties > Properties > Tooltip" in the Inspector window and enter your text.
Configuring event-driven tasks
To configure event-driven tasks, such as a loop-in alarm, follow these steps:
1. Select the analog alarm.
2. Select "Properties > Events" in the Inspector window and configure a new function list for
the relevant event.
See also
Configuring trigger for alarm acknowledgment (Page 1003)
Output of a tag value in the alarm text (Page 977)
Formatting alarm text (Page 976)
Configuring loop-in alarm (Page 982)
Formatting alarm text
Requirements
The "HMI alarms" editor is open.
An alarm has been created.
Procedure
To format an alarm text, proceed as follows:
1. Select the alarm to edit.
2. In the Inspector window, select the characters to format under "Properties > Properties >
General > Alarm text".
3. Select the formatting from the shortcut menu, e.g. "Underscored" or "Uppercase".
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
976 System Manual, 08/2011,
Result
The selected characters are displayed in Runtime with the selected formatting.
Removing format settings
To remove all text formats, proceed as follows:
1. In the Inspector window, select the characters whose formatting you want to remove in the
alarm text.
2. Select "Delete formatting characters" from the shortcut menu.
Result
The selected characters are displayed in unformatted notation in Runtime.
Output of a tag value in the alarm text
Introduction
In WinCC, you can insert output fields into the alarm text which display the content of tags.
Requirements
The "HMI alarms" editor is open.
The alarm is selected.
Output of a tag value in the alarm text
To insert an output field for a tag value in the alarm text, proceed as follows:
1. Place the cursor onto the required position in the event text.
2. Select "Insert tag output field" in the shortcut menu.
3. Open the object list under "Tag" and select a tag.
You can also create the tag in the object list.
4. Under "Format", specify the length of the output field and the format for tag value output in
the alarm text.
Configure an output field of sufficient size. Otherwise, the tag content is not output to the
full extent in the alarm.
5. Click to save your entries.
WinCC inserts a placeholder for the output field into the alarm text: "<tag: n, [tag name]>"
whereby n = text string length.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 977
Editing output field properties
To edit the properties of an output field, proceed as follows:
Double-click on the output field in the alarm text and edit the settings.
Deleting an output field from the alarm text
To delete an output field from the alarm text, proceed as follows:
Select the output field in the alarm text and then select the "Delete" command from the
shortcut menu.
Note
The sequence of the tag output fields in the alarm text depends on the language. The
sequence of the Runtime language is used for logging alarms to a CSV log file.
Changing the tag of an output field in one language causes the modified output field to appear
at the end of the alarm text in all other languages. This changes the sequence of the output
fields in the log.
Device dependency
Logging is not available for all HMI devices.
Output of texts from a text list in an alarm
Introduction
Text lists are used to create dynamic alarm texts. For example, you can configure the output
of both states of a discrete alarm in an alarm text.
Insert a corresponding output field in the alarm text and specify the tag that returns the search
key for the text list.
Requirements
A text list is created.
The "HMI alarms" editor is open
The alarm is selected
Output of a text list value in an alarm text
To insert an output field for a value from a text list in the alarm text, proceed as follows:
1. Place the cursor at the required position in the alarm text.
2. Select "Insert text list output field" command from the shortcut menu.
3. Select the text list under "Text list".
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
978 System Manual, 08/2011,
4. Open the object list under "Tag" and select the tag that returns the search key for the text
list.
You can also create the tag in the object list.
5. Define the length of the output field under "Format".
Configure an output field of sufficient size so that the complete text from the text list is
displayed in the alarm.
6. Click on the icon to save your entries.
WinCC inserts a placeholder for the output field into the alarm text:
""<textlist: n, [textlist name]>" whereby n = text string length.
Editing output field properties
To edit the properties of an output field, proceed as follows:
Double-click on the output field in the alarm text and edit the settings.
Deleting text list from the alarm text
To delete an output field from the alarm text, proceed as follows:
Select the output field in the alarm text and then select the "Delete" command from the
shortcut menu.
Editing System Events
Editing system events
When you open the "System events" tab in the "HMI alarms" editor, WinCC prompts you to
import or update the system events. Import the system events and specify the display period.
You cannot delete or create new system events. You can only edit the alarm text with system
events.
Requirements
You have imported the system events.
Specifying the display period
To determine the display period, proceed as follows:
1. Double-click "Runtime settings" in the project navigation.
2. Enter a value under "Alarms > System events > Display period".
This value specifies a time in seconds during which the system events are displayed on
the HMI device. If you want to display system events permanently, enter "0".
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 979
Changing the alarm text
To change the alarm text of a system event, follow these steps:
1. Open the "HMI alarms" editor and then click the "System events" tab.
2. Select the system event that you want to edit.
1. Change the alarm text under "Properties > Properties > Properties > General" in the
Inspector window.
NOTICE
If you change an alarm text for a system event that contains a placeholder, leave the number
of placeholders unchanged. A placeholder may be a "%1".
Configuring event-driven tasks
The "Incoming" event is available for certain system events, depending on the HMI device. To
configure event-driven tasks, proceed as follows:
1. Select the system event.
2. Select "Properties > Properties > Incoming" in the inspector window and configure a function
list.
Editing controller alarms
Introduction
Controller alarms are configured in STEP 7. Controller alarms are available in WinCC running
in a STEP 7 environment.
In WinCC you only edit the properties of controller alarms that are specific to an HMI device.
Different properties of a controller alarm can be edited, depending on the HMI device and PLC.
You can filter the displayed controller alarms for your project using the display classes that
were configured on the PLC for controller alarms.
Requirements
The connection was established to the PLC.
Alarms were configured in STEP 7.
Editing controller alarms
Proceed as follows to edit controller alarms:
1. Double-click "HMI alarms" in the project navigation.
The "HMI alarms" editor is opened.
2. Open the "Controller alarms" tab.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
980 System Manual, 08/2011,
3. Select the alarm that you want to change in the work area.
4. Make your changes. Depending on the HMI device, it may not be possible to display or
enable some of the controller alarm properties.
Editing SIMATIC S7 alarms
You can edit these controller alarms in the STEP 7 alarm configuration system. To do this,
proceed as follows:
1. Select the alarm that you want to change in the work area.
2. Select "Open in alarm editor of the PLC" from the shortcut menu.
The STEP 7 alarm configuration system is opened.
3. Make your changes.
Filtering the controller alarm using display classes
To filter controller alarms by display classes, proceed as follows:
1. Click "Runtime settings > Alarms" in the project navigation under your HMI device.
One or several connections to a PLC are shown in "Contoller alarms".
2. Select the display classes whose controller alarms you want to display for the connection.
Result
Only those controller alarms whose display class you have enabled for your HMI device will
be displayed on the "Controller alarms" tab of the "HMI alarms" editor.
See also
PLC alarms (Page 953)
Enabling system-defined controller alarms
Enabling system-defined controller alarms
To activate system-defined controller alarms for your HMI device, proceed as follows:
1. Select "Runtime settings > Alarms" in the project navigation.
The alarm settings open.
2. Under "System events" activate the system-defined controller alarms.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 981
3. To display the system events with alarm text, activate "With text".
4. To display these alarms in Runtime, configure an alarm view that displays alarms from the
"Diagnosis Events" alarm class.
Note
For HMI devices with small display units, specify to display only the alarm number for
system-defined controller alarms.
See also
System-defined controller alarms (Page 955)
Configuring loop-in alarm
Introduction
A Loop-In-Alarm is configured in order to change to a screen containing relevant information
on an alarm received.
Requirements
The screen called by the Loop-In-Alarm has been created.
The "HMI alarms" editor is open.
Procedure
To configure a Loop-In-Alarm for an alarm, proceed as follows:
1. Click the tab that contains the alarm for which you want to configure the Loop-In-Alarm.
2. Select the alarm.
3. In the Inspector window, select "Properties > Events > Loop-In-Alarm".
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
982 System Manual, 08/2011,
4. Select the "ActivateScreen" system function.
5. Select the screen called by the Loop-In-Alarm as parameter.
Note
To configure the Loop-In-Alarm for an alarm view with an "alarm line" format, use the
following system functions:
"EditAlarm" for HMI devices with keys
"AlarmViewEditAlarm" for HMI devices without keys
The system functions trigger the "Loop-In-Alarm" event. The alarm line has no buttons.
Result
If you click on the "Loop-In-Alarm" button of the alarm view in Runtime, a screen is opened
with information on the selected alarm.
See also
Configuring discrete alarms (Page 971)
Configuring analog alarms (Page 973)
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 983
Alarms in the "HMI tags" Editor
Configuring discrete alarms
Introduction
In WinCC, you can create and edit discrete and analog alarms, including the trigger tags, in
the "HMI tags" editor.
Note
If you delete, move or copy objects in the "HMI tags" editor, the changes also take effect in
the "HMI alarms" editor.
Requirements
The "HMI tags" editor is open.
Procedure
To configure a discrete alarm, proceed as follows:
1. To create a tag, click on "<Add>" in the table at the top of the work area.
A new tag is created.
2. Configure an internal or external tag as required.
Use the data types "Int" or "UInt" to select an HMI tag.
Use the data types "Int" or "Word" to select a PLC tag.
3. Select the tag at the top of the work area.
4. Click on "<Add>" in the table on the "Discrete alarms" tab at the bottom of the work area.
A new discrete alarm is created for the tag. If you have selected the incorrect data type,
the tag will be marked in the discrete alarm.
5. Configure the discrete alarm in the Inspector window:
Enter the alarm text under "Properties > Properties > General > Alarm text".
You can also insert output fields into the alarm text.
Select an alarm class.
Select the trigger bit of the tag that triggers the discrete alarm under "Properties >
Trigger".
6. You can create additional discrete alarms to monitor the tags.
Note
A tag is monitored using only one alarm type. You should therefore create either analog
alarms or discrete alarms for a tag.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
984 System Manual, 08/2011,
Result
The configured discrete alarms are created in the "HMI tags" editor and displayed in the "HMI
alarms" and "HMI tags" editors.
Configuring analog alarms
Introduction
In WinCC, create the discrete and analog alarms, including the trigger tags, in the "HMI tags"
editor. You can also edit the alarms as in the "HMI alarms" editor. You can create up to two
range values for a tag. You monitor these limits with analog alarms.
Requirements
The "HMI tags" editor is open.
Procedure
To configure an analog alarm in the "HMI tags" editor, proceed as follows:
1. To create a tag, click on "<Add>" in the table at the top of the work area.
A new tag is created.
2. Configure an internal or external tag as required.
3. In the Inspector window, configure the range values of the tags under "Properties >
Properties > Range":
Select whether to use a "Constant" or an "HMI tag" as limit value for your range values.
The object list opens when you select "HMI tag". Select the tag you want to use.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 985
1. Click the "Analog Alarms" tab at the bottom of the work area.
Create an analog alarm for both range values.
2. Select an analog alarm and configure it in the Inspector window:
Enter the alarm text under "Properties > Properties > General > Alarm text".
You can also insert output fields into the alarm text.
You can change the default alarm class.
3. Configure the analog alarms as in the "HMI alarms" editor.
4. Complete the configuration of all analog alarms.
Note
A tag is monitored using only one alarm type. You should therefore create either analog
alarms or discrete alarms for a tag.
Result
The configured analog alarms are created in the "HMI tags" editor and displayed in the "HMI
alarms" and "HMI tags" editors.
9.3.2.3 Configuring the Outputting of Alarms
Overview of configuring alarm output
Steps to complete when configuring alarm output
You configure the alarm output in WinCC in the following steps:
1. Create alarm view
Use the display and control objects in the "Screens" editor to display alarms in Runtime.
You can also configure an alarm view for logged alarms.
2. Configure acknowledgment
In the "Screens" editor, you can set the operator action that will trigger the acknowledgment.
3. Configure reporting
You can create reports in the "Reports" editor to print alarms in Runtime. In the "Scheduler",
"Screens", "HMI alarms" or "HMI tags" editors, you define when and how the printing of a
report is triggered.
Note
Device dependency
Reporting and logging are not available for all HMI devices.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
986 System Manual, 08/2011,
Additional configuration tasks
Additional tasks may be necessary for configuring alarm views, depending on the requirements
of your project:
1. Setting up authorizations
To make sure only authorized operators process the alarms, assign authorizations for the
alarm view and the function keys of the HMI device.
2. Configuring the filtering of the alarm view
You configure the filtering of the alarms in Runtime in the "Screens" editor. You can also
configure alarm views that only display selected alarms.
3. Configure operator input alarms
Configure the operator input alarms on the operator controls of the HMI device in the
"Screens" editor. A preconfigured operator input alarm is output for an operator action. An
operator input is, e.g. the acknowledgment of an alarm.
Displaying alarms
Options for displaying alarms on the HMI device
WinCC offers the following options for displaying alarms on the HMI device:
Alarm view
The alarm view is configured in a screen. More than one alarm can be displayed
simultaneously, depending on the configured size. You can configure multiple alarm views
with different contents.
Alarm window
The Alarm window is configured in the "Global screen" editor. The alarm window can display
multiple alarms at the same time, depending on the configured size. An event can trigger
closing and reopening of the alarm window. To hide it during configuration, create an alarm
window on its own level.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 987
Additional signals
Alarm indicator
The alarm indicator is a configurable, graphical icon. When an alarm comes in, the alarm
indicator is displayed on the HMI device. You configure the alarm indicator in the "Global
screen" editor.
The alarm indicator has two states:
Flashing: At least one alarm that requires acknowledgment is pending.
Static: The alarms are acknowledged but at least one of them has not gone out yet.
The alarm indicator also displays the number of pending alarms according to the HMI
device.
E-mail notification
To inform someone other than the operator, such as an engineer, when an alarm with a
specific alarm class arrives, assign the alarm class to an e-mail address.
Note
Device dependency
E-mail notification is not available for all HMI devices.
System functions
You can configure a list of functions for the event associated with an alarm. These functions
must be executed in Runtime when the event occurs.
Use system functions for alarms in WinCC to control the alarm view or the alarm window
other than via the toolbar.
Displaying the predefined alarm classes in Runtime
The following table shows the symbols used to display the predefined alarm classes in the
alarm view:
Alarm class Displayed icon
"Diagnosis Events" S7
"Errors" !
"System" $
"Warnings" <No symbol>
See also
Configuring an alarm view for active alarms (Page 989)
Configuring an alarm window (Page 994)
Configuring an alarm indicator (Page 995)
Configuring alarm filtering (Page 997)
Displaying Logged Alarms (Page 999)
System functions for alarms (Page 1036)
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
988 System Manual, 08/2011,
Configuring an alarm view
Configuring an alarm view for active alarms
Introduction
Current alarms are displayed in Runtime in an alarm view or alarm window.
Requirement
A screen is open in the "Screen" editor.
The "Tools" task card is open.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 989
Configuring alarms for the alarm view
To specify the alarms that will be shown in the alarm view, proceed as follows:
1. Insert an "Alarm view" object from the "Tools" task card into the screen.
2. Select the alarm view.
In the Inspector window, select "Properties > Properties > General > View > Current
alarm states".
Set whether to display alarms with and/or without mandatory acknowledgment.
To display all alarms in the alarm buffer, enable "Alarm buffer".
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
990 System Manual, 08/2011,
3. In the table, activate the alarm classes to be displayed in the alarm view.
4. Under ""Properties > Properties > View > Control tag for display area", define the tag that
returns the date as of which the alarms will be displayed.
Note
Device dependency
The "Control tag for display area" property is not available for all HMI devices.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 991
Configuring the layout of the alarm view
To specify how the alarms are shown in the alarm view, proceed as follows.
1. Under "Properties > Properties > Layout > Settings > Lines per alarm" in the Inspection
window, specify the number of lines to display for each alarm.
2. In "Properties > Properties > View", select the control elements that are available on the
HMI device.
3. Configure the columns under "Properties > Properties > Columns":
Under "Visible columns" select the columns to be output in the alarm view.
Under "Properties Column", define the properties of the columns.
Under "Sort", select the sorting order of the alarms.
Note
Select the "Edit" command in the shortcut menu for the alarm view to activate the alarm
view. You can set the column width and position in active mode. To enable the alarm
view, set the zoom factor to 100 %.
The alarm view is deactivated as soon as you deselect the object in the screen.
Result
Alarms of various alarm classes are output in the alarm view during runtime.
See also
Creating alarm classes (Page 966)
Configuring an alarm window (Page 994)
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
992 System Manual, 08/2011,
Configuring an alarm view for the S7 diagnostic alarms
Introduction
To display S7 diagnostic alarms, configure an alarm view or alarm window for the predefined
"Diagnosis Events alarm class. Activate the diagnostic alarms accordingly in the Runtime
settings of your HMI device.
Note
HMI device dependency
The "Diagnosis Events" alarm class is not available for all HMI devices.
Requirements
An alarm view or alarm window is configured in the "Screens" editor
A connection to the PLC is set up.
Configuring the display of S7 diagnostic alarms
To configure the display of S7 diagnostic alarms, follow these steps:
1. Select "Runtime settings > Alarms > System events > S7 diagnostics alarms" in the project
navigation.
2. To display the S7 diagnostics alarms with text, activate "With text".
3. Open the screen with the alarm view and select the alarm view.
4. In the Inspector window, select "Properties > Properties > General > Display > Alarm class
"Diagnosis Events".
5. Continue to configure the alarm view as for the display of current alarms.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 993
Result
In Runtime the alarm view displays the S7 diagnostic alarms of the controller.
Configuring an alarm view for logged alarms
Introduction
In Runtime, logged alarms are displayed in an alarm view or alarm window.
Requirements
An alarm view or alarm window is configured in the "Screens" editor
An alarm log was created in the "Log" editor.
The alarms are assigned the "loggable" attribute in the "HMI alarms" editor.
Configuring an alarm view for logged alarms
To configure an alarm view for logged alarms, proceed as follows:
1. Open the screen with the alarm view and select the alarm view.
2. In the Inspector window, select "Properties > Properties > General > Alarm log".
3. Click the "...." button and select the alarm log.
4. Continue to configure the alarm view as for the display of current alarms.
Result
In Runtime, the logged alarms are output in the alarm view.
Configuring an alarm window
Introduction
The alarm window displays current alarms. The alarm window is configured in the "Global
Screen" editor and opens regardless of the current screen. The HMI device can still be used,
even if alarms are pending and displayed. An alarm window is displayed and configured like
an alarm view.
To hide an alarm window during configuration, create it on its own level.
Requirement
The "Global Screen" editor is open.
The "Tools" task card is displayed.
The Inspector window is open.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
994 System Manual, 08/2011,
Procedure
Proceed as follows to configure an alarm window:
1. Insert an "Alarm window" object from the "Tools" task card into the global screen.
2. Configure the alarm window like an alarm view.
3. Under "Properties > Properties > Mode > Window" in the Inspector window, select how
the alarm window reacts and is operated in Runtime.
Activate "Modal" if the alarm window is to retain the focus in Runtime after a screen
change.
This option is important, as switching back and forth between the screen and different
windows with <Ctrl+TAB> is not supported.
Result
During runtime, the alarms of the selected alarm class are displayed in the alarm window.
See also
Configuring an alarm view for active alarms (Page 989)
Creating alarm classes (Page 966)
Configuring an alarm indicator
Introduction
The alarm indicator uses a warning triangle to indicate that alarms are pending or require
acknowledgement. If an alarm of the configured alarm class occurs, the alarm indicator is
displayed.
The alarm indicator has two states:
Flashing: At least one alarm that requires acknowledgment is pending.
Static: At least one of the acknowledged alarms has not gone out yet.
During configuration, specify whether Runtime has to open an alarm window when you operate
the alarm indicator.
Requirement
The "Global Screen" editor is open.
The "Tools" task card is open.
The Inspector window is open.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 995
Procedure
Proceed as follows to configure the alarm indicator:
1. Insert the "Alarm indicator" object from the "Tools" task card into the work area.
2. Select the alarm indicator.
3. Under "Properties > Properties > General" in the Inspector window, select the alarm
classes to be displayed by the alarm indicator.
Specify whether to display pending and/or acknowledged alarms in the alarm indicator.
4. Under "Properties > Event", assign system function "ShowAlarmWindow" to an event of
the alarm indicator.
Note
If you have configured a permanent window in the screen or template, do not position the
alarm window and alarm indicator in the vicinity of the permanent window. Otherwise the
alarm window and the alarm indicator are not displayed in Runtime. However, the
permanent window is not visible in the "Global screen" editor.
Result
The alarm indicator is displayed if alarms from the selected alarm class are pending or need
to be acknowledged in Runtime. The alarm window opens when the user operates the alarm
indicator.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
996 System Manual, 08/2011,
Configuring alarm filtering
Introduction
You can filter the display of alarms in the enhanced alarm view. The criterion is always a
character string. There are two ways to filter the alarm view:
A fixed criterion is configured in WinCC.
In Runtime, all alarms that contain the complete character string in the alarm text are
displayed.
You filter the alarm view in Runtime.
In Runtime, a filter tag sets the relevant character string in the alarm view by means of an
I/O field, e.g. as described below.
The filter affects the display in the alarm view. All alarms in the alarm buffer are retained.
Requirements
An enhanced alarm view has been configured.
The screen with the alarm view is open.
The Inspector window is open.
Configuring filters for a fixed character string
1. Select the alarm view.
2. In the Inspector window, select "Properties > Properties > Filter".
3. Enter a filter string in "Filter string".
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 997
Result
Only those alarms are displayed in Runtime that contain the complete character string from
the filter in the alarm text.
Configuring filters for a variable character string
1. Select the enhanced alarm view.
2. In the Inspector window, select "Properties > Properties > Filter".
3. Select a tag from "Filter tag". The tag must be of the "String" type.
4. In the screen, configure an I/O field for entering the filter string in Runtime.
In the Inspector window, select "Properties > Properties > General > Format > Display
format > String".
To link the I/O field to the alarm view, select "Process" to set the filter tag you selected
for the alarm view.
Result
If you enter a string in the I/O field in Runtime, the alarm view only displays alarms that contain
the complete string in their alarm text.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
998 System Manual, 08/2011,
If a permanently configured character string and a filter tag were configured, the alarms will
be filtered in Runtime according to the content of the filter tag. If the filter tag is blank, the
permanently configured character string is used as the filter.
Note
Filtering is not possible for the following alarm views:
Simple alarm view
Alarm line
Alarm window
Alarm view for logged alarms
Displaying Logged Alarms
Introduction
You display logged alarms in Runtime in an alarm view. The alarm view shows the content of
an alarm log.
Application
For example, you want to view information about the process at the end of a shift.
Requirements
An alarm log has been created.
A screen is open.
The Inspector window is open.
Procedure
Proceed as follows to configure an alarm view to output an alarm log:
1. Configure an alarm view in a screen.
2. Under "Properties > Properties > General > Display > Alarm log"" in the Inspector window,
select the required alarm log.
You can always create a new alarm log.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 999
Result
During runtime, the alarms logged in the selected alarm log appear in the Alarm view.
NOTICE
In runtime, the alarm texts logged are not displayed but rather the alarm texts in the current
project. The logged alarm texts are only intended for external evaluation of the log file.
If the alarm log displayed was configured differently, the alarm texts displayed may not
correspond with those logged.
Reporting Alarms
Overview
WinCC can report on all alarms that occur in the system. The following options are available:
Output an alarm sequence report
In Runtime, the standard printer of the HMI device will continuously print each alarm and
any changes in its status.
Output of an alarm report
You configure an alarm report in the "Reports" editor and specify when it is output in
Runtime:
For event-driven output, configure an object that is assigned the "PrintReport" system
function. The object can be a button or tag.
For time-driven output, create a "Print job" in the scheduler. Assign an alarm report to
the job.
Note
In the alarm report, specify whether to output current or logged alarms.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1000 System Manual, 08/2011,
Requirements
A printer was configured on the HMI device.
Activating continuous alarm reporting
To activate continuous reporting of alarms, follow these steps:
1. Double-click "Runtime settings" in the project navigation.
2. Select "Alarms > General > Report".
Result
The latest alarms are output at the printer of the HMI device.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1001
Excluding an alarm from reporting
To exclude specific alarms from reporting, proceed as follows:
1. Open the "HMI alarms" editor.
2. Select the alarm to exclude from reporting on the tab of the selected alarm type.
3. In the Inspector window, disable "Properties > Properties > Miscellaneous > Report".
Result
WinCC does not output these alarms currently on the connected printer.
See also
Working with reports (Page 1146)
9.3.2.4 Acknowledging alarms
Configuring alarm acknowledgment by means of alarm class
Introduction
To configure an alarm with alarm acknowledgment, assign it to an alarm class with the "Alarm
with single acknowledgment" acknowledgment model.
Requirement
The "HMI alarms" editor is open.
The required alarm class has been created.
The required alarm has been created.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1002 System Manual, 08/2011,
Selecting the acknowledgment model for an alarm class
The acknowledgment model for a predefined alarm class has already been set. You can only
set the acknowledgment model for user-defined alarm classes. Proceed as follows:
1. In the "HMI alarms" editor, click the "Alarm class" tab and select the alarm class.
2. Select the required acknowledgment model under "Properties > Properties >
Acknowledgment" in the Inspector window.
Assign alarms to an alarm class requiring acknowledgment
Proceed as follows to assign an alarm to an alarm class requiring acknowledgment.
1. In the "HMI alarms" editor, click the tab for the alarm type and select the alarm.
2. Under "Properties > Properties > General" in the Inspector window, select the alarm class
of the alarm.
Result
The alarm will not disappear in Runtime until it is acknowledged by the operator.
Configuring trigger for alarm acknowledgment
Introduction
You always specify the acknowledgment requirement for an alarm using the alarm class. Then
the operator acknowledges the alarm using the "ACK" function key of the HMI device or the
"Acknowledgment" button of the alarm view.
The following options are also available to trigger acknowledgment:
Configuring a button to acknowledge an alarm
Acknowledgment of a Discrete Alarm by the PLC
Requirement
The "HMI alarms" editor is open.
The required alarm class has been created.
The required alarm has been created.
An alarm view and a button are created in the "Screens" editor.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1003
Configuring a button to acknowledge an alarm
To configure a button for acknowledging an alarm, proceed as follows:
1. Select the button in the "Screens" editor.
2. Under "Properties > Events" in the Inspector window, assign the
"AlarmViewAcknowledgeAlarm" system function to the "Click" event.
3. Select the alarm view as parameter.
Acknowledgment of a Discrete Alarm by the PLC
1. In the "HMI alarms" editor, click the "Discrete alarm" tab and select the discrete alarm.
2. In the Inspector window, select the tag and the bit that acknowledges the PLC alarm under
"Properties > Properties > Acknowledgment > PLC".
Sending alarm acknowledgments to the PLC
Requirement
The "HMI alarms" editor is open.
The required alarm has been created and assigned to an alarm class requiring
acknowledgment.
Note
You cannot send the acknowledgment of analog alarms to the PLC.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1004 System Manual, 08/2011,
Sending alarm acknowledgments to the PLC
To configure that acknowledgment of an alarm is sent to the PLC, follow these steps:
1. In the "HMI alarms" editor, click the "Discrete alarm" tab and select the discrete alarm.
2. In the Inspector window, select "Properties > Properties > Acknowledgment".
3. Under "HMI", select the tag and the bit set by the alarm acknowledgment function.
Note
Operator and PLC only have read access to the acknowledgment tag memory area.
Result
If the operator acknowledges the alarm in Runtime, the operating step is forwarded to the PLC.
9.3.2.5 Configuring alarm buffer overflow
Introduction
The size of the alarm buffer depends on the type of HMI device. In WinCC, specify the
percentage of the alarm buffer to be deleted on alarm buffer overflow.
Requirements
You have created a project.
Procedure
To configure the response to an alarm buffer overflow, follow these steps:
1. Double-click "Runtime settings" in the project navigation under your HMI device.
2. Under "Alarms > General > Buffer clearance in percent upon buffer overflow", enter a value
between 1 and 100.
This value specifies the percentage of the alarm buffer that is deleted on alarm buffer
overflow.
Result
If data in the alarm buffer exceeds the resources of alarm buffer memory, the configured
percentage of data will be deleted from the oldest alarms in the alarm buffer.
Note
You cannot check the alarm buffer overflow separately by alarm method. You can use the
"ClearAlarmBuffer" system function to delete specific alarms of specific alarm classes from
the alarm buffer.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1005
See also
Alarm Logging Basics (Page 1006)
9.3.3 Logging Alarms
9.3.3.1 Alarm Logging Basics
Introduction
An alarm log is used to record project alarms.
Note
Alarm logging is not available for every HMI device.
Configuration steps
To log an alarm, follow these configuration steps:
1. Creating an alarm log
You define the following properties for the alarm log:
Logging method
Behavior of the log when reaching a specific fill level
Storage location and file format
Log size
Runtime start characteristics
Checksum
2. Assigning an alarm log to an alarm class
You can log the alarms from multiple alarm classes in an alarm log.
3. Assigning an alarm to a loggable alarm class
4. Configure display of logged alarms in an alarm view
Content of the alarm log
All states are logged for configured alarms. The following three entries, for example, are stored
in the log for an alarm that requires acknowledgment:
04.08.2007 10:00:25:520, analog alarm, ID5, K, error, fill level exceeded by 10 %
04.08.2007 10:01:20:442, analog alarm, ID5, Q, error, fill level exceeded by 10 %
04.08.2007 10:01:30:112, analog alarm, ID5, G, error, fill level exceeded by 10 %
In the example, the alarm states are identified by the following letters:
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1006 System Manual, 08/2011,
K = Incoming
Q = Acknowledged
G = Outgoing
All data belonging to an alarm is stored in the alarm log, including configuration data such as
the alarm class, time stamp, and alarm text.
The potential number of logged alarms depends on the data medium used.
Note
Alarm text and error location are only logged if you have configured such a setting in the log
properties.
Note
The time stamp of a logged alarm is always specified in standard UTC format (Universal Time
Coordinated).
Logging methods
The logging method determines how the alarm log responds when the configured size is
reached. WinCC supports the following logging methods:
Circular log
When the configured log size has been reached, the oldest entries are deleted. When the
configured log size has been reached, approximately 20% of the oldest entries are deleted.
It is therefore not possible to display all the configured entries. During configuration, select
an appropriate size for the circulation log. Alternatively, configure a segmented circular log.
Segmented circular log
In a segmented circular log, multiple single logs of the same size are filled in succession.
When all logs are completely full, the oldest log is overwritten.
Log with level-dependent system alarm
When a defined level is reached, such as 90 %, a system alarm is triggered. When the
configured size of the log has been reached, new alarm events are not logged.
Log with level-dependent execution of system functions
When the log is completely full, the "Overflow" event is triggered. You configure a function
list for the event.
When the configured size of the log has been reached, new alarm events are not logged.
Checksums in regulated projects
With WinCC you configure regulated projects as required by FDA guidelines, if necessary. Use
the "Audit" option to create regulated projects.
In regulated projects you supply a checksum for the logged data of an alarm log. The operator
will use this checksum during operation of the plant to see if the data of an alarm log have
been changed.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1007
For the checksum to be clear, it starts with the first line of an alarm log and integrates the
previous lines when continuously generating the checksum. This means a checksum can only
be generated for the following logs:
Log that sends a system alarm when it is full
Log with execution of system functions when log is full.
Generation of a checksum is also available for alarm logs that are saved as files of the "*.csv"
or "*.txt" (Unicode) format.
If you want to continue an existing log without checksum as one with checksum, a backup
copy of the existing log is created in the "*.keep" file format. A new log with checksums is
created.
To maintain the validity of checksums, the following limitations apply when using the system
function "CopyLog":
You cannot copy a log without checksums into a log with checksums.
You cannot copy a log with checksums into a log without checksums.
Storage location and storage medium
You can save the log data to a file on a data carrier, e.g. MMC, SD, or CF cards. If you are
using a PC as your HMI device, you may store your information in a database. You can further
process the saved data in other programs for analysis purposes, for example.
Displaying logged data
On the HMI device, the logged data is displayed in an alarm view that is configured for this
purpose.
See also
Configuring alarm buffer overflow (Page 1005)
9.3.3.2 Storage locations for log files
Introduction
The alarm log is stored in an ODBC database or in a file. Select "Database" or "File" as the
storage location.
Note
An "ODBC database" storage location is only available on a PC.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1008 System Manual, 08/2011,
Log file
Depending on the configuration of the HMI device, select one of the following storage locations
for the log file:
Local hard disk of the PC
Storage card of the Panel
Network drive
Note
Logging on network drives
Do not log alarms, tags and Audit Trail directly on a network drive. Power supply can be
interrupted at any time. This means there is no guarantee for a reliable operation of logs
and audit trails.
Save the logs on your local hard drive or a local storage card. Use the system function
"ArchiveLogFile" to save the logs long-term on a network drive. This step ensures reliable
operation.
File - CSV (ASCII)
Data is saved to a "*.csv" file in standard ASCII format.
Use the "File - CSV (ASCII)" storage location if you are going to read logged data without using
WinCC Runtime.
Note
Double quotation marks or several characters are not permitted as list separator for the
storage site "File - CSV (ASCII)." You can find the settings for list separators under "Start >
Settings > Control Panel > Regional and Language Options."
File - TXT (Unicode)
The log data are saved in Unicode.
This file format supports all characters that can be used in WinCC and WinCC Runtime. For
editing, use software that can save files in Unicode, such as Notepad.
Note
Use "File - TXT (Unicode)" as the storage location to log Asian languages.
File - RDB
Data will be saved with quick access to a proprietary database.
Use the "File - RDB" storage location if you require maximum read performance in Runtime.
Data logs of this format can only be read and displayed using WinCC Runtime.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1009
Convert the RDB file to CSV format using the "CopyLog" function to make the data available
for applications outside WinCC Runtime.
Files of logs with checksums
*.keep
This file is created in the following cases:
A log is started without checksum and will be continued with a checksum.
You update WinCC with a Service Pack or a new version. Writing of the Audit Trail or
the log with checksum is continued.
The content of the "*.keep" file remains the same when compared with the original "*.csv"
or *.txt" file.
*.bak
This file is created when WinCC Runtime has determined a serious, irregular problem in
the file.
Database
Data is saved to a database which is set up for ODBC access by the PC administrator.
If you have selected an ODBC database as storage location, select one of the following options
for naming:
"User-defined name of data source"
You define the name of the data source.
"System-defined name of data source",
The system defines the name.
You will need a special instance of Microsoft SQL Server on the target system in order to
do this. Download the free SQL Server 2005 Express from the Internet for this purpose.
Note
Device dependency
This setting is not available on the Panel PC 477.
9.3.3.3 Creating an alarm log
Introduction
In Runtime, you save alarms to the alarm logs. Specify the alarm log in the alarm class. An
alarm log contains the alarms of several alarm classes. Create the alarm log in the "Logs"
editor. When creating an alarm log, define the following parameters:
Name
Size
Storage location
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1010 System Manual, 08/2011,
Runtime start characteristics
Log type
Advanced content
Checksum
You can also enter comments for each log.
Requirement
The "Alarm log" tab is open in the "Log" editor.
The Inspector window is open.
Procedure
To create an alarm log, proceed as follows:
1. Double-click "<Add>" in the table.
A new alarm log is created.
2. Under "Properties > Properties > General" in the Inspector window, enter a unique name
for the alarm log.
Note
The log names must be unambiguous in a project. The name of a log must always be unique,
regardless of whether different storage locations are selected for the log.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1011
Note
The characters which can be used in the name of the data source depend on the storage
location.
The characters \ / * ? : " < > | are not permitted for the following storage locations:
File - RDB
File - CSV (ASCII)
File - TXT (Unicode)
If the "Database" storage location is used, the following characters may be used: a-z A-Z 0-9
_ @ # $
The characters _ @ # $ cannot be used as the first character of a name.
1. Under "Number of data records per log", define the number of alarms to be saved to a log
file.
The approximate space required on the storage medium is displayed. Memory space
requirements will increase accordingly if you log alarm texts with tag values.
2. Under "Storage location", select a file, or an ODBC database.
If you select a file, enter the corresponding path. Depending on the HMI device, save
the log files to the hard disk of the PC, to the memory card of a panel, or to a network
drive.
Different file formats are supported, depending on the HMI device.
If you select a "Database" storage location, specify the following:
Specify whether the name of the data source is accepted by the system.
Specify whether to select the name of the data source yourself.
Enter a name for the database.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1012 System Manual, 08/2011,
1. To determine if audit trail data were changed at a later time, activate "Properties >
Properties > General > Checksum".
Note
Device dependency
The "Checksum" option is only available for display and HMI devices which support logs.
Configuring the behavior of the log when it reaches a specific fill level
1. Define how the log should behave when it is full under "Properties > Properties > Logging
method".
Specify the number of logs for the "Segmented circular log" log type.
For the "Display system event on" log type, specify the fill level triggering the system
event.
If you selected the "Trigger event" log version, configure a function list under "Properties
> Events > Overflow". The function list will be processed when the log is full.
2. Under "Properties > Properties > Archiving method > Settings", specify whether to log the
alarm text and fault location.
Logged alarms that contain alarm text and the fault location exceed the estimated size of
the configured alarms. Check to see whether the specified specified storage location still
has sufficient space.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1013
Configuring the behavior of the log when Runtime starts
1. Select "Properties > Properties > Start behavior> Type".
Define whether to start the log automatically at the start of Runtime.
To overwrite logged data with new data, activate "Reset log".
To add the logged data to an existing log, activate "Continue log".
Note
Use system functions to control the restart of a log in Runtime.
Configuring a comment
To record a text to document your configuration of a log, follow these steps:
1. Enter your text under "Properties > Properties > Comment".
Result
The alarm log is created. You can assign one or several alarm classes to this alarm log.
See also
Managing logging behavior when Runtime starts (Page 1021)
Controlling the Logging in relation to the Fill Level (Page 1022)
9.3.3.4 Logging Alarms
Overview
To log alarms, follow these steps:
Create an alarm log.
Assign the created alarm log to an alarm class.
Assign the alarm class with the created alarm log to an alarm.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1014 System Manual, 08/2011,
In the Runtime settings specify the language in which you want to write the logs.
You evaluate logged alarms.
You can analyze the logged alarms directly in your WinCC project, such as in an alarm
view, or in another user program, such as Microsoft Excel.
Note
Tag fields in the alarm text
The sequence of tag fields in the alarm text is language dependent. The sequence of the
Runtime language is used for logging alarms to a "*.csv" log file.
Changing the tag of an output field in one language causes the modified output field to
appear at the end of the alarm text in all other languages. This means the sequence of
the output fields in the log file can change.
Requirements
You have created an alarm log.
The "HMI alarms" editor is open.
Assigning an alarm log to an alarm class
To assign the alarm log to an alarm class, proceed as follows:
1. Open the "Alarm classes" tab in the "HMI alarms" editor.
2. Select the required alarm class.
3. Under "Properties > Properties > General > Log" in the Inspector window, select the alarm
log.
Assign alarm to an alarm class
To assign an alarm to the alarm class, proceed as follows:
1. In the "HMI alarms" editor, open the "Analog alarms" tab, or the "Discrete alarms" tab.
2. Select the required alarm.
3. Under "Properties > Properties > General > Alarm class" in the Inspection window, select
the alarm class for which the alarm log was configured.
Result
The alarm is saved to the configured alarm log.
9.3.3.5 Configuring an alarm view for logged alarms
Introduction
In Runtime, logged alarms are displayed in an alarm view or alarm window.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1015
Requirements
An alarm view or alarm window is configured in the "Screens" editor
An alarm log was created in the "Log" editor.
The alarms are assigned the "loggable" attribute in the "HMI alarms" editor.
Configuring an alarm view for logged alarms
To configure an alarm view for logged alarms, proceed as follows:
1. Open the screen with the alarm view and select the alarm view.
2. In the Inspector window, select "Properties > Properties > General > Alarm log".
3. Click the "...." button and select the alarm log.
4. Continue to configure the alarm view as for the display of current alarms.
Result
In Runtime, the logged alarms are output in the alarm view.
9.3.3.6 Direct access to the ODBC log database
Overview
The storage location of a log can be a database or a file.
The database is addressed by means of its "Data source name" (DSN). Select the database
to be used in WinCC as follows:
Select the database from the Windows Start menu under "Settings > Control panel > ODBC
Data Sources".
In your configuration, specify the "Data source name" (DSN) instead of a directory name as
storage path for log data. With the DSN, you are referencing the database and the storage
location.
The entire functional scope of the database is available for additional processing and
evaluation of log data.
Application
The data source sets up the connection to the database. Create the data source on the same
PC on which the Runtime software is stored. Then enter the DSN configured on this PC when
you create a log in WinCC.
The ODBC interface allows you to use other programs, such as MS Access or MS SQL Server,
to access the database directly.
In addition, you can use the "StartProgram" system function to configure program calls, e.g.
MS Access, on the HMI device. Runtime is not interrupted while you configure such calls.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1016 System Manual, 08/2011,
9.3.3.7 Setting up the ODBC data source
Introduction
To store process values or alarms in the log database in Runtime, set up the ODBC data
source.
Requirement
A log database has been created.
You create the log database using the SQL Enterprise Manager. You can find more detailed
information on how to do this from Microsoft.
Procedure
To set up an ODBC data source, follow these steps:
1. In Control Panel, open "Administrative Tools" and select "Data Sources (ODBC)".
The "ODBC Data Source Administrator" dialog is opened.
2. Click "User DSN > Add".
3. Select the "SQL-Server and click on "Finish".
4. In the dialog that follows, enter a name for the User DSN and the SQL-Server and click on
"Next".
5. In the dialog that follows, define the logon procedure for the SQL database and click on
"Next".
6. Activate "Change the default database to".
7. Select the database you have created and click on "Next".
8. In the dialog that follows, click "Finish".
9.3.3.8 Configuring a checksum for a log
Introduction
In a regulated project, you have the option of assigning a checksum to the log data of an data
log or alarm log. This checksum can be used during plant operation to determine if the data
of this log has subsequently changed.
Requirement
GMP compliant configuration is enabled.
A data log or alarm log has been created.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1017
Procedure
Proceed as follows to configure a data log or alarm log for the use of a checksum:
1. Open the data log or alarm log in the corresponding log editor.
2. In the "Storage location" box, select "File - CSV (ASCII)" or "File - TXT (Unicode)".
3. Under "Properties > Properties > Logging method" in the Inspector window , select the
option "Display system event at" or "Trigger event".
4. In the editor table activate the option "Activate checksum".
Columns that are not displayed are activated with the shortcut menu of the column title.
5. Save the project.
Result
The log data of the log is assigned a checksum in runtime.
See also
GMP-compliant configuration (Page 2539)
Enabling GMP compliant configuration (Page 2543)
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1018 System Manual, 08/2011,
9.3.3.9 Evaluating the checksum of log data
Introduction
If you have configured a data log or alarm log with generation of a checksum, you can check
if the log data has subsequently changed.
The DOS program "HmiCheckLogIntegrity" is available for checking the integrity of the log
data.
The "HmiCheckLogIntegrity" program supports verification of the following files:
Log files of alarm logs, data logs, and Audit in CSV format
Log files of alarm logs, data logs, and Audit in TXT format
Recipe data records in CSV format
Recipe data records in TXT format
You can find the "HmiCheckLogIntegrity.exe" program in the installation directory of WinCC
under the folder "WinCC Runtime Advanced", for example <C:\Program Files\Siemens
\Automation WinCC Runtime Advanced>.
Note
Audit Trail and Log with Checksum
Before you update WinCC with a Service Pack or a new version, exit and save the Audit Trail
or the logs using checksum. After WinCC is updated, the audit trail or logs will be continued
with new files using checksum.
Make sure that the logs are started at a defined state with the new version.
Procedure
1. Copy the file to be checked from the HMI device to your configuration computer.
2. Open a command line prompt with "Start > Programs > Accessories > Command Prompt".
3. Enter the path to "HmiCheckLogIntegrity.exe" followed by a space in the command line
prompt. After the space, enter the storage location of the file to be checked within quotation
marks.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1019
4. Press <Enter>.
5. The check is performed.
When the checked data are consistent, the "Consistency check succeeded" message
appears.
When the checked data are inconsistent, the "Consistency check failed" message appears.
Information about the first inconsistent line in the file is also displayed.
Note
If there are spaces in the path to the "HmiCheckLogIntegrity.exe" program, you need to
specify the path in quotation marks.
You can also check the integrity of the log data with the AuditViewer.
See also
Enabling GMP compliant configuration (Page 2543)
Evaluating Audit Trails in AuditViewer (Page 2561)
9.3.3.10 Log response to language switching in runtime
Introduction
In the Runtime settings of your HMI device, select the language to be used for writing to logs
in runtime.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1020 System Manual, 08/2011,
Requirement
The languages used in your project are activated in the "Project languages" editor, for
example, "German (Germany)" and "English (USA)" .
Procedure
To determine the startup language, follow these steps:
1. Select "Runtime settings > Language and fonts" in the project navigation.
2. Activate the runtime language, for example, "German (Germany)" and "English (USA)".
3. Set the "Language switch order". Use 0 to determine the startup language, for example:
German 0.
English 1
With "0", German is specified as the "Startup language".
4. Select "Runtime settings > General" in the project navigation.
5. Select the "Logs > Logging language > Startup language".
Result
The project starts after it is transferred. German is specified as the "Startup language" with
"Language switch order". The logs are now written in German. During runtime, the operator
switches the runtime language to English. The logs will still to be written in German.
The operator closes runtime. Due to the previously performed language switch, the next time
the system starts the "startup language" is English. Since English is the startup language, the
logs are now written in English.
The logging language remains English even when the language is switched again in runtime
until runtime is closed once again.
If you use another option instead of "Startup language" to select the language, the logs are
always written in the same language. This is true regardless of the language selected by the
operator in runtime.
9.3.3.11 Managing logging behavior when Runtime starts
Introduction
When you configure a data log, you define the restart characteristics of the log when Runtime
is started. You define whether the logging should start when Runtime starts in the log
properties. You can also define whether an existing log will be continued or overwritten.
You define the restart characteristics separately for each log.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1021
Requirement
A data log has been created.
The "Data log" editor is open.
The Inspector window with the log properties is open.
Procedure
To configure the restart characteristics of a data log, proceed as follows:
1. Select the log for which you want to define the restart characteristics in the "Data Log" editor.
2. In the Inspector window select "Properties > Properties > Restart behavior."
3. If you want logging to start when Runtime starts, enable the "Enable logging at runtime
start" option in the "Logging" area.
You can also start logging in Runtime using the "StartLogging" system function, for example.
4. Select the restart behavior of the log in the "Log handling at restart" area.
The logged values are deleted and logging is started again with the option "Reset log".
The option "Append data to existing log" is used to append the values to be logged to
the existing log.
Alternatively you can configure the restart characteristics of a log directly in the "Data log"
editor table. To view hidden columns, activate the column titles using the shortcut menu.
Result
Logging will start in runtime according to your settings.
9.3.3.12 Controlling the Logging in relation to the Fill Level
Introduction
The size of a log is determined by the number of entries. You use the logging method to
determine how the log responds when it is full.
Logging methods
The following logging methods are available:
Circular log
When the configured log size has been reached, the oldest entries are deleted. When the
configured log size has been reached, approx. 20% of the oldest entries are deleted. It is
therefore not possible to display all the configured entries. During configuration, select an
appropriate size for the circulation log. Alternatively, configure a segmented circular log.
Segmented circular log
In a segmented circular log, multiple log segments of the same size are filled in succession.
When all logs are completely full, the oldest log is overwritten.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1022 System Manual, 08/2011,
Log that sends a system alarm when it is full
When a defined level is reached, such as 90 %, a system alarm is triggered. When the log
is 100% full, new tag values are not logged.
Log with level-dependent triggering of an event.
When the log is completely full, the "Overflow" event is triggered. Configure a function list
for the event that will be carried out when the "Overflow" event occurs. When the configured
size of the log is reached, new tag values are not logged.
The following system functions are available for further processing of full logs: For further
details, refer to Auto-Hotspot.
Requirement
A data log has been created.
The "Data log" editor is open.
The Inspector window with the log properties is open.
Procedure
1. Select the log for which you want to define the logging method in the "Data Log" editor.
2. Select "Properties > Properties > Logging method" in the Inspector window and select the
required logging method.
3. If you have selected the "Segmented circular log" type, enter the number of log segments.
If you selected a log with the "Display system alarm on" setting, specify the level as a
percentage at which a system alarm is to be triggered.
If you selected the "Trigger event" setting, configure the function list in the "Events" group.
Alternatively you can configure the logging method directly in the "Data log" editor table. To
view hidden columns, activate the column titles using the shortcut menu.
The "Overflow" event is not available in the editor table. You must therefore configure the
function list in the Inspector window.
Result
The selected log responds according to the settings in Runtime.
9.3.4 Using Alarms in Runtime
9.3.4.1 Alarms in Runtime
Alarms
Alarms indicate events and states on the HMI device which have occurred in the system, in
the process or on the HMI device itself. A status is reported when it is received.
An alarm could trigger one of the following alarm events:
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1023
Incoming
Outgoing
Acknowledge
Loop-in-alarm
The configuration engineer defines which alarms must be acknowledged by the user.
An alarm may contain the following information:
Date
Time
Alarm text
Location of fault
Status
Alarm class
Alarm number
Alarm group
Alarm classes
Alarms are assigned to various alarm classes.
"Warnings"
Alarms of this class usually indicate states of a plant such as "Motor switched on". Alarms
in this class do not require acknowledgment.
"Errors"
Alarms in this class must always be acknowledged. Error alarms normally indicate critical
errors within the plant such as "Motor temperature too high".
"System"
System alarms indicate states or events which occur on the HMI device.
System alarms provide information on occurrences such as operator errors or
communication faults.
Custom alarm classes
The properties of this alarm class must be defined in the configuration.
Alarm buffer
Alarm events are saved to an internal buffer. The size of this alarm buffer depends on the HMI
device type.
Alarm view
The alarm view shows selected alarms or alarm events from the alarm buffer. Whether alarm
events have to be acknowledged or not is specified in your configuration.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1024 System Manual, 08/2011,
Alarm window
An alarm window shows all pending alarms or alarms awaiting acknowledgement of a particular
alarm class. The alarm window is displayed as soon as a new alarm occurs.
You can configure the order in which the alarms are displayed. You can choose to display the
alarms in ascending or descending order of their occurrence. The alarm window can also be
set to indicate the exact location of the fault, including the date and time of the alarm event.
By means of configuration, the display can be filtered in such a way that only alarms that
contain a specific character string will be shown.
Alarm indicator
The alarm indicator is a graphic icon that is displayed on the screen when an alarm of the
specified alarm class is activated.
The alarm indicator can have one of two states:
Flashing: At least one unacknowledged alarm is pending.
Static: The alarms are acknowledged but at least one of them has not gone out yet. The
displayed number indicates the number of queued alarms.
9.3.4.2 Alarms in Runtime
Alarms
Alarms indicate events and states on the HMI device which have occurred in the system, in
the process or on the HMI device itself. A status is reported when it is received.
An alarm could trigger one of the following alarm events:
Incoming
Outgoing
Acknowledge
The configuration engineer defines which alarms must be acknowledged by the user.
An alarm may contain the following information:
Date
Time of day
Alarm text
Location of fault
Status
Alarm class
Alarm number
Alarm group
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1025
Alarm classes
Alarms are assigned to various alarm classes.
"Warnings"
Usually, alarms of this class indicate states in the plant such as "Motor switched on". Alarms
in this class do not require acknowledgement.
"Errors"
Alarms in this class must always be acknowledged. Usually, error alarms indicate critical
error events that occurred in the plant, e.g. "Motor overtemperature".
"System"
System events indicate states or events which occur on the HMI device.
System events provide information on occurrences such as operator errors or
communication faults.
"Diagnosis Events"
SIMATIC diagnostic alarms show states and events in the SIMATIC S7 controller.
STEP 7 alarm classes
The alarm classes configured in STEP 7 are also available to the HMI device.
Custom alarm classes
The properties of this alarm class are defined in the configuration.
Alarm buffer
Alarm events are saved to an internal buffer. The size of this alarm buffer depends on the HMI
device type.
Alarm report
When alarm logging is enabled in the project, alarms are output directly to the printer.
You can set the logging function separately for each alarm. Printing of such an alarm is initiated
when the "incoming" and "outgoing" alarm events are generated.
The output of alarms of the "System" alarm class to a printer must be initiated by means of the
corresponding alarm buffer. This outputs the content of the alarm buffer to the printer. To be
able to initiate this print function, you need to configure a corresponding control object in the
project.
Alarm log
Alarm events are stored in an alarm log, provided this log file is configured. The capacity of
the log file is limited by the storage medium and system limits.
Alarm view
The alarm view shows selected alarms or events from the alarm buffer or alarm log. Whether
alarm events have to be acknowledged or not is specified in your configuration. By means of
configuration, the display can be filtered in such a way that only alarms that contain a specific
character string will be shown.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1026 System Manual, 08/2011,
Alarm window
If configured, an alarm window shows all pending alarms or alarms awaiting acknowledgement
of a particular alarm class. The alarm window is displayed as soon as a new alarm occurs.
You can configure the order in which the alarms are displayed. At the first position, the current,
or the oldest alarm will be displayed. The alarm window can also be set to indicate the exact
location of the fault, including the date and time of the alarm event. By means of configuration,
the display can be filtered in such a way that only alarms that contain a specific character string
will be shown.
Alarm indicator
The alarm indicator is a graphic symbol that is displayed on the screen when an alarm of the
specified alarm class is activated.
The alarm indicator can have one of two states:
Flashing: At least one unacknowledged alarm is pending.
Static: The alarms are acknowledged but at least one of them has not gone out yet. The
number indicates the number of queued alarms.
9.3.4.3 Using the Alarm Window or Alarm View
Alarm window, alarm view in Runtime
Application
Alarms are indicated in the alarm view or in the alarm window on the HMI device. The layout
and operation of the alarm window correspond to that of the alarm view.
The alarm window is independent of the process screen. Depending on the configuration, the
alarm window appears automatically as soon as a new, unacknowledged alarm has been
received. The alarm window can be configured so that it only closes after all the alarms have
been acknowledged.
Layout
Depending on the configuration, in the alarm view different columns with information regarding
an alarm or an alarm event are displayed. If a filter is configured, only alarms that contain a
specific string in the alarm text will be displayed.
To differentiate between the different alarm classes, the first column in the alarm view contains
an icon:
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1027
Symbol Alarm class
! "Errors"
Empty "Warnings"
depends on the configuration Custom alarm classes
$ "System"
S7 "Diagnosis Event"
Operation
You use the alarm view as follows, depending on how it is configured:
Change the order of the columns.
Change the order in which the alarms are displayed.
Acknowledging alarms
Editing alarms
Control elements
The buttons have the following functions:
Button Function
Displaying a tooltip for an alarm
Editing alarms
Acknowledge alarm
Operation behavior
Linked alarm window for touch panels
When configuring the alarm window for keyboard units, enable the "Modal" property under
"Properties > Mode". This ensures that the alarm window does not defocus during screen
changes. Switching back and forth between the screen and different windows with <Ctrl+TAB>
is not supported. If the linked alarm window has the focus, then the buttons in the screen behind
it cannot be operated. The functions configured on a function key are carried out.
Changing the order of the displayed alarms
When you click on the column, first of all alarms requiring acknowledgement are sorted
according to date and time. Then those alarms that do not require acknowledgement are sorted
according to date and time.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1028 System Manual, 08/2011,
Using the Alarm Window, Alarm View
Introduction
As an alternative to using the mouse, you can operate the alarm view and the alarm window
using the <TAB> key on your HMI device. This allows you to select the button and the most
recently selected alarm in the alarm view. Depending on the configuration, you can also
operate the alarm view via the function keys.
Operation using the mouse
1. Select the alarm to be edited.
2. Click the button whose function you want to run.
Operation using the keyboard
1. Press the <Tab> key until the list of displayed alarms is selected in the alarm view.
2. Click on the alarm to be edited. Use the <Up> and <Down> keys accordingly.
3. Press the <Tab> key until the button whose function you wish to use is selected.
4. Press <Enter>.
Change the order of the columns
1. Select the column header, such as the "Date" column header.
2. While holding down the mouse button, drag the column header to the column header "Time".
The "Date" column is in front of the "Time" column.
Change the sorting
You can sort the list according to date or time.
1. Click on the corresponding column header.
The list is sorted in descending or ascending order according to this criterion.
2. Click the same column header again to reverse the sort order.
Acknowledge alarm
1. Click on the alarm to be edited.
2. Click the button.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1029
Loop-In-Alarm trigger
1. Click on the alarm to be edited.
2. Click the button.
The screen containing information about the alarm is displayed.
Note
If you trigger a Loop-In-Alarm during an unacknowledged alarm, it is acknowledged
automatically.
Displaying configured tooltip
1. Click on the alarm concerned.
2. Click the button.
The tooltip configured for the alarm is displayed.
9.3.4.4 Using the Simple Alarm Window, Alarm View
Basic alarm view, alarm window in Runtime
Application
The simple alarm view shows selected alarms or alarm events from the alarm buffer. The layout
and operation of the simple alarm window correspond to that of the simple alarm view.
Note
The "Single alarm view" object is not assigned dynamic functions by means of scripting.
In the Engineering System, for example, dynamize the visibility of an object in the
"Animations" tab of the Inspector window. In Runtime, the "Simple alarm view" does not
support animations. If you configured an animation and, for example, run a consistency check
on the project, an error alarm is displayed in the output window.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1030 System Manual, 08/2011,
Layout
Depending on the configuration, in the alarm view different columns with information regarding
an alarm or an alarm event are displayed.
To differentiate between the different alarm classes, the first column in the alarm view contains
an icon:
Symbol Alarm class
! "Errors"
empty "Warnings"
depends on the configuration Custom alarm classes
$ "System"
Operation
You use the alarm view as follows, depending on how it is configured:
Acknowledging alarms
Editing alarms
Control elements
The buttons have the following functions:
Button Function
Acknowledge alarm
Loop-In-Alarm
Changes to the screen that contains information about the error event
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1031
Button Function
Displaying a tooltip for an alarm
Displays the full text of the selected alarm in a separate window, namely the alarm text
window
In the alarm text window, you can view alarm texts that exceed the space available in
the Alarm view. Close the alarm text window with the the button.
Scrolls one alarm up.
Scrolls one page up in the alarm view.
Scrolls one page down in the alarm view.
Scrolls one alarm down.
Format of the control elements
The display of the buttons for using the simple alarm view depends on the configured size.
You should therefore check on the HMI device whether all the required buttons are
available.
Basic alarm view, using the alarm window
Introduction
As an alternative to using the mouse, you can operate the simple alarm view using the <TAB>
key on your HMI device. This allows you to select the button and the most recently selected
alarm in the alarm view. Depending on the configuration, you can also operate the alarm view
via the function keys.
Operation using the mouse
1. Select the alarm to be edited.
2. Click the button whose function you want to run.
Operation using the keyboard
1. Press the <Tab> key until the list of displayed alarms is selected in the alarm view.
2. Click on the alarm to be edited. Use the <Up> and <Down> keys accordingly.
3. Press the <Tab> key until the button whose function you wish to use is selected.
4. Press <Enter>.
Acknowledge alarm
1. Select the alarm to be acknowledged.
2. Click the button.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1032 System Manual, 08/2011,
Loop-In-Alarm trigger
1. Select the alarm to be edited.
2. Click the button.
The screen containing information about the alarm is displayed.
Calling the infotext
1. Select the alarm to be edited.
2. Click the button.
3. To close the window for displaying the operator note, press the button or use the key
combination <Alt+F4>.
9.3.4.5 Using the Alarm Indicator
Alarm indicator in Runtime
Application
The alarm indicator is displayed if alarms of the specified alarm class are pending or require
acknowledgment.
Layout
The alarm indicator can have one of two states:
Flashing: At least one unacknowledged alarm is pending.
Static: The alarms are acknowledged but at least one of them is not yet deactivated. The
number indicates the number of queued alarms.
Operation
Depending on the configuration, when operating the alarm indicator an alarm window is
opened. The icons from the symbol library can only be operated with a mouse or touch screen.
Note
Device dependency
Operation with mouse is not available for all HMI devices.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1033
Operating the alarm indicator using the mouse
Operation using the mouse
1. Click on the alarm indicator with the mouse pointer. Depending on the configuration, the
Alarm window is open.
2. Click to close the alarm window. The Alarm window can be opened again by clicking
on the alarm indicator.
9.3.4.6 Acknowledging alarms
Introduction
You can acknowledge alarms in Runtime according to your project configuration settings. You
can acknowledge alarms as follows:
Using the display and control object buttons
Using the "ACK" key on your HMI device
Using individually-configured function keys or buttons
If an operator authorization is configured for an individual control, the alarms can only be
acknowledged by authorized users.
To automatically acknowledge alarms in Runtime, use the system functions and scripts, plus
the "Acknowledgment by the PLC" option.
Note
Device dependency
Scripts are not available for all HMI devices.
Acknowledgment variants
You acknowledge individual alarms or multiple alarms together in Runtime. They are
distinguished as follows:
Single acknowledgment
Acknowledgment of an alarm using a button or a function key.
Acknowledge alarm groups
Acknowledgment of all the alarms of an alarm group using a button or a function key.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1034 System Manual, 08/2011,
Requirement
An alarm is displayed on the HMI device.
Procedure
To acknowledge an alarm, proceed as follows:
1. Select the alarm.
2. If you are using an alarm view or an alarm window, click the button.
3. If you are using a simple alarm view or a simple alarm window, click the button.
4. Press the "ACK" button on your HMI device to acknowledge an alarm in an alarm line.
Note
Device dependency
The extended alarm view or alarm window and the alarm line are not available for all HMI
devices.
Result
The alarm status changes to "Acknowledged". If the condition for triggering an alarm no longer
applies, the alarm status also changes to "Outgoing", and it is no longer displayed on the HMI
device.
9.3.4.7 Filtering Alarms
Introduction
The alarm view in Runtime does not contain a control element for entering filter criteria. To
provide this functionality, configure an I/O field using the "Screens" editor.
Requirements
A filter has been configured for the alarm view.
An I/O field for entering the criterion is displayed.
Alarms are displayed in Runtime.
Enable filter
1. Enter the filter string in the I/O field.
2. Confirm your input.
The alarm view displays only those alarms that are contained in the specified character
string. Thereby this distinguishes between upper and lower case letters.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1035
Disable filter
1. Delete the string from the I/O field that is used to filter the alarm view.
2. Confirm your input.
All alarms are displayed in the alarm view once more.
9.3.5 Reference
9.3.5.1 System functions for alarms
System functions
System functions are predefined functions you can use to implement many tasks in runtime,
even with no programming knowledge. You use system functions in a function list or in a
script.
Note
Device dependency
Scripts are not available for all HMI devices.
The table shows all the system functions available for displaying and editing alarms.
System function Effect
EditAlarm Triggers the Loop-In-Alarm event for all selected
alarms.
ClearAlarmBuffer Deletes alarms from the alarm buffer on the HMI
device.
ClearAlarmBufferProtoolLegacy Function such as "ClearAlarmBuffer". This system
function has been retained to ensure compatibility
and uses the old ProTool numbering.
AlarmViewUpdate Updates the advanced alarm view.
AlarmViewEditAlarm Triggers the event Loop-In-Alarm for all alarms
selected in the specified alarm view.
AlarmViewAcknowledgeAlarm Acknowledges the alarms that are selected in the
specified alarm view.
AlarmViewShowOperatorNotes Displays the configured tooltip for the alarm
selected in the specified alarm view.
AcknowledgeAlarm Acknowledges all selected alarms.
SetAlarmReportMode Switches the automatic reporting of alarms on the
printer on or off.
ShowAlarmWindow Hides or shows the alarm window on the HMI
device.
ShowSystemEvent Displays the value of the delivered parameter as
a system event on the HMI device.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1036 System Manual, 08/2011,
Note
Device dependency
The following system functions are not available for all HMI devices:
SetAlarmReportMode
AlarmViewUpdate
ShowSystemEvent
9.3.5.2 Alarm events
Alarm events and their display and control objects
In Runtime, the following alarm events are triggered by their display and control objects. You
can configure a function list for every event.
Object Configurable events
Alarms Incoming
Outgoing
Acknowledge
Loop-In-Alarm
Alarm view Enabling
Disable
Selection changed
Alarm indicator Click
Click when flashing
Note
Device dependency
The following events in the alarm view are not available for all HMI devices:
Enabling
Disable
Selection changed
Click
Click when flashing
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1037
9.3.5.3 System functions for logs
System functions
The following system functions are available for logging:
Function name Function method
ArchiveLogFile This function moves or copies a log to another storage location for long-
term archiving. Use the system function, for example, to move the audit
trail from a local storage medium to the server.
When handling audit trails, always use the "Move log (hmiMove)" mode in
order to avoid noncompliance with FDA guidelines as a result of redundant
data storage.
LogTag Saves the value of the given tags in the given data log. Use the system
function to log a process values at a specific time.
StartLogging Starts the logging process in the specified log. You can interrupt logging
in Runtime by calling the "StopLogging" system function.
StopLogging Stops the logging process in the specified log. To resume logging in
Runtime, select the "StartLogging" system function.
ClearLog Deletes all entries in the specified log.
StartNextLog Stops the logging process in the specified log. Logging is continued in the
sequential log that has been configured for the specified log file.
CloseAllLogs Closes all logs. The connection between WinCC and the log files or log
database is terminated. You can use this system function, for example, to
enable hot-swapping of the storage medium on the HMI device without
exiting the Runtime software.
OpenAllLogs Opens all logs to resume logging. The connection between WinCC and
the log files or log database is recovered.
CopyLog Copies the contents of the specified log to another log.
9.3.5.4 Structure of *.csv files that contain alarms
Introduction
You can save an alarm log as a file in "*.csv" format. CSV stands for Comma Separated Value.
In this format, the table columns that contain the names and the value of the entry are separated
by semicolons. Each table row terminates with a line break.
Example of a log file in *.csv format
This example shows a file with logged alarms:
"Time_ms";"MsgProc";"StateAfter";"MsgClass";"MsgNumber";"Var1";...;"Var8";"TimeString";"
MsgText";"PLC"37986550590,27;1;1;3;110001;"";...;"";"30.06.99 13:12:51";"Change to
operating mode 'online'";37986550682,87;1;1;3;140010;"";...;"";"30.06.99
13:12:59";"Connection established: PLC_1, Station 2, Rack 0, Position 2";
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1038 System Manual, 08/2011,
Structure of a log file in *.csv format
The following values are entered in the log file columns:
Parameters Description
Time_ms Specify a time stamp as a decimal value ( see below for conversion)
Msg_Proc Alarm procedures:
0 = Unknown alarm procedure
1 = System event
2 = Alarm bit procedure (operating alarms)
3 = Alarm number procedure ALARM_S
4 = Diagnostic event
7 = Analog alarm procedure
100 = Alarm bit procedure (fault alarms)
State after Alarm event:
0 = Incoming/Outgoing
1 = Incoming
2 = Incoming/Acknowledged/Outgoing
3 = Incoming/Acknowledged
6 = Incoming/Outgoing/Acknowledged
Msg_Class Alarm class:
0 = No alarm class
1 = "Errors"
2 = "Warnings"
3 = "System"
4 = "Diagnosis Events"
64 ... = of alarm classes configured by the user
Msg Number Alarm number
Var1 to Var8 Value of the trigger tag as a STRING
Time string Time stamp, as STRING in legible data format
Msg text Alarm in a readable STRING
PLC Alarm localization (relevant PLC)
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1039
Conversion of the time stamp decimal value
To further process the time stamp value using a different program, proceed as follows:
1. Divide Time_ms by 1,000,000.
Example: 37986476928 : 1.000.000 = 37986,476928
2. The whole number portion (37986) is the date calculated from 31.12.1899.
In Excel you can now convert the time stamp into days. To do this, assign to the cell that
contains the time stamp, a respective format form the "Date" group.
Result: 37986 results in 31.12.2003
3. The value after the comma (0,476928) indicates the time:
Multiply the value (0.476928) by 24 to obtain the hours (11.446272).
Multiply the remainder (0.446272) by 60 results in the minutes (26.77632).
Multiply the remainder (0.77632) by 60 results in the seconds (46.5792).
Result 11:26:46,579
This conversion is supported by Microsoft Excel, for example.
9.3.5.5 System events
Basics on system events
System events
System events on the HMI device provide information about internal states of the HMI device
and PLC.
The following overview illustrates when a system event occurs and how to eliminate the cause
of error.
Note
HMI device dependency
Some of the system events described in this section apply to the individual HMI devices based
on their scope of functions.
Note
System events are output in an alarm view. System events are output in the language
currently set on your HMI device.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1040 System Manual, 08/2011,
System event parameters
System events may contain encrypted parameters. The parameters are of relevance when
troubleshooting because they provide a reference to the source code of the Runtime software.
These parameters are output after the "Error code:" text.
10000 - Printer alarms
Meaning of the system alarms
All system alarms that can be displayed are listed below.
Table 9-1 10000 - Printer alarms
Number Effect/cause Remedy
10000 The print job could not be started or was canceled
due to an unknown error. Faulty printer setup. Or:
No authorization is available for accessing the
network printer.
Power supply failure during data transfer.
Check the printer settings, cable connections and the
power supply.
Set up the printer once again. Obtain a network printer
authorization.
If the error persists, contact the Hotline!
10001 No printer is installed or a default printer has not
been set up.
Install a printer and/or select it as the default printer.
10002 Overflow of the graphics buffer for printing. Up to two
graphics are buffered.
Allow sufficient intervals between successive print jobs.
10003 Graphics can now be buffered again. --
10004 Overflow of the buffer for printing lines in text mode
(e.g. alarms). Up to 1000 lines are buffered.
Allow sufficient intervals between successive print jobs.
10005 Text lines can now be buffered again. --
10006 The Windows printing system reports an error. Refer
to the output text and the error ID to determine the
possible causes. Nothing is printed or the print is
faulty.
Repeat the action if necessary.
20000 - Global script alarms
Meaning of the system events
All system events that can be displayed are listed below. The system events are divided into
different ranges.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1041
Table 9-2 20000 - Global script alarms
Number Effect/causes Remedy
20010 An error has occurred in the specified script line.
Execution of the script was therefore aborted. Note
the system event that may have occurred prior to
this.
Select the specified script line in the configuration.
Ensure that the tags used are of the allowed types. For
system functions, verify the correct number of
parameters and the parameter types.
20011 An error has occurred in a script that was called by
the specified script.
Execution of the script was therefore aborted in the
called script.
Note the system event that may have occurred prior
to this.
In the configuration, select the script that has been
called directly or indirectly by the specified script.
Ensure that the tags used are of the allowed types.
For system functions, verify the correct number of
parameters and the parameter types.
20012 Inconsistent configuration data. The script could
therefore not be generated.
Recompile the configuration data.
20013 Incorrect installation of the scripting component of
WinCC Runtime. Therefore, no scripts can be
executed.
Reinstall WinCC Runtime on your PC.
Recompile your project using the "Compile > Software
(compile all)" command from the context-sensitive
menu and then download the project to the HMI device.
20014 The system function returns a value that is not
written in any return tag.
Select the specified script in the configuration.
Check whether the script name has been assigned a
value.
20015 Too many successive scripts have been triggered in
short intervals. When more than 20 scripts are
queued for processing, any subsequent scripts are
rejected. In this case, the script indicated in the
alarm is not executed.
Check what is triggering the scripts. Extend the times,
e.g. the acquisition cycle of the tag initiating the script.
30000 - Alarms errors when using system functions
Meaning of the system events
All system events that can be displayed are listed below. The system events are divided into
different ranges.
Table 9-3 30000 - Alarms errors when using system functions
Number Effect/causes Remedy
30010 The tag could not accept the function result, e.g.
when it has exceeded the value range.
Check the tag types of the system function parameters.
30011 A system function could not be executed because
the function was assigned an invalid value or type in
the parameter.
Check the parameter value and tag type of the invalid
parameter. If a tag is used as a parameter, check its
value.
30012 A system function could not be executed because
the function was assigned an invalid value or type in
the parameter.
Check the parameter value and tag type of the invalid
parameter. If a tag is used as a parameter, check its
value.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1042 System Manual, 08/2011,
40000 - Linear scaling alarms
Meaning of the system alarms
All system alarms that can be displayed are listed below. The system alarms are divided into
different ranges:
Table 9-4 40000 - Linear scaling alarms
Number Effect/causes Remedy
40010 The system function could not be executed since the
parameters could not be converted to a common tag
type.
Check the parameter types in the configuration.
40011 The system function could not be executed since the
parameters could not be converted to a common tag
type.
Check the parameter types in the configuration.
50000 - Data server alarms
Meaning of the system alarms
All system alarms that can be displayed are listed below. The system alarms are divided into
different ranges:
Table 9-5 50000 - Data server alarms
Number Effect/causes Remedy
50000 The HMI device is receiving data faster than it is
capable of processing. Therefore, no further data is
accepted until all current data have been processed.
Data exchange then resumes.
--
50001 Data exchange has been resumed. --
60000 - Win32 function alarms
Meaning of the system events
All system events that can be displayed are listed below.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1043
Table 9-6 60000 - Win32 function alarms
Number Effect/causes Remedy
60000 This alarm is generated by the "ShowSystemEvent"
system function. The text to be displayed is
transferred to the function as a parameter.
--
60010 The file could not be copied in the direction defined
because one of the two files is currently open or the
source/target path is not available.
It is possible that the Windows user has no access
rights to one of the two files.
Restart the system function or check the paths of the
source/target files. In Windows NT/XP: Users executing
WinCC Runtime must be granted access to the files.
60011 An attempt was made to copy a file to itself.
It is possible that the Windows user has no access
rights to one of the two files.
Check the path of the source/target file.
In Windows NT//XP and NTFS file system: Users
executing WinCC Runtime must be granted access to
the files.
70000 - Win32 function alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-7 70000 - Win32 function alarms
Number Effect/causes Remedy
70010 The application could not be started because it could
not be found in the path specified or there is
insufficient memory space.
Check whether the application exists in the specified
path or close other applications.
70011 The system time could not be modified.
The error alarm only appears in connection with area
pointer "Date/time PLC". Possible causes:
An invalid time was transferred in the job mailbox.
The Windows user has no right to modify the
system time.
If the first parameter in the system event is displayed
with the value 13, the second parameter indicates
the byte containing the incorrect value.
Check the time which is to be set.
Using Windows NT/XP: Users running WinCC Runtime
must be granted the right to set the system time of the
operating system.
70012 Error when executing the function "StopRuntime"
with the "Runtime and operating system" option.
Windows and WinCC Runtime are not closed.
The error was possibly generated because other
programs cannot be closed.
Close all programs currently running.
Then close Windows.
70013 The system time could not be modified because an
invalid value was entered. Incorrect separators may
have been used.
Check the time which is to be set.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1044 System Manual, 08/2011,
Number Effect/causes Remedy
70014 The system time could not be modified. Possible
causes:
An invalid time was transferred.
The Windows user has no right to modify the
system time.
Windows rejects the setting request.
Check the time which is to be set.
Using Windows NT/XP: Users running WinCC Runtime
must be granted the right to set the system time of the
operating system.
70015 The system time could not be read because
Windows rejects the reading function.
--
70016 An attempt was made to select a screen by means
of a system function or job. This is not possible
because the screen number specified does not exist.
Or: A screen could not be generated due to
insufficient system memory.
Or: The screen is blocked.
Or: Screen call has not been executed correctly.
Check the screen number in the function or job with the
screen numbers configured.
Assign the number to a screen if necessary.
Check the details for the screen call and whether the
screen is blocked for specific users.
70017 Date/time is not read from the area pointer because
the address set in the PLC is either not available or
has not been set up.
Change the address or set up the address in the PLC.
70018 Acknowledgment that the password list has been
successfully imported.
--
70019 Acknowledgment that the password list has been
successfully exported.
--
70020 Acknowledgment for activation of alarm reporting. --
70021 Acknowledgment for deactivation of alarm reporting. --
70022 Acknowledgment to starting the Import Password
List action.
--
70023 Acknowledgment to starting the Export Password
List action.
--
70024 The range of values of the tag was exceeded in the
system function.
No calculation of the system function.
Check and correct the calculation.
70025 The range of values of the tag was exceeded in the
system function.
No calculation of the system function.
Check and correct the calculation.
70026 No other screens are stored in the internal screen
memory.
No other screens can be selected.
--
70027 The backup of the RAM file system has been started. --
70028 The files from the RAM have been copied in the
Flash memory.
The files from the RAM have been copied in the
Flash memory. Following a restart, these saved files
are copied back to the RAM file system.
--
70029 Backup of the RAM file system has failed.
No backup copy of the RAM file system has been
made.
Check the settings in the "Control Panel > OP" dialog
and save the RAM file system using the "Save Files"
button in the "Persistent Storage" tab.
70030 The parameters configured for the system function
are faulty.
The connection to the new PLC was not established.
Compare the parameters configured for the system
function with the parameters configured for the PLCs
and correct them as necessary.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1045
Number Effect/causes Remedy
70031 The PLC configured in the system function is not an
S7 PLC.
The connection to the new PLC was not established.
Compare the S7 PLC name parameter configured for
the system function with the parameters configured for
the PLC and correct them as necessary.
70032 The object configured with this number in the tab
sequence is not available in the selected screen.
The screen changes but the focus is set to the first
object.
Check the number of the tab sequence and correct it if
necessary.
70033 An e-mail cannot be sent because a TCP/IP
connection to the SMTP server no longer exists.
This system event is generated only at the first
attempt. All subsequent unsuccessful attempts to
send an e-mail will no longer generate a system
event. The event is regenerated when an e-mail has
been successfully sent in the meantime.
The central e-mail component in WinCC Runtime
attempts to connect to the SMTP server at cyclic
intervals (1 minute) in order to transmit the remaining
e-mails.
Check the network connection to the SMTP server and
re-establish it if necessary.
70034 Following a disruption, the TCP/IP connection to the
SMTP server could be re-established.
The queued e-mails are then sent.
--
70036 No SMTP server for sending e-mails is configured.
An attempt to connect to an SMTP server has failed
and it is not possible to send e-mails.
WinCC Runtime generates the system event after
the first attempt was made to send an e-mail.
Configure an SMTP server:
In the WinCC Engineering System
using "Device settings > Device settings"
In the Windows CE operating system
using "Control Panel > Internet Settings > E-mail >
SMTP Server"
70037 An e-mail cannot be sent for unknown reasons.
The contents of the e-mail are lost.
Check the e-mail parameters (recipient etc.).
70038 The SMTP server has rejected sending or
forwarding an e-mail because the domain of the
recipient is unknown to the server or because the
SMTP server requires authentication.
The contents of the e-mail are lost.
Check the domain of the recipient address or disable
the authentication on the SMTP server if possible.
SMTP authentication is currently not used in
WinCC Runtime.
70039 The syntax of the e-mail address is incorrect or
contains illegal characters.
The contents of the e-mail are discarded.
Check the e-mail address of the recipient.
70040 The syntax of the e-mail address is incorrect or
contains illegal characters.
--
70041 The import of the user management was aborted
due to an error.
Nothing was imported.
Check your user administration or download it again to
the panel.
70042 The range of values of the tag was exceeded while
executing the system function.
The system function was not calculated.
Check and correct the calculation.
70043 The range of values of the tag was exceeded while
executing the system function.
The system function was not calculated.
Check and correct the calculation.
70044 An error occurred while sending the e-mails. The e-
mails were not sent.
Check the SMTP settings and the error message in the
system event.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1046 System Manual, 08/2011,
Number Effect/causes Remedy
70045 Cannot load a file required for encrypting the e-mail. Update the operating system and Runtime.
70046 The server does not support encryption. Select an SMTP server that supports encryption.
70047 The SSL versions of the HMI device and SMTP
server may not be compatible.
Contact your network administrator or the operator of
the SMTP server.
80000 - Log alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-8 80000 - Log alarms
Number Effect/causes Remedy
80001 The log specified is filled to the size defined (in
percent) and must be stored elsewhere.
You swap out the file or table by executing a move or
copy function.
80002 A line is missing in the specified log. --
80003 The copying process for logging was not successful.
In this case, it is advisable to check any subsequent
system events, too.
--
80006 Since logging is not possible, this causes a
permanent loss of the functionality.
In the case of databases, check whether the
corresponding data source exists and start up the
system again.
80009 A copying action has been completed successfully. --
80010 An incorrect storage location was entered in WinCC
and causes permanent loss of functionality.
Configure the storage location for the respective log
again and restart the system when the full functionality
is required.
80012 Log entries are stored in a buffer. If the values are
read to the buffer faster than they can be physically
written (using a hard disk, for example), overloading
may occur and recording is then stopped.
Archive fewer values.
Or:
Increase the logging cycle.
80013 The overload status no longer exists. Archiving
resumes the recording of all values.
--
80014 The same action was triggered twice in quick
succession. Since the process is already in
operation, the action is only carried out once.
--
80015 This system event is used to report DOS or database
errors to the user.
--
80016 The logs are separated by system function
"CloseAllLogs" and the incoming entries exceed the
defined buffer size.
All buffer entries are deleted.
Reconnect the logs.
80017 The number of incoming entries cause a buffer
overflow. This can be caused, for example, by
several copying actions being activated at the same
time.
All copy jobs in the buffer are deleted.
Stop the copy action.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1047
Number Effect/causes Remedy
80019 The connection between WinCC and all log files was
shut down, for example, after execution of the
"CloseAllLogs" system function.
Entries are written to the buffer and written to the
logs when the connection is recovered.
There is no connection to the storage location and
the storage medium can be changed.
--
80020 The maximum number of simultaneously copy
operations has been exceeded. Copying is not
executed.
Wait until the current copying actions have been
completed, then restart the last copy action.
80021 An attempt was made to delete a log which is still
busy with a copy action. Deletion has not been
executed.
Wait until the current copying actions have been
completed, then restart the last action.
80022 An attempt was made to use system function
"StartSequenceLog" to start a sequence log for a log
which is not configured as sequence log. No
sequence log file is created.
In the project, check
whether the "StartSequenceLog" system function
was properly configured.
if the tag parameters are properly provided with data
on the HMI device.
80023 An attempt was made to copy a log to itself.
The log is not copied.
In the project, check
whether the "CopyLog" system function was
properly configured.
if the tag parameters are properly provided with data
on the HMI device.
80024 In your configuration, you specified that the
"CopyLog" system function should not allow copying
if the destination log already contains data ("Mode"
parameter). The log is not copied.
Edit the "CopyLog" system function in your
configuration, if necessary. Before you initiate the
system function, delete the destination log file.
80025 You have canceled the copy operation.
Data written up to this point are retained. The target
log file (if configured) was not deleted.
The cancellation is reported by an error entry
$RT_ERR$ at the end of the target log.
--
80026 This alarm is output after all logs are initialized.
Values are written to the logs from then on. No
entries are written to the logs before this time has
expired, irrespective of the active state of
WinCC Runtime.
--
80027 The internal Flash memory has been specified as
the storage location for a log. This is not permissible.
No values are written to this log and the log file is
not created.
Configure "Storage Card" or network path as the
storage location.
80028 The alarm serves as status report indicating that the
logs are currently being initialized. No values are
logged until the alarm 80026 is output.
--
80029 The number of logs specified in the alarm could not
be initialized. Initialization of logs was finished.
The faulty log files are not available for logging jobs.
Evaluate the additional system events related to this
alarm. Check the configuration, the ODBC (Open
Database Connectivity), and the specified drive.
80030 The structure of the existing log file does not match
the expected structure.
Logging is stopped for this log.
Delete the existing log data manually, in advance.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1048 System Manual, 08/2011,
Number Effect/causes Remedy
80031 The log in CSV format is corrupted.
The log cannot be used.
Delete the faulty file.
80032 Logs can be configured with events. These are
triggered as soon as the log is full. Assuming
WinCC Runtime is started and the log is already full,
the event would never be triggered.
The specified log is full and no longer accepts data.
Close WinCC Runtime, delete the log, and restart
WinCC Runtime.
Or:
Configure a button which contains the same actions as
the event and press it.
80033 "System Defined" is set in the data log file as the
data source name. This causes an error. No data is
written to the database logs, whereas the logging to
the CSV logs works.
Reinstall SQL Sever 2005 Express.
80034 An error has occurred in the initialization of the logs.
An attempt has been made to create the tables as a
backup. This action was successful. A backup copy
of the tables of the corrupted log file was generated
and the cleared log restarted.
No action is necessary. However, it is recommended to
save the backup files or delete them in order to make
the space available again.
80035 An error has occurred in the initialization of the logs.
An attempt has been made to create backups of the
tables and this has failed. No logging or backup has
been performed.
It is recommended to save the backups or to delete them
in order to release memory.
80044 The export of a log was interrupted because
Runtime was closed or due to a power failure. At the
restart of Runtime, it was detected that the export
must be resumed.
The export resumes automatically.
80045 The export of a log was interrupted due to an error
in the connection to the server or at the server itself.
The export is repeated automatically. Check:
The connection to the server.
If the server is running.
If there is enough free space on the server.
80046 The destination file or the associated directory could
not be created on the server.
Check whether there is enough space on the server and
it you have permission to create the log file.
80047 The log could not be read while exporting it. Check whether the storage medium is correctly inserted.
80049 The log could not be renamed while preparing to
export it.
The job can not be completed."
Check whether the storage medium is correctly inserted
and if there is sufficient space on the medium.
80050 The log which shall be exported is not closed.
The job can not be completed.
Make sure to call the "CloseAllLogs" system function
before using the "ExportLog" system function. Change
the configuration as required.
80051 The log to be copied contains an invalid checksum.
The log was not copied.
Select a log with a valid checksum. The selected log
may have been manipulated.
80052 The log cannot be read. Check the log and the specified path.
80053 The closed log cannot be read. Open the log.
90000 - FDA alarms
Meaning of the system events
All system events that can be displayed are listed below.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1049
Table 9-9 90000 - FDA alarms
Number Effect/causes Remedy
90024 No operator actions can be logged due to lack of
space on the storage medium for log. The operator
action will therefore not be executed.
Provide more storage space by inserting a blank storage
medium, or backup the log files to the server using the
"ExportLog" function.
90025 No user actions can be logged because of error
state of the archive. Therefore the user action will
not be executed.
Check whether the storage medium is correctly inserted.
90026 No operator actions can be logged because the log
is closed. The operator action will therefore not be
executed.
Before further operator actions are carried out, the log
must be reopened with the help of system function
"OpenAllLogs". Change the configuration as required.
90028 The password you entered is incorrect. Enter the correct password.
90029 Runtime was closed during ongoing operation
(perhaps due to a power failure) or a storage
medium in use is incompatible with Audit Trail. An
Audit Trail is not suitable if it belongs to another
project or has already been logged.
Ensure that you are using the correct storage medium.
90030 Runtime was closed during ongoing operation
(perhaps due to a power failure).
--
90031 Runtime was closed during ongoing operation
(perhaps due to a power failure).
--
90032 Running out of space on the storage medium for log. Provide more storage space by inserting a blank storage
medium, or backup the log files to the server using the
"ExportLog" function.
90033 No more space on the storage medium for log. As
of now, no more operator actions requiring logging
will be executed.
Provide more storage space by inserting a blank storage
medium, or backup the log files to the server using the
"ExportLog" function.
90039 You do not have the necessary authorization to
perform this action.
Adapt or upgrade your authorizations.
90040 Audit Trail is switched off because of a forced user
action.
Reactivate the "Audit Trail" with the help of system
function "StartLog".
90041 A user action which has to be logged has been
executed without a logged on user.
A user action requiring logging should only be possible
with permission. Change the configuration by setting a
required authorization for the input object.
90044 A user action which has to be confirmed was
blocked, because there is another user action
pending.
Repeat the user action if necessary.
90048 The Audit Trail cannot be printed while data
relevant to the audit is being logged.
Stop logging by calling system function "StopLogging".
90049 Access to required file is not possible. Check the network connection or the storage medium.
90056 The recipe was not imported because the file
contains no checksum.
Select a file with a checksum.
You can also disable checksum verification by calling
system function "ImportDataRecords".
90057 The recipe was not imported because the file
contains an invalid checksum. The selected file may
have been manipulated.
Select a file with a valid checksum.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1050 System Manual, 08/2011,
110000 - Offline function alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-10 110000 - Offline function alarms
Number Effect/causes Remedy
110000 The operating mode was changed. "Offline" mode
is now set.
--
110001 The operating mode was changed. "Online" mode
is now set.
--
110002 The operating mode was not changed. Check the connection to the PLCs.
Check whether the address range for the Coordination"
area pointer is present in the PLC.
110003 The operating mode of the specified PLC was
changed by the "SetConnectionMode" system
function.
The "offline" operating mode is now set.
--
110004 The operating mode of the specified PLC was
changed by the "SetConnectionMode" system
function.
The "online" operating mode is now set.
--
110005 An attempt was made to use the
"SetConnectionMode" system function to set the
specified PLC to "online" mode, although the entire
system is in "offline" mode. This changeover is not
allowed. The PLC remains in "offline" mode.
Switch the complete system to "online" mode and repeat
execution of the system function.
110006 The content of the "project ID" area pointer does not
match the project ID configured in WinCC. The
WinCC Runtime is therefore terminated.
Check:
the project ID entered on the PLC.
the project ID entered in WinCC.
120000 - Trend alarms
Meaning of the system alarms
All system alarms that can be displayed are listed below.
Table 9-11 120000 - Trend alarms
Number Effect/causes Remedy
120000 The trend is not displayed because you configured
an incorrect axis to the trend or an incorrect trend.
Change the configuration.
120001 The trend is not displayed because you configured
an incorrect axis to the trend or an incorrect trend.
Change the configuration.
120002 The trend is not displayed because the tag assigned
attempts to access an invalid PLC address.
Check whether the data area for the tag exists in the
PLC, the configured address is correct and the value
range for the tag is correct.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1051
130000 - System information alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-12 130000 - System information alarms
Number Effect/causes Remedy
130000 The action was not executed. Close all other programs.
Delete files no longer required from the hard disk.
130001 The action was not executed. Delete files no longer required from the hard disk.
130002 The action was not executed. Close all other programs.
Delete files no longer required from the hard disk.
130003 No data medium found. The operation is canceled. Check the following conditions, for example:
Access to the correct data carrier?
Is a data carrier inserted?
130004 The data carrier is write-protected. The operation is
canceled.
Check whether the correct data medium is being
accessed. Remove the write-protection if necessary.
130005 The file is read only. The operation is canceled. Check whether the correct file is being accessed.
Change the file attributes.
130006 No access to the file. The operation is canceled. Check the following conditions, for example:
Is the correct file being accessed?
Does the file exist?
Is another action preventing concurrent access to the
file?
130007 The network connection is interrupted.
Records cannot be saved or read via the network
connection.
Check the network connection and eliminate the cause
of error.
130008 No storage card available.
The specified records cannot be saved to or read
from Storage Card.
Insert the storage card.
130009 The specified folder does not exist on the storage
card.
The files stored in this directory are not backed up
after switching off the HMI device.
Insert the storage card.
130010 The maximum nesting depth can be exhausted
when, for example, value changes in a script initiate
the call of an infinite number of further scripts.
The configured functionality is not provided.
Check the configuration.
130013 No storage card available.
The specified records cannot be saved to or read
from Storage Card.
Insert the storage card.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1052 System Manual, 08/2011,
140000 - Connection alarms: Connection + device
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-13 140000 - Connection alarms: Connection + device
Number Effect/causes Remedy
140000 An online connection to the PLC is established. --
140001 The online connection to the PLC was shut down. --
140003 No tag update or write operations are executed. Check whether the connection is up and the PLC is
switched on.
In the Control Panel, check the set parameters using the
"Set PG/PC interface" function.
Restart the system.
140004 No tag update or write operations are executed due
to an incorrect access point, or incorrect module
configuration.
Verify the connection and check whether the PLC is
switched on.
Check the access point or the module configuration
(MPI, PPI, PROFIBUS) in the Control Panel with "Set
PG/PC interface".
Restart the system.
140005 No tag update or write operations are executed due
to an incorrect HMI device address (possibly too
high).
Use a different HMI device address.
Verify the connection and check whether the PLC is
switched on.
Check the parameter definitions in the Control Panel
using "Set PG/PC interface".
Restart the system.
140006 No tag update or write operations are executed due
to an incorrect baud rate setting.
Select a different baud rate in WinCC (according to
module, profile, communication peer, etc.).
140007 An incorrect bus profile prevents tag updates or
write operations (see %1).
The following parameters could not be written to the
registry:
1: Tslot
2: Tqui
3: Tset
4: MinTsdr
5: MaxTsdr
6: Trdy
7: Tid1
8: Tid2
9: Gap Factor
10: Retry Limit
Check the custom bus profile.
Check the connection and whether the PLC is switched
on.
Check the parameter definitions in the Control Panel
using "Set PG/PC interface".
Restart the system.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1053
Number Effect/causes Remedy
140008 An incorrect baud rate prevents tag updates or write
operations. The following parameters could not be
written to the registry:
0: General error
1: Wrong version
2: Profile cannot be written to the registry.
3: The subnet type cannot be written to the registry.
4: The Target Rotation Time cannot be written to
the registry.
5: Incorrect Highest Station Address (HSA).
Check whether the connection is up and the PLC is
switched on.
In the Control Panel, check the set parameters using the
"Set PG/PC interface" function.
Restart the system.
140009 No tag updates or write operations because the S7
communication module was not found.
To reinstall the module, open the Control Panel and
select "Set PG/PC interface".
140010 No S7 communication partner found because the
PLC is shut down.
DP/T:
The option PG/PC is the only master is not set in
the Control Panel under Set PG/PC interface.
Switch on the PLC.
DP/T:
If only one master is connected to the network, disable
"PG/PC is the only master" in "Set PG/PC interface".
If several masters are connected to the network, enable
these. Do not change any settings, for this will cause bus
errors.
140011 No tag updates or write operations because
communication is down.
Check the connection and whether the communication
partner is switched on.
140012 There is an initialization problem (e.g. if
WinCC Runtime was closed in Task Manager).
Or:
Another application (e.g.STEP7) with different bus
parameters is active and the driver cannot be
started with the new bus parameters (baud rate, for
example).
Restart the HMI device.
Or:
Start WinCC Runtime and then start your other
applications.
140013 The MPI cable is disconnected and, therefore, there
is no power supply.
Check the connections.
140014 The configured bus address is in use by another
application.
Change the HMI device address in the PLC
configuration.
140015 Incorrect baud rate
Or:
Incorrect bus parameters (e.g. HSA)
Or:
OP address > HSA or: Incorrect interrupt vector
(interrupt not registered by the driver)
Correct the parameters.
140016 The hardware does not support the configured
interrupt.
Change the interrupt number.
140017 The set interrupt is in use by another driver. Change the interrupt number.
140018 SIMOTION Scout disabled the consistency check.
Only a corresponding note appears.
In SIMOTION Scout, reactivate the consistency check
and once again download the project to the PLC.
140019 SIMOTION Scout is downloading a new project to
the PLC. Connection to the PLC is canceled.
Wait until the end of the reconfiguration.
140020 The version in the PLC and in the project (FWX file)
do not match.
Connection to the PLC is canceled.
The following remedies are available:
Download the current version to the PLC using
SIMOTION Scout.
Recompile the project using WinCC ES, close
WinCC Runtime, and restart with the new configuration.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1054 System Manual, 08/2011,
160000 - Connection alarms: OPC: Connection
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-14 160000 - Connection alarms: OPC: Connection
Number Effect/causes Remedy
160000 No more data is read or written. Possible causes:
The cable connection is interrupted.
The PLC does not respond or has failed, etc.
The wrong port is used for the connection.
System overload
Check whether the cable is plugged in and the PLC is
OK, and whether the correct port is used.
Restart the system if the system event persists.
160001 The connection is recovered because the cause of
the interruption has been eliminated.
--
160010 No connection to the server because the server ID
(CLS-ID) cannot be determined.
Values cannot be read or written.
Check access rights.
160011 No connection to the server because the server ID
(CLS-ID) cannot be determined.
Values cannot be read or written.
Check the following conditions, for example:
Correct server name?
Correct station name?
Is the server registered?
160012 No connection to the server because the server ID
(CLS-ID) cannot be determined.
Values cannot be read or written.
Check the following conditions, for example:
Correct server name?
Correct station name?
Is the server registered?
Note for advanced users:
Interpret the value from HRESULT.
160013 The specified server was started as InProc server.
This has not been released and may lead to
undefined behavior because the server is running
in the same process area as WinCC Runtime.
Configure the server as OutProc Server or Local Server.
160014 Only one OPC server project can be started on a
PC/MP. An alarm is output after an attempt was
made to start a second project.
The second project has no OPC server functionality
and cannot be located as an OPC server by external
sources.
Do not start a second project with OPC server
functionality on the computer.
170000 - S7 dialog alarms
Meaning of the system alarms
All system alarms that can be displayed are listed below.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1055
Table 9-15 170000 - S7 dialog alarms
Number Effect/causes Remedy
170000 S7 diagnostics events are not indicated because it
is not possible to log on to the S7 diagnostics
functions at this device. The service is not
supported.
--
170001 The S7 diagnostics buffer cannot be viewed
because communication with the PLC is shut down.
Set the PLC to online mode.
170002 The S7 diagnostics buffer cannot be viewed
because reading of the diagnostics buffer (SSL)
was canceled with error.
--
170003 An S7 diagnostics event cannot be visualized. The
system returns internal error %2.
--
170004 An S7 diagnostics event cannot be visualized. The
system returns an internal error of error class %2,
error number %3.
--
170007 It is not possible to read the S7 diagnostics buffer
(SSL) because this operation was canceled with an
internal error of class %2 and error code %3.
--
180000 - General alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-16 180000 - General alarms
Number Effect/causes Remedy
180000 A component/OCX received configuration data with
a version ID which is not supported.
Install a newer component.
180001 System overload because too many actions are
running in parallel. Certain actions can be executed,
while others are discarded.
Several remedies are available:
Generate alarms at a slower rate (polling).
Initiate scripts and functions at greater intervals.
If the alarm appears more frequently:
Restart the HMI device.
180002 The screen keyboard could not be activated.
Possible causes:
"TouchInputPC.exe" was not registered due to
faulty Setup.
Reinstall WinCC Runtime.
190000 - Tag alarms
Meaning of the system events
All system events that can be displayed are listed below.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1056 System Manual, 08/2011,
Table 9-17 190000 - Tag alarms
Number Effect/causes Remedy
190000 It is possible that the tag is not updated. --
190001 The tag is updated after the cause of the last error
state has been eliminated (recovery of normal
operation).
--
190002 The tag is not updated because communication with
the PLC is down.
Select system function "SetOnline" to enable
communication.
190004 The tag is not updated because the address
configured for this tag does not exist.
Check the configuration.
190005 The tag is not updated because the configured PLC
type does not exist for this tag.
Check the configuration.
190006 The tag is not updated because it is not possible to
map the PLC type in the data type of the tag.
Check the configuration.
190007 The tag value is not modified because the
connection to the PLC is interrupted or the tag is
offline.
Set online mode or reconnect to the PLC.
190008 The configured tag limits were violated due to one
of the following events:
Value input
System function
Script
Observe the configured or current tag limits.
190009 An attempt was made to assign this tag a value that
is outside the valid range of values for this data type.
For example, input of the value 260 for a byte tag,
or input of the value -3 for an unsigned word tag.
Observe the range of values for the data type of the tags.
190010 The rate at which values are written to the tag is too
high (for example, in a loop triggered by a script).
Values are lost because only up to 100 operations
are saved to the buffer.
The following remedies are available:
Extend the interval between multiple write actions.
Do not use an array tag longer than 6 words when
configuring an acknowledgment on the HMI device
using "HMI acknowledgment tag".
190011 Possible cause 1:
The value entered could not be written to the
configured PLC tag because the high or low limit
was exceeded.
The system discarded the entry and restored the
original value.
Possible cause 2:
The connection to the PLC was interrupted.
Note that the value entered must be within the range of
values of the control tag.
Check the connection to the PLC.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1057
Number Effect/causes Remedy
190012 It is not possible to convert a value from a source
format to a target format, for example:
An attempt is being made to write a counter value
that is outside the valid, PLC-specific range of
values.
A tag of the type Integer should be assigned a value
of the type string.
Check the range of values, or the data type of the tag.
190013 You entered a string that exceeds the tag length.
The string is truncated automatically to a valid
length.
Always enter strings that do not exceed the valid tag
length.
190100 - Area pointer alarms
190100 - Area pointer alarms
Number Effect/causes Remedy
190100 The area pointer is not updated because the
address configured for this pointer does not exist.
Type
1 Warnings
2 Errors
3 PLC acknowledgment
4 HMI device acknowledgment
5 LED image
6 Trend request
7 Trend transfer 1
8 Trend transfer 2
No.:
Consecutive number displayed in WinCC ES.
Check the configuration.
190101 The area pointer is not updated because it is not
possible to map the PLC type to the area pointer
type.
Parameter type and no.:
see alarm 190100
--
190102 The area pointer is updated after the cause of the
last error state has been eliminated (recovery of
normal operation). Parameter type and no.: See
alarm 190100.
--
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1058 System Manual, 08/2011,
200000 - PLC coordination alarms
200000 - PLC coordination alarms
Number Effect/causes Remedy
200000 Coordination is not executed because the address
configured in the PLC does not exist/is not set.
Change the address or set up the address in the PLC.
200001 Coordination is canceled because the write access
to the address configured in the PLC is not possible.
Change the address or set the address in the PLC at an
area which allows write access.
200002 Coordination is not carried out at the moment
because the address format of the area pointer
does not match the internal storage format.
Internal error
200003 Coordination can be executed again because the
last error state is eliminated (return to normal
operation).
--
200004 The coordination may not be executed. --
200005 No more data is read or written. Possible causes:
The cable is defective.
The PLC does not respond, is defective, etc.
System overload
Ensure that the cable is plugged in and the PLC is
operational.
Restart the system if the system alarm persists.
210000 - PLC job alarms
210000 - PLC job alarms
Number Effect/causes Remedy
210000 Jobs are not processed because the configured
address does not exist/has not been set up in
the PLC.
Change the address or set up the address in the PLC.
210001 Jobs are not processed because read/write
access to the configured address is not possible
in the PLC.
Change the address, or set up the address in a PLC
area at which read/write access is possible.
210002 Jobs are not executed because the address
format of the area pointer does not match the
internal storage format.
Internal error
210003 The job buffer is processed again because the
last error status has been eliminated (recovery
of normal operation).
--
210004 The job buffer is possibly not going to be
processed.
--
210005 A job mailbox with invalid number was initiated. Check the PLC program.
210006 An error occurred while executing the job
mailbox. As a result, the control job is not
executed. Observe the next/previous system
event.
Check the parameters of the control job. Recompile
the configuration data.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1059
220000 - WinCC communication driver alarms
220000 - WinCC communication driver alarms
Number Effect/causes Remedy
220001 The tag is not downloaded because write access
to data type Bool/Bit is not supported by the
sublevel communication driver/HMI device.
Change the configuration.
220002 The tag is not downloaded because write access
to data type Byte is not supported by the
sublevel communication driver/HMI device.
Change the configuration.
220003 The communication driver cannot be loaded as
it is possibly not installed.
Install the driver by reinstalling WinCC Runtime.
220004 Communication is down and no update data is
transferred because the cable is not connected
or defective etc.
Check the connection.
220005 Communication is up. --
220006 The connection between the specified PLC and
the specified port is active.
--
220007 The connection to the specified PLC is
interrupted at the specified port.
Check the following:
Is the cable plugged in?
Is the PLC OK?
Is the right port being used?
Is your configuration OK (port parameters,
protocol settings, PLC address)?
Restart the system if the system event persists.
220008 The communication driver cannot access or
open the specified port. This port might be in use
by another application, or a port that does not
exist on the target device is being used.
No communication with the PLC.
Close all applications that access the port and restart
the computer.
Use another port that exists in the system.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1060 System Manual, 08/2011,
230000 - Screen object alarms
230000 - Screen object alarms
Number Effect/causes Remedy
230000 The value entered could not be used. The system
discards this entry and restores the previous
value.
Possible causes:
The range of values is exceeded.
You entered invalid characters
The valid maximum number of users has
been exceeded.
Enter a practical value, or delete a user that is no
longer required.
230002 The user currently logged on does not have the
necessary authorization, so the system discards
the entry and restores the previous value.
Log on as user with appropriate authorization.
230003 Change to the specified screen failed because
this screen is not available/configured. The
current screen remains selected.
Configure the screen and check the selection
function.
230005 The range of values of the tag has been
exceeded in the I/O field.
The original tag value is retained.
Observe the range of values for the tag when
entering a value.
230100 During navigation in the Web browser, the
system returned a message which may be of
interest to the user.
The Web browser continues to run but may not
(fully) show the new page.
Navigate to another page.
230200 The HTTP channel connection was interrupted
due to an error. This error is explained in detail
by another system event.
Data is no longer exchanged.
Check the network connection.
Check the server configuration.
230201 The HTTP channel connection is set up.
Data is exchanged.
--
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1061
Number Effect/causes Remedy
230202 WININET.DLL has detected an error. Usually,
this error occurs if it is not possible to connect to
the server, or the server denies a connection
because the client lacks proper authorization.
An unknown server certificate may also be the
cause if the connection is encrypted by means of
SSL.
The alarm text provides details.
This text is always in the language of the
Windows installation because it is returned by the
Windows OS.
Process values are no longer exchanged.
The part of the alarm returned by the Windows
OS might not be displayed, e.g. "An error has
occurred". WININET.DLL returns the following
error: Number: 12055 Text:HTTP: <no error text
available>."
Depending on the cause:
When an attempt to connect fails, or a timeout occurs:
Check the network connection and the network.
Check the server address.
Check whether the WebServer is actually running
on the target station.
Incorrect authorization:
The configured user name and/or password do
not match the entries on the server. Set
consistent data.
If the server certificate is rejected:
Certificate signed by an unknown CA ( ):
Ignore this point, or install a certificate that has
been signed with one of the root certificates
known to the client station.
The date of the certificate is invalid:
Ignore this point, or install a certificate with valid
date on the server.
Invalid CN (Common Name or Computer Name):
Ignore this point, or install a certificate with a
name that corresponds to the server address.
230203 Although a connection can be made to the
server, the HTTP server refused to connect.
Possible causes:
WinCC Runtime does not run on the server
The HTTP channel is not supported (503
Service unavailable).
Other errors can only occur if the Webserver
does not support the HTTP channel. The
language of the alarm text depends on the
Webserver.
Data is not exchanged.
On 503 Service unavailable error:
Check whether WinCC Runtime is running on the
server and whether the HTTP channel is supported.
230301 Internal error. An English text explains the error
in more detail. The error may be caused by
insufficient memory.
OCX does not work.
--
230302 The name of the remote server cannot be
resolved.
An attempt to connect has failed.
Check the configured server address.
Check whether the DNS service is available on the
network.
230303 The remote server is not running on the
addressed computer.
incorrect server address.
An attempt to connect has failed.
Check the configured server address.
Check whether the remote server is running on the
target computer.
230304 The remote server on the addressed computer is
incompatible with VNCOCX.
An attempt to connect failed.
Use a compatible remote server.
230305 Authentication has failed due to incorrect
password.
An attempt to connect failed.
Configure the correct password.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1062 System Manual, 08/2011,
Number Effect/causes Remedy
230306 Error in the connection to the remote server. This
may occur as a result of network problems.
An attempt to connect failed.
Check whether the network cable is plugged in, or
whether there are network problems.
230307 The connection to the remote server was shut
down. Possible causes:
The remote server was shut down
The user instructed the server to close all
connections.
The connection is cancelled.
--
230308 This alarm provides information on the
connection status.
An attempt is made to connect.
--
240000 - Authorization alarms
240000 - Authorization alarms
Number Effect/causes Remedy
240000 WinCC Runtime is running in demo mode.
You have no authorization, or your authorization
is corrupted.
Install the authorization.
240001 WinCC Runtime is running in demo mode.
You configured too many tags for the installed
version.
Load an adequate authorization / powerpack.
240002 WinCC Runtime is running with time-limited
emergency authorization.
Restore the full authorization.
240004 Error when reading the emergency authorization.
WinCC Runtime is running in demo mode.
Restart WinCC Runtime. Install or repair the
authorization (see Commissioning Instructions for
Software Protection).
240005 Automation License Manager has detected an
internal system error.
Possible causes:
Corrupted file
Faulty installation
No free memory space for Automation
License Manager, or similar.
Restart the HMI device/PC. If this procedure does not
solve the problem, remove and then reinstall
Automation License Manager.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1063
250000 - S7 Status/Force alarms
250000 - S7 Status/Force alarms
Number Effect/causes Remedy
250000 The tag in the specified line in "Status Force" is
not updated because the address configured for
this tag is not available.
Check the set address and then verify that the
address is set up in the PLC.
250001 The tag in the specified line in "Status Force" is
not updated because the PLC type configured
for this tag does not exist.
Check the set address.
250002 The tag in the specified line in "Status Force" is
not updated because it is not possible to map the
PLC type in the tag type.
Check the set address.
250003 An attempt to connect to the PLC failed. The tags
are not updated.
Check the connection to the PLC. Check that the PLC
is switched on and is online.
260000 - Password system alarms
260000 - Password system alarms
Number Effect/causes Remedy
260000 An unknown user or an unknown password has
been entered in the system.
The current user is logged off from the system.
Log on to the system as a user with a valid password.
260001 The logged in user does not have sufficient
authorization to execute the protected functions
on the system.
Log on to the system as a user with sufficient
authorization.
260002 This alarm output when the "TrackUserChange"
system function is triggered.
--
260003 The user has logged off from the system. --
260004 The user name entered into the user view
already exists in the user management.
Select another user name because user names have
to be unique in the user management.
260005 The entry is discarded. Enter a shorter user name.
260006 The entry is discarded. Use a shorter or longer password.
260007 The logoff time entered is outside the valid range
from 0 to 60 minutes.
The new value entered is discarded and the
original value is retained.
Enter a logon timeout value between 0 and 60
minutes.
260008 An attempt was made in WinCC to read a
PTProRun.pwl file created with ProTool V 6.0.
Reading of the file was canceled due to
incompatibility of the format.
--
260009 You have attempted to delete the user "Admin"
or "PLC User". These users are fixed
components of the user management and
cannot be deleted.
If you need to delete a user, because perhaps you
have exceeded the maximum number permitted,
delete another user.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1064 System Manual, 08/2011,
Number Effect/causes Remedy
260012 The password entries in the "Change Password"
dialog and in the confirmation field do not match.
The password is not changed. User will be
logged off.
You have to log on to the system again. Then enter
the identical password twice to be able to change the
password.
260013 The password entered in the "Change
Password" dialog is invalid because it is already
in use.
The password is not changed. User will be
logged off.
You have to log on to the system again. Then enter a
new password that has not been used before.
260014 You have tried to log on with an incorrect
password three times in a row.
You will be locked out and assigned to group no.
0.
You can log on to the system with your correct
password. Only an administrator can change the
assignment to a group.
260024 The password you entered does not meet the
necessary security guidelines.
Enter a password that contains at least one number.
260025 The password you entered does not meet the
necessary security guidelines.
Enter a password that contains at least one special
character.
260028 Upon system start-up, an attempt to log on, or
when trying to change the password of a
SIMATIC log-on user, the system attempts to
access the SIMATIC Logon Server.
If attempting to log on, the new user is not logged
in. If a different user was logged on before, then
this user is logged off.
Check the connection to the SIMATIC Logon Server
and its configuration; for example:
1. Port number
2. IP address
3. Server name
4. Functional transfer cable
Or use a local user.
260030 The SIMATIC Logon user could not change his
password on the SIMATIC Logon Server. The
new password is possibly noncompliant with
password rules set on the server, or the user is
not authorized to change his password.
The old password remains and the user is
logged off.
Log in again and choose a different password. Check
the password rules on the SIMATIC Logon Server.
260033 The action change password or log on user
could not be carried out.
Check the connection to the SIMATIC Logon Server
and its configuration; for example:
1. Port number
2. IP address
3. Server name
4. Functional transfer cable
Or use a local user.
260034 The last logon operation has not yet ended. A
user action or a logon dialog can therefore not
be called.
The logon dialog is not opened. The user action
is not executed.
Wait until the logon operation is complete.
260035 The last attempt to change the password was
not completed. A user action or a logon dialog
can therefore not be called.
The logon dialog is not opened. The user action
is not executed.
Wait until the procedure is complete.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1065
Number Effect/causes Remedy
260036 There are insufficient licenses on the SIMATIC
Logon Sever. The logon is not authorized.
Check the licensing on the SIMATIC Logon Server.
260037 There is no license on the SIMATIC Logon
Sever. A logon is not possible.
It is not possible to log on via the SIMATIC Logon
Server, only via a local user.
Check the licensing on the SIMATIC Logon Server.
260040 The system attempts to access the SIMATIC
Logon Server upon system start-up or when
trying to change the password.
If attempting to log on, the new user is not logged
in. If a different user was logged on before, then
this user is logged off.
Check connection to the domain and its configuration
in the Runtime security settings editor.
Or use a local user.
260043 It was not possible to log the user on to the
SIMATIC Logon Server. The user name or the
password could be incorrect or the user does not
have sufficient rights to log on.
The new user is not logged in. If a different user
was logged on before, then this user is logged
off.
Try again. If necessary, check the password data on
the SIMATIC Logon Server.
260044 It was not possible to log the user on to the
SIMATIC Logon Server as his account is
blocked.
The new user is not logged in. If a different user
was logged on before, then this user is logged
off.
Check the user data on the SIMATIC Logon Server.
260045 The SIMATIC Logon user is not associated to
any or several groups.
The new user is not logged in. If a different user
was logged on before, then this user is logged
off.
Check user data on the SIMATIC Logon Server and
the configuration in your WinCC project. A user may
only be assigned to one group.
270000 - System alarms
270000 - System Alarms
Number Effect/causes Remedy
270000 The alarm does not indicate the tag because it
is accessing an invalid address in the PLC.
Check whether the data area for the tag exists on the
PLC, whether the configured address is correct, and
whether the value range for the tag is correct.
270001 There is a device-specific limit as to how many
alarms may be queued for viewing (see the
operating instructions). This limit has been
exceeded.
The view no longer contains all the alarms.
However, all alarms are written to the alarm
buffer.
--
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1066 System Manual, 08/2011,
Number Effect/causes Remedy
270002 The view shows alarms of a log for which there
is no data in the current project.
Placeholders are output for the alarms.
Delete old log data, if necessary.
270003 The service cannot be set up because too many
devices want to access this service.
A maximum of four devices can execute this
action.
Reduce the number of HMI devices which want to use
the service.
270004 Access to the persistent alarm buffer is not
possible. Alarms cannot be restored or backed
up.
If the problems persist at the next restart, contact
Customer Support (delete Flash).
270005 Persistent alarm buffer corrupted: Alarms
cannot be restored.
If the problems persist at the next restart, contact
Customer Support (delete Flash).
270006 Project modified: Alarms cannot be restored
from the persistent alarm buffer.
The project was compiled and downloaded again to
the HMI device. The error should no longer occur at
the next restart of the HMI device.
270007 A configuration problem is preventing you from
the restoring the data (e.g. a DLL was deleted,
or unknown directory).
Update the operating system and download your
project again to the HMI device.
290000 - Recipe system alarms
290000 - Recipe system alarms
Number Effect/causes Remedy
290000 The recipe tag could not be read or written. It is
assigned the start value.
The alarm can be entered in the alarm buffer for
up to four more faulty tags. After that, alarm
290003 is output.
Check the configuration to see whether the address
has been set up in the PLC.
290001 An attempt was made to assign the recipe tag a
value that is outside the valid range of values for
this type.
The alarm can be entered in the alarm buffer for
up to four more faulty tags if necessary. After
that, alarm 290004 is output.
Observe the range of values for the tag type.
290002 It is not possible to convert a value from a source
format to a target format.
The alarm can be entered in the alarm buffer for
up to four more faulty recipe tags if necessary.
After that, alarm 290005 is output.
Check the range of values or type of the tag.
290003 This alarm is output after alarm 290000 was
triggered more than five times.
In this case, no further separate alarms are
generated.
Check the configuration to see whether the tag
addresses have been set up in the PLC.
290004 This alarm is output after alarm 290001 was
triggered more than five times.
In this case, no further separate alarms are
generated.
Observe the range of values for the tag type.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1067
Number Effect/causes Remedy
290005 This alarm is output after alarm 290002 was
triggered more than five times.
In this case, no further separate alarms are
generated.
Check the range of values or type of the tag.
290006 The limits configured for the tag have been
exceeded by the values entered.
Observe the configured or current tag limits.
290007 There is a difference between the source and
target structure in the recipe currently being
processed. The target structure contains an
additional recipe tag that is not available in the
source structure.
The recipe tag specified is assigned its start
value.
Insert the specified recipe tag into the source
structure.
290008 There is a difference between the source and
target structure in the recipe currently being
processed.The source structure contains an
additional recipe tag that is not available in the
target structure and cannot be assigned.
The value is discarded.
Remove the specified recipe tag in the specified
recipe from the project.
290010 The storage location configured for the recipe is
invalid.
Possible causes:
Invalid characters, write protection, data carrier
out of space or not available.
Check the configured storage location.
290011 A data record of the specified number does not
exist.
Check the source for the number (constant or tag
value).
290012 A recipe of the specified number does not exist. Check the source for the number (constant or tag
value).
290013 An attempt was made to save a data record
under a data record number that already exists.
The operation is not executed.
The following remedies are available:
Check the source for the number (constant or tag
value).
First, delete the data record.
Modify the "Overwrite" function parameter.
290014 The specified import file was not found. Check the following:
The file name
Ensure that the file is in the specified directory.
290020 Check back to verify that the download of data
records from the HMI device to the PLC has
started.
--
290021 Check back to verify that the download of
records from the HMI device to the PLC was
completed.
--
290022 Check back to indicate that the download of data
records from the HMI device to the PLC was
canceled due to an error.
Check the following conditions in the configuration:
Are the tag addresses configured in the PLC?
Does the recipe number exist?
Does the data record number exist?
Is the "Overwrite" function parameter set?
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1068 System Manual, 08/2011,
Number Effect/causes Remedy
290023 Check back to verify that the download of data
records from the PLC to the HMI device has
started.
--
290024 Check back to verify that the download of data
records from the PLC to the HMI device was
completed.
---
290025 Check back to indicate that the download of data
records from the PLC to the HMI device was
canceled due to an error.
Check the following conditions in the configuration:
Are the tag addresses configured in the PLC?
Does the recipe number exist?
Does the data record number exist?
Is the "Overwrite" function parameter set?
290026 An attempt was made to read/write a data record
that is not free at present.
This error can occur if recipes were configured
for download with synchronization.
Set the mailbox status to zero.
290027 Unable to connect to the PLC at present. As a
result, the data record cannot be read or written.
Possible causes:
No hardware connection to the PLC (no cable
plugged in, cable is defect), or the PLC is
switched off.
Check the connection to the PLC.
290030 This alarm is output after you selected screen
which contains a recipe view in which a data
record is already selected.
Reload the data record from the storage location, or
retain the current values.
290031 While saving, it was detected that a data record
with the specified number already exists.
Overwrite the data record, or cancel the action.
290032 During the export of data records, a file with the
specified name was found.
Overwrite the file, or cancel the process.
290033 Confirmation prompt before deleting data
records.
--
290040 A data record error with error code %1 that
cannot be described in more detail occurred.
The action is canceled.
It is possible that the mailbox was not installed
correctly on the PLC.
Check the storage location, the data record, the "Data
record" area pointer, and the connection to the PLC.
Restart the action after a short waiting time.
If the error persists, contact Customer Support.
Forward the relevant error code to Customer Support.
290041 A data record or file cannot be saved because
the storage location is out of sufficient space.
Delete files no longer required.
290042 An attempt was made to execute several recipe
actions simultaneously. The last action is not
executed.
Retrigger the action after a short waiting time.
290043 Confirmation prompt before saving data records. --
290044 The database for the recipe was corrupted and
will be deleted.
--
290050 A check back indicates that the export of data
records was started.
--
290051 A check back indicates successful completion of
the export of data records.
--
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1069
Number Effect/causes Remedy
290052 A check back indicates that the export of data
records was canceled due to an error.
Ensure that the structure of the data records at the
storage location and the current recipe structure on
the HMI device are identical.
290053 A check back indicates that the import of records
was started.
--
290054 A check back indicates successful completion of
the import of data records.
--
290055 A check back indicates that the import of data
records was canceled due to an error.
Ensure that the structure of the data records at the
storage location and the current recipe structure on
the HMI device are identical.
290056 Error when reading/writing the value in the
specified row/column.
The action was canceled.
Check the specified row/column.
290057 The tags of the recipe specified were toggled
from "offline" to "online" mode.
Each change of a tag in this recipe is now
immediately transferred to the PLC.
--
290058 The tags of the specified recipe were toggled
from "online" to "offline" mode.
Modifications to tags in this recipe are no longer
immediately transferred to the PLC but must be
transferred there explicitly by downloading a
data record.
--
290059 A check back indicates that the specified record
was successfully saved.
--
290060 A check back indicates that the specified data
record memory was cleared.
--
290061 A check back indicates that deletion of the data
record memory was canceled due to an error.
--
290062 The data record number exceeds the maximum
of 65536.
This data record cannot be created.
Select another number.
290063 This occurs when you execute system function
"ExportDataRecords" while the "Overwrite"
parameter is set to "No".
An attempt was made to save a recipe under a
file name that already exists.
The export is canceled.
Check the parameters of the "ExportDataRecords"
system function.
290064 A check back indicates that the deletion of data
records was started.
--
290065 A check back indicates successful completion of
the deletion of data records.
--
290066 Confirmation prompt before deleting data
records.
--
290068 Confirmation prompt for deletion of all recipe
data records.
--
290069 Confirmation prompt for deletion of all recipe
data records.
--
290070 The data record specified was not found in the
import file.
Check the source of the data record number, or the
data record name (constant, or tag value).
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1070 System Manual, 08/2011,
Number Effect/causes Remedy
290071 When the editing data record values, you
entered a value that is below the low limit of the
recipe tag.
The entry is discarded.
Enter a value within the recipe tag limits.
290072 When editing data record values, you entered a
value that exceeds the high limit of the recipe tag.
The entry is discarded.
Enter a value within the recipe tag limits.
290073 An action (e.g. saving a record) failed for an
unknown reason.
The error corresponds to status alarm
IDS_OUT_CMD_EXE_ERR in the large recipe
view.
--
290074 While saving, a data record with the specified
number but with different name was found.
Overwrite the record, change the record number or
cancel the action.
290075 A data record of this name already exists.
The data record is not saved.
Select a different data record name.
290110 The default values could not be set due to an
error.
--
290111 The recipes subsystem cannot be used. Recipe
views have no content and recipe-specific
functions will not be executed.
Possible causes:
Error when loading the recipes.
The recipe structure was changed in the ES.
The recipes were not included in the latest
project download. This means that the new
configuration data no longer matches the old
recipes on the device.
Download the project to the device again, including
the recipes (the corresponding check box in the
download dialog must be check marked).
300000 - Alarm_S alarms
300000 - Alarm_S alarms
Number Effect/causes Remedy
300000 Faulty configuration of process monitoring (e.g.
using PDiag or S7 Graph): More alarms are
queued than specified in the specifications of the
CPU. No further ALARM_S alarms can be
managed by the PLC and reported to the HMI
devices.
Change the PLC configuration.
300001 ALARM_S is not registered on this PLC. Select a controller that supports the ALARM_S
service.
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1071
310000 - Reporting alarms
310000 - Reporting alarms
Number Effect/causes Remedy
310000 An attempt is being made to print too many
reports in parallel.
Only one log file can be output to the printer at
a given time; the print job is therefore rejected.
Wait until the previous active log was printed.
Repeat the print job if necessary.
310001 An error occurred on triggering the printer. The
report is either not printed or printed with errors.
Evaluate the additional system alarms related to this
alarm.
Repeat the print job if necessary.
330000 - Interaction alarms
330000 - Interaction alarms
Number Effect/causes Remedy
330022 Too many open dialogs on the HMI device. Close all dialogs you do not require on the HMI device.
350000 - PROFIsafe alarms
350000 - PROFIsafe alarms
Number Effect/causes Remedy
350000 PROFIsafe packets were not received within the
specified time.
There is a communication problem with the F-
CPU.
RT is terminated.
Check the WLAN connection.
350001 PROFIsafe packets were not received within the
specified time.
There is a communication problem with the F-
CPU.
The PROFIsafe connection is set up again.
Check the WLAN connection.
350002 Internal error.
Runtime is terminated.
Internal error
350003 Check back for indicating the connection setup
to the F-CPU.
The Emergency-Off buttons are active
immediately.
--
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
1072 System Manual, 08/2011,
Number Effect/causes Remedy
350004 PROFIsafe communication was set up and the
connection was shut down.
Runtime can be terminated.
The Emergency-Off buttons are deactivated
immediately.
--
350005 Incorrect address configured for the F-Device.
A PROFIsafe connection cannot be set up.
Check and modify the address of the F-Device in
WinCC ES.
350006 The project was started. At the start of the
project, check the proper function of the ACK
buttons.
Press the two ACK buttons successively in the
"Acknowledge" and "Panic" positions.
350008 You configured an incorrect number of failsafe
buttons.
A PROFIsafe connection cannot be set up.
Modify the number of failsafe buttons in the project.
350009 The device is in Override mode.
It may no longer be possible to detect the
location because transponder detection fails.
Exit the override mode.
350010 Internal error: The device has no failsafe buttons. Return the device to Siemens.
Worldwide contact partners
Visualizing processes (Advanced)
9.3 Working with alarms
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1073
9.4 Working with logs
9.4.1 Working with logs for Runtime Advanced and Panels
9.4.1.1 Log Basics
Introduction
WinCC provides the following types of log for logging process data for HMI Runtime:
Data logs
Alarm logs
A data log is used to log process data from an industrial plant.
An alarm log is used to log alarms that occur in the monitored process.
Principle
The two types of log both have roughly the same structure and largely work in the same way.
They are very clear and easy to configure. With both types of log you define the same properties
for the log. The same logging methods are also available for both types of log.
The following logging methods are available:
Circular log
If a circular log is totally full, the oldest entries are overwritten.
Segmented circular log
In a segmented circular log, multiple single logs of the same size are filled in succession.
When all log segments are filled, the oldest log segment is overwritten.
Log with level-dependent system alarm
A system alarm is triggered when a defined level is reached.
Log with level-dependent triggering of an event
The "Overflow" event is triggered when the log is full. The "Overflow" event triggers a system
function.
9.4.1.2 Properties of Logs
Introduction
You define the properties of a data log in the "Data logs" editor.
You define the properties of an alarm log in the "Alarm log" editor.
The properties of the data log and alarm log are configured in the same way. You configure
the properties either directly in the table of the respective editor or in the log properties of the
Inspector window.
Visualizing processes (Advanced)
9.4 Working with logs
WinCC Advanced V11.0 SP1
1074 System Manual, 08/2011,
General properties
Name
You can assign any name to the log. The name must contain at least one letter or one
number.
Storage location
The log is stored in a file or a database. You can only save to a database on a PC. Select
"File" or "Database" as the storage location.
You can specify a folder on the local PC hard disk or a folder on a network drive as the
storage location, depending on how the HMI device is configured. The following storage
locations are available for an HMI device:
Memory card
USB storage medium
Network drive
The selection available depends on the HMI device in use.
Size
The size of a log depends on the type of log and the selected settings.
Size of a data log
The size of a data log is calculated as follows:
The number of items * the length of each tag value to be logged.
In the "Properties" window, the maximum size that the log accepts for retention of the
currently selected number of data records is displayed in the input field "Number of data
records". The maximum log size is limited by the volume of the storage medium.
Size of an alarm log
The size of an alarm log is calculated from the number of data records and the
approximate size of an entry. The size of an entry depends on whether the alarm text
and the associated tag values are to be logged as well.
Restart characteristics
Under Restart characteristics you can specify that the logging starts when Runtime starts.
Check the "Enable logging at runtime start" check box.
You can also control the behavior when Runtime starts. Enable "Reset log" if you want to
overwrite existing logged data with the new data. Select the "Append data to existing log"
option if you want to retain the existing logged data. This setting adds the data to be logged
to an existing log.
See "Auto-Hotspot" and "Auto-Hotspot" for more details.
Note
You can use system functions to control the restarting of a log in Runtime.
Visualizing processes (Advanced)
9.4 Working with logs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1075
9.5 Working with recipes
9.5.1 Basics
9.5.1.1 Definition and applications
Introduction
Recipes are collections of related data, for example, machine parameterizations or production
data.
NOTICE
Restrictions for recipes
Recipes are not available on the HMI device OP 73:
Examples:
Machine parameter settings that are needed to convert production to a different product
variant.
Product components that result in different compositions for different end products.
A recipe has a fixed data structure. The structure of a recipe is defined during configuration.
A recipe contains recipe data records. These differ in terms of their values, but not their
structure.
Recipes are stored on the HMI device or on an external storage medium. Recipe data records
are always transferred complete and in a single pass between the HMI device and the PLC.
In addition, production data can be imported in runtime, in the form of a CSV file.
NOTICE
Restrictions for Import / Export
It is not possible to export or import the recipes for the following HMI devices:
Basic Panels
OP 77A
OP 177A
TP 177A (Portrait)
Complete recipe data, but not single recipe data records, can be exported and imported using
ProSave in CSV format and transferred to the HMI device. Thereby, Runtime is interrupted.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1076 System Manual, 08/2011,
Using recipes
Recipes can be used in the following situations:
Manual production
You select the required recipe data and display it on the HMI device. You modify the recipe
data as required and save it on the HMI device. You transfer the recipe data to the PLC.
Automatic production
The control program starts transfer of the recipe data between the PLC and HMI device.
You can also start the transfer from the HMI device. Production is then implemented
automatically. It is not essential to display or modify the data.
Teach-in mode
You optimize production data that was optimized manually on the system, e.g. axis positions
or filling volumes. The values thus determined are transferred to the HMI device and saved
in a recipe data record. You can then transfer the saved recipe data back to the PLC at a
later date.
Entering and modifying the recipe data
You enter the data in the individual recipe data records and modify it as required. The following
options are available:
Data entry during configuration
If the production data exists already, you enter the data in the "Recipes" editor during recipe
configuration.
Entering the data in Runtime
If you have to frequently modify production data, you can do this directly in Runtime as
follows:
Enter the data directly on the HMI device.
Set the parameters directly on the machine. You then transfer the data from the PLC to
the HMI device and save it in the recipe.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1077
9.5.1.2 Examples for using recipes
Recipes are used in the manufacturing industry and mechanical engineering, for example. The
following recipes show typical applications which you can implement with the recipe function
of WinCC:
Machine parameter assignment
One field of application for recipes is the assignment of machine parameters in the
manufacturing industry: A machine cuts wooden boards to a certain size and drills holes.
The guide rails and drill have to be moved to new positions according to the board size.
The required position data are stored as data records in a recipe. You reassign the machine
parameters using "Teach in" mode if, for example, a new board size is to be processed.
You transfer the new position data directly from the PLC to the HMI device and save it as
a new data record.
Batch production
Batch production in the food processing industry represents another field of application for
recipes: A filling station in a fruit juice plant produces juice, nectar, and fruit drinks in a
variety of flavors. The ingredients are always the same, differing only in their mixing ratios.
Each flavor corresponds to a recipe. Each mixing ratio corresponds to a data record. All of
the required data for a mixing ratio can be transferred to the machine control at the touch
of a button.
9.5.1.3 Recipe structure
Introduction
The basic structure of a recipe is illustrated with reference to the filling station in a fruit juice
plant.
There may be several different recipes in an HMI device. A recipe can be compared to an
index card box that contains several index cards. The index card box contains several variants
for manufacturing a product family. All the data for each manufacturing variant is contained on
a single index card.
Example:
In a soft drinks production plant, a recipe is needed for different flavors. Drink variants include
fruit juice drink, juice and nectar.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1078 System Manual, 08/2011,
Recipe
The recipe contains all the recipe data records for the different drink variants.
5
30
23
80
15
35
20
70
Juice
Recipe
Water:
Flavor:
Sugar:
Concentrate:
Water:
Sugar:
Flavor:
Concentrate:
Nectar
Recipe data record
Recipe element
Recipe data records
Each index card represents a recipe data record needed to manufacture a product variant.
Recipe entries
Each index card in a drawer has the same structure. All the index cards contain fields for the
different ingredients. Each field corresponds to a recipe entry. All the records of a recipe thus
contain the same entries. The records differ, however, in the value of the individual entries.
Example:
All the drinks contain the following ingredients:
Water
Concentrate
Sugar
Flavoring
The records for juice drink, fruit juice or nectar differ, however, in the quantity of sugar used
in production.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1079
9.5.1.4 Display of recipes
Introduction
You can display recipes in the following ways:
Recipe view
Recipe screen
Input in the recipe view and recipe screen
You change the values of a recipe in the recipe screen or recipe view and thus modify the
manufacturing process or a machine.
The recipe view and recipe screen can perform the same functions when using recipes. They
differ in the following respects:
Display options
Operation
Possibility of transferring data between the PLC and the HMI device
Recipe view
The recipe view is suitable for viewing simple recipes.
The recipe view is an off-the-shelf WinCC display and operator control object for managing
recipe data records. The recipe view is always part of a screen. The recipe view shows recipe
data records in tabular form. You adapt the appearance and the possible operations to suit
your specific needs.
If you are editing recipes with a recipe view in your project, the values are saved in recipe data
records. The values are not transferred between the HMI device and PLC until you use the
relevant operator control object.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1080 System Manual, 08/2011,
Recipe screen
The recipe screen is an individual screen that contains:
Input fields for recipe variables
Operator control objects for using the recipes, e.g. "SaveDataRecord"
Water
Concentrate
Sugar
Flavoring
Recipe name:
Data record name:
No.:
No.:
Save
Load
Data from the PLC
Data to PLC
Orange
Nectar
1
2
40
70
30
30
l
l
kg
l
The recipe screen is suitable in the following situations:
Large recipes
Allocation of recipe fields to the graphic display of the relevant plant area
Breakdown of the recipe data into several screens
Note
The values of recipe variables are transferred between the PLC and recipe screen at the
following times depending on the configuration:
Immediately after modification
When a relevant operator control object is used
Synchronizing recipe view and recipe screen
There may be differences in Runtime between the values displayed in the recipe view and the
values saved in the associated tags when you edit recipes in both a recipe view and a recipe
screen. To prevent this, you must synchronize the recipe data record values with the values
of the recipe tags.
A complete recipe data record will always be saved or synchronized.
Note
Recipe tags can only be synchronized in the advanced recipe view. Synchronization only
takes place if the "Synchronize recipe view and recipe tags" setting is activated for the recipe.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1081
9.5.1.5 Transferring recipe data records
Flow of data in recipes
The following picture illustrates the flow of data in recipes:
PLC
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
Recipe view
Recipe
screen
Recipe tag
External
storage medium
Teach-in mode
Synchronizing
Interaction between the components
There is interaction between the following components at runtime:
Recipe view / recipe screen
On the HMI device, recipes are displayed and edited in the recipe view or in a recipe screen:
The recipe data records from the internal memory of the HMI device are displayed and
edited in the recipe view.
The values of the recipe tags are displayed and edited in the recipe screen.
You synchronize the values displayed in the recipe view with the values of recipe tags
according to the configuration.
HMI device recipe memory
Recipes are saved in the form of recipe data records in the HMI device's recipe memory.
Recipe tags
The recipe tags contain recipe data. When you edit recipes in a recipe screen, the recipe
values are stored in recipe tags. The point at which the values of the recipe tags are
exchanged with the PLC depends on the configuration.
Note
You can synchronize the recipe tags with the recipe data records so that the same values
are saved in both.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1082 System Manual, 08/2011,
Loading and saving recipe data
Complete recipe data records are loaded from or saved to the recipe memory on the HMI
device in the recipe view.
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
Recipe view
Recipe
screen
Recipe tag
Synchronizing
The values of the recipe data record are loaded from the recipe memory to the recipe tags in
the recipe screen. When they are saved, the values of the recipe tags are saved to a recipe
data record in the recipe memory.
Transferring the recipe values between the HMI device and the PLC
Complete recipe data records are transferred between the recipe view and PLC.
PLC
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
Recipe view
Recipe
screen
Recipe tag
Synchronizing
Teach-in mode
The following transfers are possible between the recipe screen and PLC, depending on the
configuration:
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1083
Transferring recipe data records between recipe view and recipe tags
Immediate transfer of individual modified values between the recipe tags and PLC. The
following settings are needed in the recipe in order to do this:
"Synchronizing recipe view and recipe tags" is activated.
"Manual transfer of individual modified values (teach-in mode)" is deactivated.
Recipe data records can be transferred directly between the HMI device and PLC. In these
situations, the display on the HMI device is not essential.
Exporting and importing recipe data records
Recipe data records are exported from the HMI device recipe memory and are saved to a CSV
file on the external storage medium. The records can be reimported from the storage medium
to the recipe memory.
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
External
storage medium
The following external storage media may be used, depending on the HMI device:
No storage medium, for example, for basic panels
Memory card
USB stick
Hard disk
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1084 System Manual, 08/2011,
9.5.1.6 Configuration of recipes
Introduction
Recipes are configured differently according to the intended use:
If you are editing recipes with a recipe view in your project, the values are only saved in
recipe data records.
If you are editing recipes in a recipe screen in your project, the values are saved in recipe
tags.
The following possible settings determine how the recipe data records, recipe tags and PLC
all interact.
"Synchronizing recipe view and recipe tags" deactivated
The data in a data record is only displayed and can only be edited in the recipe view. If you
use data outside the recipe view, they are not synchronized with the recipe view.
"Synchronizing recipe view and recipe tags" activated
There may be differences in Runtime between the values displayed in the recipe view and the
values saved in the associated tags when you edit recipes in both a recipe view and a recipe
screen. To prevent this, you must synchronize the recipe data record values with the values
of the recipe tags.
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
PLC
Recipe view
Recipe
screen
Recipe tag
Synchronizing
Teach-in mode
Note
Recipe tags can only be synchronized in the advanced recipe view.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1085
The values of the recipe view and the associated recipe tags are not synchronized
automatically. The recipe tags and the recipe view are not synchronized until you use the
operating element with the "RecipeViewSynchronizeDataRecordWithTags" function.
"Synchronize recipe view and recipe tags" activated and "Manual transfer of individual modified values
(teach-in mode)" activated
With this setting, modified recipe values are not synchronized immediately between the recipe
tags in the recipe screen of the HMI device,and PLC.
There must be an operating element with the "SetDataRecordToPLC" and
"GetDataRecordFromPLC" functions present in order to synchronize the values.
If recipe values are changed in the controller, the modified values are displayed immediately
in the recipe screen if you use the operating element with the "GetDataRecordFromPLC"
function.
"Synchronize recipe view and recipe tags" activated and "Manual transfer of individual modified values
(teach-in mode)" deactivated
With this setting, modified recipe values are synchronized immediately between the recipe
tags on the HMI device and PLC.
When you change recipe values in the recipe screen, these changes are applied immediately
by the PLC and immediately influence the process.
If recipe values are changed in the PLC, the changed values are displayed immediately in the
recipe screen.
9.5.1.7 Special features of some devices
PLC
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
Recipe view
Recipe tag
Synchronizing
Teach-in mode
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1086 System Manual, 08/2011,
Basic panels, OP 77A, TP 177A and TP 177A (Portrait) respond differently to the other HMI
devices in the following respects:
Only the simple recipe view is supported.
Recipe tags are always synchronized with the recipe view (see figure above): When the
operator changes a value of the recipe element in recipe view, the value of the associated
recipe tag will also change.
Recipe tags are not automatically transferred between the PLC and HMI device when they
are modified. Recipe tags are always transferred manually in teach-in mode.
There must be an operator control object with the "SetDataRecordToPLC" and
"GetDataRecordFromPLC" functions present in order to synchronize the values with the
PLC.
NOTICE
Restrictions for recipe tags
Generally, in Basic Panels and OP77A, TP177A (Portrait) recipe tags cannot be used,
except in a recipe.
NOTICE
Restrictions for Import / Export
It is not possible to export or import the recipes for the following HMI devices:
Basic Panels
OP 77A
OP 177A
TP 177A (Portrait)
Complete recipe data, but not single recipe data records, can be exported and imported
using ProSave in CSV format and transferred to the HMI device. Thereby, Runtime is
interrupted.
CAUTION
Data loss with several recipe views in the screen
Applies only to Basic Panels, OP73, OP77A, TP177A and TP177A (Portrait): If two or
more recipe views show the same recipe in a screen, you have a conflict when accessing
the data.
The result is data loss and unpredictable status of recipe data.
Make sure the operators do not select and edit the same recipe in different recipe views.
Display only one recipe in a recipe view.
Display a different recipe in each recipe view.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1087
Interaction between the components
There is interaction between the following components at runtime:
Recipe view
Recipes are displayed and edited in the recipe view on the HMI device.
The recipe data records from the internal memory of the HMI device are displayed and
edited in the recipe view.
HMI device recipe memory
Recipes are saved in the form of recipe data records in the HMI device's recipe memory.
Recipe tags
The recipe tags contain the values of recipe elements.
9.5.1.8 Synchronization of recipe data records with the PLC
Overview
When recipe data records are transferred between the HMI device and PLC, both
communication peers access common communication areas on the other peer.
Recipe data records are always transferred directly. The values of the tags are written directly
to or read directly from the configured addresses without being placed on the clipboard.
Data transfer types
There are two ways to transfer recipe data records between the HMI device and PLC:
Transfer without coordination
Coordinated transfer via the "Data record" area pointer.
Note
Coordinated transfer
Transfer with coordinated transfer is used to prevent the uncontrolled overwriting of data
in either direction in your control program.
Requirements for coordinated transfer
The following requirements apply to coordinated transfer:
The "Data record" area pointer must be set up for the required connection in the
"Communication > Connections" editor.
In the properties of the recipe "Coordinated transfer of data records" is activated.
The connection to the PLC is specified in the properties of the recipe with which the HMI
device coordinates the transfer.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1088 System Manual, 08/2011,
Coordinated transfer
In the case of coordinated transfer, both the PLC and the HMI device set the status bits in the
shared data compartment.
Coordinated transfer of recipe data records can be a useful solution in the following cases:
The PLC is the "active partner" for the transfer of recipe data records.
The PLC evaluates information about the recipe number and name, as well as the recipe
data record number and name.
The transfer of recipe data records is started by the following PLC jobs:
"Set_data_record_in_PLC"
"Get_data_record_from_PLC"
9.5.1.9 "Recipes" editor
Introduction
You can create, configure and edit recipes, recipe entries and recipe data records in the
"Recipes" editor. The "Recipes" editor also allows you to enter values in recipe data records.
Structure of the "Recipes" editor
You create recipes in the top part of the table editor. You can also configure them there or in
the Inspector window.
The bottom part of the table editor has the following tabs:
Elements
Define the recipe elements of the selected recipe using the table cells provided here. You
can move recipe elements within the table with the shortcut menu commands, "Up" and
"Down".
Data records
Define the values of the data records of the selected recipe using the table cells provided
here.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1089
You can then configure the selected recipe, the recipe element or the recipe data record in the
Inspector window. You will find further notes on configuring the components of a recipe under
"Configuring Recipes".
Recipe settings
The following settings are available for recipes:
Setting Description
Name of the recipe This is a unique identification for the recipe within the HMI device.
Display name Appears in the recipe view, for example, in Runtime. You can configure
display names in multiple languages. Assign descriptive names or
designations which the operator can associate directly with a recipe, e.g. "fruit
juice drink".
Recipe number This is a unique identification for the recipe within the HMI device.
Version Information about the recipe. The date and time of the last change to the
recipe is set by default.
Path Defines the storage location for recipes. The recipes are stored as a file.
Size type [fixed] The recipe data records are limited to a predetermined number by default.
Number of data
records [fixed]
Maximum number of data records in a recipe in Runtime. The number is
limited by the recipe memory of the HMI device.
Communication type
[fixed]
The recipe data records are written directly to the addresses of the recipe
tags and read from there.
Tooltip Tooltip for the recipe which is shown to the operator in Runtime.
NOTICE
Path
The storage location depends on the storage media available on the HMI device.
Basic Panels and OP77A, TP177A (Portrait)
These HMI devices have no external memory. Recipes are always saved in the internal Flash
memory. The "Path" setting is therefore not available.
Recipe element settings
You can make the following settings on the "Elements" tab:
Setting Description
Name of the recipe element Identifies a recipe element uniquely within the recipe. Enter meaningful
names or labels that you can allocate uniquely, such as axis labels on
a machine or ingredients such as "Flavoring".
Display name Appears in the recipe view, for example, in Runtime. You can configure
display names in multiple languages. Assign meaningful names or
designations which the operator can associate directly, e.g. "fruit juice
flavoring".
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1090 System Manual, 08/2011,
Setting Description
Recipe tag An assigned tag in Runtime stores the current value of the recipe
element in the recipe data record.
Data type Data type of the recipe tag.
Data length [fixed] Data length of the recipe tag, depending on the data type.
Text list Text is assigned to a value or range of values in a text list. You can
display this text in an output field, for example.
The assigned recipe tag must have the data type of a number. The tag
value must be within the range of values of the text list.
Default value This is used as the default entry when you create a new recipe data
record.
Minimum value [fixed] The smallest representable value of a number-based recipe tag,
depending on the type of data.
Maximum value [fixed] The largest representable value of a number-based recipe tag,
depending on the type of data.
Decimal places Determines how many places a decimal number is rounded to, e.g. 3
decimal places and vice versa by what power of ten an integer value
is multiplied, e.g. 1,000.
Tooltip Tooltip about the recipe element which is shown to the operator in
Runtime.
Recipe data record settings
You can make the following settings on the "Data records" tab:
Setting Description
Name of the recipe data
record
Identifies a recipe data record uniquely within the recipe.
Display name Appears in the recipe view, for example, in Runtime. You can configure
display names in multiple languages. Assign meaningful names or
product numbers which the operator can associate directly with a
product, e.g. "yellow fruit juice E231".
Recipe data record number Identifies a recipe data record uniquely within the recipe.
Recipe elements 1 to n You can store various values for each recipe element even during
configuration. Together with the values of the other recipe elements, a
value always forms a recipe data record. You can store multiple recipe
data records.
If enabled in the transfer settings, the recipe data records are
transferred to the HMI device when downloading the project and
existing data records on the HMI device are overwritten.
Comment Comment about the recipe data record
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1091
9.5.2 Displaying and Editing Recipes in Runtime
9.5.2.1 Recipe screen and recipe view
You can display and edit recipes on the HMI device with a recipe view or recipe screen.
Recipe view
The recipe view is an off-the-shelf WinCC display and operator control object.
The recipe view is available in the following views:
As anvanced recipe view
As simple recipe view
NOTICE
Availability
In basic panels and OP77A, TP177A, only the simple recipe view is available.
Recipe screen
The recipe screen contains an individual screen form for entering the recipes. The screen form
contains I/O fields and other display and operator control objects. The recipe functionality is
implemented with system functions, e.g. for saving recipe data records.
NOTICE
Availability
In basic panels and OP73, OP77A, TP177A (Portrait), the recipe screens are not available.
9.5.2.2 Simple recipe view
Recipe view
The simple recipe view is a ready-made display element and operator control that is used to
manage recipe data records. The recipe view shows recipe data records in tabular form.
The displayed buttons and information in the columns are adjustable.
The values displayed or entered in the recipe view are saved in recipe data records. The
displayed recipe data record can be written into the PLC by buttons or values can be read in
from the PLC.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1092 System Manual, 08/2011,
Layout of the display
The simple recipe view consists of three areas:
Recipe list
Data record list
Element list
In the simple recipe view, each area is shown separately on the HMI device. Depending on
the configuration, the simple recipe view starts with the recipe list.
The figure below shows an example of the data record list.
Beverage
Juice
Nectar
1
2
3
Display of values
NOTICE
Processed recipe data record is changed in the background
Only applies for Basic Panels: if an operator has changed a recipe data record and a PLC
job wants to read or write any recipe data record of this recipe, the PLC job is stopped and
a system alarm is output. On the other hand, the changed value is displayed immediately if
only the PLC job and no operator has changed recipe data.
Does not apply for Basic Panels: If an operator has changed a recipe data record and a PLC
job has changed the values of the recipe data record concerned, the recipe view is not
updated automatically. To update the recipe view, reselect the respective recipe data record.
See also
Recipe view (Page 828)
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1093
9.5.2.3 Configuration options of the simple recipe view
The response of the simple recipe view can be defined in the recipe view inspector window.
NOTICE
Validity
Some devices, for example basic panels, only support the simple recipe view.
For all other devices, observe the following:
In the Inspector window, under "Properties > Display > Mode", select "Simple view" as
"View type".
The "Properties > Simple view" area contains additional properties only applicable to the
simple recipe view.
All other properties are also applicable to the advanced recipe view.
Displaying recipe data record values only
To display the recipe data in a recipe view for checking only, proceed as follows:
1. Deselect "Edit mode" in the "General" group.
You cannot create, rename, edit or delete recipe data.
Writing a recipe data record number or name to a tag
A tag to each recipe data record can be configured in the advanced recipe view. Depending
on the "String" or "Int" data type of the tag, the name or number of the recipe data record is
stored in the tag. Conversely, the tag can also be used to select a recipe data record by entering
the corresponding value. For example, the tag can be transferred as a parameter for a system
function.
Proceed as follows:
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1094 System Manual, 08/2011,
1. Enter a tag of the "Int" type in the field "Tag", under "Properties > General > Recipe data
record".
The number of the recipe data record is stored in a tag.
Configuring an event on the recipe view
NOTICE
Events and buttons
The "Events" register is faded out when a minimum of one button is enabled.
To configure an event for the recipe view, proceed as follows:
1. Select the recipe view that was added to the screen in the "Screens" editor.
The properties of the recipe view are shown in the Inspector window.
2. Deactivate all buttons under "Properties > Toolbar" and "Properties > Simple view".
3. In the Inspector window, under "Properties > Events", click the event to be configured, e.g.
"Enable".
4. Configure a function list for the event.
The function list is processed when the operator enables the recipe view.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1095
Animation properties of the recipe view
To configure an animation of a recipe view, proceed as follows:
1. Select the recipe view that was added to the screen in the "Screens" editor.
The properties of the recipe view are shown in the Inspector window.
2. Click under "Properties > Animations" in the Inspector window.
3. Link a tag to one or more of the following properties.
X-Position and y-Position
Design: Colors, flashing
Operability
Visibility
In the "Animations> Overview" area, all animations are summarized in tabular form.
Under "Animations> Tag links > Tag linkage", as well as visibility and position a tag can
also be linked to height and width.
NOTICE
Animations and buttons
If all buttons are not disabled, an error message appears whilst compiling the project
for windows-CE HMI devices.
Constraints on the simple recipe view
The following functions are not possible in the simple recipe view:
Synchronizing recipe view and recipe tags
Writing a recipe number / name to a tag
Display status bar
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1096 System Manual, 08/2011,
Display data record number
Display label
Display table
9.5.2.4 Advanced recipe view
Recipe view
The advanced recipe view is an off-the-shelf display and operator control object that is used
to manage recipe data records. The recipe view shows recipe data records in tabular form.
The buttons, headers and information displayed in the columns are variable.
The values displayed or entered in the recipe view are saved in recipe data records.
Layout of the display
The picture below contains an example of the advanced recipe view:
Display of values
NOTICE
Changing the recipe data record in the background
Applies to the processing of a recipe data record:
If values of the corresponding recipe data record are changed by a control job, the recipe
view is not updated automatically.
To update the recipe view, reselect the respective recipe data record.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1097
See also
Recipe view (Page 828)
9.5.2.5 Configuration options of the advanced recipe view
The response of the advanced recipe view in the recipe view inspector window can be
determined.
NOTICE
Validity
The following description also applies to the advanced recipe view. In the Inspector window,
under "Properties > Display > Mode", select "Advanced view" as "View type".
All properties described for the simple recipe view are also applicable in the advanced recipe
view, except "Properties > Simple view". The "Simple view" area contains additional
properties only applicable to the simple recipe view.
Basic Panels, OP77A and TP177A (Portrait) do not support any advanced recipe view.
Displaying a recipe
To allow access to the recipe data records of a specific recipe only in a screen, proceed as
follows:
1. Enter the recipe or select an existing recipe in the "Recipe" field, under "Properties >
General".
2. When a recipe is entered in the "Recipe" field, you will have to enable the "Selection list" if
you want to display the recipe name in Runtime.
The selected recipe appears in the recipe view.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1098 System Manual, 08/2011,
Writing a recipe number or name and recipe data record number or name to a tag
Both the recipe and the recipe data record can each be configured to a tag in the recipe view.
Depending on the "String" or "Int" data type of the tag, the name or number of the recipe or
recipe data record is stored in the tag. Conversely, the tag can be used to select the recipe or
recipe data record by entering the corresponding value. For example, the tag can be
transferred as a parameter for a system function.
Proceed as follows:
1. Enter a tag of the "String" type in the field "Recipe tag", under "Properties > General >
Recipe".
2. Enter a tag of the "Int" type in the field "Tag", under "Properties > General > Recipe data
record".
The name of the recipe and the number of the recipe data record are each stored in a tag.
Using the recipe view as a drop-down list
To use the recipe view as a selection field for recipes and recipe data records in a recipe
screen, proceed as follows:
1. Select the tag for the recipe name under "General > Recipe > Recipe tag".
2. Select the tag for the recipe data record name under "General > Recipe data record >Tag".
3. Disable the "Edit mode". You cannot create, rename, edit or delete recipe data.
4. In order to select recipes, enable "Show selection list" and make sure that no recipe is
selected under "Properties > General > Recipe".
5. Deactivate all buttons under "Properties > Toolbar".
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1099
Configuring an event on the recipe view
To configure an event on the recipe view, proceed as follows:
1. Select the recipe view that was added to the screen in the "Screens" editor.
The properties of the recipe view are shown in the Inspector window.
2. In the Inspector window, click the event you want to configure under "Properties > Events".
3. Configure a function list for the selected event.
The function list is processed when the configured event occurs.
9.5.2.6 Response of the recipe view in Runtime
Screen change
If you change to another screen and have not yet saved changes to the recipe data in the
recipe view, you will be prompted to save the recipe data. The recipe name and the name of
the recipe data record are displayed to show which recipe data have not been saved yet.
Create, change, copy or delete recipe data records
If you attempt to create a new recipe data record and a recipe data record already exists, a
system alarm will appear on screen.
Operating the recipe view with function keys
The Recipe view can be operated with function keys, e.g. if the HMI device does not have
touch functionality. You can assign functions such as "SaveDataRecord" to the function keys
on the HMI device.
Display after import of recipe data
NOTICE
Availability
Import and export of recipe data is not available for Basic Panels and OP77A, TP177A
(Portrait).
If you open the recipe view during the import of recipe data, only the recipe data that is already
completely imported will be displayed. The recipe view is not automatically updated with a data
import. In order to have a complete view of all the recipe data, do not open the recipe view
until the system prompts you that the recipe data has been imported successfully. Alternatively,
update the recipe view after successful completion of the import procedure.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1100 System Manual, 08/2011,
Updating tag for recipes and recipe data records
NOTICE
Availability
Tags for recipes and recipe data records are not available for Basic Panels and OP77A,
TP177A (Portrait).
The current recipe data record or its number can be saved to a tag, depending on the
configuration. The tag will be updated under the following conditions:
The recipe data record has been loaded.
The screen with the recipe view was not exited during loading.
This operation may take some time.
9.5.2.7 Basics on the recipe screen
Introduction
The recipe screen contains an individual screen form for entering the recipes. The screen form
contains I/O fields and other display and operator control objects. The recipe functionality is
implemented with system functions, e.g. for saving recipe data records.
The picture below contains an example of a recipe screen:
Water
Concentrate
Sugar
Flavoring
Recipe name:
Data record name:
No.:
No.:
Save
Load
Data from the PLC
Data to PLC
Orange
Nectar
1
2
40
70
30
30
l
l
kg
l
NOTICE
Availability of recipe screens
Basic Panels and OP73A, OP77A, TP177A (Portrait) do not support any recipe screens.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1101
Principle
Configuring a recipe screen allows you to customize the display. You can spread large recipes
over several screens according to topic and display them clearly using features such as
graphical display and operator control objects.
Spreading recipes over several screens according to topic
You can distribute recipe data records with multiple entries across several screens. For
example, for each plant area you can configure a screen containing the associated
screen forms for the recipe data records.
Spreading recipes over several screens is useful for HMI devices with small displays as
they avoid having to scroll through tables in Runtime.
Visual machine simulation
You can visually simulate your machine in a screen using graphical screen objects. This
enables you to display parameter settings more clearly by positioning I/O fields immediately
next to machine elements such as axes or guide rails. which produces a direct relationship
between the values and the machine.
Synchronizing recipe values
To enter recipe data record values outside the advanced recipe view in the configured I/O
fields, activate "Synchronize recipe view and recipe tags" under "Properties > Synchronization"
in the recipe properties.
The "Synchronize recipe view and recipe tags" option is not available for the simple recipe
view.
Transferring recipe values automatically
If the entered recipe values must be immediately transferred to the connected PLC in Runtime,
deactivate "Manual transfer of individual modified values (teach-in mode)" under "Properties
> Options".
Configure the "SetRecipeTags" system function if you want to enable and disable the
immediate transfer of entered recipe values in Runtime.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1102 System Manual, 08/2011,
System functions
The following system functions are available for operator control of a recipe screen:
ImportDataRecords
ExportDataRecords
LoadDataRecord
SaveDataRecord
SetDataRecordTagsToPLC
GetDataRecordTagsFromPLC
The following system functions are available for operator control of the recipe view when it is
being used in the recipe screen:
RecipeViewSaveDataRecord
RecipeViewSaveAsDataRecord
RecipeViewSynchronizeDataRecordWithTags
RecipeViewDeleteDataRecord
RecipeViewNewDataRecord
RecipeViewGetDataRecordFromPLC
RecipeViewRenameDataRecord (for simple recipe view only)
RecipeViewShowOperatorNotes
RecipeViewMenu (for simple recipe view only)
RecipeViewOpen (for simple recipe view only)
RecipeViewBack (for simple recipe view only)
The system functions for loading, saving and transferring recipe data records and recipes are
located in the "Recipes" group.
9.5.3 Configuring Recipes
9.5.3.1 General configuration procedure
Carry out the following configuration steps when you create a new recipe:
Step Description
1 Define the structure of the recipe.
2 Create tags according to the recipe structure.
Assign process names to these tags.
3 Create the recipe.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1103
Step Description
4 Enter the required properties for the recipe:
Language-dependent view name of the recipe
"Coordinated transfer of data records" option
Not for Basic Panels:
Recipe storage location
"Synchronize recipe view and recipe tags" option
"Manual transfer of individual modified values (teach-in mode)" option
5 Create the recipe elements and enter the required properties:
Language-dependent view name of the recipe elements
Tag binding of the recipe elements
Standard values and decimal places (power of ten) for the recipe elements
6 Create the recipe data records.
Enter the language-specific display names for the recipe data records.
7 Configure a screen with recipe view or a recipe screen.
NOTICE
Basic Panels and OP77A, TP177A (Portrait)
The selection of the storage location is not available for these devices. The recipes are always
saved in the internal Flash memory.
Recipe tags cannot be used outside a recipe, e.g. not in I/O fields, not in alarms as trigger
tags, not in systems functions as parameters, etc.
NOTICE
Restrictions recipe view and recipe image
Only the simple recipe view is available in Basic Panels and OP77A, TP177A. Recipe images
are not available in Basic Panels and OP73, OP77A, TP177A (Portrait).
9.5.3.2 Creating and Editing Recipes
Creating a new recipe
Introduction
To create a complete recipe, start by creating a new recipe, assign the corresponding recipe
elements and then define the associated values in a recipe data record.
Requirement
The tags for the recipe have been created.
The "Recipes" editor is open.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1104 System Manual, 08/2011,
Create recipe
Create a recipe as follows:
1. Click "Add" in the first free row of the table in the "Recipes" editor.
The new recipe is created and displayed on a line.
2. Enter a descriptive name for the recipe under "Name" in the "General" area.
This name identifies the recipe unambiguously within the project.
3. Select "Display name" to enter the language-specific name to be displayed in runtime.
4. Select a recipe number in "Number".
The number identifies the recipe unambiguously within the HMI device.
The recipe is automatically assigned a version that indicates the date and time of the last
change. As an alternative, you can enter specific information relating to the recipe.
5. Specify the storage location for recipe data records in "Data medium". The options offered
depend on the specific HMI device used.
NOTICE
Basic Panels and OP77A, TP177A (Portrait)
The selection of the storage location is not available for these devices. The recipes are
always saved in the internal Flash memory.
Recipe tags cannot be used outside a recipe, e.g. not in I/O fields, not in alarms as trigger
tags, not in systems functions as parameters, etc.
6. Enter a tooltip that is shown to the operator in runtime.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1105
7. To compare recipe tags which are configured in I/O fields with the recipe view in Runtime,
activate "Synchronize recipe view and recipe tags" in the Inspector window under
"Properties > Synchronization".
NOTICE
Basic Panels and OP77A, TP177A (Portrait)
Because the recipe tags cannot be additionally used in I/O fields in screens for Basic
Panels, the "Synchronize recipe view and recipe tags" is not available; you will also not
be able to use the "Manual transfer of individual modified values (teach-in mode)" option.
8. Deactivate "Manual transfer of individual modified values (teach-in mode)" to specify that
the recipe tags are automatically transferred to the PLC when editing the I/O fields.
9. Activate "Coordinated transfer of data records" to monitor the transfer of recipe data in
Runtime using area pointers.
10.Select the appropriate connection to the PLC for coordinated transfer under "Synchronize
with".
Create recipe element
To create recipe elements, proceed as follows:
1. Click the "Elements" tab.
2. Click "Add" in the first free line of the table editor.
A new recipe element is created.
3. Enter a descriptive name for the element under "Name".
The name identifies the element uniquely within the recipe.
4. Enter a language-specific display name for the element under "Display name".
The display name appears in the recipe view, for example, in runtime.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1106 System Manual, 08/2011,
5. Select the tag you want to link to the recipe element under "Tag".
The value of the recipe data element is saved in Runtime in this tag, which is stored in a
recipe data record.
6. Enter a tooltip.
The tooltip is shown to the operator in Runtime.
7. Under "Default value", enter the value that you want to use as the default entry when you
create a new recipe data record.
8. To assign text to a value or range of values, select the relevant text list here. The assigned
recipe tag must have the data type of a number. The tag value must be within the range of
values of the text list.
The text stored in the text list is displayed in an output field, for example, in Runtime.
9. Determine exactly how many places a decimal number is rounded to in the "Decimal places"
column, e.g. 3 decimal places and vice versa by what power of ten an integer value is
multiplied, e.g. 1,000.
Examples for 3 decimal places: Entering "5" for a recipe element with the "Integer" data
type gives the value "5000". Entering "5.6789" for a recipe element with the "Real" data
type gives the value "5.679".
10.Create as many recipe entries as needed for the recipe. The maximum number of recipe
entries possible depends on the HMI device being used.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1107
Create recipe data record with known recipe values
To create recipe elements, proceed as follows:
1. Click the "Data records" tab.
2. Click "Add" in the first free line of the table editor.
A new recipe data record is created. The recipe data record has a separate column for
every recipe element created in the recipe.
3. Enter a descriptive name under "Name".
The name identifies the data record uniquely within the recipe.
4. Enter a language-specific name under "Display name".
The display name appears in the recipe view, for example, in runtime.
5. Enter a recipe data record number under "Number".
The recipe data record number identifies the recipe data record uniquely within the recipe.
6. If you already know the recipe values at the configuration stage, you can enter the relevant
value for each recipe element.
7. Create as many data records as you need for the recipe.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1108 System Manual, 08/2011,
Enter the values in runtime
The following options are available for entering values in the recipe data records at runtime:
Transfer data directly from the PLC (Teach-in mode)
Import of values from a CSV file
Input values on the HMI device
NOTICE
Basic Panels and OP77A, TP177A (Portrait)
The import of values is not available for these devices.
Result
The complete recipe is configured.
Recipe data records with date or time stamp
If you use date or time data, make sure that the system setting for time and date on the
configuring computer match those on the target system. Example: You load a recipe data
record on the target system at 13:55 in which 14 h is stored as the processing time. If it is
already 14:05 on the target computer, the recipe will not be processed. If an operator processes
the recipe, change information will not written back correctly into the database.
After loading to the target system, check the recipes with date or time stamps on the target
system.
Editing a recipe
Purpose
You want to modify, extend or delete parts of a recipe.
Requirement
You have created at least one recipe.
The "Recipes" editor is open.
Changing recipe settings
To change the recipe settings, proceed as follows:
1. Select the recipe that you want to change in the "Recipes" editor.
The Inspector window opens.
2. Change the recipe configuration in the Inspector window.
You change recipe elements and recipe data records in the same way.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1109
Change recipe values
To change recipe values, proceed as follows:
1. Select the recipe whose values you want to change.
2. Click the "Data records" tab.
3. Enter the new values in the value columns.
Adding a recipe element
To add more recipe elements to a recipe, proceed as follows:
1. Select the recipe to which you want to add more elements in the "Recipes" editor.
2. Click the "Elements" tab.
3. Click "Add" in the first free line.
The recipe element is created.
4. Configure the recipe element.
You add recipe data records in the same way.
Managing recipes
Requirement
You have created a recipe with recipe elements and recipe data record.
The "Recipes" editor is open.
Renaming recipes
We distinguish between internal names and display names for recipes, recipe entries and
recipe data records.
To rename recipe elements, proceed as follows:
1. Select the recipe that you want to rename.
The Inspector window opens.
2. Select the "Rename" command from the shortcut menu.
3. Enter the new name.
You rename recipe elements and recipe data records on the relevant tab in the same way.
Note
The view names in the "Recipes" editor can also be renamed under "Languages &
Resources > Project Texts". This possibility is useful when you have already configured
in several languages for example.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1110 System Manual, 08/2011,
Copying and pasting recipes
To copy and paste recipes, proceed as follows:
1. Select the recipe that you want to copy.
2. Select the "Copy" command from the shortcut menu.
3. Select the "Paste" command from the shortcut menu in the first free table row.
The copied recipe is pasted into the table. The recipe elements and recipe data records are
also copied in the appropriate tab with the recipe.
You also copy the recipe elements and recipe data records on the appropriate tab in the same
way.
If a recipe data record of the same name already exists, the name of the copied recipe data
record is extended by one digit. This ensures that the name is unique. Recipe data records
can only be copied or pasted within the same recipe.
Deleting a recipe
To delete a recipe, proceed as follows:
1. Select the recipe that you want to delete.
2. Select the "Delete" command from the shortcut menu.
The recipe is deleted.
You delete recipe elements and recipe data records on the relevant tab in the same way.
Note
When a recipe is deleted, the recipe data records contained in the recipe are also deleted.
Note
When you delete a recipe element, the associated values in the recipe data records are also
deleted. The assigned tags are retained.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1111
9.5.3.3 Configuring the display of recipes
Configuring the simple recipe view
Requirement
You have created the recipe.
The "Screens" editor is open.
The screen has been created and opened.
CAUTION
Data loss with several recipe views in the screen
Applies only to Basic Panels, OP73, OP77A, TP177A and TP177A (Portrait): If two or
more recipe views show the same recipe in a screen, you have a conflict when accessing
the data.
The result is data loss and unpredictable status of recipe data.
Make sure the operators do not select and edit the same recipe in different recipe views.
Display only one recipe in a recipe view.
Display a different recipe in each recipe view.
Procedure
To configure a simple recipe view, proceed as follows:
1. Paste the recipe view into the screen. You will find the recipe view under "Controls" in the
"Tools" task card.
2. Only in devices which also support the extended recipe view: Activate "Simple view" under
"Properties > Display > Mode".
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1112 System Manual, 08/2011,
3. If you want to display only the recipe data records of a specific recipe in the recipe view,
select the specific recipe under "Properties > General > Recipe".
4. If you only want to display the recipe data in the recipe view, deactivate "Processing mode"
in the "Recipe data record" area.
5. You can define additional options for the recipe view under "Properties > Appearance" and
"Properties > Layout".
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1113
6. Select "Properties > Simple view" to select the position, the field length, and the number of
lines required.
Select "Position > Top" to display the recipe value in the first line of the recipe entry.
Select "Position > Bottom" to display the recipe value in the last line of the recipe entry.
7. Under "Properties" > Toolbar" specify which menu commands are available in the recipe
view in Runtime.
Result
The simple recipe view is configured. You can use the recipe view to display and edit recipe
data during runtime.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1114 System Manual, 08/2011,
Configuring the Advanced Recipe View
Requirement
The recipe has been created.
The "Screens" editor is open.
The screen has been created and opened.
Procedure
To configure an advanced recipe view, proceed as follows:
1. Paste the recipe view into the screen. The recipe view is found under "Controls", in the
"Tools" task card.
2. Select "Advanced view" under "Properties > Display > Mode" in the Inspector window.
3. Select the required settings from the "General" group in the Inspector window.
If you want to display only the recipe data records for a particular recipe in the recipe
view, select the recipe under "Recipe" in the "Recipes" area.
If no recipe is selected in the "Recipe" recipe view, the operator can select the recipe
himself in Runtime.
If you want to save the recipe name or the recipe number in a tag, select the tag under
"Recipe tag" in the "Recipe" area.
If you want to save the recipe data record name or number in a tag, select the tag under
"Tag" in the "Recipe data record" area.
If you only want to display the recipe data in the recipe view, deselect "Edit mode".
If you only want to use the recipe view to select recipes, deselect "Display table" under
"Properties > Table".
4. You can define additional options for the recipe view under "Properties > Appearance" and
"Properties > Layout".
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1115
5. If you want to change the label in the recipe view, enter a suitable text under "Properties"
> "Label".
6. Under "Properties" > Toolbar" specify which buttons are available in the recipe view in
Runtime.
Note
If you select the "Edit" command in the context menu of the recipe view, the recipe view
becomes active. To activate the recipe view, the zoom factor must be set to 100%.
You can set the column width and the position of the "Entry name" and "Value" columns
in active mode.
Result
The recipe view is configured. You can use the recipe view to display and edit recipe data
during runtime.
Configuring a recipe screen
Introduction
The recipe screen is a screen in which you configure a customized screen form in the "Screens"
editor. You create the screen form from input/output fields and other display and operator
control objects. System functions are used to configure the recipe functionality, such as saving
recipe data records.
NOTICE
Availability
Recipe screens cannot be created for basic panels and OP73, OP77A and TP177A (Portrait).
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1116 System Manual, 08/2011,
Application
You can spread recipe data records containing lots of entries across several screens. For
example, for each plant you can configure a screen containing the associated screen forms
for the recipe data records.
You can visually simulate your machine in a screen using graphical screen objects. This
enables you to display parameter settings more clearly by positioning I/O fields immediately
next to machine elements, such as axes or guide rails. You can use this to produce a direct
reference between the values and the machine.
Requirement
You have created the recipe.
The "Screens" editor is open.
Procedure
To configure a recipe screen, proceed as follows:
1. Configure the screen and create the I/O fields for the input mask of the recipe.
You can create multiple screens to suit the size and complexity of the recipe.
2. Configure the I/O fields with the tags you have linked to the recipe element.
3. Configure I/O fields for selecting recipes and recipe data records.
Alternatively:
1. Configure a recipe view as a selection list for recipe data records and recipes.
2. Hide the buttons that are not required in the recipe view.
3. Configure the system functions for editing recipe data records on the configured control
elements.
Control elements are configured buttons in the screen or function keys on the HMI device.
You will find the system functions for editing recipe data records under "Recipes" and
"Keyboard operation for screen objects".
Result
The recipe screen is created.
9.5.3.4 Importing recipes into the configuration and exporting them
Introduction
You can export recipes as a CSV file and import them again into the configuration.
Application case
Recipe data is exported for long-term storage and backup on a computer.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1117
In order to unify and distribute recipe data, export the recipe data to an HMI device. Change
the CSV file in Microsoft Excel and import the CSV file to all HMI devices that require the same
recipe data.
You want to exchange recipe data between different projects. You change the recipe data in
Runtime. To transfer the modified recipe data to WinCC ES, export the recipe data records in
Runtime and copy the CSV file to the configuring computer. There you import the CSV file
containing the recipe data records into the recipe. And in the opposite direction, you transfer
the modified recipe data records to the HMI device in WinCC ES in Runtime.
Requirement
You have created the recipe.
The structures of the exported CSV file and the recipe in WinCC ES match; name, number
and data type of the recipe elements are identical.
The "Recipes" editor is open.
Importing CSV files
To import recipe data records into a recipe, proceed as follows:
1. Select the row which contains the desired recipe in the "Recipes" tab.
2. Select the "Import recipe data" command from the shortcut menu.
The "Import" dialog box opens.
3. To select the desired CSV file, go to "File name".
4. Under "Strategy", specify whether a recipe data record with the same recipe number in
WinCC ES should be overwritten.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1118 System Manual, 08/2011,
5. Specify the list separator and decimal separator under "Data separation". The list separator
separates individual recipe elements in the CSV file. The decimal separator separates
integers and decimal places.
NOTICE
Use the same list separator for import as in the CSV file for export.
6. Click "Import" to start the operation.
Result
The recipe will be amended by recipe data records from the CSV file that have not yet been
entered. If the option is selected, existing recipe data records will be overwritten.
An error message is shown in the "Info" of the Inspector window if the structure of the recipe
does not match the structure of the CSV file.
Exporting CSV files
1. Select the row which contains the recipe to export in the "Recipes" tab.
2. Select the "Export recipe data" command from the shortcut menu.
The "Export" dialog box opens.
3. Under "File name", specify the path of the CSV file.
4. Select all recipe data records under "Selection content", or restrict the selection to specific
record numbers of the recipe data.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1119
5. Specify the list separator and decimal separator under "Data separation". The list separator
separates individual recipe elements in the CSV file. The decimal separator separates
integers and decimal places.
6. Click "Export" to start the operation.
Result
The configuration is exported as a CSV file.
9.5.4 Using Recipes in Runtime
9.5.4.1 Simple recipe view
Description of the simple recipe view
Layout
The simple recipe view consists of the following display areas:
Recipe list
Data record list
Element list
This application is illustrated below:
Beverage
Juice
Nectar
1
2
3
In the simple recipe view, each area is shown separately on the HMI device. You can use the
shortcut menu to operate each of these display areas.
The simple recipe view always begins with the recipe list.
Operation
You have the following options for using the simple recipe view, according to the configuration:
Create, change, copy or delete recipe data records
Read recipe data records from the PLC or transfer to the PLC
Using the display area and shortcut menu
Toggle between the display areas and the shortcut menus to operate the simple recipe views.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1120 System Manual, 08/2011,
The table below shows the operation of the display area.
Button Key Function
<Enter> The next lowest display area is opened, i.e. the data record
list or the element list.
<Esc> The previous display area opens.
<INS> Creates a new data record for the selected recipe if the list
of recipes or recipe data records is displayed. Then changes
to the list of recipe element.
Requirement: "Properties >General > Processing mode" is
activated.
The button can be simulated with the "Key
SimulateSystemKey" function even on devices without keys.
<DEL> Deletes the selected recipe data record in the list of recipe
data records.
Requirement: "Properties >General > Processing mode" is
activated.
<Up>/<Down> Selects the previous/next entry.
<Pg Up>/<Pg Down> Moves the display up or down one page.
<Home>/<End> Selects the first/last entry. The first/last entry is selected.
The table below shows the operation of the shortcut menu:
Button Key Function
<Right> The shortcut menu of the display area opens.
<Esc> The menu is closed.
The display area opens.
Input of the number of
the menu command
The menu command is executed.
Shortcut menus of the simple recipe view
You can click the button in each display area to call up a selection of commands. The
command selection lists those commands that are available in the current display area. A
number is assigned to each command. The command is executed when you enter this number.
Alternatively select the command and press the <Return> key.
Shortcut menus in the recipe list
Menu command Function
New A new recipe data record is created for the selected recipe.
If a start value is configured, it is displayed in the input field.
Display tooltip The tooltip configured for the recipe is displayed.
Open The record list of the selected recipe opens.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1121
Shortcut menus of the recipe data record list
Menu command Function
New Creates a new recipe data record.
If a start value is configured, it is displayed in the input field.
Deleting The displayed record is deleted.
Save as The selected data record is saved under a different name. A dialog box opens
where you can enter the name.
Rename Renames the selected data record. A dialog box opens where you can enter
the name.
Open The element list of the selected data record opens.
Previous The recipe list opens.
Shortcut menus of the recipe element list
Menu command Function
Save The selected data record with the recipe element is saved.
To PLC The displayed values of the selected data record are transferred from the
HMI device to the PLC.
From PLC The recipe values from the PLC are displayed in the recipe view of the HMI
device.
Save as The data record is saved under a new name. A dialog box opens where you
can enter the name.
Display tooltip The tooltip configured for the recipe element is displayed.
Rename The selected recipe element is renamed. A dialog box opens where you can
enter the name.
Previous The data record list opens.
Shortcut menus in the data record list
Note
HMI device dependency
The following menu commands are configured in Basic Panels and in OP 77A, TP 177A,
TP 177A (Portrait) and TB 177B.
Menu command Function
To PLC The displayed values of the selected data record are transferred from the
HMI device to the PLC.
From PLC The recipe values from the PLC are displayed in the recipe view of the HMI
device.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1122 System Manual, 08/2011,
Using the simple recipe view
Controlling the simple recipe view with mouse or touchpad
To control the simple recipe view with mouse or touchpad, proceed as follows:
1. Select the desired recipe from the recipe view.
2. Click the button.
The shortcut menu is opened.
3. Select the desired menu command.
The menu command is executed.
Controlling the simple recipe view with the keyboard
To control the simple recipe view with the keyboard, proceed as follows:
1. Press the <Tab> key until the simple recipe view is selected.
2. Select the desired recipe with the cursor keys.
3. Press <Right>.
The shortcut menu is opened.
4. Press the <Down> key until the desired menu command is selected.
5. Press <Enter> to confirm the command.
Key shortcuts for the simple recipe view
The following key shortcuts are activated for the simple recipe view in Runtime if "Activate
keyboard operation" is enabled in the ES.
Key shortcut Effect Menu command
<Insert> Generates a new recipe data record New
<Del> Deletes the recipe data record displayed. Delete
Managing recipe data records
Recipe data record administration
You have the following options for managing the simple recipe view, according to the
configuration:
Creating new recipe data records
Copy recipe data records
Edit recipe data records
Delete recipe data records
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1123
Creating new recipe data records
To create a new recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to create a new recipe data record.
2. Select the "New" command from the shortcut menu for the recipe list.
A new data record with the next available number will be created.
The element list of the new recipe data record opens.
3. Enter values for the elements of the recipe data record.
The configuration data may already contain default values for the recipe data record.
4. Select the "Save" command from the shortcut menu for the element list.
The dialog "Save as" opens.
5. Enter the name and number of the recipe data record.
6. Click the "OK" button.
Result
The new recipe data records will be saved to the selected recipe. If the recipe data records
already exists, a system event will be output to the screen.
Copying a recipe data record
To copy a recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to copy an existing recipe data record.
2. On the HMI device, select the recipe data record of which you want to save a copy.
3. Select the "Save As" command from the shortcut menu for the data record list.
The dialog "Save as" opens. The recipe data record is automatically given the next free
recipe data record number.
4. Under name, enter the name of the record.
5. Click the "OK" button.
Result
The recipe data record is stored under the new name.
Modify recipe data record
To change a recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to edit an existing recipe data record.
2. Select the recipe data record that you want to edit on the HMI device.
3. Select the recipe data record.
The element list of the recipe data record is displayed.
4. Replace the old values with new ones.
5. Select the "Save" command from the shortcut menu for the element list.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1124 System Manual, 08/2011,
Result
The modified values are applied to the recipe data record.
Deleting a recipe data record
To delete a recipe data record, proceed as follows:
1. Select the recipe on the HMI device from which you want to delete an existing recipe data
record.
2. Select the recipe data record that you want to delete on the HMI device.
3. Select the "Delete" command from the shortcut menu for the data record list.
4. Confirm this security prompt to delete the data record.
Result
The recipe data record is deleted.
Read recipe data record from PLC
Introduction
In Runtime, you can change values directly in the plant that are also stored in recipes in the
HMI device. This applies if a valve was opened further directly in the plant than was specified
in the recipe. The values of the recipe data records saved in the HMI device possibly no longer
match the values in the PLC.
You can read the values of the recipe tags from the PLC and write them to a recipe data record.
The read values are written to the recipe data record that is currently displayed on the HMI
device.
Procedure
To read a recipe data record from the PLC, proceed as follows:
1. Open the recipe on the HMI device.
The data record list opens.
2. Select the element list of the recipe data record to which you want to apply the values from
the PLC.
3. Select the "From PLC" command from the shortcut menu for the element list.
The values are read from the PLC and displayed in the current recipe data record.
4. If you want to save the values, select the "Save" or "Save As" command.
Result
The values are read from the PLC, visualized on the HMI device and saved to the recipe data
record.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1125
Transferring a recipe data record to the PLC
Introduction
For the values of a data record that was changed in the recipe view to take effect, you must
transfer the values to the PLC.
The values displayed in the recipe view are always transferred to the PLC.
Procedure
To transfer a recipe data record to the PLC, proceed as follows:
1. Open the recipe you want to use.
The data record list opens.
2. Select the element list of the recipe data record whose values you want to transfer to the
PLC.
3. Select the "To PLC" command from the shortcut menu for the element list.
Result
The values of the recipe data record are transferred to the PLC.
9.5.4.2 Advanced recipe view
Description of the advanced recipe view
Application
The recipe view is used to display, edit and manage data records.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1126 System Manual, 08/2011,
Operation
Depending on the configuration you can:
Create, change, copy or delete recipe data records
Synchronizing recipe data records with the associated recipe tags
Read recipe data records from or transfer to the PLC
Operating elements
The following operating elements can be configured in the recipe view:
Operating
element
Key combination Function
The configured tooltip is displayed.
<Ctrl+Space
Bar>
Creates a new recipe data record.
If a start value is configured, it is shown in the input field.
<Ctrl+Enter> Saves the displayed values of the recipe data record.
The storage location is predefined by the project.
<Ctrl+*> The recipe data record is saved under a different name regardless
of the recipe view. A dialog box opens where you can enter the
name.
<Ctrl+Del> The displayed recipe data record is deleted.
<Ctrl+=> The system always updates the current value of the recipe view
with the up-to-date recipe tag value.
When the value shown in the recipe view is more recent than the
current recipe tag value, the system writes this value to the recipe
tag.
"Synchronize recipe view and recipe tags" must be activated in the
recipe properties before this function can be used.
<Ctrl+Down> The values of the set recipe data record displayed in the recipe view
are transferred to the PLC.
<Ctrl+Up> The recipe values from the PLC are displayed in the recipe view.
Using the advanced recipe view
Introduction
You can control the recipe view using both mouse or touchpad or with the keyboard.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1127
Controlling the recipe view with mouse or touchpad
To control the recipe view with mouse or touchpad, proceed as follows:
1. Select the recipe you want to use.
The records for the recipe are displayed.
2. Click on the data record you wish to edit.
3. Click the button whose function you want to run.
Controlling the recipe view with the keyboard
To control the recipe view with the keyboard, proceed as follows:
1. Press the <Tab> key until the cursor reaches the field for selecting the recipe.
2. Press <Enter>.
The drop-down list box for the recipes opens.
3. Select a recipe. You navigate between the next or previous entry in the list by using the
cursor keys <Left>, <Right>, <Up> and <Down>.
4. Select a data record.
5. Press the <Tab> key until the operator control object you wish to use is selected.
Alternatively you can control the recipe view using certain key combinations.
Key shortcuts for the advanced recipe view
The following key shortcuts are activated for the advanced recipe view in Runtime if "Activate
keyboard operation" is enabled in the ES.
Keys
shortcut
Effect Menu command Button
<Ctrl
+Space>
Generates a new recipe data record.
Any configured start value is displayed in
the input field.
Add data record
<Ctrl+Del> Deletes the recipe data record displayed. Delete data record"
<Ctrl+Enter> Saves the edited data record by its current
name.
Save
<Ctrl+*> Saves the edited data record by a new
name.
Save as
<Ctrl+=> Compares the values of the selected data
record with the values on the PLC.
Any value in the recipe view which is more
recent compared to the current recipe tag
value is written to the recipe tag.
This function is only available if enabled in
the ES.
Synchronizing recipe tags
<Ctrl+Down> Transfers the current value to the PLC. Write to PLC
<Ctrl+Up> Reads the actual value from the PLC. Read from PLC
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1128 System Manual, 08/2011,
Managing recipe data records
Administration of recipe data records
You have the following options for managing recipe data records, according to the
configuration:
Create new recipe data records
Copy recipe data records
Edit recipe data records
Delete recipe data records
Creating new recipe data records
To create a new recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to create a new recipe data record.
2. Click the button or press the <Ctrl + Spacebar> keys.
A new recipe data record with the next available number is created.
If you change the new data record number to an existing data record number, the existing
data record is overwritten.
3. Enter values for the elements of the data record.
The elements of the recipe data record can be assigned default values depending on the
configuration.
4. Click the button or press the <Ctrl + *> keys.
The dialog "Save as" opens.
5. Enter a name for the data record.
6. Click on "OK" to confirm your input.
The data record is saved under the new name.
If the recipe data record already exists, a dialog is opened. In this dialog, specify whether
the existing data record is to be overwritten.
Result
The new recipe data records will be saved to the selected recipe. If the recipe data records
already exists, a system alarm will be output to the screen.
Copying a recipe data record
To copy a recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to copy an existing recipe data record.
2. Select the recipe data record that you want to copy on the HMI device.
3. Click the button in the recipe view or press the <Ctrl + *> keys.
The dialog "Save as" opens.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1129
4. Enter a name for the data record.
5. Click on "OK" to confirm your input.
Result
The recipe data record is stored under the new name.
Modify recipe data record
To change a recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to edit an existing recipe data record.
2. Select the recipe data record that you want to edit on the HMI device.
3. Replace the old values with new ones.
4. Click the button in the recipe view or press the <Ctrl + Enter> keys.
Result
The modified values are applied to the recipe data record.
Delete recipe data record
To delete a recipe data record, proceed as follows:
1. Select the recipe on the HMI device in which you want to delete an existing recipe data
record.
2. Select the recipe data record that you want to delete on the HMI device.
3. Click the button in the recipe view or press the <Ctrl + Del> keys.
Result
The recipe data record is deleted.
Synchronizing recipe data record
Introduction
Differences between the following values may occur during runtime:
The values displayed in the recipe view
The actual values of the recipe tags
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1130 System Manual, 08/2011,
Depending on the configuration, the values displayed in the recipe view are synchronized with
the recipe tags. Synchronization encompasses all tags of a recipe data record.
NOTICE
Changed tag name
The tag and the value of the recipe data record cannot be associated if you have renamed
the tag you want to synchronize. The tags in question are not synchronized.
Note
Recipe tags can only be synchronized in the advanced recipe view.
Requirement
A recipe data record is displayed in the recipe view.
The values of recipe tags were modified by teaching, for example.
Procedure
To synchronize a recipe data record, proceed as follows:
1. Click the button in the recipe view or press the <Ctrl + => keys.
Result
The system always updates the current value of the recipe view with the up-to-date recipe tag
value.
When the value shown in the recipe view is more recent than the current recipe tag value, the
system writes this value to the recipe tag.
Read recipe data record from PLC
Introduction
In Runtime, you can change values directly in the plant which are also stored in recipes in the
HMI device. This applies if a valve was opened further directly in the plant than was specified
in the recipe. The values of the recipe data records saved in the HMI device possibly no longer
match the values in the PLC.
You can read the values of the recipe tags from the PLC and write them to a recipe data record.
The read values are written to the recipe data record that is currently displayed on the HMI
device.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1131
Procedure
To read a recipe data record from the PLC, proceed as follows:
1. Select the recipe on the HMI device.
2. On the HMI device, select the recipe data record of which you want to fetch the values from
the PLC.
3. Click the button in the recipe view or press the <Ctrl + Up> keys.
Result
The values are read from the PLC and displayed on the HMI device.
Transferring recipe data records to the PLC
Introduction
For the values of a data record that was changed in the recipe view to take effect, you must
transfer the values to the PLC.
The values displayed in the recipe view are always transferred to the PLC.
Procedure
To transfer a recipe data record to the PLC, proceed as follows:
1. Select the recipe on the HMI device.
2. On the HMI device, select the recipe data record of which you want to transfer the values
to PLC.
3. Click the button in the recipe view, or press the <CTRL+DOWN> shortcut key.
Result
The values of the recipe data record are transferred to the PLC.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1132 System Manual, 08/2011,
9.5.4.3 Exporting and importing recipe data records
Introduction
Depending on configuration and the HMI device, either export recipe data records to a CSV
file, e.g. for editing in MS Excel, or import these from a CSV file. The extent to which you can
influence these processes is determined by the project configuration.
Note
Restrictions for Import / Export
It is not possible to export or import the recipes for the following HMI devices:
Basic Panels
OP 77A
OP 177A
TP 177A (Portrait)
Complete recipe data, but not single recipe data records, can be exported and imported using
ProSave in CSV format and transferred to the HMI device. Thereby, Runtime is interrupted.
A list separator is used to separate the data records during importing and exporting.
Note
The list separator used as the default depends on the setting for formats and numbers in the
operating system. Select "Start > Settings > Control Panel > Regional and Language
Options". If you want to import or export recipe data records, do not use this list separator in
the display name of the recipe data records.
The following fields can be configured on the user interface, for example, in order to use the
export/import function:
Selection field for the recipe
Selection field for the recipe data record
Operating element with the "ExportDataRecords" functionality
Operating element with the "ImportDataRecords" functionality
Export recipe data record
To export a recipe data record, proceed as follows:
1. Select the relevant recipe and recipe data record from the selection boxes.
2. Click the control element with the "ExportDataRecords" functionality.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1133
Result
The recipe data record are exported to a CSV file.
Note
New data records created in runtime can be exported to an external file.
Importing recipe data records
To import a recipe data record, proceed as follows:
1. Select the relevant recipe and recipe data record from the selection boxes.
2. Click the control element with the "ImportDataRecords" functionality.
Result
The recipe data record are imported.
9.5.4.4 Reactions to modifications of the recipe structure
Introduction
Different recipe structures can occur in the following situations:
In the event of changes during commissioning
When work is carried out on the machine by the machine manufacturer (retrofit)
When CSV files are imported, the structure of the CSV file can differ from the recipe
structure.
Nevertheless, you can still use any recipe data records already created.
CAUTION
When a tag is renamed, the assignment is lost.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1134 System Manual, 08/2011,
Effects
Handle any structural differences as follows:
If the old recipe data record or the CSV file contains additional values, these values will be
discarded.
If the old recipe data record or the CSV file contains values of the wrong data type, the
configured default value will be used in the recipe data record.
Example: The recipe data record contains values that show the tank contents and were
input as floating point numbers. However, the corresponding recipe tag expects an integer
value. In this case, the system discards the transferred value and the configured default
value is used.
If the old recipe data record or the CSV file contains too few values, the configured default
value will also be used in the recipe data record.
9.5.5 Examples
9.5.5.1 Example of creating a recipe
Task
In this example, you create three recipes for a fruit juice mixing machine. The fruit juice mixing
machine produces drinks with "orange", "apple" and "tropical" flavors. You create a recipe for
each flavor.
Each recipe contains a recipe data record for the following mixing ratios:
Beverage
Nectar
Juice
Settings
The settings relate to an HMI device which is connected to a SIMATIC S7-300 or
SIMATIC S7-400.
In this example, you will need the following tags, recipes, recipe entries and recipe data records:
Tags:
Name PLC connection Address Type
Liter water Yes DB 120, DBW 0 Integer
Liter concentrate Yes DB 120, DBW 4 Integer
Kilo sugar Yes DB 120, DBW 8 Integer
Gram flavoring Yes DB 120, DBW 12 Integer
Recipes:
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1135
Orange
Apple
Tropical
Recipe entries:
Recipe element Associated tag
Liter water Liter water
Liter concentrate Liter concentrate
Kilo sugar Kilo sugar
Gram flavoring Gram flavoring
Recipe data records for drink, nectar and juice:
Data record name Liter water Liter concentrate Kilo sugar Gram flavoring
Beverage 30 70 45 600
Nectar 50 50 10 300
Juice 5 95 3 100
Procedure
To create a recipe, proceed as follows:
1. Create the following tags with the settings specified above: "LiterWater", "LiterConcentrate",
"KiloSugar" and "GramFlavoring".
2. Create the "Orange", "Apple" and "Tropical" recipes with the settings indicated above.
Create the recipe entries in each recipe.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1136 System Manual, 08/2011,
3. Not for Basic Panels: Configure each recipe so that you can synchronize the recipe data
records between the recipe screen and recipe view. The values of the recipe tags should
not be transferred automatically to the PLC.
You will have to make the following settings in the Properties dialog for the recipe concerned:
Under "Properties > Options":
Activate the "Synchronize recipe view and recipe tags" option.
Activate the "Manual transfer of individual modified values (teach-in mode)" option.
4. Create the data records indicated above in each recipe. Enter the values indicated above
in each of the data records.
Result
The "Orange", "Apple" and "Tropical" recipes have been created.
9.5.5.2 Example of configuring a recipe screen
Task
In this example, you create a recipe screen for the visualization of values of the fruit juice
mixing machine. You use a recipe view to select the recipes and their associated recipe data
records.
You should be able to use the following functions with the buttons:
"Load" Button
The selected recipe data record is loaded from the recipe memory on the HMI device and
displayed in the recipe screen.
"Save" Button
The displayed recipe tags are saved in the recipe memory of the HMI device.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1137
"Data to PLC" button
The displayed tags are transferred to the PLC.
"Data from PLC" button
The current recipe data record in the PLC is transferred to the recipe variables and
displayed on the HMI device.
Requirement
The "Creating a recipe" sample application has been carried out.
You have created and opened the "Fruit juice mixing plant" screen.
Settings
In this example, you need the following tags and buttons with the indicated settings:
Tags:
Name PLC connection Type
RecipeNumber No Integer
Data record number No Integer
Buttons:
Labeling Configured event System function
Load Click LoadDataRecord
Save Click SaveDataRecord
Data to PLC Click SetDataRecordTagsToPLC
Data from PLC Click GetDataRecordTagsFromPLC
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1138 System Manual, 08/2011,
Procedure
To configure a recipe screen, proceed as follows:
1. Drag-and-drop the "Liter water", "Liter concentrate", "Kilo sugar" and "Gram flavoring" tags
from the object view to the "Fruit juice mixing machine" process screen.
Four IO fields are created and linked by the specified tags.
2. Add a recipe view containing selection fields for the recipe name and data record name
only.
Make the following settings in the Inspector window for the recipe view:
Select the "Advanced view" display type under "General".
Deselect "Edit mode" under "Properties > General" and "Display table" under "Properties
> Table".
Connect the "Recipe tag" field to the "RecipeNumber" tag.
Connect the "Tag" field to the "DataRecordNumber" tag.
Disable all the buttons under "Properties > Buttons".
3. Assign the above settings to four buttons. Transfer each "Recipe number" and "Data record
number" tag as a parameter for the recipe number and recipe data record number.
Result
You can select the recipe and the associated recipe data record from the recipe view and
modify the recipe values at runtime. You can load, save and transfer the recipe data records
using the buttons.
9.5.5.3 Scenario for Entering Recipe Data Records in Runtime
Objective
You want to enter production data on the HMI device without disturbing the process that is
currently underway. Therefore, the production data should not be transferred to the PLC.
Requirement
The recipe has been created.
The recipe has the following settings:
"Synchronizing recipe view and recipe tags" is activated or deactivated.
If "Synchronize recipe view and recipe tags" is activated, "Manual transfer of individual
modified values (teach-in mode)" has to be activated.
This will prevent the recipe tags being transferred automatically between the HMI device
and PLC.
A recipe screen or a screen with recipe view is available.
There is an operating element for saving the recipe data records.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1139
Sequence
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
PLC
Recipe view
Recipe
screen
Recipe tag
Synchronizing
Teach-in mode
1. Enter the production data in the recipe view or recipe screen.
2. Save the modified recipe data record.
Transfer the recipe data to the PLC
The configuration may provide operating elements for transferring recipe data to the PLC.
9.5.5.4 Scenario for a manual production sequence
Objective
A reading device connected to the PLC reads a bar code on the work piece to be processed.
The recipe data record names correspond to the respective bar code names. This will enable
the PLC to load the necessary recipe data record from the storage medium of the HMI device.
The recipe data record is displayed for inspection on screen.
You want to be able to correct the transferred production data online, if necessary.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1140 System Manual, 08/2011,
Requirement
You have created the recipe.
The recipe has the following settings:
"Synchronizing recipe view and recipe tags" is activated.
"Manual transfer of individual modified values (teach-in mode)" is deactivated.
Note
The changes are immediately transferred to the PLC
There is a recipe screen available.
There may also be an operating element for saving the recipe data records in the recipe
screen.
Sequence
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
PLC
Recipe
screen
Recipe tag
Synchronizing
Teach-in mode
Behavior when the recipe view is used
If the recipe view is used, it is not possible to transfer changes immediately. You must use the
operating element to transfer the recipe data record to the PLC.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1141
9.5.5.5 Scenario for an Automatic Production Sequence
Objective
You want production to be executed automatically. The production data is to be transferred
directly to the PLC, either from the recipe memory in the HMI device or from an external storage
medium. The screen display is not necessary.
Requirement
You have created the recipe.
The recipe has the following settings:
"Coordinated transfer of data records" is activated.
The production data is transferred to the PLC, so a coordinated transfer with the PLC
in necessary to prevent the data from being accidentally overwritten.
Sequence
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
PLC
External storage
medium
Coordinated transfer
Implementation
You can control the flow of data in the following ways:
The control program controls the automatic transfer via control jobs or via WinCC system
functions, if necessary.
The sequence is controlled via the status information in the mailbox and via return values
from the functions used.
One or more scripts control the automatic transfer via WinCC system functions.
The sequence can be checked using the values returned by the functions used.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
1142 System Manual, 08/2011,
You can implement the automatic production sequence with available system functions:
"ImportDataRecords"
This function loads data records from a *.CSV file into the recipe memory of the HMI device.
"SetDataRecordToPLC"
This function transfers a data record from the HMI device's recipe memory to the PLC.
Visualizing processes (Advanced)
9.5 Working with recipes
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1143
9.6 Working with reports
9.6.1 Basics
9.6.1.1 Reports
Introduction
Reports are used to record process data and processed production cycles. You have the
opportunity, for example, to create regular shift reports, output batch data, or record the
production process for quality control (QC).
Creating reports
A report is created and edited in the "Reports" editor. In this editor, you configure the following
report items:
Formal appearance
Specify the formal layout of the report in the Inspector window. In this window, for example,
you specify the page format, page margins, title page, back page, headers, or footers for
the report.
Content
In the work area, specify the content of the report, for example, the alarms of a shift. To
this purpose you insert the corresponding objects into the report.
The modular structure lets you configure reports that suit all of your applications.
Note
The "Reports" editor is not available at HMI devices that do not support reporting.
Report output
In runtime, the configured reports are printed on the default printer of the HMI device.
In runtime, report output is event or time-controlled.
Time-controlled: Automatic print at specific dates, times or intervals.
Event-driven: Printing is initiated by specific events, e.g. click on a button, or when a limit
is exceeded.
See also
Principles for preparation of reports (Page 1146)
Printing reports (Page 1151)
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1144 System Manual, 08/2011,
9.6.1.2 Structure of reports
Introduction
A report in WinCC consists of several sections that can be enabled or disabled, as required.
Sections of a report
The following figure shows an example of the different sections of a report in the "Reports"
editor.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1145
Title page and back page
The title page contains important information about the report content. The back page is used,
for example, as Impressum, on which you provide contact information of shift managers or
service technicians. The title page and back page are output separately on a single page. Each
of them consist of exactly one page and page breaks are not used.
Detail page
Configure the output of runtime data such as recipe or alarm reports on the detail pages of the
report.
Use the shortcut menu on the detail page to insert additional detail pages or change their order.
Header and footer
The header and footer are output on each detail page of the report. You typically insert the
page numbers or the date in the header or footer.
See also
Reports (Page 1144)
Principles for preparation of reports (Page 1146)
9.6.2 Working with reports
9.6.2.1 Creating reports
Principles for preparation of reports
Introduction
A report in WinCC consists of several sections that can be enabled or disabled, as required.
Title page
Back page
Detail pages
Headers and footers for the detail pages
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1146 System Manual, 08/2011,
Procedure
The following figure shows the general procedure for creating a report:
Assign name
Create report
Title page
lnsert additional
detail pages
n x detail
pages
Configure report
object 1)
Optional
Optional
lnsert report
object on detail
page
Configure "Print
report" system
function
Header/Footer
Configure rear
page
1) Settings depend on the report object used.
Tools for the design of reports
The tools that you can use to design reports are available in the "Tools" task card.
For graphic design insert "basic objects", "elements" and "graphics" in the different sections
of the report. For example, for a Logo in the header, separation lines and a page number
in the footer.
Using the "Controls" in the detail pages, configure the output of runtime data.
Note
The "Screens" editor provides many objects for designing a report however, with
restricted functionality. Data input properties are not available. The I/O fields in the reports,
for example, serve only to output data.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1147
Position and size of objects
Insert the objects at the position where you want them to be output in the report. The objects
are output in their configured size and with the following special features:
On the detail pages, configure "recipe reports" or "alarm reports" that serve to output runtime
data in tabular format.
The width of the table is set up automatically to fit the width of the detail page. You cannot
modify the width.
WinCC automatically wraps the height of the table to fit the data content for output in the
report. The table can be continued on the next page.
In the detail page, WinCC automatically extends tables of dynamic length to the bottom
margin.
The following figure shows an example of a detail page in the report and its output in Runtime:
Detail page in the report Report output in Runtime
Additional detail pages
Use the shortcut menu on the detail page to insert additional detail pages or change their order.
See also
Objects in reports (Page 1166)
Structure of reports (Page 1145)
Administration of detail pages (Page 1150)
Create a report
Requirement
A project with an HMI device is open.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1148 System Manual, 08/2011,
Procedure
To create a report, proceed as follows:
1. Double-click "Add new report" under "Reports" in the project navigation.
A new blank report is displayed in the "Reports" editor.
2. Select the "Report properties" command in the shortcut menu of the report.
3. In the "Properties > Properties > General" area of the Inspector window, specify whether
you want to configure the "Title page", "Back page", "Header" and "Footer" in the report.
The report sections are updated accordingly.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1149
4. Configure the format, the page layout, and the page margins of the report under "Properties
> Properties > Layout."
5. Enter a meaningful report name under "Properties > Properties > Miscellaneous."
6. Design the report sections as required.
Drag and drop the necessary basic objects, elements, graphic images and controls from
the "Tools" task card to the required position.
Alternatively, you can also copy or move objects already configured from a screen to the
report.
7. Configure the objects in the Inspector window:
See also
Objects in reports (Page 1166)
Administration of detail pages
Adding a detail page
1. Open the shortcut menu of a detail page.
2. Select the command "Pages > Insert page before" or "Pages > Insert page after."
Depending on the selected command, the new detail page is inserted either before or after
the existing detail page.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1150 System Manual, 08/2011,
Deleting a detail page
1. Open the shortcut menu of the detail page that you want to remove.
2. Select the command "Pages > Delete detail page".
The detail page is deleted.
Sorting detail pages
1. Open the shortcut menu of the detail page that you want to move.
2. Select the "Pages > Move one page up" or "Pages > Move one page down" command.
Depending on the selected command, the detail page is moved either upward or downward.
Showing and hiding sections
1. To show or hide a specific section, click on the plus or minus sign in the title bar of the
section in the working area.
2. If you want to show or hide all sections of a report, select the command "Show all pages"
or "Hide all pages" in the report shortcut menu.
See also
Structure of reports (Page 1145)
9.6.2.2 Printing reports
Introduction
In Runtime, report output is event-driven or time-driven.
Event-driven output
The report is output after an event was generated.
Examples:
A tag value changes or exceeds a limit.
Alarm is incoming, outgoing or acknowledged
Action by the operator, for example, clicking a button
Time-driven output
The report is output automatically.
Examples:
Once at a specified date, e.g. on December 31, 2010
At intervals, e.g. daily at 8 am, or on Mondays at 6 pm
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1151
Configuration steps
Configuring event-driven output:
An event is configured on a button or tag with the "PrintReport" system function.
Configuring time-driven output:
In the scheduled tasks, configure a "Print job" task and assign it to the desired report.
In the task properties, specify the time and frequency of report output.
Output in Runtime
On the control panel of the HMI device, the report is output to the printer that is specified as
the default printer.
The default printer enabled for a HMI device can be found in the "Printer list". For further
information about the "Printer list", refer to the Internet page of Siemens Customer Support
and the Article ID "11376409".
See also
Configuring a function list (Page 1227)
Planning jobs (Page 1845)
Printing reports (Page 1165)
9.6.2.3 Working with objects
Inserting an object
Introduction
In the "Screens" or "Reports" editor, insert the objects to the "Toolbox" task card. Use the
mouse to drag the objects into the work area. You either keep the objects in their original size,
or scale them up or down when you paste them.
In addition, you can copy or move objects via the clipboard from one editor to another, for
example to transfer a screen object to a report. Alternatively, you can also use the mouse
instead of the clipboard for copying and moving:
Copying: <Ctrl + Drag&Drop>
Moving: Drag&drop
Note
Basic Panels
The "Reports" editor is not available for Basic Panels.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1152 System Manual, 08/2011,
Requirement
The "Tools" task card is open.
Inserting objects in their standard size
1. In the "Toolbox" task card, select the desired graphic object or the desired graphic in the
WinCC graphics folder.
When you move the cursor across the work area, it turns into a crosshair with an appended
object icon.
2. Click the location in the work area where you want to insert the object or graphic.
The object is inserted with its standard size at the desired position in the work area.
Alternatively, double-click the object in the "Toolbox" task card.
Copying an object
1. Select the desired object.
2. Select "Copy" in the shortcut menu.
3. Click the desired location and select "Paste" in the shortcut menu.
WinCC inserts a copy of the object at the desired location. You can only change the properties
that are appropriate for the relevant context.
Example: In the "Screens" editor, you can set for I/O fields and the mode for input and output.
In the "Reports" editor, the mode is set to "Output".
Original and copy are not interconnected and are configured independently from one another.
Inserting lines
1. Select the desired graphic object in the "Tools" task card.
2. Click on a location in the work area. A line in the standard size is inserted.
Inserting a polygon or polyline
1. Select the desired object "Polyline" or "Polygon" in the "Tools" task card.
2. Click on a location in the work area. This fixes the starting point of the object.
3. Click another location in the work area. A corner point is set.
4. For every additional corner point, click on the corresponding location in the work area.
5. Double-click on a location in the work area. The last corner point is set.
This fixes all the points of the polygon or polyline.
Note
Basic Panels
The "Polyline" and "Polygon" objects are not available for Basic Panels.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1153
Note
If you want to insert several objects of the same type, use the "Stamp" function. This avoids
having to reselect the object in the "Tools" task card every time before inserting it. To do so,
select the icon in the toolbar of the "Tools" task card.
See also
Deleting an object (Page 1154)
Inserting multiple objects of the same type (stamping tool) (Page 1155)
Positioning objects (Page 1156)
Resizing objects (Page 1159)
Storing an object in a library (Page 748)
Inserting a library object (Page 749)
Deleting an object
Introduction
You can delete objects individually or with a multiple selection.
Requirement
You have opened the work area containing at least one object.
Procedure
1. Select the object that you want to delete.
To delete multiple objects, keep the <Shift> key pressed and select the objects to be deleted
one after the other. Alternatively, drag and maximize an area around the desired objects
with the mouse.
2. Select "Delete" from the shortcut menu.
Result
The selected objects are deleted.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1154 System Manual, 08/2011,
Inserting multiple objects of the same type (stamping tool)
Introduction
WinCC offers the possibility to "stamp" several objects of the same type directly one after the
other, i.e. paste without having to reselect the object every time. In addition you have the
possibility of multiplying an object that has already been inserted.
Requirement
The "Tools" task card is open.
Inserting several objects of one type
1. Select the object that you want to insert in the "Tools" task card.
2. Click the icon in the toolbar of the "Tools" task card.
The "Stamp" function is activated.
3. To insert the object with its standard size, click the relevant insertion position in the work
area.
To insert the object with another size, position the mouse pointer at the desired location in
the work area. Press the left mouse button and drag the object to the required size.
The object is inserted in the work area as soon as you release the mouse button.
4. Repeat step 3 to insert further objects of the same type.
5. Click the icon again.
The "Stamp" function is deactivated.
Note
You can copy existing objects using the drag-and-drop +<CTRL> function. The existing
object is not moved in this case. You paste a copy of this object into the new position
instead.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1155
Inserting and multiplying an object
1. Insert the desired object from the "Tools" task card.
2. Press the <Ctrl> key and position the cursor on one of the handles displayed in the figure
shown below.
Multiplication
in horizontal
direction
Multiplication
in vertical
direction
Multiplication
in vertical and
horizontal
direction
3. Drag the handles to the right and/or down while keeping the left mouse button pressed.
4. The object is multiplied depending on available space if you keep moving the cursor.
Result
You have pasted and stamped an object in a screen.
Positioning objects
Introduction
When you select an object, it is enclosed by a rectangle with resizing handles. This rectangle
is the rectangle which surrounds the object. The position of an object is defined by the
coordinates of the top left corner of the rectangle surrounding the object.
Note
If the position is outside the work area the object is not displayed in Runtime.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1156 System Manual, 08/2011,
Position and align
You have the possibility of having a grid displayed in the work area. You have three options
for easier positioning of objects:
"Snap to grid" When you resposition objects, they are automatically snapped and pasted
to the grid. If you hold down the <Alt> key, the object is no longer snapped to the grid.
"Snap to objects" When you reposition objects, they are displayed with help lines. You can
use other objects for orientation during positioning.
"None": You position the objects in any position.
You activate and deactivate the grid and options as follows:
In the "Options > Settings > Visualization > Screens" menu
In the "Layout > Grid" task card
Requirement
You have opened the work area containing at least one object.
Procedure
1. Select the object you want to move.
The selected object is framed by a rectangle with resizing handles.
2. Left-click the object and keep the mouse button pressed.
3. Move the mouse pointer onto the new position.
The contour of the object moves with the mouse and displays the new position for the object.
The object initially remains at its original position.
4. Now release the mouse button.
The object is moved into the position indicated by the contour of the selection rectangle.
Alternative procedure
1. In the Inspector window, select "Properties > Properties > Layout".
2. Enter the X and Y values for the position under "Position & Size".
Result
The object appears at its new position.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1157
See also
Rotating objects (Page 1163)
Moving an object forwards or backwards
Introduction
You can use the "Order" functions in the shortcut menu of a selected object or in the toolbar
to move a selected object in front of or behind other objects within an object layer.
Note
ActiveX controls are always positioned in front of an object layer (.NET property).
Requirement
You have opened a screen which contains a layer with multiple objects.
Procedure
1. Select the object you want to move forward or backward.
2. Select the "Sort" command and one of the following commands from the shortcut menu:
Icon Description
Moves the selected object before all the other objects of the same layer
Moves the selected object to the lowest position in the same layer
Moves the selected object up by one position
Moves the selected object down by one position
Alternative procedure
1. Open the "Layers" palette of the "Layout" task card.
2. Navigate to the required object.
3. Hold down the mouse button, and drag the object in the tree topology to the required position
in the layer.
4. Now release the mouse button.
Result
The object is moved up or down.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1158 System Manual, 08/2011,
Resizing objects
Introduction
When you select an object, it is enclosed by a rectangle with handles. You have the following
options of resizing an object:
Drag the handles using the mouse.
Modify the "Size" property in the Inspector window.
Requirement
You have opened the work area containing at least one object.
Procedure
1. Select the object you want to resize.
The selection rectangle appears. The following figure shows a selected object:
2. Drag a resizing contact of the rectangle to a new position.
The size of the object changes.
The size of the object is aligned to the grid pattern, provided the "Snap to grid" function
is set.
Press <ALT> to disable this function while you drag the object.
Note
In order to scale the object proportionally, keep the <Shift> key pressed while changing
the size with the mouse.
Alternative procedure
1. In the Inspector window, select "Properties > Properties > Layout".
2. Enter the size of the object under "Position & Size".
Result
The object now appears with its new size.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1159
Selecting multiple objects
Introduction
Select all objects you want to align with each other or to change global properties. This
procedure is called "multiple selection."
The Inspector window shows all the properties of the selected objects.
You now have several options of selecting multiple objects:
Draw a selection frame around the objects.
Hold down the <Shift> key, and click the required objects.
Selection frame of a multiple selection
The selection frame surrounds all objects of a multiple selection. The selection frame is
comparable with the rectangle that surrounds an individual object.
The selection frame is not visible. When you have made your multiple selection, the following
frame is displayed:
The reference object is indicated by the rectangle around it.
The other selected objects are indicated by a dashed-line frame.
Specifying a reference object
The reference object is the object upon which the other objects are oriented. The reference
object is framed by a rectangle with handles. The following figure shows a reference object
with two other selected objects:
You have the following options to specify the reference object:
Select the objects via multiple selection. The object selected first is then the reference
object.
Draw a selection frame around the objects. The reference object compiled automatically.
If you wish to specify a different object within the selection as the reference object, click on
the desired object. This action does not cancel your multiple selection.
Requirement
You have opened the work area containing at least two objects.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1160 System Manual, 08/2011,
Selecting multiple objects with a selection frame
1. Position the mouse pointer in the work area close to one of the objects to be selected.
2. Hold down the mouse button, and draw a selection frame around the objects to be selected.
Or:
1. Hold down the <Shift> key.
2. Click the relevant objects, working in succession.
All the selected objects are identified by frames.
The object selected first is identified as reference object.
Note
To remove an object from the multiple selection, press <SHIFT>, hold it down and then
click the relevant object once again.
Result
Multiple objects are selected. One of those is identified as the reference object. You can now
perform the following steps:
Changing the object properties of all the objects
Resizing all the objects by the same ratio, by dragging the selection frame to increase or
reduce the size
Moving all the objects in one group
Aligning the objects to the reference object
Repositioning and resizing multiple objects
Possible modifications
After you have selected multiple objects, you edit them:
Shift using the mouse
To change the absolute position of the marked objects, position the mouse pointer over
an object, and shift the multiple selection with the mouse button pressed.
To resize all the objects by the same ratio, grab the resizing handles of the reference
object.
Move over the work area with the icons of the toolbar
Change the position of the marked objects with respect to each other
Align the height and width of the marked objects
Moving with the shortcut menu commands of the work area
Change the position of the marked objects with respect to each other
Align the height and width of the marked objects
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1161
Aligning objects
Procedure
1. Select the objects via multiple selection.
2. Specify an object as the reference object.
3. Select the desired command in the toolbar or the shortcut menu - see table below.
The selected objects will be aligned.
Aligning objects flush
The selected objects will be aligned flush to the reference object.
Icon Description
Aligns the selected objects to the left edge of the reference object.
Aligns the selected objects to the vertical center axis of the reference object.
Aligns the selected objects to the right edge of the reference object.
Aligns the selected objects to the upper edge of the reference object.
Aligns the selected objects to the horizontal center axis of the reference object.
Aligns the selected objects to the lower edge of the reference object.
Centers the selected objects to the center points of the reference object.
Centers the selected objects vertically in the screen.
Distributing objects evenly
You need at least three selected objects. A reference object is not required.
1. Select the objects.
2. Click one of the buttons "Distribute horizontally equal" or "Distribute vertically equal."
The selected objects are distributed at equal distances.
The following screen shows how you align the vertical spacing of the selected objects:
Icon Description
Aligns the horizontal distance between the objects.
The position of the objects on the extreme left and right side remains unchanged. All
other objects are distributed evenly between them.
Aligns the vertical distance between the objects.
The position of the objects at the extreme top and bottom (right and left) remains
unchanged. All other objects are distributed evenly between them.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1162 System Manual, 08/2011,
Harmonizing the object size
1. Select the objects.
2. Now, click one of the following buttons: or or
The size of the selected objects is matched to each other.
The following screen shows how the selected objects are adapted to the height of the reference
object:
Icon Description
Aligns the selected objects to the width of the reference object.
Aligns the selected objects to the height of the reference object.
Aligns the selected objects to the width and height of the reference object.
Rotating objects
Introduction
You can rotate a suitable object clockwise or counterclockwise around its center axis in steps
of 90.
Note
Not all the objects can be rotated. Some objects that can be rotated in screens cannot be
rotated in reports.
You can also rotate multiple objects using the multiple selection function. Certain WinCC
objects such as buttons cannot be rotated.
The alignment of elements in an object will change in a rotated object. The following figure
shows how a rectangle and an ellipse behave under the different commands for rotating an
object:
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1163
90 to the right
180 to the right
3x 90 to the right
90 to the left
Requirement
You have opened the work area containing at least one object.
Procedure
1. Select the object that you want to rotate.
2. Click one of the following toolbar icons:
, to rotate the object clockwise around its center point. The angle of rotation is 90.
, to rotate the object counterclockwise around its center point. The angle of rotation is
90.
, to rotate the object clockwise by 180.
Result
The object is shown at its new angle.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1164 System Manual, 08/2011,
Flipping objects
Introduction
You can flip an object along its vertical or horizontal center axis. The alignment of elements in
an object will change when you flip an object. The following figure shows how a rectangle and
an ellipse behave under the different commands for flipping an object.
horizontal
horizontal + vertical
vertical
Requirement
You have opened a screen which contains at least one object.
Procedure
1. Select the object that you want to flip.
2. Click the "Flip" command in the shortcut menu and select one of the options displayed:
, to flip the selected object along its vertical center axis.
, to flip the selected object along its horizontal center axis.
Result
The object is shown at its flipped position.
9.6.3 Operation in Runtime
9.6.3.1 Printing reports
Printing a report in Runtime
If you have configured an object with the "PrintReport" system function, the operator can print
out a report in Runtime. To do this, the operator uses the "Print report" button on a screen.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1165
The operator can set or change further settings for the report. The report is output to the default
printer.
See also
Printing reports (Page 1151)
Principles for preparation of reports (Page 1146)
9.6.4 Objects in reports
9.6.4.1 Audit report
Application
With the audit report, the content of the audit trail of a HMI device is output as a report.
Requirements
The "audit report" object is available only if the following requirements are met:
The HMI device supports a GMP-compliant configuration.
GMP-compliant configuration is active in the Runtime settings of the HMI device.
Note that operator actions and system operations are only recorded if a corresponding log is
configured.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1166 System Manual, 08/2011,
Layout
In the Inspector window the position, shape, style, color and font types of the object are
customized. In particular, the following can be adjusted:
Visibility of the comment
See also
Enabling GMP compliant configuration (Page 2543)
Audit Trail (Page 2545)
Creating an audit trail (Page 2546)
Principles for preparation of reports (Page 1146)
Reporting an audit trail (Page 2554)
Audit Trail reporting (Page 2555)
Parameters for the audit trail report (Page 2556)
Printing out an audit trail report (Page 2559)
9.6.4.2 Date/time field
Application
The "Date/time field" object shows the system time of the HMI device or the date and / or time
of a connected tag. The layout depends on the language setting on the HMI device.
Layout
In the Inspector window, you customize the position, shape, style, color, and font types of the
object. In the "Properties > Properties > General" dialog, you can adapt the following properties
in particular:
Long date/time format: This setting defines the format displayed for the data and / or time.
System time: Specifies whether to use the system time of the HMI device, or the data and /
or time of a connected tag.
Long date/time format
Option Description
"Enabled" Date and / or time is fully displayed, for example "Sunday, December 31, 2000
10:59:59 AM"
"Disabled" Date and / or time is displayed in abbreviated form, e.g. "12/31/2000 10:59:59
AM"
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1167
System time
Option Description
"Enabled" The system time of the HMI device is displayed
"Disabled" The date and / or time of the connected tag is displayed
Select a tag of the "DateTime" data type, e.g. an internal tag. Information about
data types which are available for connection to other PLCs can be found in
the documentation about the respective communication drivers.
See also
Create a report (Page 1148)
Principles for preparation of reports (Page 1146)
9.6.4.3 I/O field
Application
The "I/O field" object is used to enter process values.
Layout
In the Inspector window, you customize the position, shape, style, color and font types of the
object. You can adapt the following properties in particular:
Display format: Specifies the format in which the values in the I/O field are output.
Note
The "I/O field" object is also available in "Screens" editor. In reports, the object only outputs
data. Accordingly only configure the output of data for application in reports.
Display format
The "display format" for the output of values is specified in "Properties > Properties > General
> Format", in the Inspector window.
Layout
"Binary" Output of values in binary form
"Date" * Output of date specifications. The format depends on the language setting on the
HMI device.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1168 System Manual, 08/2011,
Layout
"Date/time" * Output of date and time specifications. The format depends on the language
setting on the HMI device.
"Decimal" * Output of values in decimal form.
"Hexadecimal" Output of values in hexadecimal form.
"Time" * Output of time specifications. The format depends on the language setting on the
HMI device.
"Character string" Output of strings.
*: not in Runtime Professional
Avoid overlaps with output fields
If several I/O fields are configured as output fields with a transparent background in a report,
these I/O fields may overlap. The transparent part of the one field covers the digits of the other
field. This may cause display problems in the report. In order to avoid such overlaps, set the
margins of the I/O fields to zero in the object properties under "Properties > Properties >
Appearance". Activate "Properties > Properties > Layout > Fit object to contents."
See also
Create a report (Page 1148)
Principles for preparation of reports (Page 1146)
9.6.4.4 Graphic view
application
The "Graphic view" object is used to display graphics.
Layout
In the Inspector window, you customize the position, shape, style, color and font types of the
object. You can adapt the following properties in particular:
Graphic: Specifies the graphic file that is displayed in the object.
Stretch graphic: Specifies the automatic size stretching for objects with graphics.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1169
Inserting graphics
The following graphic format is used in the "Graphic view" object: *.bmp, *.tif, *.png, *.ico, *.emf,
*.wmf, *.gif, *.jpg or *.jpeg. You may also use graphics as OLE objects in the Graphic view .
1. In the Inspector window, select "Properties > Properties > General":
2. Select the graphic you want to add in the drop-down list under "Graphic".
The graphic preview is shown in the right pane.
3. Click "Assign" to insert the graphic in the Graphic view .
Stretch graphic
Whether a graphic displayed in a Graphic view is stretched to the size of the Graphic view in
runtime is specified in the Inspector window.
1. In the Inspector window, select "Properties > Properties > Layout".
2. Select one of the following options from the "Fit to size" area:
Fit object size to content
Fit content to object size
9.6.4.5 Graphic I/O field
Application
With the "Graphic I/O field" object, the graphics of a graphics list are displayed, depending on
the tag value. In the Inspector window, the tag and graphics list are configured, under
"Properties > Properties > General":
Note
The "Graphic I/O field" object is also available in "Screens" editor. In reports, the object only
outputs data. Accordingly only configure the output of data for application in reports.
Layout
Customize settings for color, frame, position and object size in the inspector window. In
particular, the "Fit to size" is defined by specifying whether the object is adjusted to the graphics
during output in the report or the graphic is adjusted in the object.
See also
Create a report (Page 1148)
Objects in reports (Page 1166)
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1170 System Manual, 08/2011,
9.6.4.6 Alarm report
Application
Use the "Alarm report" object to output alarms of the selected alarm classes from the alarm
buffer or alarm log to the report.
Layout
In the Inspector window, you customize the position, shape, style, color, and font types of the
object. You can adapt the following properties in particular:
Source
Alarm classes
Time range
Additional settings for the display
Visible columns
Specifying the source
Under "Properties > Properties > General > Settings > Source", specify whether to display
alarms from the alarm buffer, or from the alarm log. Select the alarm log in the "Alarm log"
dialog.
Specifying alarm classes
Under "Properties > Properties > General > Alarm classes, enable the alarm classes for the
alarms output to the report.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1171
Specifying the time range
If you want to restrict alarm output to a specific time range, select the start and end tags for
the time range in the "Properties > Properties > General > Time range" dialog. The tag must
be of the "DateTime" type.
Additional settings for the display
Under "Properties > Properties > General > Settings, specify the following settings for the
display in the alarm report:
Under "Sorting", specify whether to start the display with the oldest or most recent alarm.
Under "Lines per entry", specify the number of lines to be available for each alarm. The
required number of lines depends on the following factors:
Number and width of the selected columns for the output
Font size used
Paper format of the printer
Select "Visible heading" to enable the display of column headers.
Select "Display milliseconds" to enable the display of milliseconds for time data.
Visible columns
Under ""Properties > Properties > Layout > Visible columns", enable the columns to be
displayed in the alarm report.
See also
Create a report (Page 1148)
Principles for preparation of reports (Page 1146)
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1172 System Manual, 08/2011,
9.6.4.7 Recipe report
application
Use the "Recipe report" object to output the elements of recipe data records in the report.
Layout
In the Inspector window, you customize the position, shape, style, color, and font types of the
object. You can adapt the following properties in particular:
Recipe
Data record
Format
Visible entries
Selecting a recipe
Specify the recipes to be output in the recipe report under "Properties > Properties > General
> Recipe". You can define the recipes based on their recipe name, or on a range of recipe
numbers. Under "First recipe" and "Last recipe", enter a value or select a tag.
You can also choose to display all recipes.
Selecting a data record
Under "Properties > Properties > General > Data record", specify which data records of the
selected recipes are to be output in the recipe report. You can define the data records based
on the data record name, or on a range of data record numbers. Under "First recipe" and "Last
recipe", enter a value or select a tag.
You can also choose to display all data records of the selected recipes.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1173
Format
In the "Format" field of the "Properties > Properties > Layout > Settings" dialog, specify whether
to output the data records as a table in column format or line report format.
WinCC updates the preview in the detail page accordingly.
Visible entries
Under ""Properties > Properties > Layout > Visible entries", enable the columns to be displayed
in the recipe report. Select "Show headings" to enable the display of column headers.
See also
Create a report (Page 1148)
Principles for preparation of reports (Page 1146)
9.6.4.8 Page number
application
Use the "Page number" object to output the current page number in the report.
Layout
In the inspector window, change the settings for color, font, position and object size. In
particular, specify "Size adaptation":
Fit to size
Under "Properties > Properties > Layout > Fit to size", the "Fit object to content" option is used
to specify whether WinCC adjusts to the object size of the field content:
Enabled "Fit object to contents" option:
WinCC automatically adjusts the size of the object to the configured format. The font size
and field length are defined under "Properties > Properties > General > Text".
The object can be moved in the working area, however, the size cannot be changed. During
report output, the entire field content is output at the time of report output.
Disabled "Fit object to contents" option:
Customize the field size by yourself. WinCC does not resize the field for report output. It
can be possible that not all content of the field is output in the report. Therefore, configure
a field of sufficient size.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1174 System Manual, 08/2011,
See also
Create a report (Page 1148)
Principles for preparation of reports (Page 1146)
9.6.4.9 Symbolic I/O field
application
With the "Symbolic I/O field" object, the content of a text list in reports is displayed, depending
on the tag value. In the inspector window, the tag and text list is configured under "Properties
> Properties > General":
Layout
In the inspector window, change the settings for color, frame, font, position and object size. In
particular, the "Fit to size" is defined, by specifying whether the object size is adjusted to the
text during output in the report or not.
Note
The "Symbolic I/O field" object is also available in "Screens" editor. In reports, the object only
outputs data. Accordingly only configure the output of data for application in reports.
See also
Create a report (Page 1148)
Principles for preparation of reports (Page 1146)
9.6.4.10 Text field
Application
The "Text field" is a closed object which you can fill with a color.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1175
Layout
In the Inspector window, you customize the position, shape, style, color and font types of the
object. You can adapt the following properties in particular:
Text: Specifies the text for the text field.
Size of text field: Defines whether the size of the object is adapted to the space required
by the largest list entry.
Text
Specify the text for the text field in the Inspector window.
1. In the Inspector window, select "Properties > Properties > General":
2. Enter a text.
For texts over several lines you can set a line break by pressing the key combination <Shift
+ Enter>.
Size of text field
In the Inspector window, you can define whether the size of the object is adapted to the space
required by the largest list entry.
1. In the Inspector window, select "Properties > Properties > Layout".
2. Activate "Auto-size".
Otherwise you can set the size manually. Deactivate "Auto-size". Press the mouse button and
drag the text field to the required size.
Visualizing processes (Advanced)
9.6 Working with reports
WinCC Advanced V11.0 SP1
1176 System Manual, 08/2011,
9.7 Configuring user administration
9.7.1 Field of application of the user administration
Principle
The access protection controls access to data and functions in Runtime. This feature protects
your applications against unauthorized operation. Safety-related operations are already limited
to specific user groups when a project is being created. To this purpose you set up users and
user groups that you equip with characteristic access rights, so-called authorizations. You then
configure the authorizations required for operation of safety-related objects. Operators only
have access, for example, to specific operator controls. Commissioners, for example, have
unlimited access in Runtime.
Definition
You administer users, user groups and authorizations centrally in the user administration of
WinCC. You transfer users and user groups together with the project to the HMI device. The
users and passwords are managed on the HMI device in the User view.
Application example
You configure the "Service" authorization so that only service technicians have access to the
configuration parameters. You assign the authorization to the "Service technician" user group.
This allows all members of this group to set the protected configuration parameters.
CAUTION
Access protection does not protect against incorrect operations. It is your job to ensure that
only authorized personnel with appropriate training will design, commission, operate and
maintain plants and machines.
Access protection is not suitable for defining work routines and monitoring their observance.
9.7.2 Form of the user administration
Introduction
In case of a project in manufacturing engineering, the environment at the equipment
manufacturer has to be differentiated from the environment at the end customer as plant
operator.
The equipment manufacturer allows users, for example Mr. Foreman, a specific access within
the application or HMI device. However, a user Foreman does not exist at the end customer.
The machine manufacturer cannot know the end users and the tasks they have to perform for
configuration. The final users are usually set after commissioning at the end customer.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1177
Program
WinCC Workbench
Administrator Configuration
User group
"Service Technician"
Authorizations
Miller
Smith group
Foreman
Operator
controls
Edit recipe data records
Change system parameters
Log process values
Mr. Foreman
Block
Process
values
Recipe
System
parameters
Logging
Principle
To minimize the work required for management, authorizations are assigned via user groups
and not directly to individual users.
A user group assembles configured authorizations according to common jobs. For example,
all permissions required for a service job are collected in a "Service technician" group. When
you create a user who should be responsible for servicing, you simply assign him to the
"Service technician" group.
The user view enables user administration in Runtime. Use user view to create, delete and
assign an authorization to users in Runtime.
The user administration separates the administration of the users from the configuration of the
authorizations. This ensures flexibility at the access protection.
Defaults can be set for the user administration during the configuration phase in the
Engineering System.
9.7.3 Basics
9.7.3.1 Users
Introduction
You can create users in the "Users" tab of the "User administration" editor and assign them to
user groups. The "Users" tab is part of the user administration in WinCC.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1178 System Manual, 08/2011,
Open
To open the "Users" tab, double-click "User administration" in the project window.
Work area
The users are managed in the work area:
You create or delete users.
You assign users to user groups.
Note
You can assign a user to exactly one user group.
Inspector window
When you select a user, you can change the password in the "General" group. Under
"Automatic logoff" you can specify if the user is to be automatically logged off by the HMI device
when there is no operator activity after the specified time.
9.7.3.2 Users work area
Introduction
The "Users" work area lists the users and user groups in table form. You administrate the users
and assign them to a user group.
Principle
The work area consists of the "Users" and "Groups" tables.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1179
The "Users" table shows the existing users. When you select a user in this table, the "Groups"
table shows the user group to which the user belongs.
9.7.3.3 User groups
Introduction
You can create users and authorizations in the "User groups" tab of the "User Administration"
editor. The "User groups" tab is part of the user administration in WinCC.
Open
Double-click the "User administration" in the project window. Open the "User groups" tab.
Work area
The user groups and authorizations are managed in the work area:
You create new user groups and authorizations or delete them.
You assign the authorizations to the user groups.
Inspector window
When a user group or an authorization is selected, you can edit the name in the "General"
group. You can also enter a brief description in the "Comment" group.
9.7.3.4 User groups work area
Introduction
The "User groups" work area shows a table of the groups and their authorizations. You
administer the user groups and assign authorizations to them.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1180 System Manual, 08/2011,
Principle
The work area consists of the "Groups" and "Authorizations" tables.
The "Groups" table shows the existing user groups. When you select a user group in this table,
the "Active" column of the "Authorizations" table shows the authorizations which were assigned
to the user group.
The number of the user group and of the authorization is assigned by the user administration.
The designations and descriptions are assigned by you.
The number of predefined authorizations are fixed. Authorizations that you create can be freely
edited. Ensure that the assigned numbers are unique.
9.7.3.5 Settings for the user administration
Introduction
In the "Runtime settings > User administration" editor, configure the security settings for users
and their passwords in runtime.
Open
Double-click the "Runtime settings" editor in the project window. Click "User administration."
Work area
You carry out the settings for the validity of passwords in runtime in the work area. You
determine the complexity of the password, for example.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1181
Effects in runtime
The security settings have the following effects in runtime, depending on the configuration.
"Runtime services" group
"Enable limit for logon attempts" check box selected
The number entered in the "Number of incorrect logon attempts" box defines the number
of logon attempts a user is allowed before being assigned to the "Unauthorized" group.
"Enable limit for logon attempts" check box not selected
The user has an unlimited number of logon attempts in runtime.
"Number of incorrect logon attempts" field
If you enter "4" in the field, for example, and the fourth logon attempt fails, the user is
automatically assigned to the "Unauthorized" group.
You can specify 1 to 9 attempts.
"Logon only with password" check box
When the check box is selected, the user will be authenticated by the password. The
user name is not required.
To match users to passwords, you cannot configure passwords more than once.
"Hierarchy level" group
"Group-specific rights for user administration" check box
When this check box is selected, administrators only manage users whose group
number is less than or equal to their own.
For example, an administrator whose group number is 5 can only manage users whose
group number is less than or equal to 5. This means that the administrator can assign
users only to groups with a group number less than or equal to 5.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1182 System Manual, 08/2011,
"Password" group
"Enable password aging" checkbox selected
The password expires after the number of days set in the "Validity of the password
(days)" field.
The "Password aging" column is selected in the "User groups" editor. This enables you
to specify group-by-group, if the passwords should expire or if the password generations
should be saved. Passwords never expire for groups for which password aging is not
enabled.
"Prewarning time (days)" field
The user is informed that the password will expire the specified number of days before
the password expires.
"Password generations" field
If the user changes the password, the new password must be different from the specified
number of previous passwords. The number of password generations ranges from 1 to
5.
"Password complexity" group
"Must include special characters" check box selected
The user must enter a password containing at least one special character at any position.
"Must include number" check box selected
The user must enter a password containing at least one number at any position.
"Minimum password length" field
The user must enter a password with a minimum length, as specified in the "Minimum
password length" field.
The minimum length of the password is 3 characters.
9.7.3.6 Settings for the user administration
Introduction
In the "Runtime settings > User administration" editor, configure the security settings for users
and their passwords in runtime.
Open
Double-click the "Runtime settings" editor in the project window. Click "User administration."
Work area
You carry out the settings for the validity of passwords in runtime in the work area. You
determine the complexity of the password, for example.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1183
Effects in runtime
The security settings have the following effects in runtime, depending on the configuration.
"Runtime services" group
"Change initial password" check box selected
The user must change the administrator-assigned password when logging on for the
first time.
"Change logoff time" checkbox selected
Simple user rights are sufficient for changing the logoff time.
The logoff time is the period after which the user administration automatically logs off a
user when no operator activity is detected in the system.
The logoff time for the SIMATIC Logon user corresponds to the logoff time of the default
user, "Admin".
Any user changes of the logoff time are logged in the Audit Trail.
"Enable limit for logon attempts" check box selected
The number entered in the "Number of incorrect logon attempts" box defines the number
of logon attempts a user is allowed before being assigned to the "Unauthorized" group.
"Enable limit for logon attempts" check box not selected
The user has an unlimited number of logon attempts in runtime.
"Number of incorrect logon attempts" field
If you enter "4" in the field, for example, and the fourth logon attempt fails, the user is
automatically assigned to the "Unauthorized" group.
You can specify 1 to 9 attempts.
"Logon only with password" check box
When the check box is selected, the user will be authenticated by the password. The
user name is not required.
To match users to passwords, you cannot configure passwords more than once.
"Hierarchy level" group
"Group-specific rights for user administration" check box
When this check box is selected, administrators only manage users whose group
number is less than or equal to their own.
For example, an administrator whose group number is 5 can only manage users whose
group number is less than or equal to 5. This means that the administrator can assign
users only to groups with a group number less than or equal to 5.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1184 System Manual, 08/2011,
"Password" group
"Enable password aging" checkbox selected
The password expires after the number of days set in the "Validity of the password
(days)" field.
The "Password aging" column is selected in the "User groups" editor. This enables you
to specify group-by-group, if the passwords should expire or if the password generations
should be saved. Passwords never expire for groups for which password aging is not
enabled.
"Prewarning time (days)" field
The user is informed that the password will expire the specified number of days before
the password expires.
"Password generations" field
If the user changes the password, the new password must be different from the specified
number of previous passwords. The number of password generations ranges from 1 to
5.
"Password complexity" group
"Must include special characters" check box selected
The user must enter a password containing at least one special character at any position.
"Must include number" check box selected
The user must enter a password containing at least one number at any position.
"Minimum password length" field
The user must enter a password with a minimum length, as specified in the "Minimum
password length" field.
The minimum length of the password is 3 characters.
"External Runtime services" group
"SIMATIC Logon" checkbox selected
A connection is established to the server. Authorization is performed via SIMATIC Logon.
"Encrypted transfer" checkbox selected
The data is encrypted before it is transferred to the server.
9.7.4 Building up and structuring a user administration
9.7.4.1 Basics of user administration
Principle
This section addresses four target groups. The topics are organized correspondingly. The
target groups serve as examples for different groups of persons who use the user
administration.
1. Administrator OEM
2. Administrator RT
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1185
3. Planners
4. Operator
As Administrator OEM you create the user groups, users and authorizations for Runtime in
the Engineering System of, for example, an equipment manufacturer.
As Administrator RT you administer users in Runtime by means of the "User view."
As the project engineer you assign the authorizations to the user groups in the Engineering
System. In addition, you configure the authorizations for objects.
As Operator you log on in runtime. You can only access a protected object if you have the
required authorization.
Note
The Administrator RT target group already exists in the Runtime user administration as the
predefined user group "Administrator group." For a better understanding the predefined user
groups and authorizations are not used below.
9.7.4.2 Administering users for Runtime
Creating an authorization
Introduction
You create an authorization and assign it to one or more user groups.
Requirements
The "User groups" work area is open.
Procedure
1. Double-click "Add" in the "Authorizations" table.
2. Enter "Archive data" as the name of the authorization.
3. Enter a brief description as the "Comment."
See also
Creating a user group (Page 1187)
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1186 System Manual, 08/2011,
Creating a user group
Introduction
User groups are created so that you do not have to assign an authorization to every single
user. You create a user group, assign authorizations and then assign users to it.
Note
The name of the user group has to be unique within the project. Otherwise the input is not
accepted.
Note
Using SIMATIC Logon
Ensure that the names of the user groups in Windows and WinCC are identical.
Requirements
The "User groups" work area is open.
Procedure
1. Double-click "Add" in the "Groups" table.
2. Enter "Operators" as the "Name" of the user group.
3. Change the "Number" of the user group as required.
4. Enter "Display name" of the "Operators" user group.
5. Enter a brief description as the "Comment".
In runtime, the user view shows the display name of the user group. The display name of the
user group depends on the language. You can specify the name in several languages and
switch between languages in runtime.
See also
Creating an authorization (Page 1186)
Example: Configuring a button with logon dialog box (Page 1211)
Example: Logging the logon and logoff events (Page 1212)
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1187
Assigning an authorization
Introduction
When you allocate an authorization to a user group, all assigned users have this authorization.
Requirements
An "Archive data" authorization has been created.
An "Operators" user group has been created.
The "User groups" work area is open.
Procedure
1. Click on the "Operators" user group in the "Groups" table. The "Authorizations" table shows
all authorizations.
2. Activate the "Archive data" authorization in the "Authorizations" table.
NOTICE
The "Archive data" authorization is only a designation and does not having any relation
to the function "Archiving." You have to establish this relation yourself. To do so, configure
the "StartArchiving" system functions at a control button and select "Archive data" as the
"Authorization."
Creating users
Introduction
You create a user so that users can log on with their user names in runtime after loading to
the device.
As an alternative, you can create and change users by means of the "User view" in Runtime.
In order for a created user to have authorizations you have to assign him to a user group and
allocate authorizations to the user group.
The logon is successful when the user name entered during the logon matches a user in
Runtime. In addition, the entered password must agree with the stored password of the user.
Note
Note that the entry is case-sensitive.
Requirements
The "Users" work area is open.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1188 System Manual, 08/2011,
Procedure
1. Double-click "Add" in the "Users" table.
2. Enter "Foreman" as the user name.
Note
The user name must be unique within the project. Otherwise the input is not accepted.
3. Click the button in the "Password" column. A dialog box for entering the password is
displayed.
4. Enter the password of the user.
5. To confirm the password enter it a second time in the lower field.
6. Close the dialog box by using the icon.
7. If a user is to be logged off after a specific time period, activate "Automatic logoff".
8. Click in the "Logoff time" column. The preset value for "Logoff time" is 5 minutes.
9. Enter a brief description as the "Comment".
Assigning a user to a user group
Introduction
When you assign a user to a user group, the user has the authorizations of the user group.
Note
You have to assign a user to exactly one user group. The assignment is checked during the
consistency check and generation of the project.
Requirements
The user "Foreman" has been created.
An "Operators" user group has been created.
The "Users" work area is open.
Procedure
1. Click on the "Foreman" user in the "Users" table. The "Groups" table shows all user groups.
2. Activate the "Operators" user group in the "Groups" table.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1189
Managing users
Introduction
In the work area, you can administer users and assign them to user groups.
Requirements
The "Users" work area is open.
Changing the user name
1. In the "Users" table, double-click the field in the "Name" column to change the user name.
2. Change the user name.
3. Confirm your entry with <Return>.
Alternatively, select the user in the work area. Change the user name under "Properties >
Properties > General" in the Inspector window.
Changing the password of the user
1. Click the button in the "Password" column of the "Users" table. A dialog for entering the
password opens.
2. In the "Enter password" field, enter the new password.
3. Reenter the new password in the "Confirm password" field.
4. Confirm your entry with <Return>.
Alternatively, select the user in the work area. Change the password under "Properties >
Properties > General" in the Inspector window.
Displaying invisible columns
1. Position the mouse cursor on the title of the "Users" table.
2. Right-click to open the shortcut menu and enable the display of the "Logoff time" column,
for example.
Changing the logoff time of the user
1. In the "Users" area, double-click on the field in the "Logoff time" column to change the logoff
time.
2. Change the logoff time.
3. Confirm your entry with <Return>.
Alternatively, select the user in the work area. Change the logoff time under "Properties >
Properties > Automatic logoff" in the Inspector window.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1190 System Manual, 08/2011,
Deleting a user
1. Select the line of the user to be deleted.
2. Open the shortcut menu with the right mouse button and select the "Delete" command.
Note
Predefined users cannot be deleted.
Managing user groups
Introduction
In the workplace you administer user groups and assign authorizations for use in runtime.
Requirements
The "User groups" work area is open.
Changing the name of the user group
1. In the "Groups" table, double-click the field in the "Name" column to change the name of
the user group.
2. Change the name of the user group.
3. Confirm your entry with <Return>.
Alternatively, select the user group in the work area. Change the name under "Properties >
Properties > General" in the Inspector window.
Note
Predefined user groups cannot be deleted.
Displaying invisible columns
1. Position the mouse cursor on the title of the "Users" table.
2. Right-click to open the shortcut menu and enable the display of the "Display name" column,
for example.
Changing the displayed name of the user group
1. In the "Groups" table, double-click the field in the "Display name" column to change the
display name of the user group.
2. Change the displayed name of the user group.
3. Confirm your entry with <Return>.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1191
Alternatively, select the user group in the work area. Change the display name under
"Properties > Properties > General" in the Inspector window.
Deleting a user group
1. Mark the line of the user group to be deleted.
2. Open the shortcut menu with the right mouse button and select the "Delete" command.
Note
Predefined user groups cannot be deleted.
Changing the name of the authorization
1. In the "Authorizations" table, double-click the field in the "Name" column to change the
name of the authorization.
2. Change the name of the authorization.
3. Confirm your entry with <Return>.
Alternatively, select the authorization in the work area. Change the name under "Properties >
Properties > General" in the Inspector window.
Deleting authorizations
1. Mark the line of the authorization to be deleted.
2. Open the shortcut menu with the right mouse button and select the "Delete" command.
Note
Predefined authorizations cannot be deleted.
9.7.4.3 Managing users on the server
Central user administration using SIMATIC Logon
Introduction
To manage users and user groups for several applications or HMI devices, activate SIMATIC
Logon.
Principle
SIMATIC Logon is a tool for system-wide user administration. If you use SIMATIC Logon, the
users are centrally managed outside the application or HMI device.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1192 System Manual, 08/2011,
You configure the user groups and their permissions as you usually do with the local user
administration in WinCC. You assign identical names to the user groups on the server and in
WinCC. Authorizations are assigned in Runtime to a user group when the names are identical.
You do not have to create users in WinCC flexible because they are taken dynamically from
Windows user management during the logon process. The application or HMI device forwards
each logon or password change to SIMATIC Logon for processing.
Note
SIMATIC Logon is a product requiring a license. For more information on SIMATIC Logon
go to <http://support.automation.siemens.com>.
Enter the ID "34519648" in the search field and start searching. The "SIMATIC Logon -
Electronic Signature" manual is available to download.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1193
Log on process via SIMATIC Logon Service
The following diagram illustrates the process that runs automatically when a user logs onto
Runtime.
The application opens the logon dialog box
1. Query: Login and password
The user enters the logon data in the logon dialog box:
<Login>
<Password>
Logon
dialog box
2. Transfer: Logon data
Logon data is verified
3. Query: Does Windows recognize the user?
Logon data is verified
on the local computer or in the domain
4. User authentication in progress
SIMATIC
Logon
Service
Determining user data:
Operating
system
User and group
administration
Transfer of user data:
6. Transfer: full user name,
group membership,
password age
5. Query: Which user data
is known?
Verifying and transferring user data:
7. Transfer: full user name,
group membership
8. Determining roles
9. Setting rights in accordance with role
Results: The user can implement the role functions.
Applications
which use
SIMATIC Logon
functions
Making settings on the server
Introduction
Perform the following steps on your sever to ensure correct operation of SIMATIC Logon.
Procedure
1. Install SIMATIC Logon Services.
2. Create the user group in the user administration of the operating system.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1194 System Manual, 08/2011,
3. Create the users in the user administration of the operating system.
NOTICE
Users of SIMATIC Logon must be members of a user group of the operating system.
Members of a subgroup cannot be logged on.
4. Assign the new users to a group.
5. Transfer the licenses for each HMI device on the server.
Note
You can find more detailed information in the documentation supplied with SIMATIC Logon.
Note
The password policies stored on the server are valid if users are authorized by means of
SIMATIC Logon.
The logoff time for the SIMATIC Logon user corresponds to that of the predefined
"Administrator" user.
Logging on using SIMATIC Logon
Requirements
User administration exists.
The groups created in WinCC agree with the Windows groups on the server.
There is a server with SIMATIC Logon Service installed.
NOTICE
A user may only be a member of one user group in WinCC. When a user is a member of
several user groups on the server, only one of these user groups can be made known in
WinCC.
"Administrators" and "Users" are predefined groups in both Windows and WinCC. Any new
user created in Windows is automatically a member of the "Users" group. A user will be a
member of two groups if assigned to a new group, for example, to the "SL user" group.
Remove this user from the "Users" group of the operating system to enable logon of this user
using SIMATIC Logon.
A system message in Runtime always confirms the successful logon of a user on the server.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1195
Procedure
1. Open the "Runtime settings > User administration" editor in the Project window.
2. Select "External Runtime services > SIMATIC Logon".
3. Enter the name or IP address of the SIMATIC Logon server in the "Server name" text box.
Note
Make sure your SIMATIC Logon Server always has the same IP address if you use IP
addresses.
4. Enter the port number for TCP/IP communication in the "Port number" text box. The valid
range of values lies between 1024 and 49151. The preset port number is "16389" and used
by SIMATIC Logon as the default.
5. Enter the Windows domain or the logon server in the "Windows domain" text box, including
the user data.
Enter the name of the sever to access users on the logon server.
Enter the name of the domain if the logon sever is in a domain and you wish to access
users of the domain.
Note
Local Windows users are not accepted when the logon server is in a domain.
6. Activate the "Encrypted transmission" check box in order to encrypt the data before sending
it to the server.
Emergency user
If the server cannot be accessed, all local users that were created in WinCC user administration
can also be used as emergency users.
Emergency users have the rights of the user group to which they were assigned.
Note
For further information, refer to the included SIMATIC Logon documentation.
This documentation is available at: [SIMATIC Logon installation directory] \manuals
9.7.4.4 Administering users in Runtime
Users in runtime
Principle
You create users and user groups and assign authorizations to them. You configure objects
with authorizations. After download to the HMI device, all objects which were configured with
an authorization are protected against unauthorized access in Runtime.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1196 System Manual, 08/2011,
User view
When you configure a user view in the Engineering System, you administer users in this user
view following download to the HMI device.
CAUTION
Changes in the user view are effective immediately in Runtime. Changes in runtime are not
updated in the engineering system. When downloading the user administration to the HMI
device, all changes in the user view are overwritten after a security prompt and based on the
settings.
Users who have a "User administration" authorization have unlimited access to the user view.
This allows them to administer all users. Any other user has only limited access to the user
view for self administration.
See also
Complex user view (Page 1198)
Basic user view
Purpose
You configure a user view in the engineering system to also administer the users in
Runtime.
Structure
The user view shows the following in each line:
The user
The corresponding user group.
If no user is logged on, the user view is empty. The content of the individual fields is displayed
after logon.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1197
User view of an administrator
When an administrator is logged on, the user view shows all the users. The administrator
changes the user name and the password. The administrator creates new users and assigns
them to an existing user group.
User view of a user
When no administrator is logged on, the user view shows only the logged-on user. Users can
change their own passwords.
Complex user view
Purpose
You configure a user view in the engineering system to also administer the users in
Runtime.
Structure
The user view shows the following in each line:
The user
The encrypted password
The corresponding user group
The logoff time
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1198 System Manual, 08/2011,
If no user is logged on, the user view is empty. The content of the individual fields is displayed
after logon.
User view of an administrator
When an administrator is logged on, the user view shows all the users. The administrator
changes the user name and the password. The administrator creates new users and assigns
them to an existing user group.
User view of a user
When no administrator is logged on, the user view shows only the logged-on user. Users can
change their own passwords and logoff time.
See also
Users in runtime (Page 1196)
Configuring a user view
Introduction
You configure a user view in the Engineering System to also administer users in Runtime.
Requirements
A screen has been created.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1199
Procedure
1. Select the "User view" object from the "Controls" category in the toolbox.
2. Drag-and-drop the "User view" object into the screen.
3. Click on "Properties > Properties" in the Inspector window.
4. Specify the appearance of the "User view".
5. You can, for example, select " "Display mode > Fit to size > Fit object to contents".
Result
You have created a user view in the screen.
Creating users
Introduction
You create a user so that users can log on under their user name in runtime.
As an alternative, you can create users in the engineering system and download them to the
HMI device.
The logon is successful only when the user name entered during the logon matches a user in
runtime. In addition, the password entered at logon has to match that of the user.
Note
Note that the entry is case-sensitive.
You assign the user to a user group. The user then has the authorizations of the user group.
NOTICE
Runtime users must be assigned to a user group. The user group is created in the Engineering
System. The designation of the user group is language-dependent.
Requirements
The user view is open.
A "Group 2" user group has been created.
Procedure
1. Click "<New User>" in the user view. A dialog box opens.
2. Enter "Foreman" as the user name.
3. Press the <Return> button.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1200 System Manual, 08/2011,
4. Click "Password."
5. Enter the password of the user.
6. Press the <Return> button. The password is hidden.
7. Click in the "Group" column.
8. Select "Group 2" as the "Group".
9. Press the <Return> button.
10.Click in the "Logoff time" column.
11.Enter the time after which the user is logged off automatically.
Managing users in the simple user view
Introduction
If you have configured a user view in the engineering system, the users and user groups can
be managed in runtime.
CAUTION
Changes in the user view are effective immediately in runtime. Changes in runtime are not
updated in the Engineering System. When downloading the user administration to the HMI
device, all changes in the user view are overwritten after a security prompt and based on the
settings.
Requirements
Runtime is enabled.
The simple user view has been created.
The screen with the simple user view is open.
You have the default "User administration" authorization.
NOTICE
If you do not have a "User administration" authorization, you can only change your own
password and your logoff time.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1201
Changing a user name
1. Click on the line of the user whose name you want to change. A dialog box opens.
2. Enter a new user name.
3. Click "OK" to confirm your entry.
NOTICE
The user can then no longer log on with his previous password in runtime. If you delete
the name and press <Return>, the user is deleted.
Changing the user password in basic user display
1. Click on the line of the user whose password you want to change. A dialog box opens.
2. Enter a new password.
3. Click "OK" to confirm your entry.
NOTICE
The user can then no longer log on with his previous password in runtime.
If you delete the password in the basic user view and press <Return>, a message will be
generated. The message specifies that the password does not lie within the defined limits.
Changing the logoff time of the user
1. Click on the line of the user whose logoff time you want to change. A dialog box opens.
2. Enter a new logoff time.
3. Click "OK" to confirm your entry.
Deleting a user
1. Click the name of the user to be deleted.
2. Delete the name.
3. Press the <Return> button.
NOTICE
The user can no longer log on in runtime.
Assigning a user to a different user group
1. Click on the line of the user whose user group you want to change. A dialog box opens.
2. Click on the "User group" box.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1202 System Manual, 08/2011,
3. Select a user group.
4. Click "OK" to confirm your selection.
Managing users in the complex user view
Introduction
If you have configured a user view in the engineering system, the users and user groups can
be managed in runtime.
CAUTION
Changes in the user view are effective immediately in runtime. Changes in runtime are not
updated in the engineering system. When downloading the user administration to the HMI
device, all changes in the user view are overwritten after a security prompt and based on the
settings.
Requirements
Runtime is enabled.
A complex user view has been created.
The screen with the user view is open.
You have the default "User administration" authorization.
NOTICE
If you do not have a "User administration" authorization, you can only change your own
password and your logoff time.
Changing the user name
1. Enter a new user name in the "Users" column in the user display.
2. Confirm your entry with <Return>.
NOTICE
The user can then no longer log on with his previous password in runtime. If you delete
the name and press <Return>, the user is deleted.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1203
Changing the password of the user
Availability of complex user display in selected devices only.
1. Enter a new password in the "Password" column in the user display.
2. Confirm your entry with <Return>.
NOTICE
The user can then no longer log on with his previous password in runtime.
If you delete the password in the complex user view and press <Return>, the user will be
deleted.
Changing the logoff time of the user
1. Enter a new logoff time in the "Logoff time" column in the user display.
2. Confirm your entry with <Return>.
Deleting a user
1. Click the name of the user to be deleted.
2. Delete the name.
3. Press the <Return> button.
NOTICE
The user can no longer log on in runtime.
Assigning a user to a different user group
1. Activate the user group field for the corresponding user.
2. Select a user group.
3. Confirm your selection with <Return>.
Unlock locked out users
Unlock locked out users
The check box "Activate limit for login attempts" is activated in the "Runtime settings > User
administration".
The number 3 is entered in the field "Number of invalid login attempts".
If users have three failed attempts at login, e.g. by entering an incorrect password, they are
assigned to the "Unauthorized" group. The user loses all authorizations. The user can still log
on, but no longer has any authorizations. Only a user with administrator rights re-assigns the
unauthorized user to a user group.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1204 System Manual, 08/2011,
Exporting the user administration
Introduction
The users and user groups are transferred to the HMI device from the Engineering System. If
you have configured a user view, you administer the users at the HMI device via the user
view.
If a user has access to several HMI devices, the same user and the same password must be
configured on each HMI device. Create a standard for user administration of the different HMI
devices. Export the users and passwords on an HMI device to a storage medium, such as a
floppy, memory card or a network drive. You import the users and passwords from this storage
medium at all the other HMI devices.
You program a function which exports the user data at a button.
The system function "ExportImportUserAdministration" is not available on all HMI devices.
CAUTION
When exporting, the user data are encrypted and written from the HMI device to the target
file. The target file is overwritten.
Requirements
You have created an HMI device with Runtime Advanced.
A screen has been created.
A button has been created in the screen.
The Inspector window is open.
Procedure
1. Click the button in the screen.
2. Click "Properties > Events > Release" in the Inspector window.
3. Click the entry "Add function" in the function list.
4. Select the "ExportImportUserAdministration" system function.
5. Select "Export" as the "Direction". When exporting, the target file is overwritten with the
user data.
6. Enter the full path of the destination file as the "File name", for example "a:\test
\usersview.txt".
NOTICE
Ensure that the file name is written correctly. If the directory, for example "\test\", does not
exist, it will be created without a prompt.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1205
Importing the user administration
Introduction
If a user has access to several HMI devices, the same user and the same password must be
configured on each HMI device. Create a standard for user administration of the different HMI
devices. Export the users and passwords on an HMI device to a storage medium, such as a
floppy, memory card or a network drive. You import the users and passwords from this storage
medium at all the other HMI devices.
You configure a function which imports the user data at a command button.
The system function "ExportImportUserAdministration" is not available on all HMI devices.
CAUTION
When importing, the user data are read in from the source file and written into the HMI device.
The users and passwords currently valid in the HMI device are overwritten. The imported
users and passwords are valid immediately.
Requirements
A screen has been created.
A command button has been created in the screen.
The Inspector window is open.
Procedure
1. Click the button in the screen.
2. Click "Properties > Events > Release" in the Inspector window.
3. Click the entry "Add function" in the function list.
4. Select the "ExportImportUserAdministration" system function.
5. Select "Import" as the "Direction." When importing, the user data in the HMI device are
overwritten.
6. Enter the full path of the source file as the "File name", for example "a:\test\usersview.txt".
Note
Ensure that the file name is written correctly. If the folder, for example "\test\", or the file
does not exist, an error message will be displayed.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1206 System Manual, 08/2011,
Logging on as a user
Introduction
As a rule you log-on as a user by means of a special button. The logon dialog box is displayed
to this purpose.
The logon dialog box is displayed by default during access to a protected object if
No user is logged on in Runtime.
The logged-on user does not have the required authorization.
Note
The system always opens the logon dialog on the OP 73, OP 77A, TP 177A and Basic
Panels HMI devices when you press an access-protected button:
Requirements
Under "Runtime settings > User administration" the
"Enable limit for logon attempts" check box has been selected.
The number 3 is entered in the field "Number of invalid login attempts".
The "ShowLogonDialog" system function is configured on a button called "Logon".
Procedure
1. Click the "Logon" button. The logon dialog box is displayed.
2. Enter your user name as it was specified in the user administration, for example "Foreman".
If someone has logged on before you, the name of the user will be displayed.
3. Enter the corresponding password. The input is concealed.
4. Click "OK" to close the dialog box.
Logon was successful
If you have entered the user name "Foreman" and the entered password corresponds with the
stored password, you are logged on as the user "Foreman" in Runtime. You have the
authorizations of the user "Foreman".
When the user "Foreman" accesses a protected object such as the "Logging" button, access
to this protected object will only be authorized if the user "Foreman" has the required
authorization. The programmed function is executed immediately.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1207
If you do not have the required authorization after the successful log-on, a corresponding error
message is displayed. However, you remain logged on in Runtime.
Logon was unsuccessful
An error message is displayed.
In order to maintain security, you or the user logged-on before you no longer has any
authorizations. However, access to unprotected objects remains possible. The user view does
not, however, show any entries. The user view and the authorizations change after the next
successful log-on.
If the third login attempt has failed, the user will be assigned to the "Unauthorized" group. For
this reason, do not configure a user group with this display name.
If the "Log off" function is called up or the logoff time of the user has expired, the user is logged
off.
9.7.4.5 Configuring access protection
Access protection
Introduction
You configure an authorization at an object in order to protect it against access. All logged-on
users who have this authorization can then access the object. If a user does not have
authorization to operate an object, the logon dialog is displayed automatically.
Note
Several system functions are available under "User administration" so that user, password,
and user group can be edited, for example, in the PLC.
Configuring operating authorizations
Introduction
You configure the "Archive data" authorization for a button. Then only those users who have
the appropriate authorization have access to this button, for example all the users of the
"Operators" user group.
This ensures that access to the command button is protected. If a logged-on user who belongs
to the "Operators" user group and has the required authorizations clicks the button, alarms
and variables are archived.
An example describes in detail how to configure a command button with access protection.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1208 System Manual, 08/2011,
Requirements
The "Operators" user group has been created.
The "Archive data" authorization has been created.
A screen has been created and opened.
The screen contains a button.
Procedure
1. Click the button in the screen.
2. Click "Properties > Properties > Security" in the Inspector window.
3. Select "Archive data" as the "Authorization".
4. In the Inspector window, select "Properties > Events > Click".
5. Select a system function from the function list.
Note
The "Enable" and "Disable" events are only used to detect whether an object was selected
or deselected. The events do not, however, trigger a password prompt.
Do not use the "Enable"or "Disable" event if you want to configure access protection at
the function call of the object.
9.7.5 Reference
9.7.5.1 Objects with access protection
Introduction
The following objects can be configured with an authorization:
Date/time field
I/O field
Graphic I/O field
Recipe view
Switch
Button
Symbolic I/O field
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1209
9.7.5.2 Objects with access protection
Introduction
The following objects can be configured with an authorization:
Date/time field
I/O field
Graphic I/O field
Alarm view
Alarm window
Recipe view
Switch
Button
Slider
Symbol library
Symbolic I/O field
9.7.5.3 Default user groups and authorizations
Principle
The predefined user groups and authorizations have the following numbers:
User group Number
"Administrator group" 1
"Users" 2
Authorization Number
"User administration" 1
"Monitor" 2
"Operate" 3
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1210 System Manual, 08/2011,
9.7.6 Examples
9.7.6.1 Example: Configuring a button with logon dialog box
Task
In the following example, you configure the function "ShowLogonDialog" for a button. A
different user can then log on in runtime when the shift changes, for example. In the process
the user previously logged on is logged off.
Note
In runtime the logon dialog box is not displayed by default until you access a protected object.
Either no user is logged on or the logged-on user does not have the required authorization.
Requirements
A screen has been created.
A button has been created in the screen.
Procedure
1. Click the button in the screen.
2. Click "Properties > Events > Release" in the Inspector window.
3. Click the entry "Add function" in the "Function list" table.
4. Select the system function "ShowLogonDialog" from the "User administration" group.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1211
Result
If the user clicks on the button in runtime, the function "ShowLogonDialog" is called up. When
the function "ShowLogonDialog" is called up, the logon dialog box is displayed. The user logs
on with his user name and password.
9.7.6.2 Example: Logging the logon and logoff events
Task
In the following example, you configure the function "TraceUserChange" to the event "User
change".
Principle
The "TraceUserChange" function is called when a user logs on or off. When a function is called
up, a system message with information about the corresponding user is output.
This system message can be archived. When archiving, the system message is provided with
a date stamp and time stamp. This ensures that you can track which user was logged on at
the HMI device at which time and for how long.
Requirements
You have created an HMI device with Runtime Advanced.
The Inspector window is open.
Procedure
1. Double-click the "Scheduler" in the Project view.
2. Double-click "Add" in the table of the tasks.
3. Enter "Logon-Protocol" as the "Name".
4. Select "User change" as the "Trigger".
5. Open "Properties > Events" in the Inspector window.
6. Click the entry "Add function" in the "Function list" table.
7. Select the "TraceUserChange" system function.
Result
A system message is output when a user logs on or logs off.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1212 System Manual, 08/2011,
9.7.6.3 Example of a user administration
Example: Structure of user administration
Task
In the following example you set up a user administration for different users and user groups.
The example orientates itself to a typical requirement profile from manufacturing engineering.
Principle
Completely different groups of persons are involved in a plant or project. Each group of persons
protects its respective data and functions against access by others. For this purpose, users
are created and assigned to a user group.
You can reproduce different views through user groups.
Example:
Organizational view: Commissioners, Operators, Shift I, Shift II
Technological view: Axis control, Tool changers, Plant North, Plant South
The following example orientates itself to the organizational view.
Every user group has characteristic requirements regarding access protection: A user group
has operating authorizations for specific application cases. A programmer changes, for
example, recipe data records.
In the example the users Miller, Group Smith and Foreman are created and assigned to
different user groups.
Ms. Miller works as a programmer in the engineering system. The Group Smith are
commissioners. Mr. Foreman is an operator.
Requirements
A new project has been created.
The "User administration" editor is open.
Procedures overview
Working with user administration has the following procedure in the example:
1. Creating authorizations The planner specifies which authorizations are required for access
protection.
2. Configuring authorizations: The planner specifies which objects may be operated and which
functions may be executed.
3. Creating user groups and allocating authorizations: The administrator creates the user
groups together with the planner. The planner uses the authorizations to specify who may
operate objects and change parameters.
4. Creating users and assigning them to a user group: The administrator administers the users.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1213
Result
The aim is the following structure of the user administration of users, user groups and
authorizations:
Users User groups Authorizations
Miller Smith Foreman Roles Changing
recipe
records
Changing
system
parameters
Changing
process
parameters
Managing
Administrator group x
X Programmer X
X Commissioning
engineers
X X X
X Operators x
The user "Foreman" who belongs to the "Operators" user group has access to the configured
"To Recipe view" button.
Note
Alternatively, you can create several users as operators with different operating
authorizations, for example, Operator Level 1, Operator Level 2.
Example: Creating and configuring authorizations
Task
The following example shows you how to create the authorizations
Procedure
1. Open the "User groups" work area.
2. Double-click "Add" in the "Authorizations" table.
3. Enter "Change recipe data records" as the "Name" of the authorization.
4. Repeat steps 2 and 3 to create additional authorizations: "Change system parameters",
"Change process parameters".
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1214 System Manual, 08/2011,
Result
Example: Configuring a button with access protection
Task
In the following example you use a system function to create a button for a screen change.
You protect the "To Recipe view" button against unauthorized operation. To do so, you
configure the "Change recipe data records" authorization at the "To Recipe view" button.
Requirements
A "Change recipe data records" authorization has been created.
A "Recipes" screen has been created.
A "Start" screen has been created and opened.
A button has been created and marked in the "Start" screen.
Procedure
1. Click "Properties > Properties > General" in the Inspector window.
2. Enter "To Recipe view" as the text.
3. Click "Properties > Events > Click" in the Inspector window.
4. Click the "Add function" entry in the first line of the "Function list" table.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1215
5. Select the "ActivateScreen" system function in the "Screens" group.
6. Click the button in the "Screen name" field. A dialog box for selecting the screen opens.
7. Select the "Recipes" screen and use the button to close the dialog box.
8. Click "Properties > Properties > Security" in the Inspector window.
9. Select "Change recipe data records" as the "Authorization."
Result
Access to the "To Recipe view" button is protected. If, for example, the user "Smith" clicks the
button in Runtime, the function "Recipe view" screen is called up. Prerequisite is that the user
"Smith" has logged on correctly and has the required authorization. The "Recipes" screen
contains a recipe view and other screen objects.
If the logged-on user does not have the required authorization or if no user is logged on, the
"Logon dialog box" is displayed.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1216 System Manual, 08/2011,
Example: Creating user groups and assigning authorizations:
Task
In the following example you create the user groups and assign authorizations to them.
Procedure
1. Open the "User groups" work area.
2. Double-click "Add" in the "Groups" table.
3. Enter "Programmer" as the "Name".
4. Repeat steps 2 and 3 to create the "Commissioner" and "Operator" user groups.
5. Click "Administrator" in the "Groups" table.
6. Activate the "Change system parameters" authorization in the "Authorizations" table.
Interim result
Procedure
1. Click "Operator" in the "Groups" table.
2. Activate the "Change recipe data records" authorization in the "Authorizations" table.
3. Click "Commissioner" in the "Groups" table.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1217
4. Activate the authorizations "Change recipe data records", "Change system parameters"
and "Change process parameters" in the "Authorizations" table.
5. Click "Programmer" in the "Groups" table.
6. Activate the "Change recipe data records" authorization in the "Authorizations" table.
Result
Example: Creating users and assigning them to a user group
Task
In the following example you create the users and assign user groups to them. The users are
sorted alphabetically immediately after the name has been entered.
Procedure
1. Open the "Users" work area.
2. Double-click "Add" in the "Users" table.
3. Enter "Miller" as the user name.
4. Click the button in the "Password" column. The dialog box for entering the password is
displayed.
5. Enter "miller" as the password.
6. To confirm the password enter it a second time in the lower field.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1218 System Manual, 08/2011,
7. Close the dialog box by using the icon.
8. Activate the "Programmer" user group in the "Groups" table.
Interim result
Procedure
1. Double-click "Add" in the "Users" table.
2. Enter "Smith" as the user name.
3. Click the button in the "Password" column. The dialog box for entering the password is
displayed.
4. Enter "smith" as the password.
5. To confirm the password enter it a second time in the lower field.
6. Close the dialog box by using the icon.
7. Activate the "Commissioner" user group in the "Groups" table.
8. Repeat steps 2 to 6 for the user "Foreman."
9. Activate the "Operators" user group in the "Groups" table.
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1219
Result
Visualizing processes (Advanced)
9.7 Configuring user administration
WinCC Advanced V11.0 SP1
1220 System Manual, 08/2011,
9.8 Working with system functions and Runtime scripting
9.8.1 Working with system functions and Runtime scripting
9.8.1.1 Basics
Runtime scripting
Term definition
The following terms are used in the documentation:
Term
Runtime scripting Generic term for all activities in user-defined functions.
Function Generic term for system functions and user-defined functions.
System functions System functions are all functions supplied with WinCC. The system functions
are used either in function lists or user-defined functions.
User-defined functions User-defined functions are functions written in the "Scripts" editor. For more
precise specification, the term "User-defined VB function" is used in the
documentation.
VBS / VBScript Abbreviation for Visual Basic Script
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1221
Applying Runtime scripting
The following figure serves as a decision guide for programming tasks at hand:
User-defined
function
Writing
Using a system
function
Yes
END
No
System function
available?
No
Yes Can it be
implemented in
AS?
Adapting PLC
program
See also
Availability for specific devices of system functions (Page 1262)
System functions
Applications
You use system functions for the following:
Function lists
A function list is executed from top to bottom in Runtime. If a function list includes system
functions with longer runtime, these are processed asynchronously. See "Runtime behavior
in Runtime (Page 1252)" for additional information.
User-defined functions
If the HMI device supports customized functions, you use system functions in combination
with instructions and conditions in the code of a customized function. In this way you
execute a customized function depending on a specific system state. In addition, you can
evaluate return values of system functions, for example. Depending on the return value,
you then perform test functions, for example, that in turn affect the user-defined function
flow.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1222 System Manual, 08/2011,
Application examples of system functions
Calculations, increase tag value by a defined or variable amount.
Log function, e.g. to start a process value log.
Settings, e.g. to switch the PLC or set a bit in the PLC.
Alarms, e.g after changing the user.
Usage
Function list
When configuring a function list, you select the system functions from a selection list that
is sorted by categories:
User-defined function
If you are using a system function in a user-defined function, you choose it from a selection
list. To open the selection list, use the key shortcut <Ctrl+Space> or click .
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1223
Language dependency
In the function list, the names of the system functions are dependent on the set project
language. The functionality can then be recognized immediately by the project planner.
You use the English name of the system function in user-defined functions. You will find the
English name of the system function in the reference.
Availability
Which system functions are available depends on the selected HMI device.
HMI device replacement
If you use system functions in a function list that are not available on the set HMI device, these
system functions are marked in color.
If you use a system function in a user-defined function which is not available on the set HMI
device, a warning is issued. In addition, the respective system function will be underlined with
a wavy blue line.
See also
Runtime behavior in Runtime (Page 1252)
System functions for logs (Page 930)
User-defined functions
Applications
You use customized functions for the following for example: :
Configuring an extended function list
In a customized function you have the option to have customized functions and system
functions executed depending on conditions or executed repeatedly. You then add the
customized function to a function list.
Programming new functions
Customized functions are only valid in the project in which they are defined. For user-
defined functions you define transfer parameters and return values, for example, for
conversion of values.
Properties of customized functions
A customized function has the following properties:
Name
Parameter (optional)
Return value and type (optional)
Can be modified centrally
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1224 System Manual, 08/2011,
has no trigger. You have to call the customoized function explicitly, e.g. in a function list.
behaves like a system function
Usage
You create customized functions with the "Scripts" editor. See "Scripts" editor (Page 1230)
for additional information.
Customized functions are saved in the project. To protect user-defined functions, set up know-
how protection. See Auto-Hotspot for additional information.
Project tree
The user-defined functions are listed in the project tree under "VB scripts".
Function list
The user-defined functions are listed in a function list under "VB functions".
User-defined function
If you are using a system function in a user-defined function, you choose it from a selection
list. To open the selection list, use the key shortcut <Ctrl+Space> or click .
Recursion level
The recursion level in user-defined functions is limited by the stack size of the HMI device. If
the number is exceeded, a system error message is output in Runtime. This means you should
limit the number of recursions in a user-defined function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1225
9.8.1.2 Working with function lists
Basics of the function list
Introduction
A function list performs one or more system functions and user-defined functions when the
configured event occurs.
Principle
The function list is configured for an event of an object, for example, for a screen object or a
task. You can configure a function list precisely on every event. The events which are available
depend on the selected object and the HMI device.
Events occur only when the project is in Runtime. Events include:
Execution of a task
Pressing of a button
Acknowledging an alarm
Note
The choice of configurable system functions in a function list is dependent on the selected
HMI device. For additional information, refer to "Availability for specific devices of system
functions".
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1226 System Manual, 08/2011,
Properties of a function list
Status information
During configuration the project data is tested in the background.
With the following causes the function list is not executed in Runtime and the incorrect entries
are marked red:
At least one system function or one user-defined function is not completely supplied with
parameters.
At least one system function or one customized function is contained which is not supported
by the selected HMI device, e.g. by changing the device type.
Processing of system functions and user-defined functions (WinCC Runtime Advanced and Panels)
A function list is executed from top to bottom in Runtime. If a function list includes system
functions with longer runtime, these are processed asynchronously. See "Executing a function
list in Runtime (Page 1252)" and "Processing sequence for user-defined functions and system
functions (Page 1253)" for more details.
See also
Runtime behavior in Runtime (Page 1252)
Executing a function list in Runtime (Page 1252)
Processing sequence for user-defined functions and system functions (Page 1253)
Configuring a function list
Introduction
You configure a function list by selecting the system functions and customized functions from
a drop-down list. The system functions are arranged in the selection list according to
categories.
You only use customized functions of a programming language in a function list. Your selection
of the first user-defined function determines whether user-defined VB functions or user-defined
C functions can be selected in the function list. Which programming languages are available
depends on the selected HMI device.
If you have created a user-defined VB function, for example, the user-defined function is
available under the entry "VB functions".
Requirement
Object has at least one configurable event.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1227
Procedure
Proceed as follows to configure a function list:
1. Open the editor in which the object is located.
2. Select the object.
3. Click "Properties > Events" in the Inspector window. Choose the event for which you want
to configure the function list.
4. Mark the "<Add function>" entry in the inspector window in the drop-down list.
5. Select the desired system function or the desired user-defined function from the selection
list. You can also enter the name of the system function or the user-defined function.
The system function or the customized function is entered in the function list.
6. If the system function or the customized function has parameters, select the appropriate
values for the parameters.
7. If you want to add other system functions or user-defined functions to the function list, repeat
steps 4) to 6).
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1228 System Manual, 08/2011,
Result
The function list is configured. In addition, to the configured event, the status of the function
list is displayed in the Inspector window. When the configured event occurs in Runtime, the
function list is completed from top to bottom.
Editing a function list
Introduction
A function list can be edited as follows:
Change the order of system functions and user-defined functions.
Remove system functions or user-defined functions.
Requirement
The function list is configured and opened.
Changing the order of a system function or a customized function
1. Select the desired system function or customized function in the function list.
2. Then click the appropriate direction arrow in the inspector window until the system function
or customized function is in the desired position.
Changing the order of several system functions and customized functions
1. Hold down the <Shift> key.
2. Click desired system functions or customized functions one after another with the mouse.
3. Move the selection to the desired position by drag&drop.
Removing a system function or customized function
1. Select the desired system function or customized function in the function list.
2. Select "Delete" in the shortcut menu.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1229
9.8.1.3 Working with user-defined VB functions
"Scripts" editor
Introduction
The "Scripts" editor supports you in the creating of customized functions with functionalities
such as auto-completion and syntax highlighting. You can insert code templates for frequently
used instructions with the "Instructions" task card for example.
Autocompletion and parameter entry
The "Scripts" editor provides you context-dependent programming support with
autocompletion parameter entry support.
When you use system functions, the parameters of the function are shown as a tooltip.
<Ctrl+J>
The object list can be called context-specifically by using the shortcut <Alt+J>. Use the object
list to supply values to system functions, methods, and properties: For example, you select
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1230 System Manual, 08/2011,
screens, screen objects, tags, or colors. You transfer a selected object from the object list into
the code by double-clicking it.
Note
Tags and screens can also be inserted using a drag-and-drop operation. Use, for example,
drag-and-drop to assign values to parameters.
<Ctrl+Space>
With the key combination <Ctrl+Space> you call a list with the following contents:
Constants and functions of the programming language used in the "Scripts" editor.
Customized functions
System functions
"Instructions" task card
The "Instructions" task card contains the "Code templates" and "Function list" palettes.
Code templates
To insert frequently used instructions, double click the desired instruction in the "Code
templates" palette. Replace the space holders with the used expressions.
Function list
In the function list you select the system functions and customized functions from a drop-
down list. Proceed as for configuring a function list. To transfer the function list to the code,
click the "Transfer" button. The function list is automatically converted into the correct
syntax.
Note
Not all system functions are available in the "Scripts" editor. For additional information,
refer to the reference.
Edit functions
Use the buttons of the toolbar "Advanced Edit" to make the code more readable by means of
indentation and the use of comments.
Bookmarks help you keep an overview, even of many lines of code.
Further information regarding each button can be obtained in the accompanying direct help.
Synchronization of tags and objects
If you change tag names or object names in the project which you use in a user-defined
function, the names are adapted automatically in the user-defined function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1231
If you change the tag name or object name in the function, the tag names or object names are
not adapted in the project. An appropriate error message is output when executing the user-
defined function.
Syntax highlighting
Keywords in the "Scripts" editor are highlighted using different colors. Unknown words are
underlined with a red wavy line.
The table shows the preset colors for the most important keywords:
Color Meaning Example
Blue Keyword If, Then
Dark violet Function FahrenheitToCelsius
Chocolate System function SetTag
Orange HMI tag Tag_1
Green Comment 'This is a comment'
Adapting display properties
When you have opened a user-defined function, you can customize the display properties in
the editor. Select the "Options > Settings" menu command. Click "General > Text editors" in
the "Settings" editor. For example, you can change the colors for syntax highlighting or adapt
the indents for code in the work area.
See also
Create customized VB functions (Page 1238)
Access to HMI tags
Introduction
In user-defined VB functions, you have access to HMI tags which you have created in the
project. Change or read the tag value with a user-defined VB function in Runtime.
In addition, you can create local tags as counters or buffers in the user-defined VB function.
You must declare each tag to avoid errors due to misspelled tags.
HMI tags
The user-defined VB function accesses the tag value which is saved in Runtime memory. Next,
the tag value will be updated to the set cycle time. The user-defined VB function first accesses
the tag values which were read at the previous cycle time.
If the tag name matches the VBS name conventions in the project, you can use the HMI tag
directly in the function.
'VBS_Example_03
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1232 System Manual, 08/2011,
If BeltDriveOilTemperature > 100 Then [instruction]
If the tag name in the project does not match the VBS name conventions, you must reference
the HMI tag using the "SmartTags list". In the following example the tag name contains the "&"
character that is not permitted in accordance with the VBS name conventions:
'VBS_Example_04
SmartTags("Test&Trial")= 2005
Local tags
You define local tags with the Dim instruction. You can only use local tags within user-defined
VB functions. They therefore do not appear in the "HMI Tags" editor. You use a local tag in
the user-defined VB function, for example, as a counter in a For instruction.
'VBS_Example_05
Dim intCount
For intCount = 1 To 10 [instruction] Next
Access to HMI tags with a dynamic name
The user-defined VB function accesses the tag value using the tag name. You can specify the
tag name in such a way that the tag name is composed at the runtime of the user-defined
function.
If you only call the user-defined VB function in a screen in which the HMI tag is also used
elsewhere, for example in an I/O field, you should for performance reasons configure the HMI
tag with "Cyclic in operation" acquisition mode.
If the user-defined VB function is accessed and the HMI tag is not being used in the screen
currently displayed, configure the HMI tag with "Cyclic continuous" acquisition mode. This
ensures that the current value of the tag is always available.
See also
SmartTags (Page 1574)
Access to objects
Introduction
The objects of the VBS object model with the appropriate properties and methods are available
in user-defined VB functions.
The object properties can be read and changed in Runtime.
Referencing objects
In customized VB functions you reference the objects by the corresponding list. To identify the
object, use its name or the position number within the list.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1233
If you access the properties of an object more often, create an object reference. You can
access object properties with and without object reference.
With the following instruction the first object is referenced in the "MainScreen":
'VBS_Example_01
Dim objObject
'Change to Screen "MainScreen"
HMIRuntime.BaseScreenName = "MainScreen"
Set objObject = HMIRuntime.Screens(1).ScreenItems(1)
With the following instruction an object is referenced by its name and an object property is
changed. You must have created the object with this name in the screen.
'VBS_Example_02
Dim objCircle
HMIRuntime.BaseScreenName = "MainScreen"
Set objCircle = HMIRuntime.Screens(1).ScreenItems("Circle_01")
objCircle.BackColor = vbGreen
See also
Objects (Page 1568)
Calling system functions
Introduction
You can insert system functions in a user-defined VB function.
This can be done in the following ways:
With <Ctrl+Space> or with
Direct input
With the "Function list" palette
With <Ctrl+Space> or with
Open the list of system functions with <Ctrl+Space> or with and select the desired system
function.
Direct input
You enter the system functions directly into the code. You use the English name of the system
function. You can find the English name of the system function in the system function reference
under "Syntax". The editing language setting is not taken into consideration.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1234 System Manual, 08/2011,
References to objects, e.g. screens, connections and logs are transferred in inverted commas:
Calling system functions without return value in VBS
SetTag "Tag1",64
Calling system functions with return value in VBS
InverseLinearScaling "XValue","Tag1", 0, 1
With the "Function list" palette
Select the system functions from a selection list that is sorted by categories in the "Function
list" palette. Proceed as for configuring a function list. You will find further information about
this under "Configuring a function list".
To transfer the list to the code, click the "Transfer" button. The list is automatically converted
into the correct syntax.
HMI device replacement
The code of a customized function depends on the selected HMI device. If you use system
functions in the customized function which are not supported by the selected HMI device, you
receive an error message in the output window. See "Availability for specific devices of system
functions (Page 1262)" for additional information.
Calling user-defined VB functions
Introduction
You can only insert user-defined VB functions in a user-defined VB function.
This can be done in the following ways:
With <Ctrl+Space> or with
Direct input
With the "Function list" palette
With <Ctrl+Space> or with
Open the list of user-defined VB functions with <Ctrl+Space> or with and select the desired
user-defined VB function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1235
Direct input
You enter the user-defined VB function directly into the code. References to objects, e.g.
screens, connections and logs are transferred in inverted commas.
Function Average(ByVal Var1, ByVal Var2)
Average = (Var1+Var2)*(1/2)
End Function
Calling user-defined VB functions without return value in VBS
Average 4,10
Calling user-defined VB functions with return value in VBS
Dim ValueA
ValueA = Average (4,10)
If you do not want to evaluate the return value, use the call as for a user-defined VB function
without return value.
With the "Function list" palette
Select the desired user-defined VB function from a selection list in the "Function list" palette.
Proceed as for configuring a function list. You will find additional information under "Configuring
a function list".
To transfer the list to the code, click the "Transfer" button. The list is automatically converted
into the correct syntax.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1236 System Manual, 08/2011,
Transfer and return of values in VBS
Transfer of a value
The following options are available for transferring parameters.
"Call by Value" - ByVal
ByVal transfers the parameter value. If you transfer a tag as a parameter, the tag value is
transferred to the user-defined function when the user-defined function is executed.
"Call by Reference" - ByRef
ByRef transfers the address of the parameter. If you transfer a tag as a parameter, the tag
address is transferred to the user-defined function when the user-defined function is
executed.
When user-defined functions and system functions are called in user-defined functions, the
parameter is transferred as ByRef.
Return of a value
Return values can return the result of a calculation (e.g., average value of two numbers). But
a return value can also give information about whether an instruction was executed correctly.
Therefore, the system functions that perform file operations such as "Delete" also have return
values.
For a user-defined function to return a value, you must set the "Function" type. You assign the
function name to the return value in the user-defined function:
To form an average value of two numbers, call the user-defined VB function Average and
transfer the result to the HMI tag for example AverageValue.
In a customized VB function
SmartTags("AverageValue") = Average ("4", "10")
In the function list
You can output the value of the HMI tag AverageValue in an I/O field.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1237
See also
Create customized VB functions (Page 1238)
Create customized VB functions
Introduction
When you create a customized VB function, you define the following settings:
The name with which you call the user-defined VB function.
The type of user-defined VB function.
The parameters which are transferred to the user-defined VB function in Runtime.
Use only the following characters for the name:
"A" to "Z"
"a" to "z"
"0" to "9"
"_" as a separator
Note
When you change the parameters or the function type, the change is color marked at the
application point, e.g. in the function list.
Procedure
To create a user-defined VB function, follow these steps:
1. Open "Scripts" in the project tree.
2. Double click "Add new VB function" in the project tree under "VB scripts".
The user-defined VB function is created as a new tab in the work area. The input mask for
the configuration settings of the user-defined VB function opens in the Inspector window.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1238 System Manual, 08/2011,
3. Configure the user-defined VB function in the Inspector window "Properties > General >
General".
4. Enter a descriptive "Name" for the user-defined VB function.
5. Select the "Type" of the user-defined VB function.
"Function" have a return value.
"Sub" have no return value.
6. Click "<Add>" in the "Parameters" list to add parameters. Enter the parameter name and
specify the parameter type.
Further information can be found in "Transfer and return of values in VBS (Page 1237)".
"ByVal" transfers the parameter value.
"ByRef" transfers the address of the parameter.
7. Enter its code in the work area.
You will find further information about this in ""Scripts" Editor" (Page 1230)".
Result
The user-defined VB function has been created. The type, name, and function parameters are
displayed in the title bar.
The start and end are inserted automatically when the user-defined function is created.
If you have protected the user-defined VB functions by a password, it is saved encrypted in
the project. For additional information, refer to "Protecting user-defined functions".
The figure below shows a user-defined VB function which converts the temperature from
"Fahrenheit" to "Degrees Celsius":
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1239
Testing the syntax of customized functions
Introduction
During programming, the code is tested in the background. Syntactical errors are marked with
a wavy red line. The customized function is checked for correct syntax and valid object
references.
Check the syntax in the "Scripts" editor to identify all the errors in the code and output the
appropriate error messages. In this case, error messages generated by the script parser are
output.
Use a separate debugger to check customized VB functions for logical programming errors.
Error types
The following error types are detected in the syntax test and output in the "output window":
Unknown string (e.g., not a keyword)
Assignment of value to a constant
The name of a local tag created with the Dim instruction is already known, e.g.: as a
parameter, object, or component of the object model
Syntax error
Requirements
Customized function is open.
Procedure
Proceed as follows to check the syntax:
1. Click to start the syntax check.
The syntax is checked. The result of the syntax check is displayed in the Inspector window
under "Info > Compilation." Syntax errors are output with the line number.
2. Correct the errors in the customized function if necessary.
Special consideration in the syntax checking of customized functions
Customized functions are not interpreted until in Runtime. When an HMI device is being
compiled, the system checks its user-defined functions for correct syntax. However, runtime
errors may occur in certain circumstances.
See also
Configuring a function list (Page 1227)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1240 System Manual, 08/2011,
Renaming customized VB functions
Renaming a user-defined VB function in the project tree
Proceed as follows to rename a user-defined VB function in the project tree:
1. Select the desired user-defined VB function in the project tree.
2. Select the "Rename" (F2) command in the shortcut menu of the user-defined VB function.
3. Enter a new name for the user-defined VB function.
Renaming a user-defined VB function in the Inspector window
Proceed as follows to rename a user-defined VB function in the Inspector window:
1. Open the user-defined VB function in the "Scripts" editor.
2. In the Inspector window, click "Properties > Properties > General".
3. Enter the new function name.
Result
The user-defined VB function is renamed. The application points are adapted automatically.
Executing customized VB functions
Introduction
In WinCC you have the following options to execute a customized function:
Function list
Customized VB function
Calling a customized VB function in a function list
1. Add the user-defined VB function to a function list like a system function. You will find the
customized VB functions in the drop-down list under "VB functions". You will find further
information in "Configuring a function list (Page 1227)".
2. If the VB function has parameters, supply the parameters with static values or HMI tags.
3. If the VB function has a return value, select an HMI tag. The value to be processed is
transferred to the HMI tag.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1241
Calling a customized VB function in a customized VB function
1. Open the user-defined VB function in which you want to call the user-defined VB function.
2. Call the customized VB function in the syntax of the programming language. You will find
further information in "Calling user-defined VB functions (Page 1235)".
3. If the VB function has a return value, assign an expression, e.g. a local tag, to the VB
function.
See also
Configuring a function list (Page 1227)
Calling system functions (Page 1234)
Calling user-defined VB functions (Page 1235)
Protecting user-defined functions
Setting up know-how protection
Procedure
To set up know-how protection for user-defined functions, follow these steps:
1. Select the user-defined function without know-how protection that you want to protect.
2. Select the command "Know-how protection" in the "Edit" menu.
The "Know-how protection" dialog will open.
3. Click "Define".
The "Define password" dialog box opens.
4. Enter a password in the "New" field.
5. Enter the same password in the "Confirm" field.
6. Confirm your entries with "OK".
7. Close the "Know-how protection" dialog by clicking on "OK".
Result
The user-defined function receives know-how protection. User-defined functions with know-
how protection are marked with a lock in the project tree. The password entered is valid for all
user-defined functions selected.
Opening user-defined functions with know-how protection
You can only open multiple user-defined functions with know-how protection at once if they
are protected with the same password.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1242 System Manual, 08/2011,
Procedure
To create a user-defined function with know-how protection, follow these steps:
1. Double-click the user-defined function you want to open.
The "Access protection" dialog will open.
2. Enter the password for the user-defined function with know-how protection.
3. Confirm your entry with "OK".
Result
The user-defined function with know-how protection will open provided you have entered the
correct password. However, the function will remain know-how protected.
Once you have opened the user-defined function, you can edit it for as long as the user-defined
function or TIA portal is open. You must enter the password again the next time you open the
user-defined function. If you close the "Access protection" dialog with "Cancel" or "Close", the
user-defined function is opened but the code is not displayed. You cannot edit the user-defined
function.
Removing know-how protection
Procedure
To remove the know-how protection of a user-defined function, follow these steps:
1. Select the user-defined function for which you want to remove know-how protection.
Note
To remove know-how protection for several user-defined functions at once, all selected
user-defined functions must have the same password.
2. Select the command "Know-how protection" in the "Edit" menu.
The "Know-how protection" dialog will open.
3. Deactivate the check box "Hide code (know-how protection)".
4. Enter the password.
5. Confirm your entries with "OK".
Result
Know-how protection will be disabled for the selected user-defined function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1243
Changing a password
Procedure
To change the password, follow these steps:
1. Select the user-defined function with know-how protection for which you want to change
the password.
Note
To change the password for several user-defined functions at once, all selected user-
defined functions must have the same password.
2. Select the command "Know-how protection" in the "Edit" menu.
The "Know-how protection" dialog will open.
3. Click the "Change" button.
4. Enter the old password in the "Old" field.
5. Enter the new password in the "New" field.
6. Enter the new password again in the "Confirm" field.
7. Confirm your entries with "OK".
8. Close the "Know-how protection" dialog by clicking on "OK".
9.8.1.4 Debugging user-defined VB functions
Debugging user-defined VB functions
Introduction
Debugging allows you to test the user-defined VB functions for logical programming errors in
Runtime. For example, you can test whether the proper values were transferred to the tags,
and whether cancellation terms are realized correctly.
The following VBScript-capable debuggers have been tested and approved:
"Microsoft Script Debugger"
"Microsoft Script Editor": The debugger is included in Microsoft Office XP.
"Microsoft Script Debugger" provides the following functionality:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1244 System Manual, 08/2011,
Viewing the source code of the function you are debugging
Checking the step-by-step execution of the functions
Viewing and editing tags and property values
Note
Your code is displayed in the debugger, but is write-protected. You cannot edit the code
directly in the debugger; you can only test the required changes.
Note
Difference with regard to VBScript for Windows and Windows CE
The debugger checks the syntax for VBScript for Windows. If the function contains a
VBScript function for Windows CE, a corresponding error message is output. Some
VBScript functions are different, e.g., CreateObject. You can find a list of these VBScript
functions under "VBScript for Windows CE (Page 1548)".
Error types
The following error types are distinguished when debugging:
Runtime error
A runtime error is generated if an attempt is made to execute an invalid or faulty instruction,
e.g., if a tag is not defined.
To intercept runtime errors, use the "On Error Resume Next" instruction in the user-defined
VB function. With this instruction, the next instruction is executed after a runtime error. You
check the error code with the Err object in the next line. To stop the handling of runtime
errors in the user-defined VB function again, use the "On Error Goto 0" instruction.
Logical error
A logical error occurs when the event you are expecting does not take place, e.g., because
a condition was checked incorrectly. To debug logical errors, you go through the user-
defined VB function step by step. This way, you identify the portion of the user-defined VB
function that is not working.
Basic procedure
The debugger is only intended for identifying error locations in the user-defined VB function.
For this purpose, for example, you use break points or execute the user-defined VB function
step-by-step. For detailed information, refer to the documentation of the debugger you are
using. In order to correct errors, you change to the "Scripts" editor in WinCC. After having
recompiled and reloaded the script, you test the user-defined VB function once again using
the debugger.
Note
For tips and tricks on debugging, common sources of error, and further information, refer to
the online help for the Microsoft Script Debugger.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1245
Screen change while debugging
If you change to another screen while debugging, the user-defined VB function of the previous
screen stays open but is no longer valid. The debugger could return invalid error messages in
this case, as the objects called will no longer exist after the screen change.
Integrating the Debugger
Installing a script debugger for WinCC
A VBScript-capable debugger must be installed to search for errors in user-defined VB
functions.
The following VBScript-capable debuggers have been tested and released:
Microsoft Script Editor by Office XP
Microsoft Script Debugger: The English version "scd10en.exe" must be used. The German
version "scd10de.exe" may not be installed.
An installed debugger is started as follows:
If a runtime error occurs during execution
Via "Online > Simulate Runtime > With script debugger"
Microsoft Script Editor
The Microsoft Office XP component "Microsoft Script Editor" contains a Script Debugger. If
the default configuration was installed by Microsoft Office Setup, the "Microsoft Script Editor"
component is not installed until called the first time ("Installed on First Use"). If you wish to
explicitly install these components, you must specify it in the Microsoft Office setup. Select the
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1246 System Manual, 08/2011,
component selection menu, click"Web Debugging" component and then select the "Run from
My Computer" option.
If a project is activated in WinCC via "Online > Simulate Runtime > With script debugger", a
dialog containing the list of available script debuggers appears when the first user-defined
function is run.
Other installed script debuggers such as "Microsoft Visual Interdev" or "Microsoft Visual
Studio .NET" may also appear in the list. Select "Microsoft Script Editor" and confirm your
selection with "Yes".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1247
Activate the "Script" program object in the "Step Into Remote Procedure Call" dialog and
confirm your selection with "OK".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1248 System Manual, 08/2011,
The "Microsoft Script Editor" is launched. The execution pauses at the first line of the first
function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1249
Microsoft Script Debugger
If a script debugger is not available, download "Microsoft Script Debugger" (scd10en.exe) free
of charge from Microsoft (www.microsoft.com). It will be started automatically in WinCC once
it is installed.
Note
The "Microsoft Script Debugger" can no longer be called or installed when another VBScript-
capable script debugger is available on your computer.
Script Debugger is not started at the start of Runtime
If you installed a script debugger and the "Start Runtime with Script Debugger" command still
fails to start it, make the following settings in the Windows registry to set Microsoft Script
Debugger as default Just-In-Time (JIT) Debugger:
"HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}]
(Default)="ScriptDebugSvc Class"
"AppID"="{A87F84D0-7A74-11D0-B216-080000185165}"
[HKEY_CLASSES_ROOT\CLSID
\{834128A2-51F4-11D0-8F20-00805F2CD064}\LocalServer32]
(Default)="c:\\Program Files\\Microsoft Script Debugger\\msscrdbg.exe"
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1250 System Manual, 08/2011,
[HKEY_CLASSES_ROOT\CLSID\{834128A2-51F4-11D0-8F20-00805F2CD064}\ProgID]
(Default)="ScriptDebugSvc.ScriptDebugSvc.1"
[HKEY_CLASSES_ROOT\CLSID
\{834128A2-51F4-11D0-8F2000805F2CD064}\VersionIndependentProgID]
(Default)="ScriptDebugSvc.ScriptDebugSvc"
The "LocalServer32" file path must point to the installation folder of Microsoft Script Debugger.
If you have installed Microsoft Script Debugger in a different folder, adapt the path information.
Starting and stopping the debugger
Requirement
VBScript-capable debugger (e.g., MS Script Debugger) and WinCC Runtime are installed
on the configuration PC.
Project is open.
Starting the debugger
To start the debugger, proceed as follows:
1. Select the HMI device and then select the "Online > Simulation > With script debugger"
menu command.
The Runtime software searches for debuggers installed on the configuration PC.
2. If several debuggers are found click on the one required.
Or:
1. Click "Start > Run".
2. Enter the following command: "HmiRtm /ScriptDebug /<ProjectFile>".
Further information about the project file can be found in "Starting Runtime Advanced and
Panels (Page 2403)".
Or:
1. Select the "debug" command in the project file shortcut menu in the Windows Explorer.
Result
The debugger is connected automatically with the runtime software.
Stopping the debugger
The debugger is not closed automatically when you close the Runtime software. Therefore,
close the debugger separately.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1251
9.8.1.5 Runtime behavior in Runtime
Executing a function list in Runtime
Principle
A function list is executed from top to bottom in Runtime. A distinction is made between
synchronous and asynchronous execution, so that no waiting periods ensue during execution.
The distinction is made by the system by evaluating the different runtimes of the system
functions. User-defined functions are always executed synchronously independent of the
runtime. If a system function returns an error status, the execution of the function list is
cancelled.
Synchronous execution
During synchronous execution, the system functions in a function list are executed one after
the other. The previous system function must be finished before the next system function can
be executed.
Asynchronous execution
System functions that perform file operations such as saving and reading have a longer runtime
than system functions that, for example, set a tag value.
Therefore, system functions with longer runtimes are executed asynchronously. For example,
while a system function is writing a recipe data record to a storage medium, the next system
function is already being executed. Due to the parallel execution of system functions, waiting
periods at the HMI device are avoided.
Executing user-defined functions in Runtime
Principle
Only one user-defined function at a time is executed in Runtime. If several user-defined
functions are waiting to be executed, they are lined up in a queue and executed one after the
other.
Note
A loop in a user-defined function therefore blocks the execution of the other functions in the
queue even if the functions were initiated asynchronously.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1252 System Manual, 08/2011,
WinCC supports a maximum nesting depth of eight user-defined functions. Note that the
nesting depth is not checked.
Note
If a user-defined function is configured for the "Runtime stop" event, the only system functions
that may be used in this user-defined function are those which are available at the "Runtime
stop" event.
Ensure that the ending of the Runtime is not interfered with by the execution of the user-
defined function.
Note
Configuration of user-defined functions
During configuration make sure that not too many user-defined functions are activated at the
same time. Avoid a continuous system load of 100%.
User-defined functions are processed at a lower priority so as not to interfere with the display
of values and operability. If system utilization is extreme, the user-defined functions to be
executed are therefore first only reserved for execution. The maximum size of the reservation
list is dependent on the HMI device and is limited by the maximum permitted number of user-
defined functions. For additional information, see the performance features. If more user-
defined functions are activated at one time than can be reserved, excess calls are discarded
and a system alarm displayed.
HMI device changeover
If you use system functions in a customized function which are not available on the set HMI
device, you get a warning. In addition, the corresponding system function in the user-defined
function will be underlined with a wavy blue line.
See also
Runtime Stop (Page 1460)
Processing sequence for user-defined functions and system functions
WARNING
Adherence to the expected processing sequence for user-defined functions and system
functions in Runtime cannot always be guaranteed. This fact may lead to unexpected
operating states.
Please note the following description in which the correlations are explained. Instructions for
a solution are available under "Remedy".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1253
Use of user-defined functions for events
It is not always possible to adhere to the processing sequence for user-defined functions and
system functions expected in the configuration, for example, when the processing of a user-
defined function lasts beyond the trigger time of a subsequent event. In this case, system
functions that are configured for the following event may be executed before the system
functions that were configured with the user-defined function for the same event.
Background
User-defined functions are arranged in a low-priority queue. The queue is processed in
sequence. If system functions and user-defined functions are configured for an event, all
system functions and user-defined functions configured for this event are executed in this
queue.
Example
On a button, you have configured:
Event Functions
Press User-defined function (1)
SetBit(Tag) (2)
Release ResetBit(Tag) (3)
A
B
Press
Interrupts
lower priority
program
Release
Press
Release
(1) Execution time of the user-defined function
(2) Execution time of system function SetBit(Tag)
(3) Execution time of system function ResetBit(Tag)
A: Expected execution of the user-defined function and system functions in the configuration.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1254 System Manual, 08/2011,
When you press the button, user-defined function (1) and then system function SetBit(Tag)
(2) are executed. When you release the key, system function ResetBit(Tag) (3) is then
executed.
B: Processing of the user-defined function is not yet complete when you release the key.
When you press the key, the user-defined function (1) is then executed. The execution of the
user-defined function (1) is not yet complete and you have already released the key. System
function ResetBit(Tag) (3) interrupts the execution of the function. In this case, system function
ResetBit(Tag) (3) is executed before system function SetBit(Tag) (2). As a result, the bit
remains placed.
System function "SetBitWhileKeyPressed" shows the same behavior, if the system function is
configured together with user-defined functions.
Remedy
The processing sequence of the previous Example A is adhered to, if you additionally configure
a user-defined function for the "Release" event. The user-defined function does not require
functionality for this purpose.
Event Functions
Press User-defined function (1)
SetBit(Tag) (2)
Release User-defined function_2 (3)
ResetBit(Tag) (4)
NOTICE
Make sure that the user-defined function queue does not overflow; otherwise the system
function for the following event may not be executed.
An overflow is recognizable by "Overload: Script <name> is rejected" or "Adherence to the
expected processing order for user-defined functions and system functions in Runtime cannot
always be ensured".
Making object properties dynamic in Runtime
Introduction
You can use user-defined functions to access object properties of screen objects as well as
tags in Runtime. If you use a user-defined function to change values of object properties, this
will not affect the project data.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1255
Changes to object properties
If you use a user-defined function in Runtime to change an object property of a screen element,
this change will only remain effective while the screen is active. If you change to the screen,
or reload the screen, the configured object properties are displayed once more.
Language switching
If you switch the language in Runtime, the foreign language labels are loaded from the project
data. If you use a user-defined function to change texts, the texts changed by the user-defined
function are overwritten again.
9.8.1.6 Examples
Example: Converting Fahrenheit into degrees Celsius
Scheduled task
In this example, create a user-defined VB function which converts the values of a temperature
sensor from Fahrenheit to degrees Celsius. The temperature is displayed in an output field on
the HMI device.
Settings
For the example you need two HMI tags and a user-defined VB function with the following
settings:
HMI tags:
Name PLC connection Type
Fahrenheit Yes Real
Centigrade No Real
User-defined VB function:
Name Type Parameters
FahrenheitToCelsius Function Fahrenheit
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1256 System Manual, 08/2011,
Procedure
1. Create the two HMI-tags "Fahrenheit" and "Celsius" with the settings named above.
2. Create the user-defined VB function "FahrenheitToCelsius" with the settings given above.
3. Write the following VBS code:
FahrenheitToCelsius = (Fahrenheit-32) * (5/9)
Interim result
The HMI tags and the VB user-defined function are created.
Procedure
1. Open the "HMI Tag"editor and click on the "Fahrenheit" tag.
2. Click the "Properties > Events" tab in the Inspector window. Select the "Value change"
event.
3. Configure the user-defined VB function "FahrenheitToCelsius" to the "Value change" event.
4. Select the tag "Fahrenheit" for the parameter "Fahrenheit".
5. Select the HMI-tag "Celsius" for the return value "Fahrenheit to Celsius".
6. Configure an output field in a screen and connect it with the tag "Celsius".
Alternative procedure
Instead of using a user-defined VB function of the "Function" type, you can also use the "Sub"
type. In this case, assign the converted value directly to the HMI-tag "Celsius".
SmartTags("Celsius") = (Fahrenheit-32) * (5/9)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1257
In this case the return value of the user-defined VB function is not applicable.
Result
When the tag value of "Fahrenheit" changes in Runtime, the user-defined VB function
"Fahrenheit to Celsius" is performed. The converted temperature value is returned to the HMI-
tag "Celsius" and displayed in the output field.
Example: Converting inches into meters
Scheduled task
In this example you create a user-defined VB function that converts the value of a length
measuring system from inches into meters. The length in meters is displayed on the HMI device
in an output field.
Settings
For the example you need two HMI tags and a user-defined VB function with the following
settings:
HMI tags:
Name PLC connection Type
VarInch Yes Real
VarMeter No Real
Customized VB function
Name Type Parameters
InchToMeter Sub Inch
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1258 System Manual, 08/2011,
Procedure
1. Create the two HMI tags "VarInch" and "VarMeter" with the above settings.
2. Create the user-defined VB function "InchToMeter" with the settings given above.
3. Write the following VBS code:
VarMeter = Inch*0.0254
Interim result
The tags and the user-defined VB function are created.
Procedure
1. Open the "HMI tags" editor and click the "VarInch" tag.
2. Click "Properties> Events" in the Inspector window. Select the "Value change" event.
3. Configure the user-defined VB function "InchToMeter" to the "Value change" event.
4. Select the "VarInch" HMI tag for the "Inch" parameter.
5. Configure an output field in a screen and connect it with the "VarMeter" HMI tag.
Result
When the tag value of "VarInch" changes in Runtime, the "InchToMeter" user-defined VB
function is performed. The calculated value is written into the "VarMeter" HMI tag and displayed
in the output field.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1259
Example: Changing the operating mode on the HMI device with the current display
Scheduled task
In this example, you use the "SetDeviceMode" system function to switch between the "online"
and "offline" modes on the HMI device. You also display the current set operating mode on
the HMI device.
Requirements
A screen has been created.
Settings
For this example you require a HMI-tag and a text list with the following settings:
HMI tag:
Name PLC connection Type
OperatingMode No Bool
Text list:
Name Contains Values
ShowOperatingMode Bit (0/1) 1: Operating mode: "Online"
0: Operating mode: "Offline"
Procedure
1. Create the "OperatingMode" HMI-tag indicated above.
2. Create the "ShowOperatingMode" text list indicated above.
3. Open the screen and insert a button for which you configure the operating mode change
to "online".
4. Click "Properties> Events" in the Inspector window. Select the "Press" event.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1260 System Manual, 08/2011,
5. Configure the "SetDeviceMode" system function for the "Press" event. The system function
is found in the selection list under "Settings".
6. For the "Mode" parameter, select the "Online" entry.
7. Configure the system function "SetBit" on the event "Press". The system function is found
in the selection list under "Bit processing".
8. Select the HMI-tag "Operating mode" from the selection list for the parameter "Tag".
9. Add a button in the process screen for which you configure the operating mode change to
"offline".
10.Repeat steps four to seven. For the "Mode" parameter, select the "Offline" entry. Configure
the system function "ResetBit" in place of the system function "SetBit."
Interim result
You can toggle the operating mode of the HMI device with the two buttons in Runtime.
You want to display the current set operating mode in an output field on the HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1261
Procedure
1. Create a "Symbolic I/O field" in the process image. Click "Properties > Properties" in the
Inspector window.
2. Make the following settings in the "General" group:
Select "Output" as the "Mode".
Select the text list "Show operating mode" as "Text list".
Select "Operating mode" as "Tag".
Result
When you change the operating mode with the buttons, the currently set operating mode on
the HMI device is always shown.
9.8.2 Reference
9.8.2.1 Function list
Availability for specific devices of system functions
System functions on Basic Panels
Availability of system functions
The following table shows the availability of the system functions on the Basic Panels.
Technical data subject to change.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1262 System Manual, 08/2011,
Overview
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
User-defined functions No No No No No No No
Logoff (Page 1297) Yes Yes Yes Yes Yes Yes Yes
ActivateScreen (Page 1297) Yes Yes Yes Yes Yes Yes Yes
ActivateScreenByNumber
(Page 1298)
Yes Yes Yes Yes Yes Yes Yes
ActivateCleanScreen (Page 1299) No Yes Yes Yes Yes Yes Yes
ActivateSystemDiagnosticsView
(Page 1300)
No No No No No No No
ActivatePreviousScreen
(Page 1301)
Yes Yes Yes Yes Yes Yes Yes
UpdateTag (Page 1302) Yes Yes Yes Yes Yes Yes Yes
AdjustContrast (Page 1302) Yes Yes No Yes
1)
Yes Yes Yes
Logon (Page 1303) Yes Yes Yes Yes Yes Yes Yes
ArchiveLogFile (Page 1304) No No No No No No No
LogTag (Page 1305) No No No No No No No
EditAlarm (Page 1306) Yes Yes Yes Yes Yes Yes No
ScreenObjectCursorDown
(Page 1307)
Yes Yes Yes Yes Yes Yes Yes
ScreenObjectCursorUp
(Page 1307)
Yes Yes Yes Yes Yes Yes Yes
ScreenObjectPageDown
(Page 1308)
Yes Yes Yes Yes Yes Yes Yes
ScreenObjectPageUp
(Page 1309)
Yes Yes Yes Yes Yes Yes Yes
Encode (Page 1309) No No No No No No No
EncodeEx (Page 1310) No No No No No No No
DirectKey (Page 1311) No No No No No No No
DirectKeyScreenNumber
(Page 1314)
No No No No No No No
PrintScreen (Page 1315) No No No No No No No
PrintReport (Page 1315) No No No No No No No
NotifyUserAction (Page 1316) No No No No No No No
IncreaseFocusedValue
(Page 1317)
Yes Yes Yes Yes Yes Yes No
IncreaseTag (Page 1318) Yes Yes Yes Yes Yes Yes Yes
ExportDataRecords (Page 1319) No No No No No No No
ExportDataRecordsWithChecksu
m (Page 1321)
No No No No No No No
ExportImportUserAdministration
(Page 1324)
No No No No No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1263
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
GoToHome (Page 1324) Yes Yes Yes Yes Yes Yes No
GoToEnd (Page 1325) Yes Yes Yes Yes Yes Yes No
SafelyRemoveHardware
(Page 1326)
No No No No No No No
HTMLBrowserStop (Page 1326) No No No No No No No
HTMLBrowserRefresh
(Page 1327)
No No No No No No No
HTMLBrowserForward
(Page 1327)
No No No No No No No
HTMLBrowserBack (Page 1328) No No No No No No No
ImportDataRecords (Page 1328) No No No No No No No
ImportDataRecordsWithChecksu
m (Page 1330)
No No No No No No No
InvertBit (Page 1332) Yes Yes Yes Yes Yes Yes Yes
InvertBitInTag (Page 1333) Yes Yes Yes Yes Yes Yes Yes
InvertLinearScaling (Page 1334) Yes Yes Yes Yes Yes Yes Yes
CalibrateTouchScreen
(Page 1335)
No Yes Yes Yes Yes Yes Yes
CopyLog (Page 1336) No No No No No No No
TrendViewScrollForward
(Page 1337)
Yes Yes Yes Yes Yes Yes Yes
TrendViewScrollBack
(Page 1337)
Yes Yes Yes Yes Yes Yes Yes
TrendViewExtend (Page 1338) Yes Yes Yes Yes Yes Yes Yes
TrendViewCompress (Page 1339) Yes Yes Yes Yes Yes Yes Yes
TrendViewRulerLeft (Page 1339) Yes Yes Yes Yes Yes Yes Yes
TrendViewRulerRight
(Page 1340)
Yes Yes Yes Yes Yes Yes Yes
TrendViewSetRulerMode
(Page 1341)
Yes Yes Yes Yes Yes Yes Yes
TrendViewStartStop (Page 1342) Yes Yes Yes Yes Yes Yes Yes
TrendViewBackToBeginning
(Page 1342)
Yes Yes Yes Yes Yes Yes Yes
LoadDataRecord (Page 1343) No No No No No No No
GetUserName (Page 1344) Yes Yes Yes Yes Yes Yes Yes
GetDataRecordFromPLC
(Page 1345)
No No No No No No No
GetDataRecordName
(Page 1346)
No No No No No No No
GetDataRecordTagsFromPLC
(Page 1348)
No No No No No No No
GetGroupNumber (Page 1349) Yes Yes Yes Yes Yes Yes Yes
GetBrightness (Page 1349) No No No No No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1264 System Manual, 08/2011,
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
GetPassword (Page 1350) Yes Yes Yes Yes Yes Yes Yes
Auto-Hotspot No No No No No No No
LinearScaling (Page 1351) Yes Yes Yes Yes Yes Yes Yes
ClearLog (Page 1352) No No No No No No No
ClearDataRecord (Page 1352) No No No No No No No
ClearDataRecordMemory
(Page 1354)
No No No No No No No
ClearAlarmBuffer (Page 1355) Yes Yes Yes Yes Yes Yes Yes
ClearAlarmBufferProTool
(Page 1356)
Yes Yes Yes Yes Yes Yes Yes
AlarmViewUpdate (Page 1357) No No No No No No No
AlarmViewEditAlarm (Page 1357) Yes Yes Yes Yes Yes Yes Yes
AlarmViewAcknowledgeAlarm
(Page 1358)
Yes Yes Yes Yes Yes Yes Yes
AlarmViewShowOperatorNotes
(Page 1359)
Yes Yes Yes Yes Yes Yes Yes
OpenAllLogs (Page 1359) No No No No No No No
OpenScreenKeyboard
(Page 1360)
No No No No No No No
OpenCommandPrompt
(Page 1361)
No No No No No No No
OpenInternetExplorer
(Page 1362)
No No No No No No No
OpenControlPanel (Page 1362) No No No No No No No
OpenTaskManager (Page 1363) No No No No No No No
AcknowledgeAlarm (Page 1364) Yes Yes Yes Yes Yes Yes No
RecipeViewNewDataRecord
(Page 1364)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewGetDataRecordFromP
LC (Page 1365)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewClearDataRecord
(Page 1366)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewMenu (Page 1366) Yes Yes Yes Yes Yes Yes Yes
RecipeViewOpen (Page 1367) Yes Yes Yes Yes Yes Yes Yes
RecipeViewSetDataRecordToPLC
(Page 1367)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewSaveDataRecord
(Page 1368)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewSaveAsDataRecord
(Page 1368)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewSynchronizeDataReco
rdWithTags (Page 1369)
No No No No No No No
RecipeViewRenameDataRecord
(Page 1370)
Yes Yes Yes Yes Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1265
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
RecipeViewShowOperatorNotes
(Page 1370)
Yes Yes Yes Yes Yes Yes Yes
RecipeViewBack (Page 1371) Yes Yes Yes Yes Yes Yes Yes
ResetBit (Page 1372) Yes Yes Yes Yes Yes Yes Yes
ResetBitInTag (Page 1372) Yes Yes Yes Yes Yes Yes Yes
PressButton (Page 1373) Yes Yes Yes Yes Yes Yes No
ReleaseButton (Page 1374) Yes Yes Yes Yes Yes Yes No
ShiftAndMask (Page 1375) Yes Yes Yes Yes Yes Yes Yes
CloseAllLogs (Page 1376) No No No No No No No
SetDataRecordToPLC
(Page 1377)
No No No No No No No
SetDataRecordTagsToPLC
(Page 1378)
No No No No No No No
PageDown (Page 1379) Yes Yes Yes Yes Yes Yes No
PageUp (Page 1380) Yes Yes Yes Yes Yes Yes No
SendEMail (Page 1380) No No No No No No No
SetAcousticSignal (Page 1381) No No No No No No No
SetDisplayMode (Page 1382) No No No No No No No
SetDeviceMode (Page 1383) Yes Yes Yes Yes Yes Yes Yes
SetBit (Page 1384) Yes Yes Yes Yes Yes Yes Yes
SetBitInTag (Page 1384) Yes Yes Yes Yes Yes Yes Yes
SetBitWhileKeyPressed
(Page 1385)
Yes Yes Yes Yes Yes Yes Yes
SetColorBackgroundLighting
(Page 1387)
Yes No No No No No No
SetBrightness (Page 1387) No No No No No No No
SetScreenKeyboardMode
(Page 1388)
No No No No No No No
SetAlarmReportMode
(Page 1389)
No No No No No No No
SetRecipeTags (Page 1390) No No No No No No No
SetDaylightSavingTime
(Page 1391)
No No No No No No No
SetLanguage (Page 1392) Yes Yes Yes Yes Yes Yes Yes
SetTag (Page 1393) Yes Yes Yes Yes Yes Yes Yes
SetConnectionMode (Page 1394) Yes Yes Yes Yes Yes Yes Yes
SetWebAccess (Page 1395) No No No No No No No
BackupRAMFileSystem
(Page 1396)
No No No No No No No
SimulateSystemKey (Page 1396) Yes Yes Yes Yes Yes Yes No
SimulateTag (Page 1397) Yes Yes Yes Yes Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1266 System Manual, 08/2011,
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
SmartClientViewRefresh
(Page 1398)
No No No No No No No
SmartClientViewWriteProtectionOf
f (Page 1399)
No No No No No No No
SmartClientViewWriteProtectionO
n (Page 1399)
No No No No No No No
SmartClientViewDisconnect
(Page 1400)
No No No No No No No
SmartClientViewConnect
(Page 1401)
No No No No No No No
SmartClientViewLeave
(Page 1401)
No No No No No No No
SaveDataRecord (Page 1402) No No No No No No No
StartLogging (Page 1403) No No No No No No No
StartNextLog (Page 1404) No No No No No No No
StartProgram (Page 1404) No No No No No No No
StatusForceGetValues
(Page 1406)
No No No No No No No
StatusForceSetValues
(Page 1407)
No No No No No No No
ControlSmartServer (Page 1407) No No No No No No No
ControlWebServer (Page 1408) No No No No No No No
StopLogging (Page 1409) No No No No No No No
StopRuntime (Page 1410) Yes Yes Yes Yes Yes Yes Yes
LookupText (Page 1411) No No No No No No No
ResetTagToHandWheel
(Page 1412)
No No No No No No No
SetTagToHandWheel
(Page 1412)
No No No No No No No
TraceUserChange (Page 1413) Yes Yes Yes Yes Yes Yes Yes
DecreaseFocusedValue
(Page 1413)
Yes Yes Yes Yes Yes Yes No
DecreaseTag (Page 1414) Yes Yes Yes Yes Yes Yes Yes
ChangeConnection (Page 1415) Yes Yes Yes Yes Yes Yes Yes
WinACMPUpdateStartupCharacte
ristics (Page 1417)
No No No No No No No
WinACMPUpdateModeSelectorS
witchSetting (Page 1418)
No No No No No No No
WinACMPUpdateBUSF1LED
(Page 1419)
No No No No No No No
WinACMPUpdateBUSF2LED
(Page 1420)
No No No No No No No
WinACMPUpdateAverageExecuti
onTime (Page 1421)
No No No No No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1267
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
WinACMPUpdateAverageCycleTi
me (Page 1422)
No No No No No No No
WinACMPUpdateEXTFLED
(Page 1423)
No No No No No No No
WinACMPUpdateHMIExecutionTi
me (Page 1424)
No No No No No No No
WinACMPUpdateINTFLED
(Page 1425)
No No No No No No No
WinACMPUpdateLastCycleTime
(Page 1426)
No No No No No No No
WinACMPUpdateMaximumCycleT
ime (Page 1427)
No No No No No No No
WinACMPUpdateMinimumCycleTi
me (Page 1428)
No No No No No No No
WinACMPUpdatePowerLED
(Page 1429)
No No No No No No No
WinACMPUpdateIdleTime
(Page 1430)
No No No No No No No
WinACMPUpdateRUNLED
(Page 1431)
No No No No No No No
WinACMPUpdateSTOPLED
(Page 1432)
No No No No No No No
WinACMPLogging (Page 1433) No No No No No No No
WinACMPGetStartCharacteristics
(Page 1434)
No No No No No No No
WinACMPGetVersion
(Page 1434)
No No No No No No No
WinACMPClearCycleTimeBuffer
(Page 1435)
No No No No No No No
WinACMPSetStartAtBoot
(Page 1435)
No No No No No No No
WinACMPSetModeSelectorSwitch
(Page 1436)
No No No No No No No
WinACMPSetHMIExecutionTime
(Page 1437)
No No No No No No No
WinACMPSetResetCharacteristic
s (Page 1437)
No No No No No No No
WinACMPSetIdleTime
(Page 1438)
No No No No No No No
WinACMPSetStartMode
(Page 1438)
No No No No No No No
WinACMPStartHistogram
(Page 1439)
No No No No No No No
WinACMPControl (Page 1440) No No No No No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1268 System Manual, 08/2011,
KP300
Basic PN
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic
PN
WinACMPStopHistogram
(Page 1440)
No No No No No No No
WinACMPRestore (Page 1441) No No No No No No No
ShowLogonDialog (Page 1441) Yes Yes Yes Yes Yes Yes Yes
ShowOperatorNotes (Page 1442) Yes Yes Yes Yes Yes Yes Yes
ShowAlarmWindow (Page 1443) Yes Yes Yes Yes Yes Yes Yes
ShowSoftwareVersion
(Page 1444)
No No No No No No No
ShowSystemDiagnosticsWindow
(Page 1445)
No No No No No No No
ShowSystemAlarm (Page 1445) No No No No No No No
1)
For KTP600 Basic mono PN only
System functions on Panels
Availability of system functions
The following table shows the availability of the system functions on the Panels.
Technical data subject to change.
Overview
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
User-defined functions No No No No No Yes
Logoff (Page 1297) Yes Yes Yes Yes Yes Yes
ActivateScreen (Page 1297) Yes Yes Yes Yes Yes Yes
ActivateScreenByNumber
(Page 1298)
Yes Yes Yes Yes Yes Yes
ActivateCleanScreen (Page 1299) No No No Yes Yes
4)
Yes
2)
ActivateSystemDiagnosticsView
(Page 1300)
No No No No No No
ActivatePreviousScreen
(Page 1301)
Yes Yes Yes Yes Yes Yes
UpdateTag (Page 1302) Yes Yes No Yes Yes Yes
AdjustContrast (Page 1302) Yes Yes Yes Yes Yes No
Logon (Page 1303) Yes Yes Yes Yes Yes Yes
ArchiveLogFile (Page 1304) No No No No No Yes
LogTag (Page 1305) No No No No No Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1269
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
EditAlarm (Page 1306) Yes Yes Yes No Yes Yes
1)
ScreenObjectCursorDown
(Page 1307)
Yes Yes Yes Yes Yes Yes
ScreenObjectCursorUp
(Page 1307)
Yes Yes Yes Yes Yes Yes
ScreenObjectPageDown
(Page 1308)
Yes Yes Yes Yes Yes Yes
ScreenObjectPageUp (Page 1309) Yes Yes Yes Yes Yes Yes
Encode (Page 1309) No No Yes Yes Yes Yes
EncodeEx (Page 1310) No No Yes Yes Yes Yes
DirectKey (Page 1311) No No No No Yes
)
Yes
2)
DirectKeyScreenNumber
(Page 1314)
No No No No Yes
)
Yes
2)
PrintScreen (Page 1315) No No Yes No Yes Yes
PrintReport (Page 1315) No No Yes No Yes Yes
NotifyUserAction (Page 1316) No No No No No Yes
IncreaseFocusedValue
(Page 1317)
Yes Yes Yes No Yes
1)
Yes
1)
IncreaseTag (Page 1318) Yes Yes Yes Yes Yes Yes
ExportDataRecords (Page 1319) No No Yes No Yes Yes
ExportDataRecordsWithChecksum
(Page 1321)
No No No No No Yes
ExportImportUserAdministration
(Page 1324)
No No Yes No Yes Yes
GoToHome (Page 1324) Yes Yes Yes No Yes
1)
Yes
1)
GoToEnd (Page 1325) Yes Yes Yes No Yes
1)
Yes
1)
SafelyRemoveHardware
(Page 1326)
No No No No Yes
5)
No
HTMLBrowserStop (Page 1326) No No No No No No
HTMLBrowserRefresh (Page 1327) No No No No No No
HTMLBrowserForward (Page 1327) No No No No No No
HTMLBrowserBack (Page 1328) No No No No No No
ImportDataRecords (Page 1328) No No Yes No Yes Yes
ImportDataRecordsWithChecksum
(Page 1330)
No No No No No Yes
InvertBit (Page 1332) Yes Yes Yes Yes Yes Yes
InvertBitInTag (Page 1333) Yes Yes Yes Yes Yes Yes
InvertLinearScaling (Page 1334) Yes Yes Yes Yes Yes Yes
CalibrateTouchScreen (Page 1335) No No No Yes Yes Yes
2)
CopyLog (Page 1336) No No No No No Yes
TrendViewScrollForward
(Page 1337)
No No No Yes Yes Yes
TrendViewScrollBack (Page 1337) No No No Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1270 System Manual, 08/2011,
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
TrendViewExtend (Page 1338) No No No Yes Yes Yes
TrendViewCompress (Page 1339) No No No Yes Yes Yes
TrendViewRulerLeft (Page 1339) No No No Yes Yes Yes
TrendViewRulerRight (Page 1340) No No No Yes Yes Yes
TrendViewSetRulerMode
(Page 1341)
No No No Yes Yes Yes
TrendViewStartStop (Page 1342) No No No Yes Yes Yes
TrendViewBackToBeginning
(Page 1342)
No No No Yes Yes Yes
LoadDataRecord (Page 1343) No No No No Yes Yes
GetUserName (Page 1344) Yes Yes Yes Yes Yes Yes
GetDataRecordFromPLC
(Page 1345)
No No No No Yes Yes
GetDataRecordName (Page 1346) No No No No Yes Yes
GetDataRecordTagsFromPLC
(Page 1348)
No No No No Yes Yes
GetGroupNumber (Page 1349) Yes Yes Yes Yes Yes Yes
GetBrightness (Page 1349) No No No No No No
GetPassword (Page 1350) Yes Yes Yes Yes Yes Yes
Auto-Hotspot No No Yes No Yes Yes
LinearScaling (Page 1351) Yes Yes Yes Yes Yes Yes
ClearLog (Page 1352) No No No No No Yes
ClearDataRecord (Page 1352) No No No No Yes Yes
ClearDataRecordMemory
(Page 1354)
No No No No Yes Yes
ClearAlarmBuffer (Page 1355) Yes Yes Yes Yes Yes Yes
ClearAlarmBufferProTool
(Page 1356)
Yes Yes Yes No Yes Yes
AlarmViewUpdate (Page 1357) No No Yes No Yes Yes
AlarmViewEditAlarm (Page 1357) Yes Yes Yes Yes Yes Yes
AlarmViewAcknowledgeAlarm
(Page 1358)
Yes Yes Yes Yes Yes Yes
AlarmViewShowOperatorNotes
(Page 1359)
Yes Yes Yes Yes Yes Yes
OpenAllLogs (Page 1359) No No No No No Yes
OpenScreenKeyboard (Page 1360) No No No No No Yes
OpenCommandPrompt
(Page 1361)
No No No No No Yes
OpenInternetExplorer (Page 1362) No No No No Yes
3)
Yes
OpenControlPanel (Page 1362) No No No No Yes Yes
OpenTaskManager (Page 1363) No No No No No Yes
AcknowledgeAlarm (Page 1364) Yes Yes Yes No yes
1)4)
Yes
1)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1271
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
RecipeViewNewDataRecord
(Page 1364)
No Yes Yes Yes Yes Yes
RecipeViewGetDataRecordFromPL
C (Page 1365)
No Yes Yes Yes Yes Yes
RecipeViewClearDataRecord
(Page 1366)
No Yes Yes Yes Yes Yes
RecipeViewMenu (Page 1366) No Yes Yes Yes Yes Yes
RecipeViewOpen (Page 1367) No Yes Yes Yes Yes Yes
RecipeViewSetDataRecordToPLC
(Page 1367)
No Yes Yes Yes Yes Yes
RecipeViewSaveDataRecord
(Page 1368)
No Yes Yes Yes Yes Yes
RecipeViewSaveAsDataRecord
(Page 1368)
No Yes Yes Yes Yes Yes
RecipeViewSynchronizeDataRecor
dWithTags (Page 1369)
No No No No Yes Yes
RecipeViewRenameDataRecord
(Page 1370)
No Yes Yes Yes Yes Yes
RecipeViewShowOperatorNotes
(Page 1370)
No Yes Yes Yes Yes Yes
RecipeViewBack (Page 1371) No Yes Yes Yes Yes Yes
ResetBit (Page 1372) Yes Yes Yes Yes Yes Yes
ResetBitInTag (Page 1372) Yes Yes Yes Yes Yes Yes
PressButton (Page 1373) Yes Yes Yes No Yes
)
Yes
)
ReleaseButton (Page 1374) Yes Yes Yes No Yes Yes
1)
ShiftAndMask (Page 1375) Yes Yes Yes Yes Yes Yes
CloseAllLogs (Page 1376) No No No No No Yes
SetDataRecordToPLC (Page 1377) No No No No Yes Yes
SetDataRecordTagsToPLC
(Page 1378)
No No No No Yes Yes
PageDown (Page 1379) Yes Yes Yes No yes
1)4)
Yes
1)
PageUp (Page 1380) Yes Yes Yes No yes
1).4)
Yes
1)
SendEMail (Page 1380) Yes Yes Yes No Yes
3)
Yes
SetAcousticSignal (Page 1381) No No No No No No
SetDisplayMode (Page 1382) No No No No No No
SetDeviceMode (Page 1383) Yes Yes Yes Yes Yes Yes
SetBit (Page 1384) Yes Yes Yes Yes Yes Yes
SetBitInTag (Page 1384) Yes Yes Yes Yes Yes Yes
SetBitWhileKeyPressed
(Page 1385)
Yes Yes Yes Yes Yes Yes
SetColorBackgroundLighting
(Page 1387)
No No No No No No
SetBrightness (Page 1387) No No No No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1272 System Manual, 08/2011,
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
SetScreenKeyboardMode
(Page 1388)
No No No No No Yes
SetAlarmReportMode (Page 1389) No No Yes No Yes Yes
SetRecipeTags (Page 1390) No No Yes No Yes Yes
SetDaylightSavingTime
(Page 1391)
No No No No No No
SetLanguage (Page 1392) Yes Yes Yes Yes Yes Yes
SetTag (Page 1393) Yes Yes Yes Yes Yes Yes
SetConnectionMode (Page 1394) Yes Yes Yes Yes Yes Yes
SetWebAccess (Page 1395) No No No No Yes Yes
BackupRAMFileSystem
(Page 1396)
No No No No No No
SimulateSystemKey (Page 1396) No No Yes No yes
1)4)
Yes
1)
SimulateTag (Page 1397) Yes Yes Yes Yes Yes Yes
SmartClientViewRefresh
(Page 1398)
No No No No Yes
3)
Yes
SmartClientViewWriteProtectionOff
(Page 1399)
No No No No Yes
3)
Yes
SmartClientViewWriteProtectionOn
(Page 1399)
No No No No Yes
3)
Yes
SmartClientViewDisconnect
(Page 1400)
No No No No Yes
3)
Yes
SmartClientViewConnect
(Page 1401)
No No No No Yes
3)
Yes
SmartClientViewLeave
(Page 1401)
No No No No Yes
3)
Yes
SaveDataRecord (Page 1402) No No No No Yes Yes
StartLogging (Page 1403) No No No No No Yes
StartNextLog (Page 1404) No No No No No Yes
StartProgram (Page 1404) No No No No No Yes
StatusForceGetValues (Page 1406) No No No No Yes Yes
StatusForceSetValues (Page 1407) No No No No Yes Yes
ControlSmartServer (Page 1407) No No No No Yes
3)
Yes
ControlWebServer (Page 1408) No No No No Yes
3)
Yes
StopLogging (Page 1409) No No No No No Yes
StopRuntime (Page 1410) Yes Yes Yes Yes Yes Yes
LookupText (Page 1411) No No Yes No Yes Yes
ResetTagToHandWheel
(Page 1412)
No No No No No No
SetTagToHandWheel (Page 1412) No No No No No No
TraceUserChange (Page 1413) Yes Yes Yes Yes Yes Yes
DecreaseFocusedValue
(Page 1413)
Yes Yes Yes No yes
1)4)
Yes
1)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1273
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
DecreaseTag (Page 1414) Yes Yes Yes Yes Yes Yes
ChangeConnection (Page 1415) Yes Yes Yes Yes Yes Yes
WinACMPUpdateStartupCharacteri
stics (Page 1417)
No No No No No No
WinACMPUpdateModeSelectorSwit
chSetting (Page 1418)
No No No No No No
WinACMPUpdateBUSF1LED
(Page 1419)
No No No No No No
WinACMPUpdateBUSF2LED
(Page 1420)
No No No No No No
WinACMPUpdateAverageExecutio
nTime (Page 1421)
No No No No No No
WinACMPUpdateAverageCycleTim
e (Page 1422)
No No No No No No
WinACMPUpdateEXTFLED
(Page 1423)
No No No No No No
WinACMPUpdateHMIExecutionTim
e (Page 1424)
No No No No No No
WinACMPUpdateINTFLED
(Page 1425)
No No No No No No
WinACMPUpdateLastCycleTime
(Page 1426)
No No No No No No
WinACMPUpdateMaximumCycleTi
me (Page 1427)
No No No No No No
WinACMPUpdateMinimumCycleTi
me (Page 1428)
No No No No No No
WinACMPUpdatePowerLED
(Page 1429)
No No No No No No
WinACMPUpdateIdleTime
(Page 1430)
No No No No No No
WinACMPUpdateRUNLED
(Page 1431)
No No No No No No
WinACMPUpdateSTOPLED
(Page 1432)
No No No No No No
WinACMPLogging (Page 1433) No No No No No No
WinACMPGetStartCharacteristics
(Page 1434)
No No No No No No
WinACMPGetVersion (Page 1434) No No No No No No
WinACMPClearCycleTimeBuffer
(Page 1435)
No No No No No No
WinACMPSetStartAtBoot
(Page 1435)
No No No No No No
WinACMPSetModeSelectorSwitch
(Page 1436)
No No No No No No
WinACMPSetHMIExecutionTime
(Page 1437)
No No No No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1274 System Manual, 08/2011,
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
WinACMPSetResetCharacteristics
(Page 1437)
No No No No No No
WinACMPSetIdleTime (Page 1438) No No No No No No
WinACMPSetStartMode
(Page 1438)
No No No No No No
WinACMPStartHistogram
(Page 1439)
No No No No No No
WinACMPControl (Page 1440) No No No No No No
WinACMPStopHistogram
(Page 1440)
No No No No No No
WinACMPRestore (Page 1441) No No No No No No
ShowLogonDialog (Page 1441) Yes Yes Yes Yes Yes Yes
ShowOperatorNotes (Page 1442) Yes Yes Yes Yes Yes Yes
ShowAlarmWindow (Page 1443) Yes Yes Yes Yes Yes Yes
ShowSoftwareVersion (Page 1444) No No No No No Yes
ShowSystemDiagnosticsWindow
(Page 1445)
No No No No No No
ShowSystemAlarm (Page 1445) No No Yes No Yes Yes
1)
only with keyboard units
2)
only with touch screen devices
3)
only with PROFINET Bus (PN devices)
4)
only with TP 177B
5)
Only for TP 177B 4" PN/DP
System functions on Multi Panels
Availability of system functions
The following table shows the availability of the system functions on the Multi Panels.
Technical data subject to change.
Overview
MP 177 MP 277 MP 377
User-defined functions No Yes Yes
Logoff (Page 1297) Yes Yes Yes
ActivateScreen (Page 1297) Yes Yes Yes
ActivateScreenByNumber
(Page 1298)
Yes Yes Yes
ActivateCleanScreen (Page 1299) Yes
2)
Yes
2)
Yes
2)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1275
MP 177 MP 277 MP 377
ActivateSystemDiagnosticsView
(Page 1300)
No No No
ActivatePreviousScreen (Page 1301) Yes Yes Yes
UpdateTag (Page 1302) Yes Yes Yes
AdjustContrast (Page 1302) Yes
2)
No No
Logon (Page 1303) Yes Yes Yes
ArchiveLogFile (Page 1304) No Yes Yes
LogTag (Page 1305) No Yes Yes
EditAlarm (Page 1306) No Yes
1)
No
ScreenObjectCursorDown
(Page 1307)
Yes Yes Yes
ScreenObjectCursorUp (Page 1307) Yes Yes Yes
ScreenObjectPageDown (Page 1308) Yes Yes Yes
ScreenObjectPageUp (Page 1309) Yes Yes Yes
Encode (Page 1309) Yes Yes Yes
EncodeEx (Page 1310) Yes Yes Yes
DirectKey (Page 1311) Yes
2)
Yes
2)
Yes
2)
DirectKeyScreenNumber (Page 1314) Yes
2)
Yes
2)
Yes
2)
PrintScreen (Page 1315) Yes Yes Yes
PrintReport (Page 1315) Yes Yes Yes
NotifyUserAction (Page 1316) No Yes Yes
IncreaseFocusedValue (Page 1317) Yes
1)
Yes
1)
Yes
1)
IncreaseTag (Page 1318) Yes Yes Yes
ExportDataRecords (Page 1319) Yes Yes Yes
ExportDataRecordsWithChecksum
(Page 1321)
Yes Yes Yes
ExportImportUserAdministration
(Page 1324)
Yes Yes Yes
GoToHome (Page 1324) Yes
1)
Yes
1)
Yes
1)
GoToEnd (Page 1325) Yes
1)
Yes
1)
Yes
1)
SafelyRemoveHardware (Page 1326) No Yes Yes
HTMLBrowserStop (Page 1326) No No No
HTMLBrowserRefresh (Page 1327) No No No
HTMLBrowserForward (Page 1327) No No No
HTMLBrowserBack (Page 1328) No No No
ImportDataRecords (Page 1328) Yes Yes Yes
ImportDataRecordsWithChecksum
(Page 1330)
Yes Yes Yes
InvertBit (Page 1332) Yes Yes Yes
InvertBitInTag (Page 1333) Yes Yes Yes
InvertLinearScaling (Page 1334) Yes Yes Yes
CalibrateTouchScreen (Page 1335) Yes
2)
Yes
2)
Yes
2)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1276 System Manual, 08/2011,
MP 177 MP 277 MP 377
CopyLog (Page 1336) No Yes Yes
TrendViewScrollForward (Page 1337) Yes Yes Yes
TrendViewScrollBack (Page 1337) Yes Yes Yes
TrendViewExtend (Page 1338) Yes Yes Yes
TrendViewCompress (Page 1339) Yes Yes Yes
TrendViewRulerLeft (Page 1339) Yes Yes Yes
TrendViewRulerRight (Page 1340) Yes Yes Yes
TrendViewSetRulerMode (Page 1341) Yes Yes Yes
TrendViewStartStop (Page 1342) Yes Yes Yes
TrendViewBackToBeginning
(Page 1342)
Yes Yes Yes
LoadDataRecord (Page 1343) Yes Yes Yes
GetUserName (Page 1344) Yes Yes Yes
GetDataRecordFromPLC (Page 1345) Yes Yes Yes
GetDataRecordName (Page 1346) Yes Yes Yes
GetDataRecordTagsFromPLC
(Page 1348)
Yes Yes Yes
GetGroupNumber (Page 1349) Yes Yes Yes
GetBrightness (Page 1349) No No No
GetPassword (Page 1350) Yes Yes Yes
Auto-Hotspot Yes Yes Yes
LinearScaling (Page 1351) Yes Yes Yes
ClearLog (Page 1352) No Yes Yes
ClearDataRecord (Page 1352) Yes Yes Yes
ClearDataRecordMemory (Page 1354) Yes Yes Yes
ClearAlarmBuffer (Page 1355) Yes Yes Yes
ClearAlarmBufferProTool (Page 1356) Yes Yes Yes
AlarmViewUpdate (Page 1357) Yes Yes Yes
AlarmViewEditAlarm (Page 1357) Yes Yes Yes
AlarmViewAcknowledgeAlarm
(Page 1358)
Yes Yes Yes
AlarmViewShowOperatorNotes
(Page 1359)
Yes Yes Yes
OpenAllLogs (Page 1359) No Yes Yes
OpenScreenKeyboard (Page 1360) No Yes Yes
OpenCommandPrompt (Page 1361) No Yes Yes
OpenInternetExplorer (Page 1362) No Yes Yes
OpenControlPanel (Page 1362) Yes Yes Yes
OpenTaskManager (Page 1363) No Yes Yes
AcknowledgeAlarm (Page 1364) Yes
1)
Yes
1)
Yes
1)
RecipeViewNewDataRecord
(Page 1364)
Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1277
MP 177 MP 277 MP 377
RecipeViewGetDataRecordFromPLC
(Page 1365)
Yes Yes Yes
RecipeViewClearDataRecord
(Page 1366)
Yes Yes Yes
RecipeViewMenu (Page 1366) Yes Yes Yes
RecipeViewOpen (Page 1367) Yes Yes Yes
RecipeViewSetDataRecordToPLC
(Page 1367)
Yes Yes Yes
RecipeViewSaveDataRecord
(Page 1368)
Yes Yes Yes
RecipeViewSaveAsDataRecord
(Page 1368)
Yes Yes Yes
RecipeViewSynchronizeDataRecordW
ithTags (Page 1369)
Yes Yes Yes
RecipeViewRenameDataRecord
(Page 1370)
Yes Yes Yes
RecipeViewShowOperatorNotes
(Page 1370)
Yes Yes Yes
RecipeViewBack (Page 1371) Yes Yes Yes
ResetBit (Page 1372) Yes Yes Yes
ResetBitInTag (Page 1372) Yes Yes Yes
PressButton (Page 1373) Yes Yes Yes
)
ReleaseButton (Page 1374) Yes
)
Yes
)
Yes
)
ShiftAndMask (Page 1375) Yes Yes Yes
CloseAllLogs (Page 1376) No Yes Yes
SetDataRecordToPLC (Page 1377) Yes Yes Yes
SetDataRecordTagsToPLC
(Page 1378)
Yes Yes Yes
PageDown (Page 1379) Yes
1)
Yes
1)
Yes
1)
PageUp (Page 1380) Yes
1)
Yes
1)
Yes
1)
SendEMail (Page 1380) Yes Yes Yes
SetAcousticSignal (Page 1381) No Yes
2)
Yes
2)
SetDisplayMode (Page 1382) No No No
SetDeviceMode (Page 1383) Yes Yes Yes
SetBit (Page 1384) Yes Yes Yes
SetBitInTag (Page 1384) Yes Yes Yes
SetBitWhileKeyPressed (Page 1385) Yes Yes
1)
Yes
1)
SetColorBackgroundLighting
(Page 1387)
No No No
SetBrightness (Page 1387) No No No
SetScreenKeyboardMode
(Page 1388)
No Yes Yes
SetAlarmReportMode (Page 1389) Yes Yes Yes
SetRecipeTags (Page 1390) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1278 System Manual, 08/2011,
MP 177 MP 277 MP 377
SetDaylightSavingTime (Page 1391) No Yes Yes
SetLanguage (Page 1392) Yes Yes Yes
SetTag (Page 1393) Yes Yes Yes
SetConnectionMode (Page 1394) Yes Yes Yes
SetWebAccess (Page 1395) Yes Yes Yes
BackupRAMFileSystem (Page 1396) No Yes Yes
SimulateSystemKey (Page 1396) No Yes
1)
Yes
1)
SimulateTag (Page 1397) Yes Yes Yes
SmartClientViewRefresh (Page 1398) Yes Yes Yes
SmartClientViewWriteProtectionOff
(Page 1399)
Yes Yes Yes
SmartClientViewWriteProtectionOn
(Page 1399)
Yes Yes Yes
SmartClientViewDisconnect
(Page 1400)
Yes Yes Yes
SmartClientViewConnect (Page 1401) Yes Yes Yes
SmartClientViewLeave (Page 1401) Yes Yes Yes
SaveDataRecord (Page 1402) Yes Yes Yes
StartLogging (Page 1403) No Yes Yes
StartNextLog (Page 1404) No Yes Yes
StartProgram (Page 1404) Yes Yes Yes
StatusForceGetValues (Page 1406) Yes Yes Yes
StatusForceSetValues (Page 1407) Yes Yes Yes
ControlSmartServer (Page 1407) Yes Yes Yes
ControlWebServer (Page 1408) Yes Yes Yes
StopLogging (Page 1409) No Yes Yes
StopRuntime (Page 1410) Yes Yes Yes
LookupText (Page 1411) Yes Yes Yes
ResetTagToHandWheel (Page 1412) No No No
SetTagToHandWheel (Page 1412) No No No
TraceUserChange (Page 1413) Yes Yes Yes
DecreaseFocusedValue (Page 1413) Yes
1)
Yes
1)
Yes
1)
DecreaseTag (Page 1414) Yes Yes Yes
ChangeConnection (Page 1415) Yes Yes Yes
WinACMPUpdateStartupCharacteristic
s (Page 1417)
Yes Yes Yes
WinACMPUpdateModeSelectorSwitch
Setting (Page 1418)
Yes Yes Yes
WinACMPUpdateBUSF1LED
(Page 1419)
Yes Yes Yes
WinACMPUpdateBUSF2LED
(Page 1420)
Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1279
MP 177 MP 277 MP 377
WinACMPUpdateAverageExecutionTi
me (Page 1421)
Yes Yes Yes
WinACMPUpdateAverageCycleTime
(Page 1422)
Yes Yes Yes
WinACMPUpdateEXTFLED
(Page 1423)
Yes Yes Yes
WinACMPUpdateHMIExecutionTime
(Page 1424)
Yes Yes Yes
WinACMPUpdateINTFLED
(Page 1425)
Yes Yes Yes
WinACMPUpdateLastCycleTime
(Page 1426)
Yes Yes Yes
WinACMPUpdateMaximumCycleTime
(Page 1427)
Yes Yes Yes
WinACMPUpdateMinimumCycleTime
(Page 1428)
Yes Yes Yes
WinACMPUpdatePowerLED
(Page 1429)
Yes Yes Yes
WinACMPUpdateIdleTime
(Page 1430)
Yes Yes Yes
WinACMPUpdateRUNLED
(Page 1431)
Yes Yes Yes
WinACMPUpdateSTOPLED
(Page 1432)
Yes Yes Yes
WinACMPLogging (Page 1433) Yes Yes Yes
WinACMPGetStartCharacteristics
(Page 1434)
Yes Yes Yes
WinACMPGetVersion (Page 1434) Yes Yes Yes
WinACMPClearCycleTimeBuffer
(Page 1435)
Yes Yes Yes
WinACMPSetStartAtBoot (Page 1435) Yes Yes Yes
WinACMPSetModeSelectorSwitch
(Page 1436)
Yes Yes Yes
WinACMPSetHMIExecutionTime
(Page 1437)
Yes Yes Yes
WinACMPSetResetCharacteristics
(Page 1437)
Yes Yes Yes
WinACMPSetIdleTime (Page 1438) Yes Yes Yes
WinACMPSetStartMode (Page 1438) Yes Yes Yes
WinACMPStartHistogram (Page 1439) Yes Yes Yes
WinACMPControl (Page 1440) Yes Yes Yes
WinACMPStopHistogram (Page 1440) Yes Yes Yes
WinACMPRestore (Page 1441) Yes Yes Yes
ShowLogonDialog (Page 1441) Yes Yes Yes
ShowOperatorNotes (Page 1442) Yes Yes Yes
ShowAlarmWindow (Page 1443) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1280 System Manual, 08/2011,
MP 177 MP 277 MP 377
ShowSoftwareVersion (Page 1444) No Yes Yes
ShowSystemDiagnosticsWindow
(Page 1445)
No No No
ShowSystemAlarm (Page 1445) Yes Yes Yes
1)
only with keyboard units
2)
only with touch screen devices
System functions on Comfort Panels
Availability of system functions
The following table shows the availability of the system functions on the Comfort Panels.
Technical data subject to change.
Overview
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
User-defined functions Yes Yes Yes
Logoff (Page 1297) Yes Yes Yes
ActivateScreen (Page 1297) Yes Yes Yes
ActivateScreenByNumber
(Page 1298)
Yes Yes Yes
ActivateCleanScreen (Page 1299) Yes
1)
Yes No
ActivateSystemDiagnosticsView
(Page 1300)
Yes Yes Yes
ActivatePreviousScreen (Page 1301) Yes Yes Yes
UpdateTag (Page 1302) Yes Yes Yes
AdjustContrast (Page 1302) No No No
Logon (Page 1303) Yes Yes Yes
ArchiveLogFile (Page 1304) Yes Yes Yes
LogTag (Page 1305) Yes Yes Yes
EditAlarm (Page 1306) Yes No Yes
ScreenObjectCursorDown
(Page 1307)
Yes Yes Yes
ScreenObjectCursorUp (Page 1307) Yes Yes Yes
ScreenObjectPageDown
(Page 1308)
Yes Yes Yes
ScreenObjectPageUp (Page 1309) Yes Yes Yes
Encode (Page 1309) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1281
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
EncodeEx (Page 1310) Yes Yes Yes
DirectKey (Page 1311) Yes
1)
Yes No
DirectKeyScreenNumber
(Page 1314)
Yes
1)
Yes No
PrintScreen (Page 1315) Yes Yes Yes
PrintReport (Page 1315) Yes Yes Yes
NotifyUserAction (Page 1316) Yes Yes Yes
IncreaseFocusedValue (Page 1317) Yes No Yes
IncreaseTag (Page 1318) Yes Yes Yes
ExportDataRecords (Page 1319) Yes Yes Yes
ExportDataRecordsWithChecksum
(Page 1321)
Yes Yes Yes
ExportImportUserAdministration
(Page 1324)
Yes Yes Yes
GoToHome (Page 1324) Yes No Yes
GoToEnd (Page 1325) Yes No Yes
SafelyRemoveHardware (Page 1326) Yes Yes Yes
HTMLBrowserStop (Page 1326) No No No
HTMLBrowserRefresh (Page 1327) No No No
HTMLBrowserForward (Page 1327) No No No
HTMLBrowserBack (Page 1328) No No No
ImportDataRecords (Page 1328) Yes Yes Yes
ImportDataRecordsWithChecksum
(Page 1330)
Yes Yes Yes
InvertBit (Page 1332) Yes Yes Yes
InvertBitInTag (Page 1333) Yes Yes Yes
InvertLinearScaling (Page 1334) Yes Yes Yes
CalibrateTouchScreen (Page 1335) Yes
1)
Yes No
CopyLog (Page 1336) Yes Yes Yes
TrendViewScrollForward
(Page 1337)
Yes Yes Yes
TrendViewScrollBack (Page 1337) Yes Yes Yes
TrendViewExtend (Page 1338) Yes Yes Yes
TrendViewCompress (Page 1339) Yes Yes Yes
TrendViewRulerLeft (Page 1339) Yes Yes Yes
TrendViewRulerRight (Page 1340) Yes Yes Yes
TrendViewSetRulerMode
(Page 1341)
Yes Yes Yes
TrendViewStartStop (Page 1342) Yes Yes Yes
TrendViewBackToBeginning
(Page 1342)
Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1282 System Manual, 08/2011,
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
LoadDataRecord (Page 1343) Yes Yes Yes
GetUserName (Page 1344) Yes Yes Yes
GetDataRecordFromPLC
(Page 1345)
Yes Yes Yes
GetDataRecordName (Page 1346) Yes Yes Yes
GetDataRecordTagsFromPLC
(Page 1348)
Yes Yes Yes
GetGroupNumber (Page 1349) Yes Yes Yes
GetBrightness (Page 1349) Yes Yes Yes
GetPassword (Page 1350) Yes Yes Yes
Auto-Hotspot Yes Yes Yes
LinearScaling (Page 1351) Yes Yes Yes
ClearLog (Page 1352) Yes Yes Yes
ClearDataRecord (Page 1352) Yes Yes Yes
ClearDataRecordMemory
(Page 1354)
Yes Yes Yes
ClearAlarmBuffer (Page 1355) Yes Yes Yes
ClearAlarmBufferProTool
(Page 1356)
Yes Yes Yes
AlarmViewUpdate (Page 1357) Yes Yes Yes
AlarmViewEditAlarm (Page 1357) Yes Yes Yes
AlarmViewAcknowledgeAlarm
(Page 1358)
Yes Yes Yes
AlarmViewShowOperatorNotes
(Page 1359)
Yes Yes Yes
OpenAllLogs (Page 1359) Yes Yes Yes
OpenScreenKeyboard (Page 1360) Yes Yes Yes
OpenCommandPrompt (Page 1361) Yes Yes Yes
OpenInternetExplorer (Page 1362) Yes Yes Yes
OpenControlPanel (Page 1362) Yes Yes Yes
OpenTaskManager (Page 1363) Yes Yes Yes
AcknowledgeAlarm (Page 1364) Yes No Yes
RecipeViewNewDataRecord
(Page 1364)
Yes Yes Yes
RecipeViewGetDataRecordFromPLC
(Page 1365)
Yes Yes Yes
RecipeViewClearDataRecord
(Page 1366)
Yes Yes Yes
RecipeViewMenu (Page 1366) Yes Yes Yes
RecipeViewOpen (Page 1367) Yes Yes Yes
RecipeViewSetDataRecordToPLC
(Page 1367)
Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1283
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
RecipeViewSaveDataRecord
(Page 1368)
Yes Yes Yes
RecipeViewSaveAsDataRecord
(Page 1368)
Yes Yes Yes
RecipeViewSynchronizeDataRecord
WithTags (Page 1369)
Yes Yes Yes
RecipeViewRenameDataRecord
(Page 1370)
Yes Yes Yes
RecipeViewShowOperatorNotes
(Page 1370)
Yes Yes Yes
RecipeViewBack (Page 1371) Yes Yes Yes
ResetBit (Page 1372) Yes Yes Yes
ResetBitInTag (Page 1372) Yes Yes Yes
PressButton (Page 1373) Yes Yes Yes
ReleaseButton (Page 1374) Yes Yes Yes
ShiftAndMask (Page 1375) Yes Yes Yes
CloseAllLogs (Page 1376) Yes Yes Yes
SetDataRecordToPLC (Page 1377) Yes Yes Yes
SetDataRecordTagsToPLC
(Page 1378)
Yes Yes Yes
PageDown (Page 1379) Yes No Yes
PageUp (Page 1380) Yes No Yes
SendEMail (Page 1380) Yes Yes Yes
SetAcousticSignal (Page 1381) Yes
1)
Yes No
SetDisplayMode (Page 1382) No No No
SetDeviceMode (Page 1383) Yes Yes Yes
SetBit (Page 1384) Yes Yes Yes
SetBitInTag (Page 1384) Yes Yes Yes
SetBitWhileKeyPressed (Page 1385) Yes Yes Yes
SetColorBackgroundLighting
(Page 1387)
No No No
SetBrightness (Page 1387) Yes Yes Yes
SetScreenKeyboardMode
(Page 1388)
Yes Yes Yes
SetAlarmReportMode (Page 1389) Yes Yes Yes
SetRecipeTags (Page 1390) Yes Yes Yes
SetDaylightSavingTime (Page 1391) Yes Yes Yes
SetLanguage (Page 1392) Yes Yes Yes
SetTag (Page 1393) Yes Yes Yes
SetConnectionMode (Page 1394) Yes Yes Yes
SetWebAccess (Page 1395) Yes Yes Yes
BackupRAMFileSystem (Page 1396) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1284 System Manual, 08/2011,
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
SimulateSystemKey (Page 1396) Yes No Yes
SimulateTag (Page 1397) Yes Yes Yes
SmartClientViewRefresh
(Page 1398)
Yes Yes Yes
SmartClientViewWriteProtectionOff
(Page 1399)
Yes Yes Yes
SmartClientViewWriteProtectionOn
(Page 1399)
Yes Yes Yes
SmartClientViewDisconnect
(Page 1400)
Yes Yes Yes
SmartClientViewConnect
(Page 1401)
Yes Yes Yes
SmartClientViewLeave (Page 1401) Yes Yes Yes
SaveDataRecord (Page 1402) Yes Yes Yes
StartLogging (Page 1403) Yes Yes Yes
StartNextLog (Page 1404) Yes Yes Yes
StartProgram (Page 1404) Yes Yes Yes
StatusForceGetValues (Page 1406) Yes Yes Yes
StatusForceSetValues (Page 1407) Yes Yes Yes
ControlSmartServer (Page 1407) Yes Yes Yes
ControlWebServer (Page 1408) Yes Yes Yes
StopLogging (Page 1409) Yes Yes Yes
StopRuntime (Page 1410) Yes Yes Yes
LookupText (Page 1411) Yes Yes Yes
ResetTagToHandWheel (Page 1412) No No No
SetTagToHandWheel (Page 1412) No No No
TraceUserChange (Page 1413) Yes Yes Yes
DecreaseFocusedValue (Page 1413) Yes No Yes
DecreaseTag (Page 1414) Yes Yes Yes
ChangeConnection (Page 1415) Yes Yes Yes
WinACMPUpdateStartupCharacteristi
cs (Page 1417)
No No No
WinACMPUpdateModeSelectorSwitc
hSetting (Page 1418)
No No No
WinACMPUpdateBUSF1LED
(Page 1419)
No No No
WinACMPUpdateBUSF2LED
(Page 1420)
No No No
WinACMPUpdateAverageExecutionT
ime (Page 1421)
No No No
WinACMPUpdateAverageCycleTime
(Page 1422)
No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1285
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
WinACMPUpdateEXTFLED
(Page 1423)
No No No
WinACMPUpdateHMIExecutionTime
(Page 1424)
No No No
WinACMPUpdateINTFLED
(Page 1425)
No No No
WinACMPUpdateLastCycleTime
(Page 1426)
No No No
WinACMPUpdateMaximumCycleTim
e (Page 1427)
No No No
WinACMPUpdateMinimumCycleTime
(Page 1428)
No No No
WinACMPUpdatePowerLED
(Page 1429)
No No No
WinACMPUpdateIdleTime
(Page 1430)
No No No
WinACMPUpdateRUNLED
(Page 1431)
No No No
WinACMPUpdateSTOPLED
(Page 1432)
No No No
WinACMPLogging (Page 1433) No No No
WinACMPGetStartCharacteristics
(Page 1434)
No No No
WinACMPGetVersion (Page 1434) No No No
WinACMPClearCycleTimeBuffer
(Page 1435)
No No No
WinACMPSetStartAtBoot
(Page 1435)
No No No
WinACMPSetModeSelectorSwitch
(Page 1436)
No No No
WinACMPSetHMIExecutionTime
(Page 1437)
No No No
WinACMPSetResetCharacteristics
(Page 1437)
No No No
WinACMPSetIdleTime (Page 1438) No No No
WinACMPSetStartMode (Page 1438) No No No
WinACMPStartHistogram
(Page 1439)
No No No
WinACMPControl (Page 1440) No No No
WinACMPStopHistogram
(Page 1440)
No No No
WinACMPRestore (Page 1441) No No No
ShowLogonDialog (Page 1441) Yes Yes Yes
ShowOperatorNotes (Page 1442) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1286 System Manual, 08/2011,
KTP400
KP400
TP700
TP900
TP1200
KP700
KP900
KP1200
ShowAlarmWindow (Page 1443) Yes Yes Yes
ShowSoftwareVersion (Page 1444) Yes Yes Yes
ShowSystemDiagnosticsWindow
(Page 1445)
Yes Yes Yes
ShowSystemAlarm (Page 1445) Yes Yes Yes
1)
Only on KTP 400 Comfort
System functions on Mobile Panels
Availability of system functions
The following table shows the availability of the system functions on the Mobile Panels.
Technical data subject to change.
Overview
Mobile Panel 177
DP
Mobile Panel 177
PN
Mobile Panel 277
Mobile Panel 277 IWLAN
Mobile Panel 277 F IWLAN
User-defined functions No No Yes
Logoff (Page 1297) Yes Yes Yes
ActivateScreen (Page 1297) Yes Yes Yes
ActivateScreenByNumber (Page 1298) Yes Yes Yes
ActivateCleanScreen (Page 1299) No No No
ActivateSystemDiagnosticsView
(Page 1300)
No No No
ActivatePreviousScreen (Page 1301) Yes Yes Yes
UpdateTag (Page 1302) Yes Yes Yes
AdjustContrast (Page 1302) No No No
Logon (Page 1303) Yes Yes Yes
ArchiveLogFile (Page 1304) No No Yes
LogTag (Page 1305) No No Yes
EditAlarm (Page 1306) Yes Yes Yes
ScreenObjectCursorDown (Page 1307) Yes Yes Yes
ScreenObjectCursorUp (Page 1307) Yes Yes Yes
ScreenObjectPageDown (Page 1308) Yes Yes Yes
ScreenObjectPageUp (Page 1309) Yes Yes Yes
Encode (Page 1309) Yes Yes Yes
EncodeEx (Page 1310) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1287
Mobile Panel 177
DP
Mobile Panel 177
PN
Mobile Panel 277
Mobile Panel 277 IWLAN
Mobile Panel 277 F IWLAN
DirectKey (Page 1311) Yes Yes Yes
DirectKeyScreenNumber (Page 1314) Yes Yes Yes
PrintScreen (Page 1315) No Yes Yes
PrintReport (Page 1315) No Yes Yes
NotifyUserAction (Page 1316) No No Yes
IncreaseFocusedValue (Page 1317) Yes Yes Yes
IncreaseTag (Page 1318) Yes Yes Yes
ExportDataRecords (Page 1319) Yes Yes Yes
ExportDataRecordsWithChecksum
(Page 1321)
No No Yes
ExportImportUserAdministration
(Page 1324)
Yes Yes Yes
GoToHome (Page 1324) Yes Yes Yes
GoToEnd (Page 1325) Yes Yes Yes
SafelyRemoveHardware (Page 1326) No No Yes
HTMLBrowserStop (Page 1326) No No No
HTMLBrowserRefresh (Page 1327) No No No
HTMLBrowserForward (Page 1327) No No No
HTMLBrowserBack (Page 1328) No No No
ImportDataRecords (Page 1328) Yes Yes Yes
ImportDataRecordsWithChecksum
(Page 1330)
No No Yes
InvertBit (Page 1332) Yes Yes Yes
InvertBitInTag (Page 1333) Yes Yes Yes
InvertLinearScaling (Page 1334) Yes Yes Yes
CalibrateTouchScreen (Page 1335) Yes Yes Yes
2)
CopyLog (Page 1336) No No Yes
TrendViewScrollForward (Page 1337) Yes Yes Yes
TrendViewScrollBack (Page 1337) Yes Yes Yes
TrendViewExtend (Page 1338) Yes Yes Yes
TrendViewCompress (Page 1339) Yes Yes Yes
TrendViewRulerLeft (Page 1339) Yes Yes Yes
TrendViewRulerRight (Page 1340) Yes Yes Yes
TrendViewSetRulerMode (Page 1341) Yes Yes Yes
TrendViewStartStop (Page 1342) Yes Yes Yes
TrendViewBackToBeginning (Page 1342) Yes Yes Yes
LoadDataRecord (Page 1343) Yes Yes Yes
GetUserName (Page 1344) Yes Yes Yes
GetDataRecordFromPLC (Page 1345) Yes Yes Yes
GetDataRecordName (Page 1346) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1288 System Manual, 08/2011,
Mobile Panel 177
DP
Mobile Panel 177
PN
Mobile Panel 277
Mobile Panel 277 IWLAN
Mobile Panel 277 F IWLAN
GetDataRecordTagsFromPLC (Page 1348) Yes Yes Yes
GetGroupNumber (Page 1349) Yes Yes Yes
GetBrightness (Page 1349) No No No
GetPassword (Page 1350) Yes Yes Yes
Auto-Hotspot Yes Yes Yes
LinearScaling (Page 1351) Yes Yes Yes
ClearLog (Page 1352) No No Yes
ClearDataRecord (Page 1352) Yes Yes Yes
ClearDataRecordMemory (Page 1354) Yes Yes Yes
ClearAlarmBuffer (Page 1355) Yes Yes Yes
ClearAlarmBufferProTool (Page 1356) Yes Yes Yes
AlarmViewUpdate (Page 1357) Yes Yes Yes
AlarmViewEditAlarm (Page 1357) Yes Yes Yes
AlarmViewAcknowledgeAlarm (Page 1358) Yes Yes Yes
AlarmViewShowOperatorNotes (Page 1359) Yes Yes Yes
OpenAllLogs (Page 1359) No No Yes
OpenScreenKeyboard (Page 1360) No No Yes
OpenCommandPrompt (Page 1361) No No Yes
OpenInternetExplorer (Page 1362) No Yes Yes
OpenControlPanel (Page 1362) No No Yes
OpenTaskManager (Page 1363) No No Yes
AcknowledgeAlarm (Page 1364) Yes Yes Yes
RecipeViewNewDataRecord (Page 1364) Yes Yes Yes
RecipeViewGetDataRecordFromPLC
(Page 1365)
Yes Yes Yes
RecipeViewClearDataRecord (Page 1366) Yes Yes Yes
RecipeViewMenu (Page 1366) Yes Yes Yes
RecipeViewOpen (Page 1367) Yes Yes Yes
RecipeViewSetDataRecordToPLC
(Page 1367)
Yes Yes Yes
RecipeViewSaveDataRecord (Page 1368) Yes Yes Yes
RecipeViewSaveAsDataRecord
(Page 1368)
Yes Yes Yes
RecipeViewSynchronizeDataRecordWithTa
gs (Page 1369)
Yes Yes Yes
RecipeViewRenameDataRecord
(Page 1370)
Yes Yes Yes
RecipeViewShowOperatorNotes
(Page 1370)
Yes Yes Yes
RecipeViewBack (Page 1371) Yes Yes Yes
ResetBit (Page 1372) Yes Yes Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1289
Mobile Panel 177
DP
Mobile Panel 177
PN
Mobile Panel 277
Mobile Panel 277 IWLAN
Mobile Panel 277 F IWLAN
ResetBitInTag (Page 1372) Yes Yes Yes
PressButton (Page 1373) Yes Yes Yes
ReleaseButton (Page 1374) Yes Yes Yes
ShiftAndMask (Page 1375) Yes Yes Yes
CloseAllLogs (Page 1376) No No Yes
SetDataRecordToPLC (Page 1377) Yes Yes Yes
SetDataRecordTagsToPLC (Page 1378) Yes Yes Yes
PageDown (Page 1379) Yes Yes Yes
PageUp (Page 1380) Yes Yes Yes
SendEMail (Page 1380) No Yes Yes
SetAcousticSignal (Page 1381) No No No
SetDisplayMode (Page 1382) No No No
SetDeviceMode (Page 1383) Yes Yes Yes
SetBit (Page 1384) Yes Yes Yes
SetBitInTag (Page 1384) Yes Yes Yes
SetBitWhileKeyPressed (Page 1385) Yes Yes Yes
SetColorBackgroundLighting (Page 1387) No No No
SetBrightness (Page 1387) No No No
SetScreenKeyboardMode (Page 1388) No No Yes
SetAlarmReportMode (Page 1389) No No Yes
SetRecipeTags (Page 1390) Yes Yes Yes
SetDaylightSavingTime (Page 1391) Yes Yes Yes
SetLanguage (Page 1392) Yes Yes Yes
SetTag (Page 1393) Yes Yes Yes
SetConnectionMode (Page 1394) Yes Yes Yes
SetWebAccess (Page 1395) No Yes Yes
BackupRAMFileSystem (Page 1396) No No Yes
SimulateSystemKey (Page 1396) Yes Yes Yes
SimulateTag (Page 1397) Yes Yes Yes
SmartClientViewRefresh (Page 1398) No Yes Yes
SmartClientViewWriteProtectionOff
(Page 1399)
No Yes Yes
SmartClientViewWriteProtectionOn
(Page 1399)
No Yes Yes
SmartClientViewDisconnect (Page 1400) No Yes Yes
SmartClientViewConnect (Page 1401) No Yes Yes
SmartClientViewLeave (Page 1401) No Yes Yes
SaveDataRecord (Page 1402) Yes Yes Yes
StartLogging (Page 1403) No No Yes
StartNextLog (Page 1404) No No Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1290 System Manual, 08/2011,
Mobile Panel 177
DP
Mobile Panel 177
PN
Mobile Panel 277
Mobile Panel 277 IWLAN
Mobile Panel 277 F IWLAN
StartProgram (Page 1404) No No Yes
StatusForceGetValues (Page 1406) Yes Yes Yes
StatusForceSetValues (Page 1407) Yes Yes Yes
ControlSmartServer (Page 1407) No Yes Yes
ControlWebServer (Page 1408) No Yes Yes
StopLogging (Page 1409) No No Yes
StopRuntime (Page 1410) Yes Yes Yes
LookupText (Page 1411) Yes Yes Yes
ResetTagToHandWheel (Page 1412) Yes Yes Yes
SetTagToHandWheel (Page 1412) Yes Yes Yes
TraceUserChange (Page 1413) Yes Yes Yes
DecreaseFocusedValue (Page 1413) Yes Yes Yes
DecreaseTag (Page 1414) Yes Yes Yes
1)
ChangeConnection (Page 1415) Yes Yes Yes
WinACMPUpdateStartupCharacteristics
(Page 1417)
No No No
WinACMPUpdateModeSelectorSwitchSettin
g (Page 1418)
No No No
WinACMPUpdateBUSF1LED (Page 1419) No No No
WinACMPUpdateBUSF2LED (Page 1420) No No No
WinACMPUpdateAverageExecutionTime
(Page 1421)
No No No
WinACMPUpdateAverageCycleTime
(Page 1422)
No No No
WinACMPUpdateEXTFLED (Page 1423) No No No
WinACMPUpdateHMIExecutionTime
(Page 1424)
No No No
WinACMPUpdateINTFLED (Page 1425) No No No
WinACMPUpdateLastCycleTime
(Page 1426)
No No No
WinACMPUpdateMaximumCycleTime
(Page 1427)
No No No
WinACMPUpdateMinimumCycleTime
(Page 1428)
No No No
WinACMPUpdatePowerLED (Page 1429) No No No
WinACMPUpdateIdleTime (Page 1430) No No No
WinACMPUpdateRUNLED (Page 1431) No No No
WinACMPUpdateSTOPLED (Page 1432) No No No
WinACMPLogging (Page 1433) No No No
WinACMPGetStartCharacteristics
(Page 1434)
No No No
WinACMPGetVersion (Page 1434) No No No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1291
Mobile Panel 177
DP
Mobile Panel 177
PN
Mobile Panel 277
Mobile Panel 277 IWLAN
Mobile Panel 277 F IWLAN
WinACMPClearCycleTimeBuffer
(Page 1435)
No No No
WinACMPSetStartAtBoot (Page 1435) No No No
WinACMPSetModeSelectorSwitch
(Page 1436)
No No No
WinACMPSetHMIExecutionTime
(Page 1437)
No No No
WinACMPSetResetCharacteristics
(Page 1437)
No No No
WinACMPSetIdleTime (Page 1438) No No No
WinACMPSetStartMode (Page 1438) No No No
WinACMPStartHistogram (Page 1439) No No No
WinACMPControl (Page 1440) No No No
WinACMPStopHistogram (Page 1440) No No No
WinACMPRestore (Page 1441) No No No
ShowLogonDialog (Page 1441) Yes Yes Yes
ShowOperatorNotes (Page 1442) Yes Yes Yes
ShowAlarmWindow (Page 1443) Yes Yes Yes
ShowSoftwareVersion (Page 1444) No No Yes
ShowSystemDiagnosticsWindow
(Page 1445)
No No No
ShowSystemAlarm (Page 1445) Yes Yes Yes
1)
only for Mobile Panel 277
2)
Only for Mobile Panel 277, Mobile Panel 277 IWLAN
System functions with WinCC Runtime
Availability of system functions
The following table shows the availability of the system functions for WinCC RT Advanced.
Technical data subject to change.
Overview
WinCC RT Advanced
User-defined functions Yes
Logoff (Page 1297) Yes
ActivateScreen (Page 1297) Yes
ActivateScreenByNumber (Page 1298) Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1292 System Manual, 08/2011,
WinCC RT Advanced
ActivateCleanScreen (Page 1299) Yes
ActivateSystemDiagnosticsView (Page 1300) No
ActivatePreviousScreen (Page 1301) Yes
UpdateTag (Page 1302) Yes
AdjustContrast (Page 1302) No
Logon (Page 1303) Yes
ArchiveLogFile (Page 1304) Yes
LogTag (Page 1305) Yes
EditAlarm (Page 1306) Yes
ScreenObjectCursorDown (Page 1307) Yes
ScreenObjectCursorUp (Page 1307) Yes
ScreenObjectPageDown (Page 1308) Yes
ScreenObjectPageUp (Page 1309) Yes
Encode (Page 1309) Yes
EncodeEx (Page 1310) Yes
DirectKey (Page 1311) No
DirectKeyScreenNumber (Page 1314) No
PrintScreen (Page 1315) Yes
PrintReport (Page 1315) Yes
NotifyUserAction (Page 1316) Yes
IncreaseFocusedValue (Page 1317) Yes
IncreaseTag (Page 1318) Yes
ExportDataRecords (Page 1319) Yes
ExportDataRecordsWithChecksum (Page 1321) No
ExportImportUserAdministration (Page 1324) Yes
GoToHome (Page 1324) Yes
GoToEnd (Page 1325) Yes
SafelyRemoveHardware (Page 1326) No
HTMLBrowserStop (Page 1326) Yes
HTMLBrowserRefresh (Page 1327) Yes
HTMLBrowserForward (Page 1327) Yes
HTMLBrowserBack (Page 1328) Yes
ImportDataRecords (Page 1328) Yes
ImportDataRecordsWithChecksum (Page 1330) No
InvertBit (Page 1332) Yes
InvertBitInTag (Page 1333) Yes
InvertLinearScaling (Page 1334) Yes
CalibrateTouchScreen (Page 1335) No
CopyLog (Page 1336) Yes
TrendViewScrollForward (Page 1337) Yes
TrendViewScrollBack (Page 1337) Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1293
WinCC RT Advanced
TrendViewExtend (Page 1338) Yes
TrendViewCompress (Page 1339) Yes
TrendViewRulerLeft (Page 1339) Yes
TrendViewRulerRight (Page 1340) Yes
TrendViewSetRulerMode (Page 1341) Yes
TrendViewStartStop (Page 1342) Yes
TrendViewBackToBeginning (Page 1342) Yes
LoadDataRecord (Page 1343) Yes
GetUserName (Page 1344) Yes
GetDataRecordFromPLC (Page 1345) Yes
GetDataRecordName (Page 1346) Yes
GetDataRecordTagsFromPLC (Page 1348) Yes
GetGroupNumber (Page 1349) Yes
GetBrightness (Page 1349) No
GetPassword (Page 1350) Yes
Auto-Hotspot Yes
LinearScaling (Page 1351) Yes
ClearLog (Page 1352) Yes
ClearDataRecord (Page 1352) Yes
ClearDataRecordMemory (Page 1354) No
ClearAlarmBuffer (Page 1355) Yes
ClearAlarmBufferProTool (Page 1356) Yes
AlarmViewUpdate (Page 1357) Yes
AlarmViewEditAlarm (Page 1357) Yes
AlarmViewAcknowledgeAlarm (Page 1358) Yes
AlarmViewShowOperatorNotes (Page 1359) Yes
OpenAllLogs (Page 1359) Yes
OpenScreenKeyboard (Page 1360) Yes
OpenCommandPrompt (Page 1361) No
OpenInternetExplorer (Page 1362) No
OpenControlPanel (Page 1362) No
OpenTaskManager (Page 1363) Yes
AcknowledgeAlarm (Page 1364) Yes
RecipeViewNewDataRecord (Page 1364) Yes
RecipeViewGetDataRecordFromPLC (Page 1365) Yes
RecipeViewClearDataRecord (Page 1366) Yes
RecipeViewMenu (Page 1366) Yes
RecipeViewOpen (Page 1367) Yes
RecipeViewSetDataRecordToPLC (Page 1367) Yes
RecipeViewSaveDataRecord (Page 1368) Yes
RecipeViewSaveAsDataRecord (Page 1368) Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1294 System Manual, 08/2011,
WinCC RT Advanced
RecipeViewSynchronizeDataRecordWithTags (Page 1369) Yes
RecipeViewRenameDataRecord (Page 1370) Yes
RecipeViewShowOperatorNotes (Page 1370) Yes
RecipeViewBack (Page 1371) Yes
ResetBit (Page 1372) Yes
ResetBitInTag (Page 1372) Yes
PressButton (Page 1373) Yes
ReleaseButton (Page 1374) Yes
ShiftAndMask (Page 1375) Yes
CloseAllLogs (Page 1376) Yes
SetDataRecordToPLC (Page 1377) Yes
SetDataRecordTagsToPLC (Page 1378) Yes
PageDown (Page 1379) Yes
PageUp (Page 1380) Yes
SendEMail (Page 1380) Yes
SetAcousticSignal (Page 1381) No
SetDisplayMode (Page 1382) Yes
SetDeviceMode (Page 1383) Yes
SetBit (Page 1384) Yes
SetBitInTag (Page 1384) Yes
SetBitWhileKeyPressed (Page 1385) Yes
SetColorBackgroundLighting (Page 1387) No
SetBrightness (Page 1387) No
SetScreenKeyboardMode (Page 1388) Yes
SetAlarmReportMode (Page 1389) Yes
SetRecipeTags (Page 1390) Yes
SetDaylightSavingTime (Page 1391) Yes
SetLanguage (Page 1392) Yes
SetTag (Page 1393) Yes
SetConnectionMode (Page 1394) Yes
SetWebAccess (Page 1395) Yes
BackupRAMFileSystem (Page 1396) No
SimulateSystemKey (Page 1396) Yes
SimulateTag (Page 1397) Yes
SmartClientViewRefresh (Page 1398) Yes
SmartClientViewWriteProtectionOff (Page 1399) Yes
SmartClientViewWriteProtectionOn (Page 1399) Yes
SmartClientViewDisconnect (Page 1400) Yes
SmartClientViewConnect (Page 1401) Yes
SmartClientViewLeave (Page 1401) Yes
SaveDataRecord (Page 1402) Yes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1295
WinCC RT Advanced
StartLogging (Page 1403) Yes
StartNextLog (Page 1404) Yes
StartProgram (Page 1404) Yes
StatusForceGetValues (Page 1406) Yes
StatusForceSetValues (Page 1407) Yes
ControlSmartServer (Page 1407) Yes
ControlWebServer (Page 1408) Yes
StopLogging (Page 1409) Yes
StopRuntime (Page 1410) Yes
LookupText (Page 1411) Yes
ResetTagToHandWheel (Page 1412) No
SetTagToHandWheel (Page 1412) No
TraceUserChange (Page 1413) Yes
DecreaseFocusedValue (Page 1413) Yes
DecreaseTag (Page 1414) Yes
ChangeConnection (Page 1415) Yes
WinACMPUpdateStartupCharacteristics (Page 1417) No
WinACMPUpdateModeSelectorSwitchSetting (Page 1418) No
WinACMPUpdateBUSF1LED (Page 1419) No
WinACMPUpdateBUSF2LED (Page 1420) No
WinACMPUpdateAverageExecutionTime (Page 1421) No
WinACMPUpdateAverageCycleTime (Page 1422) No
WinACMPUpdateEXTFLED (Page 1423) No
WinACMPUpdateHMIExecutionTime (Page 1424) No
WinACMPUpdateINTFLED (Page 1425) No
WinACMPUpdateLastCycleTime (Page 1426) No
WinACMPUpdateMaximumCycleTime (Page 1427) No
WinACMPUpdateMinimumCycleTime (Page 1428) No
WinACMPUpdatePowerLED (Page 1429) No
WinACMPUpdateIdleTime (Page 1430) No
WinACMPUpdateRUNLED (Page 1431) No
WinACMPUpdateSTOPLED (Page 1432) No
WinACMPLogging (Page 1433) No
WinACMPGetStartCharacteristics (Page 1434) No
WinACMPGetVersion (Page 1434) No
WinACMPClearCycleTimeBuffer (Page 1435) No
WinACMPSetStartAtBoot (Page 1435) No
WinACMPSetModeSelectorSwitch (Page 1436) No
WinACMPSetHMIExecutionTime (Page 1437) No
WinACMPSetResetCharacteristics (Page 1437) No
WinACMPSetIdleTime (Page 1438) No
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1296 System Manual, 08/2011,
WinCC RT Advanced
WinACMPSetStartMode (Page 1438) No
WinACMPStartHistogram (Page 1439) No
WinACMPControl (Page 1440) No
WinACMPStopHistogram (Page 1440) No
WinACMPRestore (Page 1441) No
ShowLogonDialog (Page 1441) Yes
ShowOperatorNotes (Page 1442) Yes
ShowAlarmWindow (Page 1443) Yes
ShowSoftwareVersion (Page 1444) Yes
ShowSystemDiagnosticsWindow (Page 1445) No
ShowSystemAlarm (Page 1445) Yes
System functions
Logoff
Description
Logs off the current user on the HMI device.
Use in the function list
Logoff
Use in user-defined functions
Logoff
Can be used if the configured device supports user-defined functions. For additional
information, refer to "Availability for specific devices of system functions".
Parameters
--
ActivateScreen
Description
Performs a screen change to the given screen.
Use the "ActivateScreenByNumber" system function to change from the root screen to the
permanent window or vice versa.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1297
Use in the function list
ActivateScreen (Screen name, Object number)
Use in user-defined functions
ActivateScreen (Screen_name, Object_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Screen name
Name of the screen to which you change.
Object number
The operator control element which receives the focus in the given screen after the screen
change. The number of the operator control element is to be determined using the tabulator
sequence during configuration.
When "0" is specified:
If the focus is in the permanent window when the system function is called up, the
permanent window maintains the focus.
If the focus is in the root screen when the system function is called up, the first operator
control element in the given screen receives the focus.
Note
If the "Reach margin" event is assigned to the "ActivateScreen" system function, only the
value "0" is valid for the "Object number" parameter. The active object is not defined by
the object number, but rather by the X position it had prior to the screen change.
See also
Availability for specific devices of system functions (Page 1262)
ActivateScreenByNumber (Page 1298)
ActivateScreenByNumber
Description
Performs a screen change to a screen depending on a tag value.
The screen is identified by its screen number.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1298 System Manual, 08/2011,
Use in the function list
ActivateScreenByNumber (Screen number, Object number)
Use in user-defined functions
ActivateScreenByNumber (Screen_number, Object_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Screen number
Tag which contains the screen number of the destination screen.
When a change from the root screen to the permanent window is desired, "0" or "-1" is specified:
0 = Change from root screen to permanent window
-1 = Change from permanent window to root screen
Object number
The number of the screen object which receives the focus in the given screen after the screen
change. The number of the operator control element is to be determined using the tabulator
sequence during configuration.
When "0" is specified:
If the focus is in the permanent window when the system function is called up, the
permanent window maintains the focus.
If the focus is in the root screen when the system function is called up, the first operator
control element in the given screen receives the focus.
See also
Availability for specific devices of system functions (Page 1262)
ActivateScreen (Page 1297)
ActivateCleanScreen
Description
Activates the clean screen on the HMI device. The display of the HMI device is disabled for
the given time period.
When the display of the HMI device is deactivated, it can be cleaned without triggering touch
functions by mistake.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1299
Use in the function list
ActivateCleanScreen (Time period)
Use in user-defined functions
--
Parameters
Time period
Time period for which the display is disabled. The time remaining is displayed as a progress
bar.
Value range in seconds from 10 through 300.
Note
The system function ActivateCleanScreen cannot be simulated.
See also
Availability for specific devices of system functions (Page 1262)
Logoff (Page 1297)
ActivateSystemDiagnosticsView
Description
Activates the system diagnostics view. The system diagnostics view shows the detail view of
the respective device.
Use in the function list
ActivateSystemDiagnosticsView (Screen name, Object name)
Use in user-defined functions
ActivateSystemDiagnosticsView (Screen_name, Object_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1300 System Manual, 08/2011,
Parameters
Screen name
Name of the screen contained in the system diagnostics view.
Object name
Object name of the system diagnostics view.
ActivatePreviousScreen
Description
Performs a screen change to the screen which was activated before the current screen. The
screen change is not performed if no screen was activated beforehand.
The last 10 screens that were called up are saved. A system alarm is output when you change
to a screen which is no longer saved.
Note
If you want to use the system function, the screen to which you change has to be used in the
navigation structure.
Use in the function list
ActivatePreviousScreen
Use in user-defined functions
ActivatePreviousScreen
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
Logoff (Page 1297)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1301
UpdateTag
Description
Reads the current value of the tag with the specified Update ID from the PLC.
Use in the function list
UpdateTag (Update ID)
Use in user-defined functions
-
Parameters
Update ID
Update ID assigned to the tag that will be updated.
See also
Availability for specific devices of system functions (Page 1262)
AdjustContrast
Description
Changes the contrast of the display one level on the HMI device.
Use in the function list
AdjustContrast (Adjust)
Use in user-defined functions
-
Parameters
Adjust
Specifies how the contrast is changed:
0 (hmiDecrease) = Decrease: Decreases the contrast one level.
1 (hmiIncrease) = Increase: Increases the contrast one level.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1302 System Manual, 08/2011,
Application example
Objective
One button each for increasing and decreasing the screen contrast is desired.
Notes on configuring
Configure two buttons and configure the "AdjustContrast" system function on the "Press" event.
The parameters "Increase" and "Decrease" are allocated.
Procedure on HMI device
When one of the two buttons is pressed in runtime, the contrast is increased or decreased one
level.
See also
Availability for specific devices of system functions (Page 1262)
Logoff (Page 1297)
Logon
Description
Logs on the current user on the HMI device.
Use in the function list
Logon (Password, User name)
Use in user-defined functions
Logon (Password, User_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Password
The tag from which the password for the user logging on is read.
If the user is logged on, the password in the tag is deleted.
User name
The tag from which the user name for the user logging on is read.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1303
See also
Availability for specific devices of system functions (Page 1262)
ArchiveLogFile
Description
This system function moves or copies a log to another storage location for long-term logging.
With Audit Trails, always use the "Move" (hmiMove)" mode, otherwise you will be violating the
FDA guideline by duplicating the data stored.
Prior to "ArchiveLogFile" always run the system function "CloseAllLogs".
After this system function, run the "OpenAllLogs" system function.
In "Copy log" mode, the logs are not reopened until the log has been successfully copied, or
unless a timeout occurs during the copy process. In "Move log" mode, the logs to be moved
are renamed and the new logs are opened immediately. To move the renamed logs, a job is
submitted which attempts to move them every 300 seconds if the server cannot be reached.
The job is also retained after Runtime is restarted until it is executed.
Use in the function list
ArchiveLogFile (Log type, Log, Directory name, Mode)
Use in user-defined functions
ArchiveLogFile (Log_type, Log, Directory_name, Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (miAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail log available for GMP compliant projects. Additional
information is available under "Activating GMP-compliant configuration".
Log
Name of the log being archived.
Directory name
Path for saving the log.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1304 System Manual, 08/2011,
Mode
0 (hmiCopy) = Copy log
1 (hmiMove) = Move log
Application example
You want to move a log file from a local storage medium to the server in order to generate a
backup copy of this file at cyclic intervals.
Notes on configuring
Set up a task in the scheduler which is executed at a specific time on a daily basis. Configure
the following function list for the task:
Procedure on HMI device
All log files will be closed.
The log file you specified is moved to the server.
All closed log files will be opened again.
See also
Availability for specific devices of system functions (Page 1262)
LogTag
Description
Saves the value of the given tags in the given data log.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1305
This system function is used to archive a process value at a certain point in time.
Use in the function list
LogTag (Tag)
Use in user-defined functions
-
Parameters
Tag
The tag whose value is logged. The tag is stored in the log which is configured for the specified
tag.
See also
Availability for specific devices of system functions (Page 1262)
EditAlarm
Description
Triggers the "Edit" event for all selected alarms.
If the alarms to be edited have not yet been acknowledged, the acknowledgment takes place
automatically when this system function is called up.
This system function can only be used for function keys.
Use in the function list
EditAlarm
Use in user-defined functions
EditAlarm
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1306 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
ScreenObjectCursorDown
Description
Results in a line-by-line, downward cursor movement in the specified screen object.
The system function can be used for the following screen objects:
User view
Alarm view
Recipe view
Use in the function list
ScreenObjectCursorDown (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the screen object in which the key function is triggered.
See also
Availability for specific devices of system functions (Page 1262)
ScreenObjectCursorUp
Description
Results in a line-by-line, upward cursor movement in the specified screen object.
The system function can be used for the following screen objects:
User view
Alarm view
Recipe view
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1307
Use in the function list
ScreenObjectCursorUp (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the screen object in which the key function is triggered.
See also
Availability for specific devices of system functions (Page 1262)
ScreenObjectPageDown
Description
Results in a page-by-page, downward cursor movement in the specified screen object.
The system function can be used for the following screen objects:
User view
Alarm view
Recipe view
Use in the function list
ScreenObjectPageDown (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the screen object in which the key function is triggered.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1308 System Manual, 08/2011,
ScreenObjectPageUp
Description
Results in a page-by-page, upward cursor movement in the specified screen object.
The system function can be used for the following screen objects:
User view
Alarm view
Recipe view
Use in the function list
ScreenObjectPageUp (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the screen object in which the key function is triggered.
See also
Availability for specific devices of system functions (Page 1262)
Encode
Description
Adapts the "String" data type of a tag for transfer to the automation system (AS). The tag of
WinCC data type "String" is converted into the AS data type "Array of byte". The result is written
to a tag.
Use in the function list
Encode (Byte array, String, Coding)
Use in user-defined functions
Encode (Byte_array, String, Encoding)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1309
Parameters
Byte array
The tag that contains the converted value.
Note
The Byte array must be twice the size of the string length + 2. The Byte array must contain
242 array elements if the string has a length of 120 characters.
Characters are either truncated or not converted if the size is insufficient.
String
The tag of data type "String" that is converted.
Encode
0 (hmiEncodeUTF16LE) - String is encoded in UTF16LE (Unicode 16 Little Endian).
See also
Availability for specific devices of system functions (Page 1262)
EncodeEx
Description
Adapts the "String" data type of a tag for transfer to the automation system (AS). The tag of
WinCC data type "String" is converted into the AS data type "Array of byte". The result is written
to a tag.
By contrast to the Encode system function, you can define the Line break parameter. Using
the Line break parameter you can delete line breaks or replace these with predefined
characters.
Use in the function list
EncodeEx (Byte array, String , Encode , Line break)
Use in user-defined functions
EncodeEx (Byte_array, String, Encoding, Line_break)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1310 System Manual, 08/2011,
Parameters
Byte array
The tag that contains the converted value.
Note
The byte array must be twice the size of the string length +2. If the string has a length of 120
characters, the byte array must contain 242 array elements.
Characters are either truncated or not converted if the size is insufficient.
String
The tag of data type "String" that is converted.
Encode
0 (hmiEncodeUTF16LE) - String is encoded in UTF16LE (Unicode 16 Little Endian).
Line break
All line breaks are either deleted or replaced with predefined characters. Do not replace line
breaks if set as the default value.
0 (replace with "\r\n' (0x000D, 0x000A)) - the line break is replaced with "\r\n".
1 (replace with "\n' (0x000A)) - the line break is replaced with "\n".
2 (do not replace) - the line break is not replaced.
3 (remove line breaks) - the line breaks are removed.
See also
Availability for specific devices of system functions (Page 1262)
DirectKey
Description
Allows rapid operation of keys on an HMI device without having communication caused delays
occur.
Use this system function, for example. to set bits in the I/O area of a SIMATIC S7 directly from
the HMI device.
Note
If you have integrated WinCC in SIMATIC STEP 7 and have configured a DP area in SIMATIC
STEP 7: When the button on which the system function was configured is activated, a bit is
set in the IO area of the CPU. Releasing the button resets the bit.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1311
Notes on configuring the system function
When a button is configured with the "DirectKey" system function, a fixed area of the touch
display is reserved for DirectKey operation.
Screen objects that are above the button with the "DirectKey" system function in this area in
runtime will hide the button visually. However, the screen objects do not interfere with the
triggering of the "DirectKey" system function.
NOTICE
If an external application, such as Pocket Internet Explorer or Control Panel is started, it will
run in the foreground and Runtime is placed in the background. The bit for the
"DirectKeyScreenNumber" function is no longer set and the keys or buttons which are
assigned the "DirectKey" function no longer to trigger the associated bit in the PLC.
WARNING
Triggering the "DirectKey" system function by mistake will endanger personnel or result in
damage to the machine.
In order to avoid this danger, the following must be observed:
When the process screen is configured, the button with the "DirectKey" system function
must not be covered by a screen object.
The dynamic positioning or display (release) of a screen object in relation to process values
must not cover the button with the "DirectKey" system function in runtime.
Note
Please observe this guideline during configuration. Check also existing configurations and
adjust them immediately.
In the following cases, the covering of a button with the "DirectKey" system function does not
lead to the problems described above:
Operation of the alarm window
Operation of the Recipe view
Cancellation of the screen saver
Use of the screen keyboard
Running the "ActivateCleanScreen" system function
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1312 System Manual, 08/2011,
Actions of DP direct-keys in offline operation
When the "ChangeConnection" system function is performed with the "Offline" parameter on
the HMI device, the connection to the specified PLC is disconnected.
NOTICE
Please note the following on the SIMATIC STEP 7 side as well as the WinCC side:
The DP DirectKeys are still active in this case. If you activate a button with the "DirectKey"
system function in "Offline" operating mode or activate the DirectKey on a keyboard device,
the corresponding bit is set in the PLC.
Use in the function list
DirectKey (Bit)
Use in user-defined functions
-
Parameters
Bit
Specifies the bit which is set. Depending on the HMI device, the bit numbers 0 to 31 or 0 to
39 are possible.
Application example
Objective
You want to set bits in the IO area of a SIMATIC S7 directly from the HMI device using a button.
Requirement
WinCC integrated in SIMATIC STEP 7 is installed.
During operation, the HMI device is coupled to a SIMATIC S7 through PROFIBUS-DP.
WinCC integrated was installed when you compiled your project.
The bit area for DirectKeys is determined in SIMATIC STEP 7. For configuration see the
"Communication" user's manual.
Notes on configuring
Configure the button to be used as the DirectKey. Assign the "DirectKey" system function to
the button. As a parameter, enter the number of the bit which is set when the key is pressed.
Procedure on HMI device
When the DirectKey is touched, the bit is set, and reset when the key is released or the screen
is exited.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1313
See also
Availability for specific devices of system functions (Page 1262)
DirectKeyScreenNumber
Description
Sets the bit within the given bit area of a DirectKey and transfers it to the S7 controller to which
the HMI device is connected. This ensures unambiguous allocation of a control bit to screen
number at all times.
Without the use of the system function, the S7 controller must distinguish the respective
functionality by means of the screen number. This delays the updating of the screen number
after a screen change.
NOTICE
If an external application, such as Pocket Internet Explorer or Control Panel is started, it will
run in the foreground and Runtime is placed in the background. Nevertheless, the bit for the
"DirectKeyScreenNumber" function is set and the keys or buttons with the configured
"DirectKey" function continue to trigger the associated bit in the PLC.
Use in the function list
DirectKeyScreenNumber (Bit)
Use in user-defined functions
-
Parameters
Bit
Specifies the bit which is set. Depending on the HMI device, the bit numbers 0 to 31 or 0 to
39 are possible.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1314 System Manual, 08/2011,
PrintScreen
Description
Prints the screen currently being displayed on the HMI device from the printer which is
connected to the HMI device.
Opened windows are also printed.
Note
The printer settings are taken over from the current settings in the Windows operation system.
Use in the function list
PrintScreen
Use in user-defined functions
PrintScreen
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
PrintReport
Description
Prints the given report from the printer which is connected to the HMI device. The report is
printed in the language which is set on the HMI device.
Note
If runtime is closed whilst log data are being printed using the system function, the report will
cease to be supplied with data as soon as runtime stops.
Use in the function list
PrintReport (Report)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1315
Use in user-defined functions
PrintReport (Report)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Protocol
Name of the report to be printed.
Note
If you have set up via the "Function list" dialog box a new report for the "PrintReport" function,
when compiling, the following warning appears: "The report "Report_1" has no printed pages."
In order to remedy the warning, open the "Report_1" via the project view and recompile the
project.
See also
Availability for specific devices of system functions (Page 1262)
NotifyUserAction
Description
This system function is used to log user actions that are not automatically logged in the audit
trail. You can also use this system function to require the user to enter an acknowledgment or
an electronic signature and a comment for the operator action. Requirement for the use of the
system function is that the GMP-compliant configuration is activated under "Runtime settings".
If you use the "NotifyUserAction" system function in a function, the debugger may open if you
cancel your input by clicking "Cancel". To compensate for this reaction, you can use the "On
Error Resume Next" statement in a function. With this setting, the script executes the next
statement when a runtime error is detected. If you use the "On Error Resume Next" statement,
output of system events is also suppressed.
Use in the function list
NotifyUserAction (Confirmation type, Mandatory commenting, Category, Object name,
Description)
Use in user-defined functions
NotifyUserAction (Confirmation_type, Mandatory_commenting, Category, Object_name,
Description)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1316 System Manual, 08/2011,
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Confirmation type
Establishes how the action must be confirmed
0 = (None): No confirmation required, an entry is created in the audit trail
1 = (Acknowledgement): Acknowledgement, the user must acknowledge the action; an entry
is created in the audit trail
2 = (Digital Signature): Electronic signature, a dialog window opens in which the user must
enter his electronic signature - an entry is created in the audit trail
Mandatory commenting
Establishes if the user has to enter a comment. The comment is logged in the audit trail.
0 = (True): True; a dialog window opens in which the user must enter a comment
1 = (False): False; no mandatory commenting
Category
Category or class name of the modified object
Object name
Name of the modified object
Description
Text which describes the archiving user action.
See also
Availability for specific devices of system functions (Page 1262)
IncreaseFocusedValue
Description
Adds the given value to the value of the tag which is connected to the input field (drop-down
list, graphic selection list, slider bar) which has the current focus.
This system function can only be used for function keys.
Use in the function list
IncreaseFocusedValue (Value)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1317
Use in user-defined functions
-
Parameters
Value
The value which is added to the tag value.
See also
Availability for specific devices of system functions (Page 1262)
IncreaseTag
Description
Adds the given value to the value of the tags.
X = X + a
Note
The system function uses the same tag as input and output values. When this system function
is used to convert a value, help tags must be used. The auxiliary tags can be assigned to the
tag value with the "SetTag" system function.
If you configure the system function on the events of an alarm and the tag is not being used
in the current screen, it is not ensured that the actual value of the tags is being used in the
PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode.
Use in the function list
IncreaseTag (Tag, Value)
Use in user-defined functions
IncreaseTag (Tag, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the given value is added.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1318 System Manual, 08/2011,
Value
The value which is added.
See also
Availability for specific devices of system functions (Page 1262)
ExportDataRecords
Description
Exports one or all data records of a recipe to a CSV file.
One file is created per recipe.
Use in the function list
ExportDataRecords (Recipe number/name, Data record number/name, File name, Overwrite,
Output status message, Processing status)
Use in user-defined functions
ExportDataRecords (Recipe_number/name,Data_record number/name, File_name,
Overwrite, Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which the data records are exported. Specify "0" if recipe
data records are to be exported from all available recipes.
File name
Name of the CSV file to which the recipe data records are exported. Enter the file location and
the file extension (*.csv), for example, "C:\TEMP\Orange.csv".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1319
Note
Storage of the CSV file
If a storage card is used as storage location, specify the storage location as follows:
"\StorageCard\<File name>".
If you only enter one file name and no path, the file will be saved in a system directory,
for example, "C:\Documents and Settings\[User]".
When only one path for the export is specified, the file name is automatically created from
the respective recipe name. It is a requirement that the folder "D:\Temp\", for example,
has been created. If the folder "D:\Temp" has not been created, the folder name will be
used as the prefix of the file name, Temp_Recipe names.csv.
Data record number/name
Number or name of the recipe data record to be exported. Specify "0" if all recipe data records
are to be exported.
Overwrite
Determines whether an existing CSV file with the same name is overwritten:
0 (hmiOverwriteForbidden) = No: CSV file will not be overwritten. The export process will not
be carried out.
1 (hmiOverwriteAlways) = Yes: CSV file is overwritten without a prompt for confirmation.
2 (hmiOverwriteWithPrompting) = With confirmation: CSV file is not overwritten until confirmed.
Output status message
Determines whether a status message is output after the export:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for
example, to delay execution of other system functions until this system function has been
successfully completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Export format of the recipe data records
If ".csv" is chosen as a file extension for the export file, then only valid characters from the
ANSI character set will be supported. This also applies to separators in decimal numbers and
list elements. The separators used are defined in the country/regional settings of the operating
system of the exporting computer.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1320 System Manual, 08/2011,
You may also set "Unicode text" (".txt") format for the export file. This file format supports the
WinCC and WinCC Runtime character set. Again, the separators used are specified in the
country/regional settings of the operating system of the exporting computer. This file format
always uses tab separators in list elements.
The corresponding file import function also supports the ".csv" and ".txt" (Unicode) file
formats.
Application example
You want to export all data records using a key.
Notes on configuring
Configure the "ExportDataRecords" system function on the "Press" event for the desired key.
Transfer the following parameters:
Recipe number/name = 1
Data record number/name = 0
File name = c:\temp\orange.csv
Overwrite = 1
Output status message = 1
Tags can also be specified in place of the constants. Depending on the configuration, the
operator can enter the desired values in the I/O field or read from the PLC. In this way, the
operator can determine which recipe data records are exported.
Procedure on HMI device
As soon as the key is activated, the system function is triggered. The constants or tags are
evaluated. All data records of Recipe 1 are exported to the orange.csv file. If the file already
exists, it will be overwritten.
After exporting the data records, a system message is output.
See also
Availability for specific devices of system functions (Page 1262)
ExportDataRecordsWithChecksum
Description
Exports one or all data records of a recipe to a CSV file and generates an incremental
checksum for each line in the file.
One file is created per recipe.
Use in the function list
ExportDataRecordsWithChecksum (Recipe number/name, Data record number/name, File
name, Overwrite, Output status message, Processing status)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1321
Use in user-defined functions
ExportDataRecordsWithChecksum (Recipe_number/name, Data_record number/name,
File_name, Overwrite, Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Recipe number/name
Number or name of the recipe from which the data records are exported. Specify "0" if recipe
data records are to be exported from all available recipes.
File name
Name of the CSV file to which the recipe data records are exported. Enter the file location and
the file extension (*.CSV) e.g. "C:\TEMP\Orange.CSV".
Note
Storage of the csv file
If a storage card is used as storage location, specify the storage location as follows:
"\StorageCard\<File name>".
If you define only a file name without specifying a path, the file is saved to the directory
from which Runtime was started. If write access to this directory is not enabled in the
Windows 7 operating system, the file is saved to the "VirtualStore" folder of the user
directory.
When only one path for the export is specified, the file name is automatically created from
the respective recipe name. This requires, for example, that the directory "D:\Temp\" has
been created. If the directory "D:\Temp" does not exist, the directory name is used as the
prefix for the file name, Temp_Recipe names.csv.
Data record number/name
Number or name of the recipe data record to be exported. Specify "0" if all recipe data records
are to be exported.
Overwrite
Determines whether an existing CSV file with the same name is overwritten:
0 (hmiOverwriteForbidden) = No: CSV file will not be overwritten. The export process will not
be carried out.
1 (hmiOverwriteAlways) = Yes: CSV file is overwritten without a prompt for confirmation.
2 (hmiOverwriteWithConfirmation) = With confirmation: CSV file is not overwritten until
confirmed.
Output status message
Determines whether a status message is output after the export:
0 (hmiOff) = Off: Status message is not output.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1322 System Manual, 08/2011,
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Export format of the recipe data records
If ".csv" is chosen as a file extension for the export file, then only valid characters from the
ANSI character set will be supported. This also applies to separators in decimal numbers and
list elements. The separators used are defined in the country/regional settings of the operating
system of the exporting computer.
You may also set "Unicode text" (".txt") format for the export file. This file format supports the
WinCC and WinCC Runtime character set. Again, the separators used are specified in the
country/regional settings of the operating system of the exporting computer. This file format
always uses tab separators in list elements.
The corresponding file import function also supports the ".csv" and ".txt" (Unicode) file formats.
Application example
Using a key, you want to export all data records and assign a checksum.
Notes on configuring
Configure the "ExportDataRecordsWithChecksum" system function on the "Press" event for
the desired key. Transfer the following parameters:
Recipe number/name = 1
Data record number/name = 0
File name = c:\temp\orange.csv
Overwrite = 1
Output status message = 1
Tags can also be specified in place of the constants. Depending on the configuration, the
operator can enter the desired values in the I/O field or read from the PLC. In this way, the
operator can determine which recipe data records are exported.
Procedure on HMI device
As soon as the key is activated, the system function is triggered. The constants or tags are
evaluated. All data records of Recipe 1 are exported to the orange.csv file and assigned
checksums. If the file already exists, it will be overwritten.
After exporting the data records, a system message is output.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1323
ExportImportUserAdministration
Description
Exports all users of the user administration of the currently active project to the given file or
imports the users from the given file into the currently active project.
Users, their passwords and rights are saved in the user administration.
All users are overwritten when importing. The imported users are valid immediately.
Use in the function list
ExportImportUserAdministration (File name, Direction)
Use in user-defined functions
ExportImportUserAdministration (File_name, Direction)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
File name
Name of the file which contains the passwords or to which the passwords are written. Enter
the file location and the file extension (*.txt), for example, "C:\TEMP\Passwords.txt".
Note
If a storage card is used as file location, specify the file location as follows: "\StorageCard
\<File name>".
Direction
Specifies whether passwords are exported or imported:
0 (hmiExport) = Export: Passwords are exported.
1 (hmiImport) = Import: Passwords are imported.
See also
Availability for specific devices of system functions (Page 1262)
GoToHome
Description
Executes the key function <Home> on the HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1324 System Manual, 08/2011,
This system function is used when the HMI device does not have this functionality by default.
The system function can only be used for the following function keys.
Use in the function list
GoToHome
Use in user-defined functions
GoToHome
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
GoToEnd
Description
Executes the key function <End> on the HMI device.
This system function is used when the HMI device does not have this functionality by default.
The system function can only be used for the following function keys.
Use in the function list
GoToEnd
Use in user-defined functions
GoToEnd
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1325
See also
Availability for specific devices of system functions (Page 1262)
SafelyRemoveHardware
Description
Checks whether there is read or write access to the external storage medium. If there is no
access, the external storage medium can be removed without data loss.
Use in the function list
SafelyRemoveHardware(Path, Result)
Use in user-defined functions
SafelyRemoveHardware(Path, Result)
Can be used if the configured device supports user-defined functions. Additional information
is available under Auto-Hotspot.
Parameters
Path
Path of storage medium , e.g. \Storage Card USB\
Result
The tag in which the result is entered.
TRUE : The storage medium can be removed safely. A corresponding system message will
be issued.
FALSE : The storage medium can be removed safely. A corresponding system message will
be issued.
See also
Availability for specific devices of system functions (Page 1262)
HTMLBrowserStop
Description
Performs the function "Stop" the HTML browser.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1326 System Manual, 08/2011,
Use in the function list
HTMLBrowserStop (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Object name of the HTML browser in which the command is performed.
See also
Availability for specific devices of system functions (Page 1262)
HTMLBrowserRefresh
Description
Performs the function "Refresh" of the HTML browser.
Use in the function list
HTMLBrowserRefresh (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Object name of the HTML browser in which the command is performed.
See also
Availability for specific devices of system functions (Page 1262)
HTMLBrowserForward
Description
Performs the function "Forward" of the HTML browser.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1327
Use in the function list
HTMLBrowserForward (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Object name of the HTML browser in which the command is performed.
See also
Availability for specific devices of system functions (Page 1262)
HTMLBrowserBack
Description
Performs the "Back" function of the HTML browser.
Use in the function list
HTMLBrowserBack (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Object name of the HTML browser in which the command is performed.
See also
Availability for specific devices of system functions (Page 1262)
ImportDataRecords
Description
Imports one or all data records of a recipe from a CSV file.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1328 System Manual, 08/2011,
When a path is specified, all records of the given directory are imported.
Use in the function list
ImportDataRecords (File name, Data record number/name, Overwrite, Output status
message, Processing status)
Use in user-defined functions
ImportDataRecords (File_name, Data_record number/name, Overwrite,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
File name
Name of the CSV file from which the recipe data records are imported. Enter the file location
and the file extension (*.csv), for example "C:\TEMP\Orange.csv".
Note
If a storage card is used as file location, specify the file location as follows: "\StorageCard
\<File name>".
Data record number/name
Number or name of the recipe data record to be imported. Specify "0" if all recipe data records
are to be imported.
Overwrite
Determines whether existing recipe data records are to be overwritten:
0 (hmiOverwriteForbidden) = No: Recipe data records are not overwritten. The import process
will not be carried out.
1 (hmiOverwriteAlways) = Yes: Recipe data records are overwritten without prompting.
2 (hmiOverwriteWithPrompting) = With confirmation: Recipe data records are not overwritten
until confirmed.
Output status message
Determines whether a status message is output after the import:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1329
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Configurable objects
Object Event
Tag Value change
High limit violated
Low limit violated
Function key (global) Release
Press
Function key (local) Release
Press
Screen Loaded
Cleared
Screen object Press
Release
Click
Change (or toggle for switch)
Switch on
Switch off
Enable
Disable
Scheduler Time expired
See also
Availability for specific devices of system functions (Page 1262)
ImportDataRecordsWithChecksum
Description
Imports one or all data records of a recipe from a CSV file with a checksum and verifies the
checksum.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1330 System Manual, 08/2011,
Use in the function list
ImportDataRecordsWithChecksum (File name, Data record number/name, Overwrite, Output
status message, Processing status, verify checksum)
Use in user-defined functions
ImportDataRecordsWithChecksum (File_name, Data_record number/name, Overwrite,
Output_status_message, Processing_status, Verify_Checksum)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
File name
Name of the CSV file from which the recipe data records are imported.
If you specify a directory instead of an individual CSV file, all files in the specified directory will
be imported.
Note
If a storage card is used as file location, specify the file location as follows: "\StorageCard
\<File name>".
Data record number/name
Number or name of the recipe data record to be imported. Specify "0" if all recipe data records
are to be imported.
Overwrite
Determines whether existing recipe data records are to be overwritten:
0 (hmiOverwriteForbidden) = No: Recipe data records are not overwritten. The import process
will not be carried out.
1 (hmiOverwriteAlways) = Yes: Recipe data records are overwritten without prompting.
2 (hmiOverwriteWithConfirmation) = With confirmation: Recipe data records are not
overwritten until confirmed.
Output status message
Determines whether a status message is output after the import:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions, until this system function has been successfully
completed.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1331
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Verify checksum
Determines if the checksum should be verified during import:
0 (hmiFalse) = No: Checksum is not verified.
1 (hmiTrue) = Yes: Checksum is verified.
See also
System functions on Basic Panels (Page 1262)
System functions on Panels (Page 1269)
System functions on Multi Panels (Page 1275)
System functions on Comfort Panels (Page 1281)
System functions on Mobile Panels (Page 1287)
System functions with WinCC Runtime (Page 1292)
Availability for specific devices of system functions (Page 1262)
InvertBit
Description
Inverts the value of the given tag of the "Bool" type:
If the tag has the value of 1 (TRUE), it will be set to 0 (FALSE).
If the tag has the value of 0 (FALSE), it will be set to 1 (TRUE).
Use in the function list
InvertBit (Tag)
Use in user-defined functions
InvertBit (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag whose bit is set.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1332 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
InvertBitInTag
Description
Inverts a bit in the given tag:
If the bit in the tag has the value of 1 (TRUE), it will be set to 0 (FALSE).
If the bit in the tag has the value of 0 (FALSE), it will be set to 1 (TRUE).
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC.
Note
If the PLC supports BOOL tags, do not use this system function. Use the "InvertBit" system
function instead.
Use in the function list
InvertBitInTag (Tag, Bit)
Use in user-defined functions
InvertBitInTag (Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag in which the given bit is set.
Bit
The number of the bit that is set.
When this system function is used in a user-defined function, the bits in a tag are counted from
right to left. The counting begins with 0.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1333
InvertLinearScaling
Description
Assigns a value to the tag X, which is calculated from the value of the given tag Y using the
linear function X = (Y - b) / a.
The tags X and Y must not be identical. This system function is the inverse of the
"LinearScaling" system function.
Note
The tags X and Y must not be identical. If a tag is to be converted into itself, a auxiliary tag
must be used.
The "SetTag" system function can be used to assign the value of the tags to be converted to
the auxiliary tags.
Use in the function list
InvertLinearScaling (X, Y, b, a)
Use in user-defined functions
InverseLinearScaling (X, Y, b, a)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
X
The tag which is assigned the value calculated from the linear equation.
Y
The tag whose value is used for the calculation.
b
The value which is subtracted.
a
The value through which is divided.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1334 System Manual, 08/2011,
CalibrateTouchScreen
Description
Calls a program for calibrating the touch screen.
During the calibration process, there is a prompt to touch five positions on the screen display.
Touch the screen display within 30 seconds, to confirm the calibration process. If the calibration
is not completed within this time span, the calibration settings are discarded. The user prompt
is in English.
Use this system function the first time you start the HMI device.
Use in the function list
CalibrateTouchScreen
Use in user-defined functions
CalibrateTouchScreen
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Note
The CalibrateTouchScreen system function cannot be simulated.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1335
CopyLog
Description
Copies the contents of a log to another log. Tag values can only be copied to other data logs
and alarms only to other alarm logs, however.
Note
If you copy a log using the "CopyLog" system function, it is possible that external applications
will be unable to read certain country-specific special characters in the logged message text
of the log copy. This does not apply to WinCC Runtime. WinCC Runtime can read the copied
log files without errors.
Use in the function list
CopyLog (Log type, Destination log, Source log, Mode, Delete source log)
Use in user-defined functions
CopyLog (Log_type, Destination log, Source_log, Mode, Delete_source_log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
Destination log
Name of the log into which the entries are copied (Destination log).
Source log
Name of the log from which the entries are copied (Source log).
Mode
Determines what is done with copied entries in the destination log:
0 (hmiOverwrite) = Overwrite: Existing entries are overwritten.
2 (hmiAppend) = Append: The entries are inserted at the end of the destination log. When the
configured size of the log has been reached, the destination log is treated like a circular log.
Delete source log
Determines whether the source log is deleted after copying.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1336 System Manual, 08/2011,
0 (hmiNo) = No: Is not deleted.
1 (hmiYes) = Yes: Is deleted.
See also
Availability for specific devices of system functions (Page 1262)
Storage locations of logs (Page 919)
TrendViewScrollForward
Description
Scrolls forward one display width in the Trend view.
Use in the function list
TrendViewScrollForward (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which is scrolled forward.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
See also
Availability for specific devices of system functions (Page 1262)
TrendViewScrollBack
Description
Scrolls back one display width to the left in the trend view.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1337
Use in the function list
TrendViewScrollBack (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which is scrolled back.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
See also
Availability for specific devices of system functions (Page 1262)
TrendViewExtend
Description
Reduces the time period which is displayed in the trend view.
Use in the function list
TrendViewExtend (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which the displayed time period is reduced.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1338 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
TrendViewCompress
Description
Increases the time period which is displayed in the trend view.
Use in the function list
TrendViewCompress (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which the displayed time period is increased.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
TrendViewRulerLeft
Description
Moves the read-line backwards (to the left) in the trend view.
Note
In order to be able to move the read-line, the read-line must have been switched on. This is
done using the "TrendViewSetRulerMode" system function.
Use in the function list
TrendViewRulerRight (Screen object)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1339
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which the read-line is moved backwards.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
See also
Availability for specific devices of system functions (Page 1262)
TrendViewSetRulerMode (Page 1341)
TrendViewRulerRight
Description
Moves the read-line forwards (to the right) in the trend view.
Note
In order to be able to move the read-line, the read-line must have been switched on. This is
done using the "TrendViewSetRulerMode" system function.
Use in the function list
TrendViewRulerLeft (Screen object)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1340 System Manual, 08/2011,
Parameters
Screen object
Name of the trend view in which the read-line is moved forward.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
See also
Availability for specific devices of system functions (Page 1262)
TrendViewSetRulerMode (Page 1341)
TrendViewSetRulerMode
Description
Hides or shows the read-line in the trend view. The read-line displays the Y value belonging
to the X value.
Note
To ensure that the ruler is displayed, you have to activate the setting "Show ruler" in the trend
view properties.
Use in the function list
TrendViewSetRulerMode (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which the read-line is hidden or shown.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1341
See also
Availability for specific devices of system functions (Page 1262)
TrendViewRulerRight (Page 1340)
TrendViewRulerLeft (Page 1339)
TrendViewStartStop
Description
Stops the trend recording or continues the trend recording in the trend view.
Use in the function list
TrendViewStartStop (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which the recording of the trend is started or stopped.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
See also
Availability for specific devices of system functions (Page 1262)
TrendViewBackToBeginning
Description
Scrolls back to the beginning of the display range in the trend view.
Use in the function list
TrendViewBackToBeginning (Screen object)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1342 System Manual, 08/2011,
Use in user-defined functions
-
Parameters
Screen object
Name of the trend view in which you scroll to the beginning of the display range.
Note
The HMI device TP 177A does not support this system function for the "screen" object.
See also
System functions with WinCC Runtime (Page 1292)
Availability for specific devices of system functions (Page 1262)
LoadDataRecord
Description
Loads the given recipe data record from the memory medium of the HMI device in the recipe
tags. This system function is used, for example, to display a recipe data record in the recipe
screen.
Activate the "Synchronize recipe view and recipe tags" option in the synchronization settings
of the recipe. If this option is deactivated, the system function has no effect.
Use in the function list
LoadDataRecord (Recipe number/name, Data record number/name, Processing status)
Use in user-defined functions
LoadDataRecord (Recipe_number/name, Data_record_number/name, Confirmation,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which a recipe data record is loaded.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1343
Data record number/name
Number or name of the recipe data record to be loaded.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
GetUserName
Description
Writes the user name of the user currently logged on to the HMI device in the given tag.
If the given tag has a control connection, the user name is also available in the PLC connection.
This system function makes it possible, for example, to implement a user-dependent release
of certain functionalities.
Use in the function list
GetUserName (Tag)
Use in user-defined functions
GetUserName (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the user name is written.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1344 System Manual, 08/2011,
GetDataRecordFromPLC
Description
Transfers the given recipe data record from the PLC to the memory medium of the HMI
device.
Use in the function list
GetDataRecordFromPLC (Recipe number/name, Data record number/name, Overwrite,
Output status message, Processing status)
Use in user-defined functions
GetDataRecordFromPLC (Recipe_number/name, Data_record_number/name, Overwrite,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which recipe data records are transferred.
Data record number/name
Number or name of the recipe data record which is transferred from the PLC to the data medium
of the HMI device.
Overwrite
Determines whether an existing recipe data record with the same name is overwritten:
0 (hmiOverwriteForbidden) = No: Recipe data record is not overwritten. The transfer process
will not be carried out.
1 (hmiOverwriteAlways) = Yes: Recipe data record is overwritten without prompting.
2 (hmiOverwriteWithPrompting) = With confirmation: Recipe data record is not overwritten until
confirmed.
Output status message
Determines whether a status message is output after the transfer:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1345
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Application example
You want to transfer a data record from the PLC to the data medium of the HMI device using
a key.
Notes on configuring
Configure the "GetDataRecordFromPLC" system function on the "Press" event for the desired
key. Transfer the following parameters:
Recipe number/name = 1
Data record number/name = 1
Overwrite = 1
Output status message = 1
Tags can also be specified in place of the constants. Depending on the configuration, the
operator can enter the desired values in the I/O field or read from the PLC. In this way, the
operator can determine which recipe data record is transferred from the PLC.
Procedure on HMI device
As soon as the key is activated, the system function is triggered. The constants or tags are
evaluated and the first data record of Recipe 1 is transferred from the PLC to the data medium
of the HMI device. If the recipe data record already exists, it will be overwritten.
A system message is output after the transfer.
See also
Availability for specific devices of system functions (Page 1262)
GetDataRecordName
Description
Writes the name of the given recipe and recipe data record to the given tags.
Note
If the recipe or the recipe data record do not exist, wildcards ("###") are written to the tags.
Use in the function list
GetDataRecordName (Recipe number, Data record number, Recipe name, Data record name,
Processing status)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1346 System Manual, 08/2011,
Use in user-defined functions
GetDataRecordName (Recipe_number, Data_record_number, Recipe_name,
Data_record_name, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number
Number of the recipe whose name is written to the given tag.
Data record number
Number of the recipe data record whose name is written to the given tag.
Recipe name
The tag to which the recipe name is written. The tag must be of the STRING type.
Data record name
The tag to which the name of the recipe data record is written. The tag must be of the STRING
type.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Application example
You want to output the names of the displayed recipes and the name of the displayed recipe
data record on the HMI device.
Configure the following tags:
"RecNumber" of type INTEGER
"RecDataNumber" of type INTEGER
"RecName" of type STRING
"RecDataName" of type STRING
Configure a recipe view with the tags "RecNumber" for the recipe number and
"RecDataNumber" for the data record number.
Configure the "GetDataRecordName" system function on the "Press" event for a button and
pass the following parameters:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1347
Recipe number: RecNumber
Data record number: RecDataNumber
Recipe name: RecName
Data record name: RecDataName
Configure two output fields and connect these to the "RecName" and "RecDataName" tags.
Select a recipe and a data record number from the recipe view. As soon as the button is
activated, the system function is triggered and the name of the recipe and the recipe data
record are displayed in both output fields.
See also
Availability for specific devices of system functions (Page 1262)
GetDataRecordTagsFromPLC
Description
Transfers the values of the recipe data record, which is loaded in the PLC, to the recipe tag.
This system function is used, for example, during teach-in mode on a machine.
Use in the function list
GetDataRecordTagsFromPLC (Recipe number/name, Processing status)
Use in user-defined functions
GetDataRecordTagsFromPLC (Recipe_number/name, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe data record whose values are written from the PLC to the tags.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1348 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
GetGroupNumber
Description
Reads the number of the group to which the user logged on to the HMI device belongs, and
writes it to the given tag.
Use in the function list
GetGroupNumber (Tag)
Use in user-defined functions
GetGroupNumber (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the number of the group is written.
See also
Availability for specific devices of system functions (Page 1262)
GetBrightness
Description
Reads the value of the brightness.
Use in the function list
GetBrightness (Brightness)
Use in user-defined functions
GetBrightness (Brightness)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1349
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Brightness
The tag to which the value is written.
See also
Availability for specific devices of system functions (Page 1262)
GetPassword
Description
Writes the password of the user currently logged on to the HMI device in the given tag.
Note
Make sure that the value of the given tag is not displayed in another place in the project.
Note
The passwords of SIMATIC Logon users cannot be read.
Use in the function list
GetPassword (Tag)
Use in user-defined functions
GetPassword (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the password is written.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1350 System Manual, 08/2011,
See also
System functions with WinCC Runtime (Page 1292)
Availability for specific devices of system functions (Page 1262)
LinearScaling
Description
Assigns a value to the tag Y, which is calculated from the value of the given tag X using the
linear function Y= (a *X) + b.
The inverse of this function is the "InvertLinearScaling" system function.
Note
The tags X and Y must not be identical. If a tag is to be converted into itself, a auxiliary tag
must be used.
The "SetTag" system function can be used to assign the value of the tags to be converted to
the auxiliary tags.
Use in the function list
LinearScaling (Y, a, X, b)
Use in user-defined functions
LinearScaling (Y, a, X, b)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Y
The tag which is assigned the value calculated from the linear equation.
a
The value with which is multiplied.
X
The tag whose value is used for the calculation.
b
The value which is added.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1351
See also
Availability for specific devices of system functions (Page 1262)
ClearLog
Description
Deletes all data records in the given log.
Use in the function list
ClearLog (Log type, Log)
Use in user-defined functions
ClearLog (Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail log Available for GMP-compliant projects Additional
information is available under "Activating GMP-compliant configuration".
Log
Name of the log from which all entries are deleted.
See also
Availability for specific devices of system functions (Page 1262)
ClearDataRecord
Description
Deletes a recipe data record.
Several data records can be deleted from one or more recipes.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1352 System Manual, 08/2011,
Use in the function list
ClearDataRecord (Recipe number/name, Data record number/name, Confirmation, Output
status message, Processing status)
Use in user-defined functions
ClearDataRecord
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which recipe data records are deleted. "0" is specified if
you want to delete recipe data records from all available recipes.
Data record number/name
Number or name of the recipe data record to be deleted. "0" is specified if you want to delete
all recipe data records.
Confirmation
Determines whether the operator should confirm the deletion:
0 (hmiOff) = Off: Deletion is begun without confirmation.
1 (hmiOn) = On: The starting of the deletion process must be confirmed.
Output status message
Determines whether a status report is output after the deletion:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1353
ClearDataRecordMemory
Description
Deletes all recipes and recipe data records from the specified storage medium.
Use in the function list
ClearDataRecordMemory (Storage location, Confirmation, Output status message,
Processing status)
Use in user-defined functions
ClearDataRecordMemory(Storage_location, Confirmation, Output_status_message,
Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Storage location
Determines the storage location:
0 (hmiFlashMemory) = Flash memory: Internal flash memory of the HMI device
1 (hmiStorageCard) = Storage card
2 (hmiStorageCard2) = Storage card 2
3 (hmiStorageCard3) = Storage card MultiMediaCard
4 (hmiStorageCard4) = Storage card USB
Confirmation
Determines whether the operator should confirm the deletion:
0 (hmiOff) = Off: Deletion is begun without confirmation.
1 (hmiOn) = On: The starting of the deletion process must be confirmed.
Output status message
Determines whether a status report is output after the deletion:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1354 System Manual, 08/2011,
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
ClearAlarmBuffer
Description
Deletes alarms from the alarm buffer on the HMI device.
Note
Alarms which have not yet been acknowledged are also deleted.
Use in the function list
ClearAlarmBuffer (Alarm class number)
Use in user-defined functions
ClearAlarmBuffer (Alarm_class_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Alarm class number
Determines which alarms are to be deleted from the alarm buffer:
0 (hmiAll) = All alarms/events
1 (hmiAlarms) = Alarms of alarm class "Errors"
2 (hmiEvents) = Alarms of alarm class "Warnings"
3 (hmiSystem) = Alarms of alarm class "System"
4 (hmiS7Diagnosis) = Alarms of alarm class "Diagnosis Events"
Note
Availability for specific devices
Alarms of alarm class "Diagnosis Events" are not available on Basic Panels.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1355
See also
Availability for specific devices of system functions (Page 1262)
ClearAlarmBufferProTool
Description
The system function exists to ensure compatibility.
It has the same functionality as the "ClearAlarmBuffer" system function, but uses the old
ProTool numbering.
Use in the function list
ClearAlarmBufferProTool (Alarm class number)
Use in user-defined functions
ClearAlarmBufferProtoolLegacy (Alarm_class_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Alarm class number
Alarm class number whose messages are to be deleted:
-1 (hmiAllProtoolLegacy) = All alarms/events
0 (hmiAlarmsProtoolLegacy) = Alarms of alarm class "Errors"
1 (hmiEventsProtoolLegacy) = Alarms of alarm class "Warnings"
2 (hmiSystemProtoolLegacy) = Alarms of alarm class "System"
3 (hmiS7DiagnosisProtoolLegacy) = Alarms of alarm class "Diagnosis Events"
Note
Availability for specific devices
Alarms of alarm class "Diagnosis Events" are not available on Basic Panels.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1356 System Manual, 08/2011,
AlarmViewUpdate
Description
Updates the enhanced alarm view.
Use in the function list
AlarmViewUpdate (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the alarm view which is updated.
See also
Availability for specific devices of system functions (Page 1262)
AlarmViewEditAlarm
Description
Triggers the event "Edit" for all alarms selected in the given alarm view.
This system function is used when the integrated button of the ActiveX control should not be
used.
A system function can in turn be configured on the "Edit" event. For example, it is possible to
change to the process screen in which the alarm appeared.
Note
If the alarms to be edited have not yet been acknowledged, the acknowledgment takes place
automatically when this system function is called up.
Use in the function list
AlarmViewEditAlarm (Screen object)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1357
Use in user-defined functions
-
Parameters
Screen object
Name of the alarm view in which the event is triggered.
Note
The HMI devices listed below do not support this system function for the "screen" object: OP
73, OP 77A, TP 177A.
See also
Availability for specific devices of system functions (Page 1262)
AlarmViewAcknowledgeAlarm
Description
Acknowledges the alarms selected in the given alarm view.
This system function is used when the integrated button of the ActiveX control should not be
used.
Use in the function list
AlarmViewAcknowledgeAlarm (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the alarm view in which the event is triggered.
Note
The HMI devices listed below do not support this system function for the "screen" object: OP
73, OP 77A, TP 177A.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1358 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
AlarmViewShowOperatorNotes
Description
Displays the configured tooltip of the alarm selected in the given alarm view.
Use in the function list
AlarmViewShowOperatorNotes (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the alarm view in which the event is triggered.
Note
The HMI devices listed below do not support this system function for the "screen" object: OP
73, OP 77A, TP 177A.
See also
System functions with WinCC Runtime (Page 1292)
Availability for specific devices of system functions (Page 1262)
OpenAllLogs
Description
Reestablishes the connection between WinCC and the logs. Logging can be continued.
Note
Run the "StartLogging" system function in order to restart logging.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1359
Use in the function list
OpenAllLogs
Use in user-defined functions
OpenAllLogs
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Application example
You are in runtime and want to change the data medium on which the process values are
logged.
Notes on configuring
Configure the "StopLogging" and "CloseAllLogs" system functions on the "Close Archive"
button.
Configure the "OpenAllLogs" and "StartLogging" system functions on the "Open Archive"
button.
As parameter transfer the respective name of the log that is to be stopped and started.
Procedure on HMI device
When the button "Close Archive" is pressed, the specified log is stopped and all open logs are
closed. The data medium can be changed. You open all logs with the "Open Archive" button.
Logging will be continued in the specified log.
See also
Availability for specific devices of system functions (Page 1262)
OpenScreenKeyboard
Description
Hides or shows the screen keyboard.
The screen keyboard remains open until the screen keyboard is explicitly closed. In this way,
the screen keyboard can also be used in other applications.
Use in the function list
OpenScreenKeyboard (Display mode)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1360 System Manual, 08/2011,
Use in user-defined functions
OpenScreenKeyboard (Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Display mode
Specifies whether the window is opened minimized or maximized with the screen keyboard:
0 (hmiScreenKeyboardMinimized) = Minimized
1 (hmiScreenKeyboardMaximized) = Maximized
See also
Availability for specific devices of system functions (Page 1262)
OpenCommandPrompt
Description
Opens a Windows system prompt.
This function is used, e.g., to copy files or to call up another application.
Use in the function list
OpenCommandPrompt
Use in user-defined functions
OpenCommandPrompt
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1361
OpenInternetExplorer
Description
Opens the Internet Explorer on the HMI device.
If the Internet Explorer is already open, it will be closed and reopened when you call the system
function.
Note
The Internet Explorer saves data temporarily in the DRAM file system of the HMI device, e.g.
the last web sites that were be called up.
This data can be saved using the "BackupRAMFileSystem" system function so that it is still
available when the HMI device is restarted.
Use in the function list
OpenInternetExplorer (Start page)
Use in user-defined functions
OpenInternetExplorer(Start_page)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Start page
The page which is loaded when Internet Explorer is started, e.g. "www.siemens.com".
See also
Availability for specific devices of system functions (Page 1262)
OpenControlPanel
Description
Opens a window which displays the Windows CE control panel. You cannot use this system
function on a PC.
This system function enables you to set the following on the Windows CE-based HMI device:
Select printer
Select transfer properties
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1362 System Manual, 08/2011,
Configure screen saver
Configure flash memory
Note
No backup or restore during Runtime
Backup and restore functions may only be executed if Runtime has been terminated.
Otherwise, this could result in undesired effects, such as display errors.
Use in the function list
OpenControlPanel
Use in user-defined functions
OpenControlPanel
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
OpenTaskManager
Description
Shows the task manager.
The task manager allows changing to other open applications on the HMI device.
Note
The appearance of the task manager depends on the operating system installed.
Use in the function list
OpenTaskManager
Use in user-defined functions
OpenTaskManager
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1363
Can be used if the configured device supports user-defined scripts. Additional information is
available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
AcknowledgeAlarm
Description
Acknowledges all selected alarms.
This system function is used when the HMI device does not have an ACK key or when the
integrated key of the alarm view should not be used.
This system function can only be used for function keys.
Use in the function list
AcknowledgeAlarm
Use in user-defined functions
AcknowledgeAlarm
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewNewDataRecord
Description
Creates a new data record in the given recipe view.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1364 System Manual, 08/2011,
Use in the function list
RecipeViewNewDataRecord (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the new recipe data record is created.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewGetDataRecordFromPLC
Description
Transfers the data record that is currently loaded in the PLC to the HMI device and displays it
in the recipe view.
Use in the function list
RecipeViewGetDataRecordFromPLC (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the recipe data record from the PLC is displayed.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1365
RecipeViewClearDataRecord
Description
Deletes the data record which is currently displayed in the recipe view.
Use in the function list
RecipeViewClearDataRecord (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the displayed recipe data record is deleted.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewMenu
Description
Opens the menu of the specified simple recipe view.
Only use this system function at a simple recipe view.
Use in the function list
RecipeViewMenu (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the menu is to be opened.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1366 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewOpen
Description
Displays the data record values in the given recipe view or changes to the next selection field.
The system function has no effect if the selection field for the recipe data record values is
displayed on the HMI device.
Operation sequence of the selection lists in runtime:
Recipe name
Data record name
RecipeDataRecordValues
This system function is used when a simple recipe view has been configured. In the simple
recipe view, only one selection list is displayed at a time on the HMI device. Use the
"RecipeViewBack" system function to display the previous selection list.
Use in the function list
RecipeViewOpen (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the command is triggered.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewSetDataRecordToPLC
Description
Transfers the recipe data record which is currently displayed in the recipe view to the PLC.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1367
Use in the function list
RecipeViewSetDataRecordToPLC (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view from which the recipe data record is transferred to the connected PLC.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewSaveDataRecord
Description
Saves the recipe data record which is currently displayed in the recipe view.
Use in the function list
RecipeViewSaveDataRecord (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the recipe data record is saved.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewSaveAsDataRecord
Description
Saves the data record currently being displayed in the recipe view under a new name.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1368 System Manual, 08/2011,
Use in the function list
RecipeViewSaveAsDataRecord (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Saves the data record currently being displayed in the recipe view under a new name and/or
new number.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewSynchronizeDataRecordWithTags
Description
Synchronizes the values of the data record which is currently displayed in the recipe view with
their recipe tags. Only use this system function at an advanced recipe view.
During synchronization, all values of the data record are written to their recipe tags.
Use in the function list
RecipeViewSynchronizeDataRecordWithTags (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the values are synchronized with their tags.
Note
The OP 77A and TP 177A HMI devices do not support this function for the "screen" object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1369
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewRenameDataRecord
Description
Renames the selected data record in the given recipe view.
Only use this system function at a simple recipe view.
Use in the function list
RecipeViewRenameDataRecord (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the recipe data record is renamed.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewShowOperatorNotes
Description
Displays the configured tooltip of the specified recipe view.
Use in the function list
RecipeViewShowOperatorNotes (Screen object)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1370 System Manual, 08/2011,
Parameters
Screen object
Name of the recipe view whose configured tooltip is displayed.
See also
Availability for specific devices of system functions (Page 1262)
RecipeViewBack
Description
Returns to the previous selection list in the given recipe view.
The system function has no effect if the selection field for the recipe is displayed on the HMI
device. Operation sequence of the selection lists in runtime:
Recipe name
Data record name
RecipeDataRecordValues
This system function is used when a simple recipe view has been configured. In the simple
recipe view, only one selection list is displayed at a time on the HMI device. Use the
"RecipeViewOpen" system function to display the recipe data record values or the next
selection field.
Use in the function list
RecipeViewBack (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the recipe view in which the command is triggered.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1371
ResetBit
Description
Sets the value of a "Bool" type tag to 0 (FALSE).
Use in the function list
ResetBit (Tag)
Use in user-defined functions
ResetBit (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The BOOL type tag which is set to 0 (FALSE).
See also
Availability for specific devices of system functions (Page 1262)
ResetBitInTag
Description
Sets a bit in the specified tag to 0 (FALSE).
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC.
Note
If the PLC supports BOOL tags, do not use this system function. Use the "ResetBit" system
function instead.
Use in the function list
ResetBitInTag (Tag, Bit)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1372 System Manual, 08/2011,
Use in user-defined functions
ResetBitInTag (Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag in which a bit is set to 0 (FALSE).
Bit
The number of the bit that is set to 0 (FALSE).
When this system function is used in a user-defined function, the bits in the specified tag will
be counted from right to left independent of the PLC used. The counting begins with 0.
See also
Availability for specific devices of system functions (Page 1262)
PressButton
Description
The system function can only be configured on the function keys of an HMI device and triggers
the "Press key" event at the specified screen object.
Use this system function when you want to operate a button in a screen with a function key of
the HMI device, for example.
Note
The "PressButton" and "ReleaseButton" system functions must always be configured
together. If you configure the "PressButton" system function on the "Press key" event for a
function key, the "ReleaseButton" system function is configured on the "Release" event for
the same function key.
Use in the function list
PressButton (Screen object)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1373
Parameters
Screen object
Name of the screen object on which the event is triggered.
See also
Availability for specific devices of system functions (Page 1262)
ReleaseButton
Description
The system function can only be configured on the function keys of an HMI device and triggers
the "Release button" event at the specified screen object.
Use this system function when you want to operate a button in a screen with a function key of
the HMI device, for example.
Note
The "PressButton" and "ReleaseButton" system functions must always be configured
together. If you configure the "PressButton" system function on the "Press key" event for a
function key, then the "ReleaseButton" system function is configured on the "Release key"
event for the same function key.
Use in the function list
ReleaseButton (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the screen object on which the event is triggered.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1374 System Manual, 08/2011,
ShiftAndMask
Description
This system function converts the input bit pattern of the source tags into an output bit pattern
of the target tags. This involves bit shifting and masking.
Note
If the source and target tag have a different number of bits, using the system function in the
target tag can result in a violation of the value range.
Use in the function list
ShiftAndMask (Source tag, Target tag, Bits to shift, Bits to mask)
Use in user-defined functions
ShiftAndMask (Source_tag, Target_tag, Bits_to_shift, Bits_to_mask)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Source tag
The tag includes the input bit pattern. Integer-type tags, e.g. "Byte", "Char", "Int", "UInt", "Long"
and "ULong" are permitted.
Example: The actual value 72 is set at the 16-bit integer source tag: 0000000001001000.
Target tag
The output bit pattern is saved in the tag. Integer type tags, e.g. "Byte", "Char", "Int", "UInt",
"Long" and "ULong" are permitted.
Example: The shifted input bit pattern is multiplied by the bit mask, with bit-by-bit logical AND
operation: 0000000000001001. The resultant decimal value "8" is saved to the target tag.
Please note the following:
The source and target tags have the same number of bits.
The number of bits to shift is less than the number of bits in the source tag and target tag.
Bits to mask does not have more bits than the source tag and the target tag.
Bits to shift
Number of bits by which the input bit pattern is shifted right. A negative value shifts the input
bit pattern to the left.
Example: "Bits to shift" has the value "+3". The input bit pattern is shifted right by three bits
when the system function is called: 0000000000001001.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1375
Bits to the left are padded with "0". Three bits are truncated on the right. The new decimal
value is "9".
Note
The left bit is "1" in a source tag of the data type with negative signed integer. This sign bit
is padded with "0" when the bits are shifted right. The sign changes to "+".
Bits to mask
An integer serves as bit mask. The bit pattern is used to multiply the shifted input bit pattern.
Example: Integer "2478" with the bit pattern "0000100110101110".
You can enter the bit mask in three different ways:
Hexadecimal: First enter the prefix "0h" or "0H", followed by an optional space for better
readability. Then group the bit pattern in blocks of four (0000)(1001)(1010)(1110) and set
each block in hexadecimal code: (0)(9)(A)(E). Only the characters 0-9, A-F, a-f are allowed:
"0h 09AE".
Binary: First enter the prefix "0b" or "0B", followed by an optional space for better readability.
Then group the binary bit pattern into blocks of four 0000 1001 1010 1110 with spaces in
between as a check. Only the characters "0" or "1" are allowed: "0b 0000 1001 1010 1110".
Decimal: Enter the value "2478" directly, without a prefix.
See also
Availability for specific devices of system functions (Page 1262)
CloseAllLogs
Description
Disconnects the connection between WinCC and all logs.
Note
Before you close a log, the logging function must first be stopped in the log. Use the
"StopLogging" system function.
Use in the function list
CloseAllLogs
Use in user-defined functions
CloseAllLogs
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1376 System Manual, 08/2011,
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Application example
You are in runtime and want to change the data medium on which the process values are
logged.
Notes on configuring
Configure the "StopLogging" and "CloseAllLogs" system functions on the "Close Archive"
button.
Configure the "OpenAllLogs" and "StartLogging" system functions on the "Open Archive"
button.
As parameter transfer the respective name of the log that is to be stopped and started.
Procedure on HMI device
When the button "Close Archive" is pressed, the specified log is stopped and all open logs are
closed. The data medium can be changed. You open all logs with the "Open Archive" button.
The logging process will continue in the specified log.
See also
Availability for specific devices of system functions (Page 1262)
SetDataRecordToPLC
Description
Transfers the given recipe data record directly from the data medium of the HMI device to the
PLC with which the HMI device is connected.
Note
The values of the recipe data record don't need to be displayed on the HMI device.
Use in the function list
SetDataRecordToPLC (Recipe number/name, Data record number/name, Output status
message, Processing status)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1377
Use in user-defined functions
SetDataRecordToPLC (Recipe_number/name, Data_record_number/name,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which recipe data record is transferred to the PLC.
Data record number/name
Number or name of the recipe data record to be transferred to the PLC.
Output status message
Determines whether a status message is output after the transfer:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
SetDataRecordTagsToPLC
Description
Transfers the values of the recipe tags to the PLC. The recipe tags contain the values of the
data record which is displayed on the HMI device.
Use in the function list
SetDataRecordTagsToPLC (Recipe number/name, Processing status)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1378 System Manual, 08/2011,
Use in user-defined functions
SetDataRecordTagsToPLC (Recipe_ number/name, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which recipe data record is transferred to the PLC.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
PageDown
Description
Executes the key function <Pagedown> on the HMI device.
This system function can only be used for function keys.
Use in the function list
PageDown
Use in user-defined functions
PageDown
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1379
See also
Availability for specific devices of system functions (Page 1262)
PageUp
Description
Executes the key function <PageUp> on the HMI device.
This system function can only be used for function keys and tasks with a time trigger.
Use in the function list
PageUp
Use in user-defined functions
PageUp
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
-
See also
Availability for specific devices of system functions (Page 1262)
SendEMail
Description
Sends an e-mail from the HMI device to the given addressee.
This system function is used, for example, when, in the case of service, the alarm is to be
passed on directly to the service technician.
Note
To send alarms as e-mails, the HMI system must have an e-mail client at its disposal.
Use in the function list
SendEMail (Address, Subject, Text, Return address)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1380 System Manual, 08/2011,
Use in user-defined functions
SendEMail (Address, Subject, Text, Return_address)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Address
The e-mail address of the addressee.
Subject
The subject line of the e-mail.
Text
The text sent in the e-mail.
Return address
The e-mail address to which the addressee of this e-mail should send the reply.
See also
Availability for specific devices of system functions (Page 1262)
SetAcousticSignal
Description
Configures the acoustic feedback of touch screen operation on the HMI device.
Note
The configuration that was set at Switch off is reestablished when restarting the HMI device.
Use in the function list
SetAcousticSignal (Volume)
Use in user-defined functions
SetAcousticSignal (Volume)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1381
Parameters
Volume
Determines whether and how loud an acoustic signal is emitted:
-1 (hmiToggle) = Toggle: Toggles the emission of the acoustic signal as follows: Muted > Quiet
> Loud.
0 (hmiMuted) = Mute: no acoustic signal
1 (hmiQuiet) = Quiet: quiet acoustic signal
2 (hmiLoud) = Loud: loud acoustic signal
See also
Availability for specific devices of system functions (Page 1262)
SetDisplayMode
Description
Changes the settings of the screen in which the runtime software runs.
The runtime software runs in full-screen mode as default. The Windows task switch is disabled.
Use in the function list
SetDisplayMode (Display mode)
Use in user-defined functions
SetDisplayMode (Display mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Display mode
Determines the settings for the screen in which the runtime software runs.
1 (hmiScreenFull): Full-screen: Title bar of the screen is not visible
2 (hmiScreenMaximized): Maximized
3 (hmiScreenRestore): Restore: The last used screen setting is used. This display mode can
only be used when the window is displayed minimized or maximized.
4 (hmiScreenMinimized): Minimized
5 (hmiScreenAutoAdjust): Automatic: The size of the window is set so that all screen objects
in it will be visible.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1382 System Manual, 08/2011,
6 (hmiScreenOnTop): On top; either the window appears in the foreground or the program
icon associated with the window flashes on the taskbar depending on the Windows setting.
The setting can be changed in the Windows configuration and applies to all Windows
applications.
See also
Availability for specific devices of system functions (Page 1262)
SetDeviceMode
Description
Toggles the operating mode on the HMI device. The following types of operation are possible:
"Online", "Offline" and "Load".
Use in the function list
SetDeviceMode (Operating mode)
Use in user-defined functions
SetDeviceMode (Operating_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Operating mode
Determines the operating mode of the HMI device:
0 (hmiOnline) = Online: The connection to the PLC is established.
1 (hmiOffline) = Offline: The connection to the PLC is disconnected.
2 (hmiTransfer) = load: A project can be transferred from the configuration computer to the
HMI device.
Note
If you use a PC as an HMI device, the runtime software will be exited when you change
operating mode after "Load".
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1383
SetBit
Description
Sets the value of a "Bool" type tag to 1 (TRUE).
Use in the function list
SetBit (Tag)
Use in user-defined functions
SetBit(Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The BOOL type tag which is set to 1 (TRUE).
See also
Availability for specific devices of system functions (Page 1262)
SetBitInTag
Description
Sets a bit in the given tag to 1 (TRUE).
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC.
Note
If the PLC supports BOOL tags, do not use this system function. Use the "SetBit" system
function instead.
Use in the function list
SetBitInTag (Tag, Bit)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1384 System Manual, 08/2011,
Use in user-defined functions
SetBitInTag(Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag in which a bit is set to 1 (TRUE).
Bit
The number of the bit that is set to 1 (TRUE).
When this system function is used in a user-defined function, the bits in the specified tag will
be counted from right to left independent of the PLC used. The counting begins with 0.
Note
The guaranteed update of the tags used with actual process values is absolutely conditional
in terms of reliable functionality. You should therefore configure the tag in an I/O field or assign
the system function to a screen object, such as a button.
If you have configured a short event such as the activation of an alarm for the system function
you can only access the actual process values by setting the tag for continuous reading.
See also
Availability for specific devices of system functions (Page 1262)
SetBitWhileKeyPressed
Description
Sets the bit of the given tag to 1 (TRUE) as long as the user keeps the configured key pressed.
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC. You should
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1385
only access tags of the BOOL type with this system function to avoid problems with overlapping
access to the same tag.
Note
All functions on the event "Release" are performed immediately by means of a screen change
configured for a key, even if the key is kept pressed.
If the "SetBitWhileKeyPressed" system function is configured for a function key, the bit will
be reset immediately following a screen change. This action is necessary since the key
assignments change after the screen change.
If the PLC supports BOOL tags, do not use this system function. Use the "SetBit" system
function instead.
Use in the function list
SetBitWhileKeyPressed (Tag, Bit)
Use in user-defined functions
-
Parameters
Tag
The tag in which a bit is temporarily set to 1 (TRUE). Use only tags of the type BOOL, as far
as allowed by the PLC.
Bit
The number of the bit that is temporarily set to 1 (TRUE).
Note
The guaranteed update of the tags used with actual process values is absolutely conditional
in terms of reliable functionality. You should therefore configure the tag in an IO field, or assign
the function to a screen element such as a button.
If you configured a short event such as the activation of an alarm for the function you can
only access the actual process values by setting the tag for continuous reading.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1386 System Manual, 08/2011,
SetColorBackgroundLighting
Description
Defines the background lighting of the button.
Note
The configuration that was set at Switch off is reestablished when restarting the HMI device.
Use in the function list
SetColorBackgroundLighting (Value)
Use in user-defined functions
-
Parameters
Value
Defines the background lighting of the button:
0 (hmiWhite) = White: No color
1 (hmiGreen) = Green: Green color
2 (hmiYellow) = Yellow: Yellow color
3 (hmiRed) = Red: Red color
See also
Availability for specific devices of system functions (Page 1262)
SetBrightness
Description
Determines the brightness of the display.
Note
The configuration that is set in the Control Panel will be reestablished when you restart the
HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1387
Use in the function list
SetBrightness (value)
Use in user-defined functions
SetBrightness(Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Value
New value for the brightness.
See also
Availability for specific devices of system functions (Page 1262)
SetScreenKeyboardMode
Description
Enables or disables the automatic display of the screen keyboard on the HMI device.
This system function is also used to prevent the display of the screen keyboard, e.g. because
an external keyboard is connected to the HMI device.
Note
To enable the "SetScreenKeyboardMode" ("SetScreenKeyboardMode") system function on
an HMI other than a Touch Panel device, set the "Use on-screen keyboard" check box in the
"Runtime settings" dialog of the device settings.
Use in the function list
SetScreenKeyboardMode (Mode)
Use in user-defined functions
SetScreenKeyboardMode(Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1388 System Manual, 08/2011,
Parameters
Mode
Determines whether the screen keyboard is hidden or shown:
0 (hmiOff) = Off: Screen keyboard is hidden
1 (hmiOn) = On: Screen keyboard is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes.
See also
Availability for specific devices of system functions (Page 1262)
SetAlarmReportMode
Description
Switches the automatic reporting of alarms on the printer on or off.
Use in the function list
SetAlarmReportMode (Mode)
Use in user-defined functions
SetAlarmReportMode(Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether alarms are reported automatically on the printer:
0 (hmiDisablePrinting) = Reporting off: Alarms are not printed automatically.
1 (hmiEnablePrinting) = Reporting On: Alarms are printed automatically.
-1 (hmiToggle) = Toggle: Toggles between the two modes.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1389
SetRecipeTags
Description
Changes the status of the recipe tags from "Online" to "Offline" and vice versa.
This system function is used, for example, when recipe data record values are fine tuned when
starting up a machine.
Use in the function list
SetRecipeTags (Recipe number/name, Status, Output status message, Processing status)
Use in user-defined functions
SetRecipeTags(Recipe_number/name, Status, Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe in which the recipe data record is saved.
Status
Determines the status of the recipe tags:
0 (hmiOnline) = Online: Value changes of the recipe tags are transferred immediately to the
PLC connected to the HMI device.
1 (hmiOffline) = Offline: Value changes to the recipe tags are only transferred to the PLC
connected to the HMI device when, for example, the "SetDataRecordTagsToPLC" system
function is executed.
Output status message
Determines whether a status report is output after saving:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1390 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
SetDaylightSavingTime
Description
The system function "SetDaylightSavingTime" changes the setting of the HMI device from
daylight saving to standard time and vice versa.
Time settings will take place immediately following system function.
Note
The "SetDaylightSavingTime" system function does not support time zones without daylight
saving time.
Note
Windows 7
The system function "SetDaylightSavingTime" is not supported for PC-based HMI devices
under Windows 7.
Use in the function list
SetDaylightSavingTime (Mode)
Use in user-defined functions
SetDaylightSavingTime(Daylight_saving_time)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether Daylight Saving Time is set on the HMI device:
0 = Daylight Saving Time is not activated.
1 = Daylight Saving Time is activated
Tag
A variable of the type Bool or Uint.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1391
See also
Availability for specific devices of system functions (Page 1262)
SetLanguage
Description
Toggles the language on the HMI device. All configured text and system events are displayed
on the HMI device in the newly set language.
Use in the function list
SetLanguage (Language)
Use in user-defined functions
SetLanguage(Language)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Language
Determines which language is set on the HMI device. The following specifications are possible:
-1 (hmiToggle) = Toggle: Changes to the next language. The sequence is determined
during configuration in the "Project languages" editor.
Number you have defined under "Languages and fonts" in the "Runtime Settings" editor.
Changes to the language with the given number.
Language you have defined under "Languages and fonts" in the "Runtime Settings" editor.
Language abbreviation in accordance with the VBScript5 reference: This changes to the
language corresponding to the specified language code, e.g. "de-DE" for German
(Germany) or "en-US" for English (United States).
An overview of the language abbreviations is available in the basic information of VBScript
under the topic "Area diagram-ID (LCID) Diagram".
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1392 System Manual, 08/2011,
SetTag
Description
Assigns a new value to the given tag.
Note
This system function can be used to assign strings and numbers, depending on the type of
tag.
Use in the function list
SetTag (Tag, Value)
Use in user-defined functions
SetTag(Tag, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the given value is assigned.
Value
The value which the given tag is assigned.
Note
The "SetTag" system function is only executed after a connection has been established.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1393
SetConnectionMode
Description
Connects or disconnects the given connection.
Note
A connection to the PLC cannot be established until the operating mode ONLINE has been
set on the HMI device. Use the "SetDeviceMode" system function for this purpose.
Use in the function list
SetConnectionMode (Mode, Connection)
Use in user-defined functions
SetConnectionMode(Mode, Connection)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether a connection to the PLC is established or disconnected:
0 (hmiOnline) = Online: Connection is established.
1 (hmiOffline) = Offline: Connection is disconnected.
Connection
The PLC to which the HMI device is connected. You specify the name of the PLC in the
connection editor.
Multiple use of the system function in a user-defined function
If you use the "SetConnectionMode" system function for different connections, it may be
possible that not all system functions are executed correctly. Proceed as follows to prevent
this situation:
1. Create a "BOOL" type tag with the start value "0".
2. Configure the "SetConnectionMode" system function on the "Value change" event of the
HMI tags. If you want to disconnect three connections, for example, you must configure the
system function three times.
3. In the user-defined function, apply the "InvertBit" system function to the HMI tag.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1394 System Manual, 08/2011,
Application example
Two typical application examples for this system function are as follows:
Test
As long as no PLC is connected to the HMI device, no error messages will be output during
the test on the HMI device. If the HMI device is connected to a PLC, the connection to the
PLC can be established by pressing a key.
Start up
Several PLCs are to be configured for a system. At first, all PLCs except one are configured
"Offline". After start up of the first PLC, the connection to each of the other PLCs is
established by pressing a key. In this way, the other PLCs are started up one after another.
See also
Availability for specific devices of system functions (Page 1262)
SetWebAccess
Description
Determines the access mode to the runtime application using the Internet.
Use in the function list
SetWebAccess (Access mode)
Use in user-defined functions
-
Parameters
Access mode
Determines the access mode to the runtime application:
-1 (hmiToggle) = Toggle: Toggles between the two modes.
0 (hmiReadOnly) = Read-only.
1 (hmiReadWrite) = Read-write.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1395
BackupRAMFileSystem
Description
Backs up the RAM file system in the memory medium of the HMI device.
After restarting the HMI device, the data is automatically reloaded in the RAM file system.
Applications such as the Internet Explorer save data (e.g. the last web sites called up)
temporarily to the DRAM file system of the HMI device.
Use in the function list
BackupRAMFileSystem
Use in user-defined functions
BackupRAMFileSystem
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
SimulateSystemKey
Description
Simulates the behavior of a System Key. Use this system function if a system key, such as
the "ACK" key, "Input" key or the number pad is not available on the HMI device.
Use in the function list
SimulateSystemKey (System key)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1396 System Manual, 08/2011,
Parameters
System Key
System Key, the behavior for which is to be simulated.
System key "+/-"
With the SimulateSystemKey system function, the system key "+/-" is only supported for the
following HMI devices:
KTP400 Basic mono PN
KTP600 Basic mono PN
KTP600 Basic color PN
KTP600 Basic color DP
KTP1000 Basic PN
KTP1000 Basic DP
KTP1500 Basic PN
Use the system keys "+" and "-" separately for all other HMI devices.
See also
Availability for specific devices of system functions (Page 1262)
SimulateTag
Description
Simulates the behavior of tags and dynamic objects such as text lists, without having the HMI
device connected to a PLC.
This system function is used, for example, to demonstrate the functionality of a project.
NOTICE
Only tags of the data type Integer can be used for simulation. Tags of the data types Integer
and Double Integer, however, can be used with OP 73, OP 77A, TP 177A.
Use in the function list
SimulateTag (Tag, Cycle, Maximum value, Minimum value, Value)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1397
Parameters
Tag
The tag whose value is changed.
Cycle
The factor by which the basic cycle of 200 milliseconds is multiplied. The cycle defines when
the tag value is changed by the specified value. Possible cycles between 1 and 32767.
Maximum value
The maximum value that the tag can assume during simulation. The maximum value must be
greater than the minimum value but less than / equal to 32767.
Minimum value
The minimum value that the tag can assume during simulation. The minimum value must be
greater than the maximum value but less than / equal to -32768.
Value
The value by which the tag value is changed during each cycle. Possible values between
-32768 and 32767.
A positive value increases the tag value. When the maximum value is reached, the tag
value is set to the minimum value after the next update cycle.
A negative value reduces the tag value. When the minimum value is reached, the tag value
is set to the maximum value after the next update cycle.
See also
Availability for specific devices of system functions (Page 1262)
SmartClientViewRefresh
Description
Updates the contents displayed in the Sm@rtClient view.
Use in the function list
SmartClientViewRefresh (Screen object)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1398 System Manual, 08/2011,
Parameters
Screen object
Name of the Sm@rtClient view in which the command is triggered.
See also
System functions with WinCC Runtime (Page 1292)
SmartClientViewWriteProtectionOff
Description
Sets read-only access to "Off" in the Sm@rtClient view.
This setting allows a distant HMI device to be operated. The
"SmartClientViewWriteProtectionOn" system function is used to switch read-only access on
again.
Use in the function list
SmartClientViewWriteProtectionOff (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the Sm@rtClient view in which the command is triggered.
See also
System functions with WinCC Runtime (Page 1292)
SmartClientViewWriteProtectionOn
Description
Sets read-only access to "On" in the Sm@rtClient view.
This setting allows a distant HMI device to be monitored only. The
"SmartClientViewWriteProtectionOff" system function is used to switch read-only access off
again.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1399
Use in the function list
SmartClientViewWriteProtectionOn (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the Sm@rtClient view in which the command is triggered.
See also
System functions with WinCC Runtime (Page 1292)
SmartClientViewDisconnect
Description
Executes the "Disconnect" command in the Sm@rtClient view.
This system function is used when the integrated button of the screen object should not be
used.
Use in the function list
SmartClientViewDisconnect (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the Sm@rtClient view in which the command is triggered.
See also
System functions with WinCC Runtime (Page 1292)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1400 System Manual, 08/2011,
SmartClientViewConnect
Description
Executes the "Connect" command in the Sm@rtClient view.
This system function is used when the integrated button of the screen object should not be
used. The Sm@rtClient view establishes a connection with the configured HMI device.
Use in the function list
SmartClientViewConnect (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the Sm@rtClient view in which the command is triggered.
See also
System functions with WinCC Runtime (Page 1292)
SmartClientViewLeave
Description
Exits the Sm@rtClient view and returns to operation of the HMI device.
The connection to the HMI device configured in the smart client view is retained.
Use in the function list
SmartClientViewLeave (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the Sm@rtClient view in which the command is triggered.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1401
See also
System functions with WinCC Runtime (Page 1292)
SaveDataRecord
Description
Saves the current values of the recipe tags as data record to the memory medium of the HMI
device.
This system function is used, for example, to save a recipe data record in the recipe screen.
Use in the function list
SaveDataRecord (Recipe number/name, Data record number/name, Overwrite, Output status
message, Processing status)
Use in user-defined functions
SaveDataRecord(Recipe_number/name, Data_record_number/name, Overwrite,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe to which a recipe data record is saved.
Data record number/name
Number or name of the recipe data record to be saved.
Overwrite
Specifies whether an existing data record is overwritten:
0 (hmiOverwriteForbidden) = No: The recipe data record is not overwritten, the data record is
not saved.
1 (hmiOverwriteAlways) = Yes: The recipe data record is overwritten without a prompt for
confirmation.
2 (hmiOverwriteWithPrompting) = With confirmation: The recipe data record is overwritten only
with confirmation by the user.
Output status message
Determines whether a status report is output after saving:
0 (hmiOff) = Off: Status message is not output.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1402 System Manual, 08/2011,
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
StartLogging
Description
Starts the logging of data or alarms in the specified log. The function can also be applied to
audit trails.
You can interrupt logging at runtime using the "StopLogging" system function.
Use in the function list
StartLogging (Log type, Log)
Use in user-defined functions
StartLogging(Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail
Log
Name of the log which is started.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1403
See also
Availability for specific devices of system functions (Page 1262)
Managing logging behavior when Runtime starts (Page 925)
StartNextLog
Description
Stops the logging of data or alarms for the given log.
Logging is continued in the next log of the segmented circular log you configured for the
specified log.
If you did not configure a segmented circular log for the specified log, the system function has
no effect.
Use in the function list
StartNextLog (Log type, Log)
Use in user-defined functions
StartNextLog(Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
Log
Name of the log for which the logging is stopped and continued in the next log.
See also
Availability for specific devices of system functions (Page 1262)
StartProgram
Description
Starts the specified program on the HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1404 System Manual, 08/2011,
The runtime software continues running in the background. Alarms continue to be output and
data continues to be updated.
When the given application is exited, the screen which was active during the performance of
the system function is displayed on the HMI device.
This system function is used, for example, to edit recipe data records in MS Excel on the HMI
device.
Note
If Windows CE is installed on the HMI device, during the configuration it must be checked
whether the desired application can be started with this system function.
This system function allows all applications to be started which can be started in the "Execute"
dialog of Windows CE.
The application to be started must be installed on the HMI device.
Use in the function list
StartProgram (Program name, Program parameters, Display mode, Wait for program to end)
Use in user-defined functions
StartProgram (Program_name, Program_parameters, Display_mode,
Wait_for_program_to_end)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Program name
Name and path of the program which is started. Upper and lower case are taken into account
in this parameter.
NOTICE
If the path contains spaces, the program can only be started correctly if the path is specified
in inverted commas, e.g. "C:\Program Files\START\start.exe".
Program parameters
The parameters you transfer at the start of the program, for example a file that is opened after
the start of the program.
The description of the necessary parameters is found in the documentation of the program to
be started.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1405
Display mode
Determines how the program window is displayed on the HMI device:
0 (hmiShowNormal) = Normal
1 (hmiShowMinimized) = Minimized
2 (hmiShowMaximized) = Maximized
3 (ShowMinimizedAndInactive) = Minimized and inactive
Wait for program to end
Determines whether there is a change back to the project after the called up program has
ended:
0 (hmiNo) = No: No change to project
1 (hmiYes) = Yes: Change to project
Note
The "Wait for program to end" parameter is only available for Runtime Advanced and Panels.
See also
Availability for specific devices of system functions (Page 1262)
StatusForceGetValues
Description
Starts or stops the updating of values in the Status/Force display. The values are read from
the PLC connected to the HMI device until the update is stopped.
Note
As long as the values are updated, no entries are possible in the input fields of the Status/
Force display.
Use in the function list
StatusForceGetValues (Screen object)
Use in user-defined functions
-
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1406 System Manual, 08/2011,
Parameters
Screen object
Name of the Status/Force display to which data from the PLC is written.
See also
Availability for specific devices of system functions (Page 1262)
StatusForceSetValues
Description
Writes the values from the Status/Force display to the PLC to which the HMI device is
connected.
Use in the function list
StatusForceSetValues (Screen object)
Use in user-defined functions
-
Parameters
Screen object
Name of the Status/Force display from which data is written to the PLC.
See also
Availability for specific devices of system functions (Page 1262)
ControlSmartServer
Description
Starts or stops the Sm@rtServer.
Use in the function list
ControlSmartServer (Mode)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1407
Use in user-defined functions
ControlSmartServer (Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Specifies whether the Sm@rtServer is started or stopped.
-1 (hmiToggle) = Toggle: Toggles between the two modes
0 (hmiStop) = Stop: Sm@rtServer is stopped
1 (hmiStart) = Start: Sm@rtServer is started
See also
Availability for specific devices of system functions (Page 1262)
ControlWebServer
Description
Starts or stops the Web server.
Use in the function list
ControlWebServer (Mode)
Use in user-defined functions
ControlWebServer (Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Specifies whether the Web server is started or stopped.
-1 (hmiToggle) = Toggle: Toggles between the two modes
0 (hmiStop) = Stop: The Web server is stopped.
1 (hmiStart) = Start: The Web server is started.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1408 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
StopLogging
Description
Stops the logging of process values or alarms in the specified log. The function can also be
applied to audit trails.
The "StartLogging" system function is used to resume logging at runtime.
Note
When logging is stopped, a connection between WinCC and the log files or log database still
exists. Use the "CloseAllLogs" system function to disconnect this connection.
Use in the function list
StopLogging (Log type, Log)
Use in user-defined functions
StopLogging (Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail
Log
Name of the log that is stopped.
Application example
You are in runtime and want to change the data medium on which the process values are
logged.
Notes on configuring
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1409
Configure the "StopLogging" and "CloseAllLogs" system functions on the "Close Archive"
button.
Configure the "OpenAllLogs" and "StartLogging" system functions on the "Open Archive"
button.
Transfer the name of the log that is to be stopped and started as the parameter.
Procedure on HMI device
When the button "Close Archive" is pressed, the specified log is stopped and all open logs are
closed. The data medium can be changed. The "Open Archive" button opens all logs and
continues logging in the specified log.
See also
Availability for specific devices of system functions (Page 1262)
StopRuntime
Description
Exits the runtime software and thereby the project running on the HMI device.
Use in the function list
StopRuntime (Mode)
Use in user-defined functions
StopRuntime(Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether the operating system is shut down after exiting runtime.
0 (hmiStopRuntime) = Runtime: Operating system is not shut down
1 (hmiStopRuntimeAndOperatingSystem) = Runtime and operating system: The operating
system is shut down (not possible with WinCE)
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1410 System Manual, 08/2011,
LookupText
Description
Identifies an entry from a text list. The result depends on the value and on the selected runtime
language. The result is saved to a tag of data type "String".
Use in the function list
LookupText (Output text, Value, Language, Text list)
Use in user-defined functions
LookupText(Output_text, Index, Language, Text_list)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Output text
The tag to which the result is written.
Value
The tag that defines the value of the list entry.
Language
Defines the runtime language in which the list entry is identified.
Tag
The tag that contains the language. Enter the runtime language as decimal value of the
country ID, for example, 1031 for German - Standard, 1033 for English - USA. Details are
available in the VBScript basics, "Locale identifier (LCID) diagram".
Runtime language
Language code as per VBScript reference, for example, "de-DE" for German (Germany)
or "en-US" for English (United States of America). The selection depends on the activated
runtime languages.
Text list
Defines the text list. The list entry is read from the text list.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1411
ResetTagToHandWheel
Description
Separates the tag that is connected with the operating element handwheel, and reconnects
the handwheel with the global tags.
Use in the function list
ResetTagToHandWheel
Use in user-defined functions
-
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
SetTagToHandWheel
Description
Connect the tag with the operating device handwheel If the handwheel is operated, the tag
value changes. The connection can be reset using the "ResetTagToHandWheel" system
function.
Use in the function list
SetTagToHandWheel (Value)
Use in user-defined functions
-
Parameters
Value
Tag names which are connected to the operating device handwheel.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1412 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
TraceUserChange
Description
Outputs a system event that shows which user is currently logged in on the HMI device.
This system function can only be used in the Scheduler.
Use in the function list
TraceUserChange
Use in user-defined functions
-
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
DecreaseFocusedValue
Description
Subtracts the specified value from the value of the tag which is connected to the screen object
and currently has the focus.
The system function can be configured:
Input field
Symbolic selection list
Graphic selection list
Slider bar
Use in the function list
DecreaseFocusedValue (Value)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1413
Use in user-defined functions
-
Parameters
Value
The value which is subtracted from the tag value.
See also
Availability for specific devices of system functions (Page 1262)
DecreaseTag
Description
Subtracts the given value from the tag values.
X = X - a
Note
The system function uses the same tag as input and output values. When this system function
is used to convert a value, help tags must be used. The auxiliary tags are assigned to the tag
value with the "SetTag" system function.
If you configure the system function on the events of an alarm and the tag is not being used
in the current screen, it is not ensured that the actual value of the tags is being used in the
PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode.
Use in the function list
DecreaseTag (Tag, Value)
Use in user-defined functions
DecreaseTag(Tag, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag from which the given value is subtracted.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1414 System Manual, 08/2011,
Value
The value which is subtracted.
See also
Availability for specific devices of system functions (Page 1262)
ChangeConnection
Description
Disconnects the connection to the currently used PLC in use and establishes a connection to
a PLC with another address. The newly connected PLC must belong to the same device class
(S7-1200, S7-300, ...etc). With S7-1200, the use of the function is also only permitted for
absolute addressing.
Note
When changing to another address, ensure that the address is not already being used by
another HMI device.
The follows address types are supported:
IP address
MPI address
The follows PLC types are supported:
SIMATIC S7 1200
SIMATIC S7 300/400
SIMATIC S7-NC
SIMOTION
Use in the function list
ChangeConnection (Connection, Address, Slot, Rack)
Use in user-defined functions
ChangeConnection (Connection, Address, Slot, Rack)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1415
Parameters
Connection
Name of the connection that is disconnected. The name is set during configuration, for
example, in the "Connections" editor.
Address
MPI/PROFIBUS or IP address of the PLC to which the connection will be established.
Note
Set the address by means of a tag. The objects list displays the tags of all data types. Select
only tags of the following data types:
Ethernet connection: "String" data type
MPI connection: "Int" data type
Slot
Slot of the PLC to which the connection will be established.
Rack
Rack of the PLC to which the connection will be established.
Application example
You want to operate one HMI device on several machines. Configure the necessary PLCs in
the project, to which you want to change by pressing a key. When changing the PLC, the
connection to the PLC in use is disconnected. Then the connection to the new PLC with other
address parameters is reestablished. To access the values of the new PLC, configure the
same tags for the PLC used.
The PLC which you have indicated when creating the project will be used as default.
1. Enter the name and address of the PLC in the "Connections" editor.
2. Configure a button in the process screen.
3. Configure the "ChangeConnection" system function on the "Press" event.
4. Enter the name of the connection and address of the PLC as parameters.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1416 System Manual, 08/2011,
WinACMPUpdateStartupCharacteristics
Description
Reads whether WinAC MP is automatically started after startup of the HMI device. The LED
display of the "StartAtBoot" button is updated.
Use in the function list
WinACMPUpdateStartupCharacteristics(Startup characteristics, Update)
Use in user-defined functions
-
Parameters
Start-up characteristics
The tag that contains the value.
Update
Determines whether the display is updated:
0 (SwitchOff) = Off: LED display is gray. WinAC MP is not started on startup of the HMI device.
1 (SwitchOn) = On: LED display has the color "cyan". WinAC MP is started automatically on
startup of the HMI device.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1417
WinACMPUpdateModeSelectorSwitchSetting
Description
Updates the status display of the position of the mode selector switch.
Use in the function list
WinACMPUpdateModeSelectorSwitchSetting (ModeSelectorSwitch, Update)
Use in user-defined functions
-
Parameters
Mode selector switch
The tag that contains the value of the mode selector switch:
0 (MRES) = MRES: PLC memory reset
1 (STOP) = STOP: STOP mode
3 (RUN) = RUN: RUN mode
Update
Determines whether the status display will be updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1418 System Manual, 08/2011,
WinACMPUpdateBUSF1LED
Description
Updates the status display of the BUSF1 LED tag.
Use in the function list
WinACMPUpdateBUSF1LED(BUSF1, Update)
Use in user-defined functions
-
Parameters
BUSF1
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Defines whether the status display of the BUSF1 LED tag is updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1419
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateBUSF2LED
Description
Updates the status display of the BUSF2 LED tag.
Use in the function list
WinACMPUpdateBUSF2LED(BUSF2, Update)
Use in user-defined functions
-
Parameters
BUSF2
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Defines whether the status display of the BUSF2 LED tag is updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1420 System Manual, 08/2011,
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateAverageExecutionTime
Description
Updates the display of the average OB 1 execution time. The OB 1 execution time will be
displayed in milliseconds.
Use in the function list
WinACMPUpdateAverageExecutionTime(Cycle time, Update)
Use in user-defined functions
-
Parameters
Cycle time
Tag that contains the value of the average OB 1 execution time.
Update
Determines whether the display is updated:
0 (SwitchOff) = Off: Display is not updated.
1 (SwitchOn) = On: Display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1421
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateAverageCycleTime
Description
Updates the display of the average cycle time. The cycle time is displayed in milliseconds.
Use in the function list
WinACMPUpdateAverageCycleTime(Cycle time, Update)
Use in user-defined functions
-
Parameters
Cycle time
The tag that contains the value of the average cycle time.
Update
Determines whether the display is updated:
0 (SwitchOff) = Off: Display is not updated.
1 (SwitchOn) = On: Display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1422 System Manual, 08/2011,
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
System functions with WinCC Runtime (Page 1292)
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateEXTFLED
Description
Updates the status display of the EXTF LED tag.
Use in the function list
WinACMPUpdateEXTFLED(EXTF, Update)
Use in user-defined functions
-
Parameters
EXTF
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Defines whether the status display of the EXTF LED tag is updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1423
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateHMIExecutionTime
Description
Updates the value of the HMI Execution Time from WinAC MP (in ms).
Use in the function list
WinACMPUpdateHMIExecutionTime(Execution Time, Update)
Use in user-defined functions
-
Parameters
Execution time
The tag that contains the value of the HMI Execution Time.
Update
Determines whether the value is updated:
0 (SwitchOff) = Off: Value is not updated.
1 (SwitchOn) = On: Value is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1424 System Manual, 08/2011,
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateINTFLED
Description
Updates the status display of the INTF LED tag.
Use in the function list
WinACMPUpdateINTFLED(INTF, Update)
Use in user-defined functions
-
Parameters
INTF
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Defines whether the status display of the INTF LED tag is updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1425
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateLastCycleTime
Description
Updates the display of the last cycle time. The cycle time is displayed in milliseconds.
Use in the function list
WinACMPUpdateLastCycleTime (Cycle time , Update)
Use in user-defined functions
-
Parameters
Cycle time
The tag that contains the value of the last cycle time.
Update
Determines whether the display is updated:
0 (SwitchOff) = Off: Display is not updated.
1 (SwitchOn) = On: Display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1426 System Manual, 08/2011,
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateMaximumCycleTime
Description
Updates the display of the longest cycle time. The cycle time is displayed in milliseconds.
Use in the function list
WinACMPUpdateMaximumCycleTime(Cycle time, Update)
Use in user-defined functions
-
Parameters
Cycle time
The tag that contains the value of the longest cycle time.
Update
Determines whether the display is updated:
0 (SwitchOff) = Off: Display is not updated.
1 (SwitchOn) = On: Display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1427
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateMinimumCycleTime
Description
Updates the display of the shortest cycle time. The cycle time is displayed in milliseconds.
Use in the function list
WinACMPUpdateMinimumCycleTime (Cycle Time, Update)
Use in user-defined functions
-
Parameters
Cycle time
The tag that contains the value of the shortest cycle time.
Update
Determines whether the display is updated:
0 (SwitchOff) = Off: The display is not updated.
1 (SwitchOn) = On: The display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1428 System Manual, 08/2011,
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdatePowerLED
Description
Updates the status display ON/OFF of the Power LED tag.
Use in the function list
WinACMPUpdatePowerLED (Power, Update)
Use in user-defined functions
-
Parameters
Power
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Determines whether the status display ON/OFF is updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1429
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateIdleTime
Description
Updates the value of the HMI Execution Time from WinAC MP (in ms).
Use in the function list
WinACMPUpdateIdleTime(IdleTime, Update)
Use in user-defined functions
-
Parameters
IdleTime
The tag that contains the value.
Update
Determines whether the value is updated:
0 (SwitchOff) = Off: Value is not updated.
1 (SwitchOn) = On: Value is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1430 System Manual, 08/2011,
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateRUNLED
Description
Updates the status display of the RUN LED tag.
Use in the function list
WinACMPUpdateRUNLED(RUN, Update)
Use in user-defined functions
-
Parameters
RUN
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Defines whether the status display of the RUN LED tag is updated:
0 (SwitchOff) = Off: Status display is not updated.
1 (SwitchOn) = On: Status display is updated.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1431
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPUpdateSTOPLED
Description
Updates the status display of the STOP LED tag.
Use in the function list
UpdateSTOPLEDtag (STOP, Update)
Use in user-defined functions
-
Parameters
STOP
The tag that contains the value of the status display.
0 = Off
1 = Slow flashing
2 = Quick flashing
3 = On
Update
Defines whether the status display of the STOP LED tag is updated:
0 (SwitchOff) = Off: Status display is not updated.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1432 System Manual, 08/2011,
1 (SwitchOn) = On: Status display is updated.
Notes on configuring
You configure this system function on the "Loaded" event or on the "Cleared" event of a screen.
Note the following during configuration:
System function on the "Loaded" event
Set the "Update" parameter to "On".
System function on the "Cleared" event
Set the "Update" parameter to "Off".
If you call the system function repeatedly in a screen, always use the same tag. Otherwise,
only the last activated tag will be updated.
If you want to configure all system functions with the prefix "WinACMPUpdate" in a screen,
every system function is only permitted once per screen.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPLogging
Description
Saves the current STEP 7 user program, the current system configuration and the current
values of the DBs in a log file.
Use in the function list
WinACMPLogging (File name)
Use in user-defined functions
-
Parameters
File name
Name of the log file in which the data is saved. Enter the file location and the file extension
(*.wld), for example, "\flash\AddOn\WinACMP\Default.wld ".
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1433
WinACMPGetStartCharacteristics
Description
Reads in the 'desired' operating state after startup of the HMI device of WinAC MP.
Use in the function list
WinACMPGetStartMode (Operating state, Update)
Use in user-defined functions
-
Parameters
Operating Mode
The tag that defines the value of the operating mode.
Update
Determines whether the operating mode is read out:
0 (SwitchOff) = Off: Operating mode is not read out.
1 (SwitchOn) = On: Operating mode is read out.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPGetVersion
Description
Reads out the value of the version number of WinAC MP.
Use in the function list
WinACMPGetVersion (Version, Update)
Use in user-defined functions
WinACMPGetVersion(Version, Action)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1434 System Manual, 08/2011,
Parameters
Version
The tag that contains the value.
Update
Determines whether the version number is read out:
0 (SwitchOff) = Off: Version number is not read out.
1 (SwitchOn) = On: Version number is read out.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPClearCycleTimeBuffer
Description
Clears the cycle time data of the histogram.
Use in the function list
WinACMPClearCycleTimeBuffer
Use in user-defined functions
-
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
WinACMPSetStartAtBoot
Description
Determines whether or not WinAC MP is started automatically after startup of the HMI device.
Use in the function list
WinACMPSetStartAtBoot(StartAtBoot)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1435
Use in user-defined functions
WinACMPSetStartAtBoot (Start at boot)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Start-up characteristics
Defines whether WinAC MP is started automatically.
0 (StartAtBootOff) = Off: WinAC MP is not started on startup of the HMI device.
1 (StartAtBootOn) = On: WinAC MP is started automatically on startup of the HMI device.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPSetModeSelectorSwitch
Description
Sets the mode selector switch to RUN or STOP and is also used for memory reset.
Use in the function list
WinACMPSetModeSelectorSwitch(ModeSelectorSwitch)
Use in user-defined functions
-
Parameters
Mode selector switch
Defines the position of the mode selector switch:
0 (MRES) = MRES: PLC memory reset
1 (STOP) = STOP: STOP mode
3 (RUN) = RUN: RUN mode
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1436 System Manual, 08/2011,
WinACMPSetHMIExecutionTime
Description
Sets the value of the HMI Execution Time of WinAC MP.
Use in the function list
WinACMPSetHMIExecutionTime (Execution Time)
Use in user-defined functions
-
Parameters
Execution time
The tag that contains the value.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPSetResetCharacteristics
Description
Sets the restart characteristics, either cold restart (CRST) or warm restart (WRST).
Use in the function list
WinACMPSetRestartCharacteristics (RestartCharacteristics)
Use in user-defined functions
-
Parameters
RestartCharacteristics
Defines the restart characteristics:
0 (WarmRestart) = Warm restart: A warm restart is performed.
1 (ColdRestart) = Cold restart: A cold restart is performed.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1437
See also
Availability for specific devices of system functions (Page 1262)
WinACMPSetIdleTime
Description
Sets the value of the HMI Execution Time of WinAC MP.
Use in the function list
WinACMPSetIdleTime (IdleTime)
Use in user-defined functions
-
Parameters
IdleTime
The tag that contains the value.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPSetStartMode
Description
Sets the operating mode of WinAC MP after startup of the HMI device.
Use in the function list
WinACSetStartMode (Autostart)
Use in user-defined functions
WinACSetStartMode (Autostart)
Can be used if the configured device supports user-defined functions. Additional information
is available under Auto-Hotspot.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1438 System Manual, 08/2011,
Parameters
Autostart
Defines whether the Autostart function of WinAC MP is activated.
0 (AutoStartOff) = Off: After startup, WinAC MP remains in the STOP operating mode.
1 (AutoStartOn) = On: After startup, WinAC MP changes to the operating mode it was in before
it was closed.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPStartHistogram
Description
Starts the cyclic sending of histogram values and updates the display. The histogram shows
the percentual distribution of the measured cycle times.
Use in the function list
WinACMPStartHistogram (Update, Percentage, Cycle Time, Highest Value of Y Axis, Register-
ID)
Use in user-defined functions
-
Parameters
Update
Defines whether WinAC returns histogram values:
0 (SwitchOff) = Off: The cyclic sending of the histogram values is not started. The display is
not updated.
1 (SwitchOn) = On: The cyclic sending of the histogram values is started. The display is
updated.
Percentage
Percentage of the cycles which are performed during the recorded cycle times.
Cycle time
Histogram of cycle times.
Highest value of Y axis
Maximum value of Y axis
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1439
Register-ID
Histogram ID
See also
Availability for specific devices of system functions (Page 1262)
WinACMPControl
Description
Starts or stops WinAC MP.
Use in the function list
WinACMPControl (WinAC)
Use in user-defined functions
-
Parameters
WinAC
Determines whether WinAC MP is started or stopped.
0 (ShutdownWinACMP) = Stop: WinAC MP is stopped.
1 (StartWinACMP) = Start: WinAC MP is started.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPStopHistogram
Description
Stops the cyclic sending of histogram data and deletes the history data.
Use in the function list
WinACMPStopHistogram (Register-ID)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1440 System Manual, 08/2011,
Use in user-defined functions
-
Parameters
Register-ID
Histogram ID
See also
Availability for specific devices of system functions (Page 1262)
WinACMPRestore
Description
Loads the STEP 7 user program, the system configuration and the DBs from a log file.
Use in the function list
WinACMPRestore (File name)
Use in user-defined functions
-
Parameters
File name
Name of the log file in which the data is saved. Enter the file location and the log file, for
example, ""\flash\AddOn\WinACMP\Default.wld ".
See also
Availability for specific devices of system functions (Page 1262)
ShowLogonDialog
Description
Opens a dialog on the HMI device with which the user can log on to the HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1441
Use in the function list
ShowLogonDialog
Use in user-defined functions
-
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
ShowOperatorNotes
Application
Displays the configured tooltip of the selected object.
If the system function is configured on a function key, the tooltip for the screen object that
currently has the focus is displayed. If a tooltip is configured for the screen itself, you can switch
to this text by pressing <Enter> or by double-clicking on the help window.
If the system function is configured on a button, only the tooltip for the current screen is
displayed. If a tooltip is configured on the button itself, initially only the tooltip for the button is
displayed. You can press <Enter> or double-click on the help window to switch to the tooltip
for the current screen.
Note
No other screen object can be used while the help window is open. To use the screen object,
close the help window.
Closing the help window
You can close the help window in the following ways:
Using the keys:
By pressing the <HELP> key again
By pressing the <ESC> key
Using the touch screen:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1442 System Manual, 08/2011,
By pressing the button
Use in the function list
ShowOperatorNotes (Display mode)
Use in user-defined functions
ShowOperatorNotes (Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Display mode
Determines whether the configured tooltip is hidden or shown:
0 (hmiOff) = Off: Configured tooltip is hidden
1 (hmiOn) = On: Configured tooltip is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Availability for specific devices of system functions (Page 1262)
ShowAlarmWindow
Description
Hides or shows the alarm window on the HMI device.
Use in the function list
ShowAlarmWindow (Object name, Display mode)
Use in user-defined functions
ShowAlarmWindow(Object_name, Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1443
Parameters
Object name
Name of the alarm view which is hidden or shown.
Display mode
Determines whether the alarm window is hidden or shown:
0 (hmiOff) = Off: Alarm view is hidden
1 (hmiOn) = On: Alarm view is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Availability for specific devices of system functions (Page 1262)
ShowSoftwareVersion
Description
Hides or shows the version number of the runtime software.
Use this system function if during servicing, for example, you required the version of the runtime
software used.
Use in the function list
ShowSoftwareVersion (Display mode)
Use in user-defined functions
ShowSoftwareVersion(Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Display mode
Determines whether the version number is shown:
0 (hmiOff) = Off: Version number is not shown
1 (hmiOn) = On: Version number is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1444 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
ShowSystemDiagnosticsWindow
Description
Hides or shows the system diagnostics window on the HMI device. The system diagnostics
window is only available in the global screen for Comfort Panels.
Use in the function list
ShowSystemDiagnosticsWindow (Target Object name)
Use in user-defined functions
ShowSystemDiagnosticsWindow(Target_Object_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Object name
Name of the system diagnostics view which is hidden or shown.
See also
Availability for specific devices of system functions (Page 1262)
ShowSystemAlarm
Description
Displays the value of the delivered parameter as a system alarm on the HMI device.
Use in the function list
ShowSystemAlarm (Text/value)
Use in user-defined functions
ShowSystemAlarm (Text/value)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1445
Parameters
Text/Value
The text or the value, which was output as a system alarm.
See also
Availability for specific devices of system functions (Page 1262)
9.8.2.2 Events
Overview
Editors
Introduction
The following table shows which events occur in which editor.
Technical data subject to change.
Icon Editor
Screens
HMI alarms
HMI tags
Logs
Scheduler
Audit Trail
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1446 System Manual, 08/2011,
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- --
Auto-Hotspot -- -- -- --
Auto-Hotspot -- -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Basic objects
Introduction
The following table shows which events occur on which objects.
Technical data subject to change.
Icon Object
Line
Polyline
Polygon
Ellipse
Circle
Rectangle
Text field
Graphic view
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1447
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1448 System Manual, 08/2011,
Elements
Introduction
The following table shows which events occur on which objects.
Technical data subject to change.
Icon Object
IO field
Button
Symbolic IO field
Graphic IO field
Date/time field
Bar
Switch
Symbol library
Slider
Gauge
Clock
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- --
Auto-Hotspot -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1449
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Controls
Introduction
The following table shows which events occur on which objects.
Technical data subject to change.
Icon Object
Alarm view/alarm window
Alarm indicator
Trend view
User view
HTML browser
Status/Force
Sm@rtClient view
Recipe view
f(x) trend view
System diagnostics view / system diagnostics window
Function key
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1450 System Manual, 08/2011,
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1451
Events
Cleared
Description
Occurs when the active screen on the HMI device is cleared.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Activate
Description
Occurs when the user selects a display or operating object using the configured tab sequence.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Note
If the user e.g. clicks a button with the mouse, the "Click" event is triggered. Users wishing
to trigger the "Enable" event must select the button using the tab key.
The "Activate" event is only used to detect whether an object was selected. The event does
not trigger a password prompt.
For this reason, do not use the "Activate" event if you want to configure access protection on
the function call of the object.
Adjust
Description
Occurs if the status of a display and operator control object changes.
The status of an object changes if, for example, the user presses the key.
Note
Please note that the availability of the event depends on the HMI device and object type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1452 System Manual, 08/2011,
Loaded
Description
Occurs when all configured display and operating objects are loaded in the active screen after
a screen change.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Note
Enable a screen change to ensure that the connection with the control is established after
switch-on.
Selection changed
Description
Occurs when the user changes the selection.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
When dialog is opened
Description
The event is triggered when a modal dialog opens.
Note
Please note that the availability of the event depends on the HMI device and object type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1453
When dialog is closed
Description
The event is triggered when a modal dialog closes.
Note
Please note that the availability of the event depends on the HMI device and object type.
User change
Description
Occurs when a user logs off at an HMI device or another user logs on at the HMI device.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Screen change
Description
Occurs when all configured display and operating objects are loaded in the screen after a
screen change.
Use the "Loaded" event if you want to perform other system functions during a screen change
to a certain screen.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Deactivate
Description
Occurs when the user takes the focus from a display and operating object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1454 System Manual, 08/2011,
A screen object can be disabled using the configured tab order or by performing another action
with the mouse.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Note
System functions or user-defined functions on the "Deactivate" event of a screen are not
executed when a screen is being closed.
The "Deactivate" event is only used to detect whether an object was deselected. The event
does not trigger a password prompt.
For this reason, do not use the "Deactivate" event if you want to configure access protection
on the function call of the object.
Double-click
Description
Occurs when the user double-clicks on an object from the symbol library.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Press
Description
Occurs when the user clicks on a button with the left mouse button, presses <RETURN> or
<SPACE>.
Also occurs when the user right-clicks on an object of the symbol library.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1455
On Finish Input
Description
Triggered when you confirm input at an I/O field by pressing ENTER, or by mouse click, or by
touch screen operation.
The "On Finish Input" event is also started if the value of a tag does not change, for example,
if a value is exceeded, or if a user cancels the dialog to acknowledge a tag (Audit option
package) that has to be acknowledged.
The event is not triggered, on the other hand, by user logon or by input fields configured with
an authorization.
Note
Please note that the availability of the event depends on the HMI device and object type.
Press ESC twice
Description
Occurs when the user presses the <ESC> key twice at the HMI device.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Outgoing
Description
Occurs when an alarm is deactivated.
Note
Please note that the availability of the event depends on the HMI device and object type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1456 System Manual, 08/2011,
Incoming
Description
Occurs when an alarm is triggered and displayed in the alarm view.
Note
Please note that the availability of the event depends on the HMI device and object type.
In the event of high limit violation
Description
Occurs when the high limit of a tag is exceeded.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
In the event of low limit violation
Description
Occurs when the low limit of a tag is undershot.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Click
Description
Occurs if the user clicks a display and operating object with the mouse or touches the touch
display with a finger.
In case you click the incorrect object, prevent processing of configured function list as follows:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1457
Move the mouse pointer away from the object while keeping the mouse button pressed.
Release the mouse button as soon as the mouse pointer leaves the object. The function
list will then not be processed.
On touch displays, the display must be touched with the finger until a reaction occurs, e.g.,
a screen change.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Click when flashing
Description
Occurs when the user clicks a flashing screen object with the mouse or touches a screen object
on the touch display with his finger.
Note
Please note that the availability of the event depends on the HMI device and object type.
Loop-in alarm
Description
Occurs as soon as the user selects an alarm in the alarm view and then clicks on the "Loop-
In-Alarm" button or double clicks on the alarm.
For the "Loop-In-Alarm" event, you configure system functions, such as a change to the screen
in which the alarm occurred.
You cannot configure local scripts for the "Loop-In-Alarm" event in Runtime Professional.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Release
Description
Occurs when the user releases a button.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1458 System Manual, 08/2011,
This even does not occur, as long as the button remains pressed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Alarm buffer overflow
Description
Occurs when the configured size of the alarm buffer is reached.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Acknowledge
Description
Occurs when the user acknowledges an alarm.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Reach margin
Description
Occurs when the user reaches the beginning or the end of a scrollable area.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Note
A user-defined function must not be configured for the "Boundary reached" event.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1459
Configurable objects
The event can only be configured on the <Up> and <Down> keys, or on the keys on which
you have configured the "ScreenObjectPageUp" or "ScreenObjectPageDown" system
functions.
Runtime Stop
Description
Occurs when the user exits the Runtime software on the HMI device.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Note
A user-defined function must not be configured for the "Runtime stop" event.
Press key
Description
Occurs when the user presses a function key.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Release key
Description
Occurs when the user releases a function key.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1460 System Manual, 08/2011,
Overflow
Description
Occurs when the configured size of the log is reached. You use the log type "Trigger event".
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Switch OFF
Description
Occurs when the user moves the display and operating object "Switch" to the OFF position.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Switch ON
Description
Occurs when the user moves the display and operating object "Switch" to the ON position.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Low free storage space
Description
This event is triggered if the storage space available on the medium to which the Audit Trail
is less than the configured minimum.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1461
Free space critically low
Description
This event is triggered if the storage medium to which an Audit Trail is saved provides
insufficient storage space due to hardware restrictions.
Value change
Description
Occurs when the value of an object or the value of an array element changes.
The value change of a tag is triggered by the PLC or by the user, e.g. when a new value is
entered.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Time expired
Description
Occurs when the time configured in the scheduler expires.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
9.8.2.3 VB scripts
System functions
AcknowledgeAlarm
Description
Acknowledges all selected alarms.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1462 System Manual, 08/2011,
This system function is used when the HMI device does not have an ACK key or when the
integrated key of the alarm view should not be used.
This system function can only be used for function keys.
Use in the function list
AcknowledgeAlarm
Use in user-defined functions
AcknowledgeAlarm
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
ActivatePreviousScreen
Description
Performs a screen change to the screen which was activated before the current screen. The
screen change is not performed if no screen was activated beforehand.
The last 10 screens that were called up are saved. A system alarm is output when you change
to a screen which is no longer saved.
Note
If you want to use the system function, the screen to which you change has to be used in the
navigation structure.
Use in the function list
ActivatePreviousScreen
Use in user-defined functions
ActivatePreviousScreen
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1463
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
ActivateScreen
Description
Performs a screen change to the given screen.
Use the "ActivateScreenByNumber" system function to change from the root screen to the
permanent window or vice versa.
Use in the function list
ActivateScreen (Screen name, Object number)
Use in user-defined functions
ActivateScreen (Screen_name, Object_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Screen name
Name of the screen to which you change.
Object number
The operator control element which receives the focus in the given screen after the screen
change. The number of the operator control element is to be determined using the tabulator
sequence during configuration.
When "0" is specified:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1464 System Manual, 08/2011,
If the focus is in the permanent window when the system function is called up, the
permanent window maintains the focus.
If the focus is in the root screen when the system function is called up, the first operator
control element in the given screen receives the focus.
Note
If the "Reach margin" event is assigned to the "ActivateScreen" system function, only the
value "0" is valid for the "Object number" parameter. The active object is not defined by
the object number, but rather by the X position it had prior to the screen change.
See also
Availability for specific devices of system functions (Page 1262)
ActivateScreenByNumber
Description
Performs a screen change to a screen depending on a tag value.
The screen is identified by its screen number.
Use in the function list
ActivateScreenByNumber (Screen number, Object number)
Use in user-defined functions
ActivateScreenByNumber (Screen_number, Object_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Screen number
Tag which contains the screen number of the destination screen.
When a change from the root screen to the permanent window is desired, "0" or "-1" is specified:
0 = Change from root screen to permanent window
-1 = Change from permanent window to root screen
Object number
The number of the screen object which receives the focus in the given screen after the screen
change. The number of the operator control element is to be determined using the tabulator
sequence during configuration.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1465
When "0" is specified:
If the focus is in the permanent window when the system function is called up, the
permanent window maintains the focus.
If the focus is in the root screen when the system function is called up, the first operator
control element in the given screen receives the focus.
See also
Availability for specific devices of system functions (Page 1262)
ActivateSystemDiagnosticsView
Description
Activates the system diagnostics view. The system diagnostics view shows the detail view of
the respective device.
Use in the function list
ActivateSystemDiagnosticsView (Screen name, Object name)
Use in user-defined functions
ActivateSystemDiagnosticsView (Screen_name, Object_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Screen name
Name of the screen contained in the system diagnostics view.
Object name
Object name of the system diagnostics view.
See also
Availability for specific devices of system functions (Page 1262)
ArchiveLogFile
Description
This system function moves or copies a log to another storage location for long-term logging.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1466 System Manual, 08/2011,
With Audit Trails, always use the "Move" (hmiMove)" mode, otherwise you will be violating the
FDA guideline by duplicating the data stored.
Prior to "ArchiveLogFile" always run the system function "CloseAllLogs".
After this system function, run the "OpenAllLogs" system function.
In "Copy log" mode, the logs are not reopened until the log has been successfully copied, or
unless a timeout occurs during the copy process. In "Move log" mode, the logs to be moved
are renamed and the new logs are opened immediately. To move the renamed logs, a job is
submitted which attempts to move them every 300 seconds if the server cannot be reached.
The job is also retained after Runtime is restarted until it is executed.
Use in the function list
ArchiveLogFile (Log type, Log, Directory name, Mode)
Use in user-defined functions
ArchiveLogFile (Log_type, Log, Directory_name, Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (miAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail log available for GMP compliant projects. Additional
information is available under "Activating GMP-compliant configuration".
Log
Name of the log being archived.
Directory name
Path for saving the log.
Mode
0 (hmiCopy) = Copy log
1 (hmiMove) = Move log
Application example
You want to move a log file from a local storage medium to the server in order to generate a
backup copy of this file at cyclic intervals.
Notes on configuring
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1467
Set up a task in the scheduler which is executed at a specific time on a daily basis. Configure
the following function list for the task:
Procedure on HMI device
All log files will be closed.
The log file you specified is moved to the server.
All closed log files will be opened again.
See also
Availability for specific devices of system functions (Page 1262)
Back up RAM file system
Description
Backs up the RAM file system in the memory medium of the HMI device.
After restarting the HMI device, the data is automatically reloaded in the RAM file system.
Applications such as the Internet Explorer save data (e.g. the last web sites called up)
temporarily to the DRAM file system of the HMI device.
Use in the function list
BackupRAMFileSystem
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1468 System Manual, 08/2011,
Use in user-defined functions
BackupRAMFileSystem
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
CalibrateTouchScreen
Description
Calls a program for calibrating the touch screen.
During the calibration process, there is a prompt to touch five positions on the screen display.
Touch the screen display within 30 seconds, to confirm the calibration process. If the calibration
is not completed within this time span, the calibration settings are discarded. The user prompt
is in English.
Use this system function the first time you start the HMI device.
Use in the function list
CalibrateTouchScreen
Use in user-defined functions
CalibrateTouchScreen
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Note
The CalibrateTouchScreen system function cannot be simulated.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1469
See also
Availability for specific devices of system functions (Page 1262)
ChangeConnection
Description
Disconnects the connection to the currently used PLC in use and establishes a connection to
a PLC with another address. The newly connected PLC must belong to the same device class
(S7-1200, S7-300, ...etc). With S7-1200, the use of the function is also only permitted for
absolute addressing.
Note
When changing to another address, ensure that the address is not already being used by
another HMI device.
The follows address types are supported:
IP address
MPI address
The follows PLC types are supported:
SIMATIC S7 1200
SIMATIC S7 300/400
SIMATIC S7-NC
SIMOTION
Use in the function list
ChangeConnection (Connection, Address, Slot, Rack)
Use in user-defined functions
ChangeConnection (Connection, Address, Slot, Rack)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Connection
Name of the connection that is disconnected. The name is set during configuration, for
example, in the "Connections" editor.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1470 System Manual, 08/2011,
Address
MPI/PROFIBUS or IP address of the PLC to which the connection will be established.
Note
Set the address by means of a tag. The objects list displays the tags of all data types. Select
only tags of the following data types:
Ethernet connection: "String" data type
MPI connection: "Int" data type
Slot
Slot of the PLC to which the connection will be established.
Rack
Rack of the PLC to which the connection will be established.
Application example
You want to operate one HMI device on several machines. Configure the necessary PLCs in
the project, to which you want to change by pressing a key. When changing the PLC, the
connection to the PLC in use is disconnected. Then the connection to the new PLC with other
address parameters is reestablished. To access the values of the new PLC, configure the
same tags for the PLC used.
The PLC which you have indicated when creating the project will be used as default.
1. Enter the name and address of the PLC in the "Connections" editor.
2. Configure a button in the process screen.
3. Configure the "ChangeConnection" system function on the "Press" event.
4. Enter the name of the connection and address of the PLC as parameters.
See also
Availability for specific devices of system functions (Page 1262)
ClearAlarmBuffer
Description
Deletes alarms from the alarm buffer on the HMI device.
Note
Alarms which have not yet been acknowledged are also deleted.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1471
Use in the function list
ClearAlarmBuffer (Alarm class number)
Use in user-defined functions
ClearAlarmBuffer (Alarm_class_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Alarm class number
Determines which alarms are to be deleted from the alarm buffer:
0 (hmiAll) = All alarms/events
1 (hmiAlarms) = Alarms of alarm class "Errors"
2 (hmiEvents) = Alarms of alarm class "Warnings"
3 (hmiSystem) = Alarms of alarm class "System"
4 (hmiS7Diagnosis) = Alarms of alarm class "Diagnosis Events"
Note
Availability for specific devices
Alarms of alarm class "Diagnosis Events" are not available on Basic Panels.
See also
Availability for specific devices of system functions (Page 1262)
ClearAlarmBufferProtoolLegacy
Description
The system function exists to ensure compatibility.
It has the same functionality as the "ClearAlarmBuffer" system function, but uses the old
ProTool numbering.
Use in the function list
ClearAlarmBufferProTool (Alarm class number)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1472 System Manual, 08/2011,
Use in user-defined functions
ClearAlarmBufferProtoolLegacy (Alarm_class_number)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Alarm class number
Alarm class number whose messages are to be deleted:
-1 (hmiAllProtoolLegacy) = All alarms/events
0 (hmiAlarmsProtoolLegacy) = Alarms of alarm class "Errors"
1 (hmiEventsProtoolLegacy) = Alarms of alarm class "Warnings"
2 (hmiSystemProtoolLegacy) = Alarms of alarm class "System"
3 (hmiS7DiagnosisProtoolLegacy) = Alarms of alarm class "Diagnosis Events"
Note
Availability for specific devices
Alarms of alarm class "Diagnosis Events" are not available on Basic Panels.
See also
Availability for specific devices of system functions (Page 1262)
ClearDataRecord
Description
Deletes a recipe data record.
Several data records can be deleted from one or more recipes.
Use in the function list
ClearDataRecord (Recipe number/name, Data record number/name, Confirmation, Output
status message, Processing status)
Use in user-defined functions
ClearDataRecord
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1473
Parameters
Recipe number/name
Number or name of the recipe from which recipe data records are deleted. "0" is specified if
you want to delete recipe data records from all available recipes.
Data record number/name
Number or name of the recipe data record to be deleted. "0" is specified if you want to delete
all recipe data records.
Confirmation
Determines whether the operator should confirm the deletion:
0 (hmiOff) = Off: Deletion is begun without confirmation.
1 (hmiOn) = On: The starting of the deletion process must be confirmed.
Output status message
Determines whether a status report is output after the deletion:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
ClearDataRecordMemory
Description
Deletes all recipes and recipe data records from the specified storage medium.
Use in the function list
ClearDataRecordMemory (Storage location, Confirmation, Output status message,
Processing status)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1474 System Manual, 08/2011,
Use in user-defined functions
ClearDataRecordMemory(Storage_location, Confirmation, Output_status_message,
Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Storage location
Determines the storage location:
0 (hmiFlashMemory) = Flash memory: Internal flash memory of the HMI device
1 (hmiStorageCard) = Storage card
2 (hmiStorageCard2) = Storage card 2
3 (hmiStorageCard3) = Storage card MultiMediaCard
4 (hmiStorageCard4) = Storage card USB
Confirmation
Determines whether the operator should confirm the deletion:
0 (hmiOff) = Off: Deletion is begun without confirmation.
1 (hmiOn) = On: The starting of the deletion process must be confirmed.
Output status message
Determines whether a status report is output after the deletion:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1475
ClearLog
Description
Deletes all data records in the given log.
Use in the function list
ClearLog (Log type, Log)
Use in user-defined functions
ClearLog (Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail log Available for GMP-compliant projects Additional
information is available under "Activating GMP-compliant configuration".
Log
Name of the log from which all entries are deleted.
See also
Availability for specific devices of system functions (Page 1262)
CloseAllLogs
Description
Disconnects the connection between WinCC and all logs.
Note
Before you close a log, the logging function must first be stopped in the log. Use the
"StopLogging" system function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1476 System Manual, 08/2011,
Use in the function list
CloseAllLogs
Use in user-defined functions
CloseAllLogs
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Application example
You are in runtime and want to change the data medium on which the process values are
logged.
Notes on configuring
Configure the "StopLogging" and "CloseAllLogs" system functions on the "Close Archive"
button.
Configure the "OpenAllLogs" and "StartLogging" system functions on the "Open Archive"
button.
As parameter transfer the respective name of the log that is to be stopped and started.
Procedure on HMI device
When the button "Close Archive" is pressed, the specified log is stopped and all open logs are
closed. The data medium can be changed. You open all logs with the "Open Archive" button.
The logging process will continue in the specified log.
See also
Availability for specific devices of system functions (Page 1262)
ControlSmartServer
Description
Starts or stops the Sm@rtServer.
Use in the function list
ControlSmartServer (Mode)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1477
Use in user-defined functions
ControlSmartServer (Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Specifies whether the Sm@rtServer is started or stopped.
-1 (hmiToggle) = Toggle: Toggles between the two modes
0 (hmiStop) = Stop: Sm@rtServer is stopped
1 (hmiStart) = Start: Sm@rtServer is started
See also
Availability for specific devices of system functions (Page 1262)
ControlWebServer
Description
Starts or stops the Web server.
Use in the function list
ControlWebServer (Mode)
Use in user-defined functions
ControlWebServer (Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Specifies whether the Web server is started or stopped.
-1 (hmiToggle) = Toggle: Toggles between the two modes
0 (hmiStop) = Stop: The Web server is stopped.
1 (hmiStart) = Start: The Web server is started.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1478 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
CopyLog
Description
Copies the contents of a log to another log. Tag values can only be copied to other data logs
and alarms only to other alarm logs, however.
Note
If you copy a log using the "CopyLog" system function, it is possible that external applications
will be unable to read certain country-specific special characters in the logged message text
of the log copy. This does not apply to WinCC Runtime. WinCC Runtime can read the copied
log files without errors.
Use in the function list
CopyLog (Log type, Destination log, Source log, Mode, Delete source log)
Use in user-defined functions
CopyLog (Log_type, Destination log, Source_log, Mode, Delete_source_log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
Destination log
Name of the log into which the entries are copied (Destination log).
Source log
Name of the log from which the entries are copied (Source log).
Mode
Determines what is done with copied entries in the destination log:
0 (hmiOverwrite) = Overwrite: Existing entries are overwritten.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1479
2 (hmiAppend) = Append: The entries are inserted at the end of the destination log. When the
configured size of the log has been reached, the destination log is treated like a circular log.
Delete source log
Determines whether the source log is deleted after copying.
0 (hmiNo) = No: Is not deleted.
1 (hmiYes) = Yes: Is deleted.
See also
Availability for specific devices of system functions (Page 1262)
DecreaseTag
Description
Subtracts the given value from the tag values.
X = X - a
Note
The system function uses the same tag as input and output values. When this system function
is used to convert a value, help tags must be used. The auxiliary tags are assigned to the tag
value with the "SetTag" system function.
If you configure the system function on the events of an alarm and the tag is not being used
in the current screen, it is not ensured that the actual value of the tags is being used in the
PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode.
Use in the function list
DecreaseTag (Tag, Value)
Use in user-defined functions
DecreaseTag(Tag, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag from which the given value is subtracted.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1480 System Manual, 08/2011,
Value
The value which is subtracted.
See also
Availability for specific devices of system functions (Page 1262)
EditAlarm
Description
Triggers the "Edit" event for all selected alarms.
If the alarms to be edited have not yet been acknowledged, the acknowledgment takes place
automatically when this system function is called up.
This system function can only be used for function keys.
Use in the function list
EditAlarm
Use in user-defined functions
EditAlarm
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
Encode
Description
Adapts the "String" data type of a tag for transfer to the automation system (AS). The tag of
WinCC data type "String" is converted into the AS data type "Array of byte". The result is written
to a tag.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1481
Use in the function list
Encode (Byte array, String, Coding)
Use in user-defined functions
Encode (Byte_array, String, Encoding)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Byte array
The tag that contains the converted value.
Note
The Byte array must be twice the size of the string length + 2. The Byte array must contain
242 array elements if the string has a length of 120 characters.
Characters are either truncated or not converted if the size is insufficient.
String
The tag of data type "String" that is converted.
Encode
0 (hmiEncodeUTF16LE) - String is encoded in UTF16LE (Unicode 16 Little Endian).
See also
Availability for specific devices of system functions (Page 1262)
EncodeEx
Description
Adapts the "String" data type of a tag for transfer to the automation system (AS). The tag of
WinCC data type "String" is converted into the AS data type "Array of byte". The result is written
to a tag.
By contrast to the Encode system function, you can define the Line break parameter. Using
the Line break parameter you can delete line breaks or replace these with predefined
characters.
Use in the function list
EncodeEx (Byte array, String , Encode , Line break)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1482 System Manual, 08/2011,
Use in user-defined functions
EncodeEx (Byte_array, String, Encoding, Line_break)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Byte array
The tag that contains the converted value.
Note
The byte array must be twice the size of the string length +2. If the string has a length of 120
characters, the byte array must contain 242 array elements.
Characters are either truncated or not converted if the size is insufficient.
String
The tag of data type "String" that is converted.
Encode
0 (hmiEncodeUTF16LE) - String is encoded in UTF16LE (Unicode 16 Little Endian).
Line break
All line breaks are either deleted or replaced with predefined characters. Do not replace line
breaks if set as the default value.
0 (replace with "\r\n' (0x000D, 0x000A)) - the line break is replaced with "\r\n".
1 (replace with "\n' (0x000A)) - the line break is replaced with "\n".
2 (do not replace) - the line break is not replaced.
3 (remove line breaks) - the line breaks are removed.
See also
Availability for specific devices of system functions (Page 1262)
ExportDataRecords
Description
Exports one or all data records of a recipe to a CSV file.
One file is created per recipe.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1483
Use in the function list
ExportDataRecords (Recipe number/name, Data record number/name, File name, Overwrite,
Output status message, Processing status)
Use in user-defined functions
ExportDataRecords (Recipe_number/name,Data_record number/name, File_name,
Overwrite, Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which the data records are exported. Specify "0" if recipe
data records are to be exported from all available recipes.
File name
Name of the CSV file to which the recipe data records are exported. Enter the file location and
the file extension (*.csv), for example, "C:\TEMP\Orange.csv".
Note
Storage of the CSV file
If a storage card is used as storage location, specify the storage location as follows:
"\StorageCard\<File name>".
If you only enter one file name and no path, the file will be saved in a system directory,
for example, "C:\Documents and Settings\[User]".
When only one path for the export is specified, the file name is automatically created from
the respective recipe name. It is a requirement that the folder "D:\Temp\", for example,
has been created. If the folder "D:\Temp" has not been created, the folder name will be
used as the prefix of the file name, Temp_Recipe names.csv.
Data record number/name
Number or name of the recipe data record to be exported. Specify "0" if all recipe data records
are to be exported.
Overwrite
Determines whether an existing CSV file with the same name is overwritten:
0 (hmiOverwriteForbidden) = No: CSV file will not be overwritten. The export process will not
be carried out.
1 (hmiOverwriteAlways) = Yes: CSV file is overwritten without a prompt for confirmation.
2 (hmiOverwriteWithPrompting) = With confirmation: CSV file is not overwritten until confirmed.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1484 System Manual, 08/2011,
Output status message
Determines whether a status message is output after the export:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for
example, to delay execution of other system functions until this system function has been
successfully completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Export format of the recipe data records
If ".csv" is chosen as a file extension for the export file, then only valid characters from the
ANSI character set will be supported. This also applies to separators in decimal numbers and
list elements. The separators used are defined in the country/regional settings of the operating
system of the exporting computer.
You may also set "Unicode text" (".txt") format for the export file. This file format supports the
WinCC and WinCC Runtime character set. Again, the separators used are specified in the
country/regional settings of the operating system of the exporting computer. This file format
always uses tab separators in list elements.
The corresponding file import function also supports the ".csv" and ".txt" (Unicode) file
formats.
Application example
You want to export all data records using a key.
Notes on configuring
Configure the "ExportDataRecords" system function on the "Press" event for the desired key.
Transfer the following parameters:
Recipe number/name = 1
Data record number/name = 0
File name = c:\temp\orange.csv
Overwrite = 1
Output status message = 1
Tags can also be specified in place of the constants. Depending on the configuration, the
operator can enter the desired values in the I/O field or read from the PLC. In this way, the
operator can determine which recipe data records are exported.
Procedure on HMI device
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1485
As soon as the key is activated, the system function is triggered. The constants or tags are
evaluated. All data records of Recipe 1 are exported to the orange.csv file. If the file already
exists, it will be overwritten.
After exporting the data records, a system message is output.
See also
Availability for specific devices of system functions (Page 1262)
ExportDataRecordsWithChecksum
Description
Exports one or all data records of a recipe to a CSV file and generates an incremental
checksum for each line in the file.
One file is created per recipe.
Use in the function list
ExportDataRecordsWithChecksum (Recipe number/name, Data record number/name, File
name, Overwrite, Output status message, Processing status)
Use in user-defined functions
ExportDataRecordsWithChecksum (Recipe_number/name, Data_record number/name,
File_name, Overwrite, Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which the data records are exported. Specify "0" if recipe
data records are to be exported from all available recipes.
File name
Name of the CSV file to which the recipe data records are exported. Enter the file location and
the file extension (*.CSV) e.g. "C:\TEMP\Orange.CSV".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1486 System Manual, 08/2011,
Note
Storage of the csv file
If a storage card is used as storage location, specify the storage location as follows:
"\StorageCard\<File name>".
If you define only a file name without specifying a path, the file is saved to the directory
from which Runtime was started. If write access to this directory is not enabled in the
Windows 7 operating system, the file is saved to the "VirtualStore" folder of the user
directory.
When only one path for the export is specified, the file name is automatically created from
the respective recipe name. This requires, for example, that the directory "D:\Temp\" has
been created. If the directory "D:\Temp" does not exist, the directory name is used as the
prefix for the file name, Temp_Recipe names.csv.
Data record number/name
Number or name of the recipe data record to be exported. Specify "0" if all recipe data records
are to be exported.
Overwrite
Determines whether an existing CSV file with the same name is overwritten:
0 (hmiOverwriteForbidden) = No: CSV file will not be overwritten. The export process will not
be carried out.
1 (hmiOverwriteAlways) = Yes: CSV file is overwritten without a prompt for confirmation.
2 (hmiOverwriteWithConfirmation) = With confirmation: CSV file is not overwritten until
confirmed.
Output status message
Determines whether a status message is output after the export:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Export format of the recipe data records
If ".csv" is chosen as a file extension for the export file, then only valid characters from the
ANSI character set will be supported. This also applies to separators in decimal numbers and
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1487
list elements. The separators used are defined in the country/regional settings of the operating
system of the exporting computer.
You may also set "Unicode text" (".txt") format for the export file. This file format supports the
WinCC and WinCC Runtime character set. Again, the separators used are specified in the
country/regional settings of the operating system of the exporting computer. This file format
always uses tab separators in list elements.
The corresponding file import function also supports the ".csv" and ".txt" (Unicode) file formats.
Application example
Using a key, you want to export all data records and assign a checksum.
Notes on configuring
Configure the "ExportDataRecordsWithChecksum" system function on the "Press" event for
the desired key. Transfer the following parameters:
Recipe number/name = 1
Data record number/name = 0
File name = c:\temp\orange.csv
Overwrite = 1
Output status message = 1
Tags can also be specified in place of the constants. Depending on the configuration, the
operator can enter the desired values in the I/O field or read from the PLC. In this way, the
operator can determine which recipe data records are exported.
Procedure on HMI device
As soon as the key is activated, the system function is triggered. The constants or tags are
evaluated. All data records of Recipe 1 are exported to the orange.csv file and assigned
checksums. If the file already exists, it will be overwritten.
After exporting the data records, a system message is output.
See also
Availability for specific devices of system functions (Page 1262)
ExportImportUserAdministration
Description
Exports all users of the user administration of the currently active project to the given file or
imports the users from the given file into the currently active project.
Users, their passwords and rights are saved in the user administration.
All users are overwritten when importing. The imported users are valid immediately.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1488 System Manual, 08/2011,
Use in the function list
ExportImportUserAdministration (File name, Direction)
Use in user-defined functions
ExportImportUserAdministration (File_name, Direction)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
File name
Name of the file which contains the passwords or to which the passwords are written. Enter
the file location and the file extension (*.txt), for example, "C:\TEMP\Passwords.txt".
Note
If a storage card is used as file location, specify the file location as follows: "\StorageCard
\<File name>".
Direction
Specifies whether passwords are exported or imported:
0 (hmiExport) = Export: Passwords are exported.
1 (hmiImport) = Import: Passwords are imported.
See also
Availability for specific devices of system functions (Page 1262)
GetBrightness
Description
Reads the value of the brightness.
Use in the function list
GetBrightness (Brightness)
Use in user-defined functions
GetBrightness (Brightness)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1489
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Brightness
The tag to which the value is written.
See also
Availability for specific devices of system functions (Page 1262)
GetDataRecordFromPLC
Description
Transfers the given recipe data record from the PLC to the memory medium of the HMI
device.
Use in the function list
GetDataRecordFromPLC (Recipe number/name, Data record number/name, Overwrite,
Output status message, Processing status)
Use in user-defined functions
GetDataRecordFromPLC (Recipe_number/name, Data_record_number/name, Overwrite,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which recipe data records are transferred.
Data record number/name
Number or name of the recipe data record which is transferred from the PLC to the data medium
of the HMI device.
Overwrite
Determines whether an existing recipe data record with the same name is overwritten:
0 (hmiOverwriteForbidden) = No: Recipe data record is not overwritten. The transfer process
will not be carried out.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1490 System Manual, 08/2011,
1 (hmiOverwriteAlways) = Yes: Recipe data record is overwritten without prompting.
2 (hmiOverwriteWithPrompting) = With confirmation: Recipe data record is not overwritten until
confirmed.
Output status message
Determines whether a status message is output after the transfer:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Application example
You want to transfer a data record from the PLC to the data medium of the HMI device using
a key.
Notes on configuring
Configure the "GetDataRecordFromPLC" system function on the "Press" event for the desired
key. Transfer the following parameters:
Recipe number/name = 1
Data record number/name = 1
Overwrite = 1
Output status message = 1
Tags can also be specified in place of the constants. Depending on the configuration, the
operator can enter the desired values in the I/O field or read from the PLC. In this way, the
operator can determine which recipe data record is transferred from the PLC.
Procedure on HMI device
As soon as the key is activated, the system function is triggered. The constants or tags are
evaluated and the first data record of Recipe 1 is transferred from the PLC to the data medium
of the HMI device. If the recipe data record already exists, it will be overwritten.
A system message is output after the transfer.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1491
GetDataRecordName
Description
Writes the name of the given recipe and recipe data record to the given tags.
Note
If the recipe or the recipe data record do not exist, wildcards ("###") are written to the tags.
Use in the function list
GetDataRecordName (Recipe number, Data record number, Recipe name, Data record name,
Processing status)
Use in user-defined functions
GetDataRecordName (Recipe_number, Data_record_number, Recipe_name,
Data_record_name, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number
Number of the recipe whose name is written to the given tag.
Data record number
Number of the recipe data record whose name is written to the given tag.
Recipe name
The tag to which the recipe name is written. The tag must be of the STRING type.
Data record name
The tag to which the name of the recipe data record is written. The tag must be of the STRING
type.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1492 System Manual, 08/2011,
Application example
You want to output the names of the displayed recipes and the name of the displayed recipe
data record on the HMI device.
Configure the following tags:
"RecNumber" of type INTEGER
"RecDataNumber" of type INTEGER
"RecName" of type STRING
"RecDataName" of type STRING
Configure a recipe view with the tags "RecNumber" for the recipe number and
"RecDataNumber" for the data record number.
Configure the "GetDataRecordName" system function on the "Press" event for a button and
pass the following parameters:
Recipe number: RecNumber
Data record number: RecDataNumber
Recipe name: RecName
Data record name: RecDataName
Configure two output fields and connect these to the "RecName" and "RecDataName" tags.
Select a recipe and a data record number from the recipe view. As soon as the button is
activated, the system function is triggered and the name of the recipe and the recipe data
record are displayed in both output fields.
See also
Availability for specific devices of system functions (Page 1262)
GetDataRecordTagsFromPLC
Description
Transfers the values of the recipe data record, which is loaded in the PLC, to the recipe tag.
This system function is used, for example, during teach-in mode on a machine.
Use in the function list
GetDataRecordTagsFromPLC (Recipe number/name, Processing status)
Use in user-defined functions
GetDataRecordTagsFromPLC (Recipe_number/name, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1493
Parameters
Recipe number/name
Number or name of the recipe data record whose values are written from the PLC to the tags.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
GetGroupNumber
Description
Reads the number of the group to which the user logged on to the HMI device belongs, and
writes it to the given tag.
Use in the function list
GetGroupNumber (Tag)
Use in user-defined functions
GetGroupNumber (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the number of the group is written.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1494 System Manual, 08/2011,
GetPassword
Description
Writes the password of the user currently logged on to the HMI device in the given tag.
Note
Make sure that the value of the given tag is not displayed in another place in the project.
Note
The passwords of SIMATIC Logon users cannot be read.
Use in the function list
GetPassword (Tag)
Use in user-defined functions
GetPassword (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the password is written.
See also
Availability for specific devices of system functions (Page 1262)
GetUserName
Description
Writes the user name of the user currently logged on to the HMI device in the given tag.
If the given tag has a control connection, the user name is also available in the PLC connection.
This system function makes it possible, for example, to implement a user-dependent release
of certain functionalities.
Use in the function list
GetUserName (Tag)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1495
Use in user-defined functions
GetUserName (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the user name is written.
See also
Availability for specific devices of system functions (Page 1262)
GoToEnd
Description
Executes the key function <End> on the HMI device.
This system function is used when the HMI device does not have this functionality by default.
The system function can only be used for the following function keys.
Use in the function list
GoToEnd
Use in user-defined functions
GoToEnd
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1496 System Manual, 08/2011,
GoToHome
Description
Executes the key function <Home> on the HMI device.
This system function is used when the HMI device does not have this functionality by default.
The system function can only be used for the following function keys.
Use in the function list
GoToHome
Use in user-defined functions
GoToHome
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
ImportDataRecords
Description
Imports one or all data records of a recipe from a CSV file.
When a path is specified, all records of the given directory are imported.
Use in the function list
ImportDataRecords (File name, Data record number/name, Overwrite, Output status
message, Processing status)
Use in user-defined functions
ImportDataRecords (File_name, Data_record number/name, Overwrite,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1497
Parameters
File name
Name of the CSV file from which the recipe data records are imported. Enter the file location
and the file extension (*.csv), for example "C:\TEMP\Orange.csv".
Note
If a storage card is used as file location, specify the file location as follows: "\StorageCard
\<File name>".
Data record number/name
Number or name of the recipe data record to be imported. Specify "0" if all recipe data records
are to be imported.
Overwrite
Determines whether existing recipe data records are to be overwritten:
0 (hmiOverwriteForbidden) = No: Recipe data records are not overwritten. The import process
will not be carried out.
1 (hmiOverwriteAlways) = Yes: Recipe data records are overwritten without prompting.
2 (hmiOverwriteWithPrompting) = With confirmation: Recipe data records are not overwritten
until confirmed.
Output status message
Determines whether a status message is output after the import:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1498 System Manual, 08/2011,
Configurable objects
Object Event
Tag Value change
High limit violated
Low limit violated
Function key (global) Release
Press
Function key (local) Release
Press
Screen Loaded
Cleared
Screen object Press
Release
Click
Change (or toggle for switch)
Switch on
Switch off
Enable
Disable
Scheduler Time expired
See also
Availability for specific devices of system functions (Page 1262)
ImportDataRecordsWithChecksum
Description
Imports one or all data records of a recipe from a CSV file with a checksum and verifies the
checksum.
Use in the function list
ImportDataRecordsWithChecksum (File name, Data record number/name, Overwrite, Output
status message, Processing status, verify checksum)
Use in user-defined functions
ImportDataRecordsWithChecksum (File_name, Data_record number/name, Overwrite,
Output_status_message, Processing_status, Verify_Checksum)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1499
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
File name
Name of the CSV file from which the recipe data records are imported.
If you specify a directory instead of an individual CSV file, all files in the specified directory will
be imported.
Note
If a storage card is used as file location, specify the file location as follows: "\StorageCard
\<File name>".
Data record number/name
Number or name of the recipe data record to be imported. Specify "0" if all recipe data records
are to be imported.
Overwrite
Determines whether existing recipe data records are to be overwritten:
0 (hmiOverwriteForbidden) = No: Recipe data records are not overwritten. The import process
will not be carried out.
1 (hmiOverwriteAlways) = Yes: Recipe data records are overwritten without prompting.
2 (hmiOverwriteWithConfirmation) = With confirmation: Recipe data records are not
overwritten until confirmed.
Output status message
Determines whether a status message is output after the import:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions, until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Verify checksum
Determines if the checksum should be verified during import:
0 (hmiFalse) = No: Checksum is not verified.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1500 System Manual, 08/2011,
1 (hmiTrue) = Yes: Checksum is verified.
See also
Availability for specific devices of system functions (Page 1262)
IncreaseTag
Description
Adds the given value to the value of the tags.
X = X + a
Note
The system function uses the same tag as input and output values. When this system function
is used to convert a value, help tags must be used. The auxiliary tags can be assigned to the
tag value with the "SetTag" system function.
If you configure the system function on the events of an alarm and the tag is not being used
in the current screen, it is not ensured that the actual value of the tags is being used in the
PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode.
Use in the function list
IncreaseTag (Tag, Value)
Use in user-defined functions
IncreaseTag (Tag, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the given value is added.
Value
The value which is added.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1501
InverseLinearScaling
Description
Assigns a value to the tag X, which is calculated from the value of the given tag Y using the
linear function X = (Y - b) / a.
The tags X and Y must not be identical. This system function is the inverse of the
"LinearScaling" system function.
Note
The tags X and Y must not be identical. If a tag is to be converted into itself, a auxiliary tag
must be used.
The "SetTag" system function can be used to assign the value of the tags to be converted to
the auxiliary tags.
Use in the function list
InvertLinearScaling (X, Y, b, a)
Use in user-defined functions
InverseLinearScaling (X, Y, b, a)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
X
The tag which is assigned the value calculated from the linear equation.
Y
The tag whose value is used for the calculation.
b
The value which is subtracted.
a
The value through which is divided.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1502 System Manual, 08/2011,
InvertBit
Description
Inverts the value of the given tag of the "Bool" type:
If the tag has the value of 1 (TRUE), it will be set to 0 (FALSE).
If the tag has the value of 0 (FALSE), it will be set to 1 (TRUE).
Use in the function list
InvertBit (Tag)
Use in user-defined functions
InvertBit (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag whose bit is set.
See also
Availability for specific devices of system functions (Page 1262)
InvertBitInTag
Description
Inverts a bit in the given tag:
If the bit in the tag has the value of 1 (TRUE), it will be set to 0 (FALSE).
If the bit in the tag has the value of 0 (FALSE), it will be set to 1 (TRUE).
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC.
Note
If the PLC supports BOOL tags, do not use this system function. Use the "InvertBit" system
function instead.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1503
Use in the function list
InvertBitInTag (Tag, Bit)
Use in user-defined functions
InvertBitInTag (Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag in which the given bit is set.
Bit
The number of the bit that is set.
When this system function is used in a user-defined function, the bits in a tag are counted from
right to left. The counting begins with 0.
See also
Availability for specific devices of system functions (Page 1262)
LinearScaling
Description
Assigns a value to the tag Y, which is calculated from the value of the given tag X using the
linear function Y= (a *X) + b.
The inverse of this function is the "InvertLinearScaling" system function.
Note
The tags X and Y must not be identical. If a tag is to be converted into itself, a auxiliary tag
must be used.
The "SetTag" system function can be used to assign the value of the tags to be converted to
the auxiliary tags.
Use in the function list
LinearScaling (Y, a, X, b)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1504 System Manual, 08/2011,
Use in user-defined functions
LinearScaling (Y, a, X, b)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Y
The tag which is assigned the value calculated from the linear equation.
a
The value with which is multiplied.
X
The tag whose value is used for the calculation.
b
The value which is added.
See also
Availability for specific devices of system functions (Page 1262)
LoadDataRecord
Description
Loads the given recipe data record from the memory medium of the HMI device in the recipe
tags. This system function is used, for example, to display a recipe data record in the recipe
screen.
Activate the "Synchronize recipe view and recipe tags" option in the synchronization settings
of the recipe. If this option is deactivated, the system function has no effect.
Use in the function list
LoadDataRecord (Recipe number/name, Data record number/name, Processing status)
Use in user-defined functions
LoadDataRecord (Recipe_number/name, Data_record_number/name, Confirmation,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1505
Parameters
Recipe number/name
Number or name of the recipe from which a recipe data record is loaded.
Data record number/name
Number or name of the recipe data record to be loaded.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
LogOff
Description
Logs off the current user on the HMI device.
Use in the function list
Logoff
Use in user-defined functions
Logoff
Can be used if the configured device supports user-defined functions. For additional
information, refer to "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1506 System Manual, 08/2011,
Logon
Description
Logs on the current user on the HMI device.
Use in the function list
Logon (Password, User name)
Use in user-defined functions
Logon (Password, User_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Password
The tag from which the password for the user logging on is read.
If the user is logged on, the password in the tag is deleted.
User name
The tag from which the user name for the user logging on is read.
See also
Availability for specific devices of system functions (Page 1262)
LookupText
Description
Identifies an entry from a text list. The result depends on the value and on the selected runtime
language. The result is saved to a tag of data type "String".
Use in the function list
LookupText (Output text, Value, Language, Text list)
Use in user-defined functions
LookupText(Output_text, Index, Language, Text_list)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1507
Parameters
Output text
The tag to which the result is written.
Value
The tag that defines the value of the list entry.
Language
Defines the runtime language in which the list entry is identified.
Tag
The tag that contains the language. Enter the runtime language as decimal value of the
country ID, for example, 1031 for German - Standard, 1033 for English - USA. Details are
available in the VBScript basics, "Locale identifier (LCID) diagram".
Runtime language
Language code as per VBScript reference, for example, "de-DE" for German (Germany)
or "en-US" for English (United States of America). The selection depends on the activated
runtime languages.
Text list
Defines the text list. The list entry is read from the text list.
See also
Availability for specific devices of system functions (Page 1262)
NotifyUserAction
Description
This system function is used to log user actions that are not automatically logged in the audit
trail. You can also use this system function to require the user to enter an acknowledgment or
an electronic signature and a comment for the operator action. Requirement for the use of the
system function is that the GMP-compliant configuration is activated under "Runtime settings".
If you use the "NotifyUserAction" system function in a function, the debugger may open if you
cancel your input by clicking "Cancel". To compensate for this reaction, you can use the "On
Error Resume Next" statement in a function. With this setting, the script executes the next
statement when a runtime error is detected. If you use the "On Error Resume Next" statement,
output of system events is also suppressed.
Use in the function list
NotifyUserAction (Confirmation type, Mandatory commenting, Category, Object name,
Description)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1508 System Manual, 08/2011,
Use in user-defined functions
NotifyUserAction (Confirmation_type, Mandatory_commenting, Category, Object_name,
Description)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Confirmation type
Establishes how the action must be confirmed
0 = (None): No confirmation required, an entry is created in the audit trail
1 = (Acknowledgement): Acknowledgement, the user must acknowledge the action; an entry
is created in the audit trail
2 = (Digital Signature): Electronic signature, a dialog window opens in which the user must
enter his electronic signature - an entry is created in the audit trail
Mandatory commenting
Establishes if the user has to enter a comment. The comment is logged in the audit trail.
0 = (True): True; a dialog window opens in which the user must enter a comment
1 = (False): False; no mandatory commenting
Category
Category or class name of the modified object
Object name
Name of the modified object
Description
Text which describes the archiving user action.
See also
Availability for specific devices of system functions (Page 1262)
OpenAllLogs
Description
Reestablishes the connection between WinCC and the logs. Logging can be continued.
Note
Run the "StartLogging" system function in order to restart logging.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1509
Use in the function list
OpenAllLogs
Use in user-defined functions
OpenAllLogs
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Application example
You are in runtime and want to change the data medium on which the process values are
logged.
Notes on configuring
Configure the "StopLogging" and "CloseAllLogs" system functions on the "Close Archive"
button.
Configure the "OpenAllLogs" and "StartLogging" system functions on the "Open Archive"
button.
As parameter transfer the respective name of the log that is to be stopped and started.
Procedure on HMI device
When the button "Close Archive" is pressed, the specified log is stopped and all open logs are
closed. The data medium can be changed. You open all logs with the "Open Archive" button.
Logging will be continued in the specified log.
See also
Availability for specific devices of system functions (Page 1262)
OpenCommandPrompt
Description
Opens a Windows system prompt.
This function is used, e.g., to copy files or to call up another application.
Use in the function list
OpenCommandPrompt
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1510 System Manual, 08/2011,
Use in user-defined functions
OpenCommandPrompt
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
OpenControlPanel
Description
Opens a window which displays the Windows CE control panel. You cannot use this system
function on a PC.
This system function enables you to set the following on the Windows CE-based HMI device:
Select printer
Select transfer properties
Configure screen saver
Configure flash memory
Note
No backup or restore during Runtime
Backup and restore functions may only be executed if Runtime has been terminated.
Otherwise, this could result in undesired effects, such as display errors.
Use in the function list
OpenControlPanel
Use in user-defined functions
OpenControlPanel
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1511
See also
Availability for specific devices of system functions (Page 1262)
OpenInternetExplorer
Description
Opens the Internet Explorer on the HMI device.
If the Internet Explorer is already open, it will be closed and reopened when you call the system
function.
Note
The Internet Explorer saves data temporarily in the DRAM file system of the HMI device, e.g.
the last web sites that were be called up.
This data can be saved using the "BackupRAMFileSystem" system function so that it is still
available when the HMI device is restarted.
Use in the function list
OpenInternetExplorer (Start page)
Use in user-defined functions
OpenInternetExplorer(Start_page)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Start page
The page which is loaded when Internet Explorer is started, e.g. "www.siemens.com".
See also
Availability for specific devices of system functions (Page 1262)
OpenScreenKeyboard
Description
Hides or shows the screen keyboard.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1512 System Manual, 08/2011,
The screen keyboard remains open until the screen keyboard is explicitly closed. In this way,
the screen keyboard can also be used in other applications.
Use in the function list
OpenScreenKeyboard (Display mode)
Use in user-defined functions
OpenScreenKeyboard (Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Display mode
Specifies whether the window is opened minimized or maximized with the screen keyboard:
0 (hmiScreenKeyboardMinimized) = Minimized
1 (hmiScreenKeyboardMaximized) = Maximized
See also
Availability for specific devices of system functions (Page 1262)
OpenTaskManager
Description
Shows the task manager.
The task manager allows changing to other open applications on the HMI device.
Note
The appearance of the task manager depends on the operating system installed.
Use in the function list
OpenTaskManager
Use in user-defined functions
OpenTaskManager
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1513
Can be used if the configured device supports user-defined scripts. Additional information is
available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
See also
Availability for specific devices of system functions (Page 1262)
PageDown
Description
Executes the key function <Pagedown> on the HMI device.
This system function can only be used for function keys.
Use in the function list
PageDown
Use in user-defined functions
PageDown
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
-
See also
Availability for specific devices of system functions (Page 1262)
PageUp
Description
Executes the key function <PageUp> on the HMI device.
This system function can only be used for function keys and tasks with a time trigger.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1514 System Manual, 08/2011,
Use in the function list
PageUp
Use in user-defined functions
PageUp
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
-
See also
Availability for specific devices of system functions (Page 1262)
PrintReport
Description
Prints the given report from the printer which is connected to the HMI device. The report is
printed in the language which is set on the HMI device.
Note
If runtime is closed whilst log data are being printed using the system function, the report will
cease to be supplied with data as soon as runtime stops.
Use in the function list
PrintReport (Report)
Use in user-defined functions
PrintReport (Report)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1515
Parameters
Protocol
Name of the report to be printed.
Note
If you have set up via the "Function list" dialog box a new report for the "PrintReport" function,
when compiling, the following warning appears: "The report "Report_1" has no printed pages."
In order to remedy the warning, open the "Report_1" via the project view and recompile the
project.
See also
Availability for specific devices of system functions (Page 1262)
PrintScreen
Description
Prints the screen currently being displayed on the HMI device from the printer which is
connected to the HMI device.
Opened windows are also printed.
Note
The printer settings are taken over from the current settings in the Windows operation system.
Use in the function list
PrintScreen
Use in user-defined functions
PrintScreen
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
--
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1516 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
ResetBit
Description
Sets the value of a "Bool" type tag to 0 (FALSE).
Use in the function list
ResetBit (Tag)
Use in user-defined functions
ResetBit (Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The BOOL type tag which is set to 0 (FALSE).
See also
Availability for specific devices of system functions (Page 1262)
ResetBitInTag
Description
Sets a bit in the specified tag to 0 (FALSE).
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC.
Note
If the PLC supports BOOL tags, do not use this system function. Use the "ResetBit" system
function instead.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1517
Use in the function list
ResetBitInTag (Tag, Bit)
Use in user-defined functions
ResetBitInTag (Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag in which a bit is set to 0 (FALSE).
Bit
The number of the bit that is set to 0 (FALSE).
When this system function is used in a user-defined function, the bits in the specified tag will
be counted from right to left independent of the PLC used. The counting begins with 0.
See also
Availability for specific devices of system functions (Page 1262)
SafelyRemoveHardware
Description
Checks whether there is read or write access to the external storage medium. If there is no
access, the external storage medium can be removed without data loss.
Use in the function list
SafelyRemoveHardware(Path, Result)
Use in user-defined functions
SafelyRemoveHardware(Path, Result)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Path
Path of storage medium , e.g. \Storage Card USB\
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1518 System Manual, 08/2011,
Result
The tag in which the result is entered.
TRUE : The storage medium can be removed safely. A corresponding system message will
be issued.
FALSE : The storage medium can be removed safely. A corresponding system message will
be issued.
See also
Availability for specific devices of system functions (Page 1262)
SaveDataRecord
Description
Saves the current values of the recipe tags as data record to the memory medium of the HMI
device.
This system function is used, for example, to save a recipe data record in the recipe screen.
Use in the function list
SaveDataRecord (Recipe number/name, Data record number/name, Overwrite, Output status
message, Processing status)
Use in user-defined functions
SaveDataRecord(Recipe_number/name, Data_record_number/name, Overwrite,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe to which a recipe data record is saved.
Data record number/name
Number or name of the recipe data record to be saved.
Overwrite
Specifies whether an existing data record is overwritten:
0 (hmiOverwriteForbidden) = No: The recipe data record is not overwritten, the data record is
not saved.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1519
1 (hmiOverwriteAlways) = Yes: The recipe data record is overwritten without a prompt for
confirmation.
2 (hmiOverwriteWithPrompting) = With confirmation: The recipe data record is overwritten only
with confirmation by the user.
Output status message
Determines whether a status report is output after saving:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
SendEMail
Description
Sends an e-mail from the HMI device to the given addressee.
This system function is used, for example, when, in the case of service, the alarm is to be
passed on directly to the service technician.
Note
To send alarms as e-mails, the HMI system must have an e-mail client at its disposal.
Use in the function list
SendEMail (Address, Subject, Text, Return address)
Use in user-defined functions
SendEMail (Address, Subject, Text, Return_address)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1520 System Manual, 08/2011,
Parameters
Address
The e-mail address of the addressee.
Subject
The subject line of the e-mail.
Text
The text sent in the e-mail.
Return address
The e-mail address to which the addressee of this e-mail should send the reply.
See also
Availability for specific devices of system functions (Page 1262)
SetAcousticSignal
Description
Configures the acoustic feedback of touch screen operation on the HMI device.
Note
The configuration that was set at Switch off is reestablished when restarting the HMI device.
Use in the function list
SetAcousticSignal (Volume)
Use in user-defined functions
SetAcousticSignal (Volume)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Volume
Determines whether and how loud an acoustic signal is emitted:
-1 (hmiToggle) = Toggle: Toggles the emission of the acoustic signal as follows: Muted > Quiet
> Loud.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1521
0 (hmiMuted) = Mute: no acoustic signal
1 (hmiQuiet) = Quiet: quiet acoustic signal
2 (hmiLoud) = Loud: loud acoustic signal
See also
Availability for specific devices of system functions (Page 1262)
SetAlarmReportMode
Description
Switches the automatic reporting of alarms on the printer on or off.
Use in the function list
SetAlarmReportMode (Mode)
Use in user-defined functions
SetAlarmReportMode(Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether alarms are reported automatically on the printer:
0 (hmiDisablePrinting) = Reporting off: Alarms are not printed automatically.
1 (hmiEnablePrinting) = Reporting On: Alarms are printed automatically.
-1 (hmiToggle) = Toggle: Toggles between the two modes.
See also
Availability for specific devices of system functions (Page 1262)
SetBit
Description
Sets the value of a "Bool" type tag to 1 (TRUE).
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1522 System Manual, 08/2011,
Use in the function list
SetBit (Tag)
Use in user-defined functions
SetBit(Tag)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The BOOL type tag which is set to 1 (TRUE).
See also
Availability for specific devices of system functions (Page 1262)
SetBitInTag
Description
Sets a bit in the given tag to 1 (TRUE).
After changing the given bit, the system function transfers the entire tag back to the PLC. It is
not checked whether other bits in the tags have changed in the meantime. Operator and PLC
have read-only access to the indicated tag until it is transferred back to the PLC.
Note
If the PLC supports BOOL tags, do not use this system function. Use the "SetBit" system
function instead.
Use in the function list
SetBitInTag (Tag, Bit)
Use in user-defined functions
SetBitInTag(Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1523
Parameters
Tag
The tag in which a bit is set to 1 (TRUE).
Bit
The number of the bit that is set to 1 (TRUE).
When this system function is used in a user-defined function, the bits in the specified tag will
be counted from right to left independent of the PLC used. The counting begins with 0.
Note
The guaranteed update of the tags used with actual process values is absolutely conditional
in terms of reliable functionality. You should therefore configure the tag in an I/O field or assign
the system function to a screen object, such as a button.
If you have configured a short event such as the activation of an alarm for the system function
you can only access the actual process values by setting the tag for continuous reading.
See also
Availability for specific devices of system functions (Page 1262)
SetBrightness
Description
Determines the brightness of the display.
Note
The configuration that is set in the Control Panel will be reestablished when you restart the
HMI device.
Use in the function list
SetBrightness (value)
Use in user-defined functions
SetBrightness(Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1524 System Manual, 08/2011,
Parameters
Value
New value for the brightness.
See also
Availability for specific devices of system functions (Page 1262)
SetConnectionMode
Description
Connects or disconnects the given connection.
Note
A connection to the PLC cannot be established until the operating mode ONLINE has been
set on the HMI device. Use the "SetDeviceMode" system function for this purpose.
Use in the function list
SetConnectionMode (Mode, Connection)
Use in user-defined functions
SetConnectionMode(Mode, Connection)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether a connection to the PLC is established or disconnected:
0 (hmiOnline) = Online: Connection is established.
1 (hmiOffline) = Offline: Connection is disconnected.
Connection
The PLC to which the HMI device is connected. You specify the name of the PLC in the
connection editor.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1525
Multiple use of the system function in a user-defined function
If you use the "SetConnectionMode" system function for different connections, it may be
possible that not all system functions are executed correctly. Proceed as follows to prevent
this situation:
1. Create a "BOOL" type tag with the start value "0".
2. Configure the "SetConnectionMode" system function on the "Value change" event of the
HMI tags. If you want to disconnect three connections, for example, you must configure the
system function three times.
3. In the user-defined function, apply the "InvertBit" system function to the HMI tag.
Application example
Two typical application examples for this system function are as follows:
Test
As long as no PLC is connected to the HMI device, no error messages will be output during
the test on the HMI device. If the HMI device is connected to a PLC, the connection to the
PLC can be established by pressing a key.
Start up
Several PLCs are to be configured for a system. At first, all PLCs except one are configured
"Offline". After start up of the first PLC, the connection to each of the other PLCs is
established by pressing a key. In this way, the other PLCs are started up one after another.
See also
Availability for specific devices of system functions (Page 1262)
SetDataRecordTagsToPLC
Description
Transfers the values of the recipe tags to the PLC. The recipe tags contain the values of the
data record which is displayed on the HMI device.
Use in the function list
SetDataRecordTagsToPLC (Recipe number/name, Processing status)
Use in user-defined functions
SetDataRecordTagsToPLC (Recipe_ number/name, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1526 System Manual, 08/2011,
Parameters
Recipe number/name
Number or name of the recipe from which recipe data record is transferred to the PLC.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
SetDataRecordToPLC
Description
Transfers the given recipe data record directly from the data medium of the HMI device to the
PLC with which the HMI device is connected.
Note
The values of the recipe data record don't need to be displayed on the HMI device.
Use in the function list
SetDataRecordToPLC (Recipe number/name, Data record number/name, Output status
message, Processing status)
Use in user-defined functions
SetDataRecordToPLC (Recipe_number/name, Data_record_number/name,
Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe from which recipe data record is transferred to the PLC.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1527
Data record number/name
Number or name of the recipe data record to be transferred to the PLC.
Output status message
Determines whether a status message is output after the transfer:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
See also
Availability for specific devices of system functions (Page 1262)
SetDaylightSavingTime
Description
The system function "SetDaylightSavingTime" changes the setting of the HMI device from
daylight saving to standard time and vice versa.
Time settings will take place immediately following system function.
Note
The "SetDaylightSavingTime" system function does not support time zones without daylight
saving time.
Note
Windows 7
The system function "SetDaylightSavingTime" is not supported for PC-based HMI devices
under Windows 7.
Use in the function list
SetDaylightSavingTime (Mode)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1528 System Manual, 08/2011,
Use in user-defined functions
SetDaylightSavingTime(Daylight_saving_time)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether Daylight Saving Time is set on the HMI device:
0 = Daylight Saving Time is not activated.
1 = Daylight Saving Time is activated
Tag
A variable of the type Bool or Uint.
See also
Availability for specific devices of system functions (Page 1262)
SetDeviceMode
Description
Toggles the operating mode on the HMI device. The following types of operation are possible:
"Online", "Offline" and "Load".
Use in the function list
SetDeviceMode (Operating mode)
Use in user-defined functions
SetDeviceMode (Operating_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Operating mode
Determines the operating mode of the HMI device:
0 (hmiOnline) = Online: The connection to the PLC is established.
1 (hmiOffline) = Offline: The connection to the PLC is disconnected.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1529
2 (hmiTransfer) = load: A project can be transferred from the configuration computer to the
HMI device.
Note
If you use a PC as an HMI device, the runtime software will be exited when you change
operating mode after "Load".
See also
Availability for specific devices of system functions (Page 1262)
SetDisplayMode
Description
Changes the settings of the screen in which the runtime software runs.
The runtime software runs in full-screen mode as default. The Windows task switch is disabled.
Use in the function list
SetDisplayMode (Display mode)
Use in user-defined functions
SetDisplayMode (Display mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Display mode
Determines the settings for the screen in which the runtime software runs.
1 (hmiScreenFull): Full-screen: Title bar of the screen is not visible
2 (hmiScreenMaximized): Maximized
3 (hmiScreenRestore): Restore: The last used screen setting is used. This display mode can
only be used when the window is displayed minimized or maximized.
4 (hmiScreenMinimized): Minimized
5 (hmiScreenAutoAdjust): Automatic: The size of the window is set so that all screen objects
in it will be visible.
6 (hmiScreenOnTop): On top; either the window appears in the foreground or the program
icon associated with the window flashes on the taskbar depending on the Windows setting.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1530 System Manual, 08/2011,
The setting can be changed in the Windows configuration and applies to all Windows
applications.
See also
Availability for specific devices of system functions (Page 1262)
SetLanguage
Description
Toggles the language on the HMI device. All configured text and system events are displayed
on the HMI device in the newly set language.
Use in the function list
SetLanguage (Language)
Use in user-defined functions
SetLanguage(Language)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Language
Determines which language is set on the HMI device. The following specifications are possible:
-1 (hmiToggle) = Toggle: Changes to the next language. The sequence is determined
during configuration in the "Project languages" editor.
Number you have defined under "Languages and fonts" in the "Runtime Settings" editor.
Changes to the language with the given number.
Language you have defined under "Languages and fonts" in the "Runtime Settings" editor.
Language abbreviation in accordance with the VBScript5 reference: This changes to the
language corresponding to the specified language code, e.g. "de-DE" for German
(Germany) or "en-US" for English (United States).
An overview of the language abbreviations is available in the basic information of VBScript
under the topic "Area diagram-ID (LCID) Diagram".
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1531
SetRecipeTags
Description
Changes the status of the recipe tags from "Online" to "Offline" and vice versa.
This system function is used, for example, when recipe data record values are fine tuned when
starting up a machine.
Use in the function list
SetRecipeTags (Recipe number/name, Status, Output status message, Processing status)
Use in user-defined functions
SetRecipeTags(Recipe_number/name, Status, Output_status_message, Processing_status)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Recipe number/name
Number or name of the recipe in which the recipe data record is saved.
Status
Determines the status of the recipe tags:
0 (hmiOnline) = Online: Value changes of the recipe tags are transferred immediately to the
PLC connected to the HMI device.
1 (hmiOffline) = Offline: Value changes to the recipe tags are only transferred to the PLC
connected to the HMI device when, for example, the "SetDataRecordTagsToPLC" system
function is executed.
Output status message
Determines whether a status report is output after saving:
0 (hmiOff) = Off: Status message is not output.
1 (hmiOn) = On: Status message is output.
Processing status
Returns the processing status of the system function. You can use the return value, for example
to delay execution of other system functions until this system function has been successfully
completed.
2 = System function is being performed.
4 = System function was successfully completed.
12 = System function was not performed because an error has occurred.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1532 System Manual, 08/2011,
See also
Availability for specific devices of system functions (Page 1262)
SetScreenKeyboardMode
Description
Enables or disables the automatic display of the screen keyboard on the HMI device.
This system function is also used to prevent the display of the screen keyboard, e.g. because
an external keyboard is connected to the HMI device.
Note
To enable the "SetScreenKeyboardMode" ("SetScreenKeyboardMode") system function on
an HMI other than a Touch Panel device, set the "Use on-screen keyboard" check box in the
"Runtime settings" dialog of the device settings.
Use in the function list
SetScreenKeyboardMode (Mode)
Use in user-defined functions
SetScreenKeyboardMode(Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether the screen keyboard is hidden or shown:
0 (hmiOff) = Off: Screen keyboard is hidden
1 (hmiOn) = On: Screen keyboard is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1533
SetTag
Description
Assigns a new value to the given tag.
Note
This system function can be used to assign strings and numbers, depending on the type of
tag.
Use in the function list
SetTag (Tag, Value)
Use in user-defined functions
SetTag(Tag, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Tag
The tag to which the given value is assigned.
Value
The value which the given tag is assigned.
Note
The "SetTag" system function is only executed after a connection has been established.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1534 System Manual, 08/2011,
ShiftAndMask
Description
This system function converts the input bit pattern of the source tags into an output bit pattern
of the target tags. This involves bit shifting and masking.
Note
If the source and target tag have a different number of bits, using the system function in the
target tag can result in a violation of the value range.
Use in the function list
ShiftAndMask (Source tag, Target tag, Bits to shift, Bits to mask)
Use in user-defined functions
ShiftAndMask (Source_tag, Target_tag, Bits_to_shift, Bits_to_mask)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Source tag
The tag includes the input bit pattern. Integer-type tags, e.g. "Byte", "Char", "Int", "UInt", "Long"
and "ULong" are permitted.
Example: The actual value 72 is set at the 16-bit integer source tag: 0000000001001000.
Target tag
The output bit pattern is saved in the tag. Integer type tags, e.g. "Byte", "Char", "Int", "UInt",
"Long" and "ULong" are permitted.
Example: The shifted input bit pattern is multiplied by the bit mask, with bit-by-bit logical AND
operation: 0000000000001001. The resultant decimal value "8" is saved to the target tag.
Please note the following:
The source and target tags have the same number of bits.
The number of bits to shift is less than the number of bits in the source tag and target tag.
Bits to mask does not have more bits than the source tag and the target tag.
Bits to shift
Number of bits by which the input bit pattern is shifted right. A negative value shifts the input
bit pattern to the left.
Example: "Bits to shift" has the value "+3". The input bit pattern is shifted right by three bits
when the system function is called: 0000000000001001.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1535
Bits to the left are padded with "0". Three bits are truncated on the right. The new decimal
value is "9".
Note
The left bit is "1" in a source tag of the data type with negative signed integer. This sign bit
is padded with "0" when the bits are shifted right. The sign changes to "+".
Bits to mask
An integer serves as bit mask. The bit pattern is used to multiply the shifted input bit pattern.
Example: Integer "2478" with the bit pattern "0000100110101110".
You can enter the bit mask in three different ways:
Hexadecimal: First enter the prefix "0h" or "0H", followed by an optional space for better
readability. Then group the bit pattern in blocks of four (0000)(1001)(1010)(1110) and set
each block in hexadecimal code: (0)(9)(A)(E). Only the characters 0-9, A-F, a-f are allowed:
"0h 09AE".
Binary: First enter the prefix "0b" or "0B", followed by an optional space for better readability.
Then group the binary bit pattern into blocks of four 0000 1001 1010 1110 with spaces in
between as a check. Only the characters "0" or "1" are allowed: "0b 0000 1001 1010 1110".
Decimal: Enter the value "2478" directly, without a prefix.
See also
Availability for specific devices of system functions (Page 1262)
ShowAlarmWindow
Description
Hides or shows the alarm window on the HMI device.
Use in the function list
ShowAlarmWindow (Object name, Display mode)
Use in user-defined functions
ShowAlarmWindow(Object_name, Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1536 System Manual, 08/2011,
Parameters
Object name
Name of the alarm view which is hidden or shown.
Display mode
Determines whether the alarm window is hidden or shown:
0 (hmiOff) = Off: Alarm view is hidden
1 (hmiOn) = On: Alarm view is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Availability for specific devices of system functions (Page 1262)
ShowOperatorNotes
Application
Displays the configured tooltip of the selected object.
If the system function is configured on a function key, the tooltip for the screen object that
currently has the focus is displayed. If a tooltip is configured for the screen itself, you can switch
to this text by pressing <Enter> or by double-clicking on the help window.
If the system function is configured on a button, only the tooltip for the current screen is
displayed. If a tooltip is configured on the button itself, initially only the tooltip for the button is
displayed. You can press <Enter> or double-click on the help window to switch to the tooltip
for the current screen.
Note
No other screen object can be used while the help window is open. To use the screen object,
close the help window.
Closing the help window
You can close the help window in the following ways:
Using the keys:
By pressing the <HELP> key again
By pressing the <ESC> key
Using the touch screen:
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1537
By pressing the button
Use in the function list
ShowOperatorNotes (Display mode)
Use in user-defined functions
ShowOperatorNotes (Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Display mode
Determines whether the configured tooltip is hidden or shown:
0 (hmiOff) = Off: Configured tooltip is hidden
1 (hmiOn) = On: Configured tooltip is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Availability for specific devices of system functions (Page 1262)
ShowSoftwareVersion
Description
Hides or shows the version number of the runtime software.
Use this system function if during servicing, for example, you required the version of the runtime
software used.
Use in the function list
ShowSoftwareVersion (Display mode)
Use in user-defined functions
ShowSoftwareVersion(Display_mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1538 System Manual, 08/2011,
Parameters
Display mode
Determines whether the version number is shown:
0 (hmiOff) = Off: Version number is not shown
1 (hmiOn) = On: Version number is shown
-1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Availability for specific devices of system functions (Page 1262)
ShowSystemAlarm
Description
Displays the value of the delivered parameter as a system alarm on the HMI device.
Use in the function list
ShowSystemAlarm (Text/value)
Use in user-defined functions
ShowSystemAlarm (Text/value)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Text/Value
The text or the value, which was output as a system alarm.
See also
Availability for specific devices of system functions (Page 1262)
ShowSystemDiagnosticsWindow
Description
Hides or shows the system diagnostics window on the HMI device. The system diagnostics
window is only available in the global screen for Comfort Panels.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1539
Use in the function list
ShowSystemDiagnosticsWindow (Target Object name)
Use in user-defined functions
ShowSystemDiagnosticsWindow(Target_Object_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Object name
Name of the system diagnostics view which is hidden or shown.
See also
Availability for specific devices of system functions (Page 1262)
StartLogging
Description
Starts the logging of data or alarms in the specified log. The function can also be applied to
audit trails.
You can interrupt logging at runtime using the "StopLogging" system function.
Use in the function list
StartLogging (Log type, Log)
Use in user-defined functions
StartLogging(Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1540 System Manual, 08/2011,
Log
Name of the log which is started.
See also
Availability for specific devices of system functions (Page 1262)
StartNextLog
Description
Stops the logging of data or alarms for the given log.
Logging is continued in the next log of the segmented circular log you configured for the
specified log.
If you did not configure a segmented circular log for the specified log, the system function has
no effect.
Use in the function list
StartNextLog (Log type, Log)
Use in user-defined functions
StartNextLog(Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
Log
Name of the log for which the logging is stopped and continued in the next log.
See also
Availability for specific devices of system functions (Page 1262)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1541
StartProgram
Description
Starts the specified program on the HMI device.
The runtime software continues running in the background. Alarms continue to be output and
data continues to be updated.
When the given application is exited, the screen which was active during the performance of
the system function is displayed on the HMI device.
This system function is used, for example, to edit recipe data records in MS Excel on the HMI
device.
Note
If Windows CE is installed on the HMI device, during the configuration it must be checked
whether the desired application can be started with this system function.
This system function allows all applications to be started which can be started in the "Execute"
dialog of Windows CE.
The application to be started must be installed on the HMI device.
Use in the function list
StartProgram (Program name, Program parameters, Display mode, Wait for program to end)
Use in user-defined functions
StartProgram (Program_name, Program_parameters, Display_mode,
Wait_for_program_to_end)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Program name
Name and path of the program which is started. Upper and lower case are taken into account
in this parameter.
NOTICE
If the path contains spaces, the program can only be started correctly if the path is specified
in inverted commas, e.g. "C:\Program Files\START\start.exe".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1542 System Manual, 08/2011,
Program parameters
The parameters you transfer at the start of the program, for example a file that is opened after
the start of the program.
The description of the necessary parameters is found in the documentation of the program to
be started.
Display mode
Determines how the program window is displayed on the HMI device:
0 (hmiShowNormal) = Normal
1 (hmiShowMinimized) = Minimized
2 (hmiShowMaximized) = Maximized
3 (ShowMinimizedAndInactive) = Minimized and inactive
Wait for program to end
Determines whether there is a change back to the project after the called up program has
ended:
0 (hmiNo) = No: No change to project
1 (hmiYes) = Yes: Change to project
Note
The "Wait for program to end" parameter is only available for Runtime Advanced and Panels.
See also
Availability for specific devices of system functions (Page 1262)
StopLogging
Description
Stops the logging of process values or alarms in the specified log. The function can also be
applied to audit trails.
The "StartLogging" system function is used to resume logging at runtime.
Note
When logging is stopped, a connection between WinCC and the log files or log database still
exists. Use the "CloseAllLogs" system function to disconnect this connection.
Use in the function list
StopLogging (Log type, Log)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1543
Use in user-defined functions
StopLogging (Log_type, Log)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Log type
Determines the type of log:
0 (hmiTagArchive) = Data log
1 (hmiAlarmArchive) = Alarm log
2 (hmiAudittrailArchive) = Audit trail
Log
Name of the log that is stopped.
Application example
You are in runtime and want to change the data medium on which the process values are
logged.
Notes on configuring
Configure the "StopLogging" and "CloseAllLogs" system functions on the "Close Archive"
button.
Configure the "OpenAllLogs" and "StartLogging" system functions on the "Open Archive"
button.
Transfer the name of the log that is to be stopped and started as the parameter.
Procedure on HMI device
When the button "Close Archive" is pressed, the specified log is stopped and all open logs are
closed. The data medium can be changed. The "Open Archive" button opens all logs and
continues logging in the specified log.
See also
Availability for specific devices of system functions (Page 1262)
StopRuntime
Description
Exits the runtime software and thereby the project running on the HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1544 System Manual, 08/2011,
Use in the function list
StopRuntime (Mode)
Use in user-defined functions
StopRuntime(Mode)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Availability for specific devices of system functions (Page 1262)".
Parameters
Mode
Determines whether the operating system is shut down after exiting runtime.
0 (hmiStopRuntime) = Runtime: Operating system is not shut down
1 (hmiStopRuntimeAndOperatingSystem) = Runtime and operating system: The operating
system is shut down (not possible with WinCE)
See also
Availability for specific devices of system functions (Page 1262)
WinACMPGetVersion
Description
Reads out the value of the version number of WinAC MP.
Use in the function list
WinACMPGetVersion (Version, Update)
Use in user-defined functions
WinACMPGetVersion(Version, Action)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Version
The tag that contains the value.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1545
Update
Determines whether the version number is read out:
0 (SwitchOff) = Off: Version number is not read out.
1 (SwitchOn) = On: Version number is read out.
See also
Availability for specific devices of system functions (Page 1262)
WinACMPSetStartAtBoot
Description
Determines whether or not WinAC MP is started automatically after startup of the HMI device.
Use in the function list
WinACMPSetStartAtBoot(StartAtBoot)
Use in user-defined functions
WinACMPSetStartAtBoot (Start at boot)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Start-up characteristics
Defines whether WinAC MP is started automatically.
0 (StartAtBootOff) = Off: WinAC MP is not started on startup of the HMI device.
1 (StartAtBootOn) = On: WinAC MP is started automatically on startup of the HMI device.
See also
Availability for specific devices of system functions (Page 1262)
WinACSetStartMode
Description
Sets the operating mode of WinAC MP after startup of the HMI device.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1546 System Manual, 08/2011,
Use in the function list
WinACSetStartMode (Autostart)
Use in user-defined functions
WinACSetStartMode (Autostart)
Can be used if the configured device supports user-defined functions. Additional information
is available under Availability for specific devices of system functions (Page 1262).
Parameters
Autostart
Defines whether the Autostart function of WinAC MP is activated.
0 (AutoStartOff) = Off: After startup, WinAC MP remains in the STOP operating mode.
1 (AutoStartOn) = On: After startup, WinAC MP changes to the operating mode it was in before
it was closed.
See also
Availability for specific devices of system functions (Page 1262)
VBScript for Windows
VBScript for Windows
VBScript
If you have worked with Visual Basic or Visual Basic for applications, then VBScript will seem
familiar to you. If you do not know Visual Basic and are getting familiar with it, then you will
learn all Visual Basic programming languages at once. The step-by-step guides from Microsoft
Press are a good introduction to programming.
You will find fundamental information on VBScript language elements on the Microsoft
homepage:
http://msdn.microsoft.com/en-us/library/t0aew7h6.aspx (http://msdn.microsoft.com/en-us/
library/t0aew7h6.aspx)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1547
VBScript for Windows CE
VBScript for Windows CE
Attr
Function
This property of the File control returns a number indicating the file mode that was used to
open the file.
Syntax
file.Attr
Parameters
File
Reference to a File control.
Return values
The return values listed in the following table indicate the file access mode. If the return value
is 0, the file is closed.
Constant Value
None 0
fsModeInput 1
fsModeOutput 2
fsModeRandom 4
fsModeAppend 8
fsModeBinary 32
Remarks
The Attr property is read-only. Use the Open method of the File control to set the file mode.
Close
Function
This method closes an open File control.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1548 System Manual, 08/2011,
Syntax
file.Close
Parameters
File
Name of a File control.
Return Values
None.
Remarks
Use the Open method to open a file.
CreateObject
Function
This function creates a reference to an Automation object.
Syntax
CreateObject (Object)
Parameters
Object
A string containing the ProgID of the object to create.
Return values
Returns a reference to an Automation object.
Remarks
Use CreateObject to create non-visible ActiveX controls at runtime. You cannot use
CreateObject to create graphical objects such as a TreeView control or a ListView control.
CreateObject produces objects that cannot respond to events. To produce objects that can
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1549
respond to events, use the CreateObjectWithEvents function. The following table lists the
ProgIDs for the ActiveX controls without events.
Control ProgID
Microsoft CE File control 6.0 .file
Microsoft CE FileSystem control 6.0 .filesystem
Microsoft CE ImageList control 6.0 CEimageList.imagelistctrl
Example
Dim f, fwModeAppend
Set f = CreateObject("FileCtl.File")
fwModeAppend=8
f.Open "\Storage Card\testfile.txt", fwModeAppend
f.Close
Dir
Function
This method returns the name of a file, directory, or folder that matches a specified pattern or
file attribute.
Syntax
File.Dir (Pathname,[Attributes])
Parameters
File
Reference to a FileSystem control.
Pathname
Optional. String expression that specifies a file name or path.
Attributes
Optional. Numeric expression whose sum specifies file attributes. If omitted, all files that match
pathname are returned.
The following table describes the parameter settings of attributes.
Constant Value Description
fsAttrNormal 0 Normal
fsAttrReadOnly 1 Read only
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1550 System Manual, 08/2011,
Constant Value Description
fsAttrHidden 2 Hidden
fsAttrSystem 4 System file
fsAttrVolume 8 Volume label. If specified, all other attributes are ignored.
fsAttrDirectory 16 Directory or folder
fsAttrArchive 32 Logs
Return values
String. File name that matches pathname and attributes. Dir returns a zero-length string ("") if
pathname is not found.
Remarks
Dir supports the use of multiple-character (*) and single-character (?) wildcards to specify
multiple files. You must specify pathname the first time you call the Dir method. In addition, if
you specify file attributes you must include pathname.
The Dir method returns the first file name that matches pathname. To get any additional file
names that match pathname, call Dir again with no parameters. When no more file names
match, Dir returns a zero-length string (" "). Once a zero-length string is returned, you must
specify pathname in subsequent calls.
EOF
Function
This property returns True when the end of a file opened for random or sequential input is
reached.
Syntax
File.EOF
Parameters
File
Reference to a File control.
Remarks
Use the EOF property to avoid the error generated by attempting to read past the end of a file.
The EOF property returns False until the end of the file has been reached. For files opened
with a fsModeRandom or fsModeBinary file mode, EOF returns False until the last executed
Get statement is unable to read an entire record.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1551
For files opened with a fsModeBinary file mode, an attempt to read through the file using the
Input function until EOF returns True generates an error. Use the LOF and LOC properties
instead of EOF when reading binary files with Input, or use Get when using the EOF property.
For files opened with a fsModeOutput file mode, EOF always returns True.
FileCopy
Function
This method copies an existing file to a new file.
Syntax
Filesystem.FileCopy PathName, NewPathName
Parameters
Filesystem
Reference to a FileSystem object.
PathName
String that contains the path and file name.
NewPathName
String that contains the file name and path of the new file.
Return Values
None.
Remarks
FileCopy returns an error if the new file does not exist.
FileLen
Function
This method returns a value specifying the length, in bytes, of a file.
Syntax
Filesystem.FileLen(pathname)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1552 System Manual, 08/2011,
Parameters
Filesystem
Reference to a FileSystem control.
Pathname
Required. String expression that specifies a file. The pathname can include a directory or folder.
Return Values
Returns the number of bytes in a file.
Remarks
If the specified file is open when the FileLen method is called, the value returned represents
the size of the file immediately before it was opened.
FileDateTime
Function
This method returns a variant (Date) that indicates the date and time when a file was created
or last modified.
Syntax
filesystem.FileDateTime(pathname)
Parameters
Filesystem
Reference to a FileSystem control.
Pathname
Required. String expression that specifies a file name. The pathname can include a directory
or folder.
Return Values
Returns the date the file was last modified.
Remarks
FileDateTime returns an error if the new file does not exist.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1553
Get
Function
This method reads data from an open disk file into a variable.
Syntax
file.Get Data, [Recnumber]
Parameters
File
Reference to a File control.
Data
Required. Variant variable into which data is read.
Recnumber
Optional. Variant. Record number at which reading begins. For files opened in binary mode,
Recnumber specifies the byte position.
Return Values
None
Remarks
Data read with the Get method usually is written to a file with the Put method. The first record
or byte in a file is at position 1, the second record or byte is at position 2, and so on. If you omit
Recnumber, the next record or byte following the last Get or Put method (or pointed to by the
last Seek function) is read.
For files opened in Random mode, the following rules apply:
If the length of the data being read is less than the length specified in the Len clause of the
Open method, Get reads subsequent records on record-length boundaries. The space
between the end of one record and the beginning of the next record is padded with the
existing contents of the file buffer. Because the amount of padding data cannot be
determined with any certainty, it is generally advisable to match the record length with the
length of the data being read.
If Data is a Variant of numeric type, Get reads 2 bytes identifying the VarType of the Variant
and then reads the data that goes into the variable. For example, when reading a Variant
of VarType 3, Get reads 6 bytes: 2 bytes identifying the Variant as VarType 3 (Long) and
4 bytes containing the Long data. The record length specified by the Len clause in the Open
method must be at least 2 bytes greater than the actual number of bytes required to store
the variable.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1554 System Manual, 08/2011,
You can use the Get method to read a Variant array from a disk, but you cannot use Get
to read a scalar Variant containing an array. You also cannot use Get to read objects from
a disk.
If the variable being read into is a Variant of VarType 8 (String), Get reads 2 bytes identifying
the VarType and 2 bytes indicating the length of the string. Then it reads the string data.
The record length specified by the Len clause in the Open method must be at least 4 bytes
greater than the actual length of the string.
If the variable being read into is a dynamic array, Get reads a descriptor whose length
equals 2 plus 8 times the number of dimensions, that is, 2 + 8 * NumberOfDimensions. The
record length specified by the Len clause in the Open method must be greater than or equal
to the sum of all the bytes required to read the array data and the array descriptor.
For files opened in Binary mode, the Len clause in the Open method has no effect. Get reads
all variables from a disk contiguously; that is, with no padding between records.
GetAttr
Function
This method returns a number representing the attributes of a file, directory, or folder.
Syntax
filesystem.GetAttr(pathname)
Parameters
File system
Reference to a FileSystem control.
Pathname
Required. String expression that specifies a file name or directory or a folder name. The
pathname can include the directory or folder.
Return values
Sum of attribute values. The following table shows the sums that can be returned.
Constant Value Description
vbNormal 0 Normal
VbReadOnly 1 Read only
VbHidden 2 Hidden
VbSystem 4 System
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1555
Constant Value Description
VbDirectory 16 Directory or folder
VbArchive 32 File has changed since last backup
Remarks
To determine which attributes are set, use the And operator to perform a bitwise comparison
of the value returned by the GetAttr method and the value of the individual file attribute you
want. If the result is not zero, that attribute is set for the named file.
Input
Function
This method returns a string containing characters from a file opened in Input or Binary mode.
Syntax
file.Input(number)
Parameters
File
Reference to a File control.
Number
Any valid numeric expression that specifies the number of characters to return.
Return Values
String containing characters read from file.
Remarks
Data read with the Input method usually is written to a file with the LinePrint or Put functions.
Use this method only with files opened in Input or Binary mode.
Unlike the LineInputString method, the Input method returns all the characters it reads,
including commas, carriage returns, line feeds, quotation marks, and leading spaces.
With files opened for Binary access, an attempt to read through the file using the Input method
until the EOF function returns True generates an error. To avoid an error, use the LOF and
Loc functions instead of EOF when reading binary files with the Input method or use Get when
using the EOF function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1556 System Manual, 08/2011,
InputFields
Function
This method reads data from an open sequential file and returns a single dimension Variant
array.
Syntax
file.InputFields(number)
Parameters
File
Reference to a File control.
Number
Number of comma-delimited fields to read from the file.
Return values
Array containing the fields read from the file.
Remarks
Data read with the InputFields method usually is written to a file with WriteFields. Use this
method only with files opened in Input or Binary mode.
InputFields reads standard string or numeric data without modification. The following table
shows how InputFields reads other input data.
Data Value Assigned to Variable
Delimiting comma or blank line Empty
#ZERO# Zero
#TRUE# or #FALSE# True or False
#yyyy-mm-dd hh:mm:ss# The date and/or time represented by the expression
Double quotation marks ("") within input data are discarded.
If you reach the end of the file while you are inputting a data item, the input is terminated and
an error occurs.
To correctly read data from a file into variables using InputFields, use the WriteFields method
instead of the LinePrint method to write the data to the files. Using WriteFields ensures each
separate data field is properly delimited.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1557
InputB
Function
This method returns bytes from a file opened in Input or Binary mode.
Syntax
file.InputB(number)
Parameters
File
Reference to a File control.
Number
Any valid numeric expression that specifies the number of bytes to return.
Return Values
Array containing bytes read from file.
Remarks
Data read with the InputB method usually is written to a file with the LinePrint or Put functions.
Use this method only with files opened in Input or Binary mode.
Kill
Function
This method deletes files from a disk.
Syntax
filesystem.Kill pathname
Parameters
Filesystem
Reference to a FileSystem control.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1558 System Manual, 08/2011,
Pathname
Required. String expression that specifies one or more file names to be deleted. The pathname
can include the directory or folder.
Return Values
None.
Remarks
The Kill method supports the use of multiple-character (*) and single-character (?) wildcards
to specify multiple files.
An error occurs if you try to use Kill to delete an open file.
LineInputString
Function
This method reads a single line from an open sequential file and assigns it to a string variable.
Syntax
file.LineInputString
Parameters
File
Reference to a File control.
Return Values
None.
Remarks
Data read with LineInputString usually is written from a file with LinePrint.
The LineInputString method reads from a file one character at a time until it encounters a
carriage return (Chr(13)) or carriage return/line feed (Chr(13) + Chr(10)) sequence. Carriage
return/line feed sequences are skipped rather than appended to the character string.
LinePrint
Function
This method writes a single line to an open sequential file.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1559
Syntax
file.LinePrint output
Parameters
File
Reference to a File control.
Output
String expression to write to a file.
Return Values
None.
Remarks
Data written with LinePrint is usually read from a file with LineInputString.
A carriage return/line feed (Chr(13) + Chr(10)) sequence is appended to the end of the string.
Loc
Function
This property returns a number specifying the current read/write position.
Syntax
file.Loc
Parameters
File
Reference to a File control.
Remarks
For files opened with the fsModeRandom file mode, Loc returns the number of the last record
read or written. For files opened with all other modes, Loc returns the position of the last byte
read or written.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1560 System Manual, 08/2011,
LOF
Function
This property returns a number representing the size, in bytes, of a file.
Syntax
file.LOF
Parameters
File
Reference to a File control.
Remarks
The LOF property can be used with the Loc property to guarantee that a read operation does
not continue past the end of a file.
MkDir
Function
This method creates a new directory.
Syntax
filesystem.MkDir PathName
Parameters
Filesystem
Reference to a FileSystem control.
Pathname
String expression that contains the directory name.
Return Values
None.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1561
Remarks
MkDir generates an error if the directory already exists.
MoveFile
Function
This method renames an existing file or a directory, including all its subdirectories.
Syntax
filesystem.MoveFile PathName, NewPathName
Parameters
Filesystem
Reference to a FileSystem control.
PathName
String that contains the file name.
NewPathName
String that contains the file name to copy to.
Return Values
None.
Open
Function
This method opens a file in either the Input (1), Output (2), Random (4), Append (8), or Binary
mode (32).
Syntax
file.Open pathname, mode, [access], [lock], [reclength]
Parameters
File
Reference to a File control.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1562 System Manual, 08/2011,
Pathname
String expression that specifies a file name.
Mode
Specifies the file mode: Input (1), Output (2), Random (4) , Append (8), or Binary (32).
Access
Operation permitted on the open file: Read, Write, or ReadWrite [Default]. (1, 2, 3)
Lock
Operations permitted on the open file by other processes: Shared, LockRead, LockWrite
[Default], and LockReadWrite. (1, 2, 3, 0)
Reclength
Number, in bytes, that is less than 32,767. For files opened for random access, this value is
the record length. For sequential files, this value is the number of characters buffered.
Return Values
None.
Remarks
The reclength parameter is ignored if the mode is Binary. When opening a file in Random
mode, you must specifiy a record size of greater than zero or an error will occur.
Put
Function
This method writes data from a variable to a disk file.
Syntax
file.Put data, [recnumber]
Parameters
Data
Required. Variant variable that contains data to be written to disk.
Recnumber
Optional. Variant (Long). Record number (Random mode files) or byte number (Binary mode
files) at which writing begins.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1563
Return Values
None.
Remarks
Data written with Put usually is read from a file with Get.
The first record or byte in a file is at position 1, the second record or byte is at position 2, and
so on. If you omit recnumber, the next record or byte after the last Get or Put method or pointed
to by the last Seek function is written.
For files opened in Random mode, the following rules apply:
If the length of the data being written is less than the length specified in the Len clause of
the Open method, Put writes subsequent records on record-length boundaries. The space
between the end of one record and the beginning of the next record is padded with the
existing contents of the file buffer. Because the amount of padding data cannot be
determined with any certainty, it generally is a good idea to have the record length match
the length of the data being written. If the length of the data being written is greater than
the length specified in the Len clause of the Open method, an error occurs.
If the variable being written is a Variant of a numeric type, Put writes 2 bytes identifying the
VarType of the Variant and then writes the variable. For example, when writing a Variant
of VarType 3, Put writes 6 bytes: 2 bytes identifying the Variant as VarType 3 (Long) and
4 bytes containing the Long data. The record length specified by the Len clause in the Open
method must be at least 2 bytes greater than the actual number of bytes required to store
the variable.
You can use the Put method to write a Variant array to disk, but you cannot use Put to write
a scalar Variant containing an array to disk. You also cannot use Put to write objects to disk.
If the variable being written is a Variant of VarType 8 (String), Put writes 2 bytes identifying
the VarType and 2 bytes indicating the length of the string. It then writes the string data. The
record length specified by the Len clause in the Open method must be at least 4 bytes greater
than the actual length of the string.
If the variable being written is a dynamic array, Put writes a descriptor whose length equals 2
plus 8 times the number of dimensions, that is, 2 + 8 * NumberOfDimensions. The record length
specified by the Len clause in the Open method must be greater than or equal to the sum of
all the bytes required to write the array data and the array descriptor. For example, the following
array declaration requires 118 bytes when the array is written to disk.
For files opened in Binary mode, the Len clause in the Open method has no effect. Put writes
all variables to disk contiguously; that is, with no padding between records.
RmDir
Function
This method deletes an existing empty directory.
Syntax
filesystem.RmDir PathName
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1564 System Manual, 08/2011,
Parameters
Filesystem
Reference to a FileSystem control.
PathName
String that contains the directory name.
Return Values
None.
Remarks
The directory must be empty before it can be removed. You must specify a complete file path.
Seek
Function
This property returns and sets the next position in a file that will be read or written.
Syntax
file.Seek [= position]
Parameters
File
Reference to a File control.
Position
Numeric expression that specifies a position within a file.
Remarks
The Seek property specifies the next file position, whereas the Loc property specifies the
current position. Seek always will be one more than Loc, except when a file is first opened and
Seek and Loc are both 1.
Negative Seek or 0 causes an error.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1565
SetAttr
Function
This method sets attribute data for a file.
Syntax
filesystem.SetAttr pathname, attributes
Parameters
File system
Reference to a FileSystem control.
Pathname
Required. String expression that specifies a file name.
Attributes
Required. Numeric expression whose sum specifies file attributes. The following table shows
the parameter settings of attributes.
Constant Value Description
vbNormal 0 Normal (default)
vbReadOnly 1 Read only
vbHidden 2 Hidden
VbSystem 4 System file
VbArchive 32 File has changed since last backup
Return values
None.
Remarks
A run-time error occurs if you try to set the attributes of an open file.
WriteFields
Function
This method writes data to a sequential file.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1566 System Manual, 08/2011,
Syntax
file.WriteFields [data]
Parameters
File
Reference to a File control.
Data
Variant or Variant array of numeric or string expressions to write to a file.
Prinzip
Return Values
None.
Remarks
Data written with WriteFields is usually read from a file with InputFields.
If you omit d ata, a blank line is printed to the file.
Numeric data is always written using the period as the decimal separator.
For Boolean data, either #TRUE# or #FALSE# is printed. The True and False keywords
are not translated, regardless of locale.
Date data is written to the file using the universal date format. When either the date or the
time component is missing or is zero, only the component provided gets written to the file.
Nothing is written to the file if Data is Empty. However, for Null data, #NULL# is written.
If d ata is Null, #NULL# is written to the file.
The WriteFields method inserts commas between items and quotation marks around strings
as they are written to the file. You do not have to put explicit delimiters in the list. WriteFields
inserts a newline characterthat is, a carriage return/line feed (Chr(13) + Chr(10))after it
has written the final character in data to the file.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1567
VBS object model
Objects
HMIRuntime
Description
Screen
Screens
SmartTag
SmartTags
HMlRuntime
Portrays the graphic runtime system.
The HMIRuntime object contains properties and methods which return the objects to the main
layer, e.g. returns the ActiveScreen property of a screen object.
Application
You use the "HMIRuntime" object, e.g. as follows:
Read or set the current Runtime language ("Language" property).
Read name of current base screen or trigger a base screen change by setting a new screen
name (property "BaseScreenName")
Access tags (List "SmartTags")
End runtime (Method "Stop")
Output information on sequence tracing output (Method "Trace")
Access the screens displayed during runtime (List "Screens")
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1568 System Manual, 08/2011,
See also
ActiveScreen (Page 1637)
Screen object (list)
Description
Screen
Screenltems
Screens
HMlRuntime
A list of screen objects.
The list contains the following two elements:
The first element with the index 0 represents the permanent window.
The second element with the index 1 represents the root screen.
Alternatively, the two elements can be addressed with their their names as follows:
Permanent window: "Overview"
Root screen: Name of the screen displayed in the root screen
If the named screen is not displayed, an error occurs during access.
Permanent window "Overview" is displayed in the objects list and in Auto complete.
Note
The alarm window and the alarm indicator are not contained in the screens list, even if they
have the focus in Runtime.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1569
Application
Use the screen property to return the screen list. In the following example, the background
color is changed from black to green:
Use the object name as an index.
'VBS_Example_BackColor
HMIRuntime.Screens("Rootscreen").BackColor = vbGreen
Note
If you perform a screen change, the open references to the screen that is no longer available
will become invalid. As a result, it is no longer possible to work with these references.
Screen
Description
Screen
Screenltems
Screens
HMlRuntime
Represents the process screen which is being displayed on the HMI device at the moment or
the permanent window in runtime. The screen object is returned to you as a result of accessing
the screen list.
The screen object also contains a list of all graphic objects in the screen that can be addressed
through the list "ScreenItems".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1570 System Manual, 08/2011,
Application
You can also use the screen object to do the following:
Read the height and width of a screen (properties "Height" and "Width").
Change the background color (property "BackColor").
Use the object name as an index.
In the following example, the background color is changed from black to green:
'VBS example background color
HMIRuntime.Screens("Rootscreen").BackColor = vbGreen
See also
ScreenItem (Page 1571)
ScreenItems (Page 1573)
ScreenItem
Description
Screen
Screenltems
Screens
Screenltem
Represents an object in the specified screen. The ScreenItem object is an element of the
ScreenItems list.
Application
You can use the ScreenItem object to access the properties of graphic objects within a screen,
depending on certain events.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1571
You use the "ScreenItem" object as follows, for example:
"Visible" property
Switch the visibility of an object on or off.
"Height" and "Width" properties
Query the width and height of an object.
"Top" and "Left" properties
Change the position of an object.
"ObjectName" property
Read the name of a graphic object
"Parent" property
Set a reference to the parent screen
Use the ScreenItems property to return an object to the screen. Use the object name as an
index.
Example
In the following example, the background color of the "RootScreen" circle in the "myCircle"
screen is set to green.
'VBS_Example_ScreenItems
Dim objCircle
Set objCircle = HMIRuntime.Screens("RootScreen").ScreenItems("myCircle")
objCircle.BackColor = vbGreen
Note
To save memory space in the HMI device, no object names are loaded during transfer of the
project. If you still want to transfer object names, call up the Runtime settings for the respective
HMI device in WinCC. You can change the setting under "General". The object name is
required when the object should be accessed via the object name or for debugging a project.
The "ScreenItem" object has different properties depending on its features. The following
properties are provided for every "ScreenItem" object:
Enabled
Height
Left
ObjectName
Parent
Top
Type
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1572 System Manual, 08/2011,
Visible
Width
If a specific object type is addressed, further properties are added to the standard properties.
The additional properties are provided in the descriptions of the individual object types.
See also
Screen (Page 1570)
ScreenItems
Description
Screen
Screenltems
Screens
HMlRuntime
A list of screen item objects with all screen objects of the given process screen. The list has a
parent property. This property provides a reference to the process screen in which the screen
object is located.
Application
By means of the "ScreenItems" list you are able
To edit or output all objects within the list (that is, all objects within a screen)
To count the objects of a screen (property "Count").
To work on a particular object in the list (method "Item").
Use the screen items property to return an object from the process screen. Use the object
name as an index.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1573
In the following example, the background color of the "RootScreen" circle in the "myCircle"
screen is set to green.
Dim objCircle
Set objCircle = HMIRuntime.Screens("RootScreen").ScreenItems("myCircle")
objCircle.BackColor = vbGreen
See also
Screen (Page 1570)
SmartTags
Description
HMlRuntime
SmartTags
SmartTag
A list of SmartTag objects which represent all of the tags in WinCC Runtime.
Note
The SmartTags list has a limited range of functions. You can only use the tag names to access
a SmartTag object. Access via the index or by using "For each" instruction is not supported.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1574 System Manual, 08/2011,
Note
In order to access a tag, which has still not been created in the project, using the SmartTags
list, no value is returned. Assignment to a non-existing tag is not executed:
Dim intVar
intVar = SmartTags("FillLevel")
"intVar" remains empty when the "FillLevel" tag has not been created.
Application
Use the SmartTags list to return a SmartTag object. Use the tag name to reference the
SmartTag object.
'VBS_Example_SmartTags
'Writes tag value to local tag and returns a user-defined text through the
operating system channel for debug alarms.
Dim strAirPressure
strAirPressure = "Current air pressure: " + CStr(SmartTags("AirPressure"))
HMIRuntime.Trace strAirPressure
In Runtime Advanced and Panels you address the tag directly using its name. If the tag name
corresponds to the VBS name conventions, you do not need to use the SmartTags list. Follow
the example below:
Dim strAirPressure
strAirPressure = "Current air pressure: " + CStr(AirPressure)
HMIRuntime.Trace strAirPressure
See also
Trace (Page 1791)
Access to HMI tags (Page 1232)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1575
SmartTag
Description
HMlRuntime
SmartTags
SmartTag
Represents the value of the specified process tag. The SmartTag object is an element of the
SmartTag list.
Application
The SmartTag object provides read and write access to the value of the specified process tag.
The SmartTag object does not return an object reference. Use the SmartTags list to return the
value of a process tag. Use the tag name as an index.
Example
'VBS_Example_SmartTags
'Writes tag value to local tag and returns a user-defined text through the
operating system channel for debug alarms.
Dim strAirPressure
strAirPressure = "Current air pressure: " + CStr(SmartTags("AirPressure"))
HMIRuntime.Trace strAirPressure
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1576 System Manual, 08/2011,
Note
In order to access a tag, which has still not been created in the project, using the SmartTags
list, no value is returned. Assignment to a non-existing tag is not executed:
Dim intVar
intVar = SmartTags("FillLevel")
"intVar" remains empty when the "FillLevel" tag has not been created.
Note
If you want to return the "TypeName" of a SmartTag object data type with the VBS function
"TypeName", use the following syntax:
TypeName(SmartTags("FillLevel").value)
Use "SmartTags("<tag>")(index)" to access the value of an array element. Set the number of
the desired array element for "index", for example, "SmartTags("AirPressure")(2)".
See also
Trace (Page 1791)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1577
Object types
Bar
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Bar" object. The Bar object is an element of the ScreenItems list.
Type identifier in VBS
HMIBar
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1578 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
BarBackColor (Page 1643)
BorderStyle3D (Page 1649)
CountSubDivisions (Page 1655)
Enabled (Page 1659)
ForeColor (Page 1669)
Height (Page 1672)
Left (Page 1678)
MaximumValue (Page 1683)
MinimumValue (Page 1683)
ObjectName (Page 1688)
Parent (Page 1690)
Processvalue (Page 1694)
ScaleColor (Page 1700)
ScaleGradation (Page 1701)
SegmentColoring (Page 1705)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1579
BatteryView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Charge condition" object. The BatteryView object is an element of the
ScreenItems list.
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
FocusWidth (Page 1668)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1580 System Manual, 08/2011,
Button
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Button" object. The Button object is an element of the ScreenItems list.
The availability of the following object properties depends on the selected mode of the "button":
Property "Text" "Text list" "Graphic"
TextOff x -- --
TextOn x -- --
Type identifier in VBS
HMIButton
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1581
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderStyle3D (Page 1649)
Enabled (Page 1659)
FocusColor (Page 1667)
ForeColor (Page 1669)
Height (Page 1672)
HelpText (Page 1674)
HorizontalAlignment (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
TextOff (Page 1727)
TextOn (Page 1727)
Top (Page 1733)
Type (Page 1758)
VerticalAlignment (Page 1763)
Visible (Page 1764)
Width (Page 1768)
FocusWidth (Page 1668)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1582 System Manual, 08/2011,
Circle
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Circle" object. The Circle object is an element of the ScreenItems list.
Type identifier in VBS
HMICircle
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1583
See also
Activate (Page 1787)
BackColor (Page 1640)
BackFillStyle (Page 1642)
BorderColor (Page 1646)
BorderWidth (Page 1649)
EdgeStyle (Page 1658)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Radius (Page 1697)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1584 System Manual, 08/2011,
Clock
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Clock" object. The Clock object is an element of the ScreenItems list.
Type identifier in VBS
Clock
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1585
See also
Activate (Page 1787)
DialColor (Page 1657)
Enabled (Page 1659)
Height (Page 1672)
HourNeedleHeight (Page 1675)
HourNeedleWidth (Page 1675)
Left (Page 1678)
MinuteNeedleHeight (Page 1684)
MinuteNeedleWidth (Page 1684)
NeedleBorderColor (Page 1685)
NeedleColor (Page 1686)
ObjectName (Page 1688)
Parent (Page 1690)
SecondNeedleHeight (Page 1704)
SecondNeedleWidth (Page 1705)
ShowTicks (Page 1714)
TicksColor (Page 1729)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1586 System Manual, 08/2011,
DateTimeField
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Date/time field" object. The DateTimeField object is an element of the
ScreenItems list.
Type identifier in VBS
HMIDateTimeField
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1587
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderColor (Page 1646)
BorderStyle3D (Page 1649)
Enabled (Page 1659)
ForeColor (Page 1669)
Height (Page 1672)
HelpText (Page 1674)
HorizontalAlignment (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
VerticalAlignment (Page 1763)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1588 System Manual, 08/2011,
Ellipse
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Ellipse" object. The Ellipse object is an element of the ScreenItems list.
Type identifier in VBS
HMIEllipse
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1589
See also
Width (Page 1768)
Visible (Page 1764)
Type (Page 1758)
Top (Page 1733)
Activate (Page 1787)
BackColor (Page 1640)
BackFillStyle (Page 1642)
BorderColor (Page 1646)
BorderWidth (Page 1649)
EdgeStyle (Page 1658)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
RadiusHeight (Page 1697)
RadiusWidth (Page 1698)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1590 System Manual, 08/2011,
FunctionTrendControl
Description
Screen
Screenltems
Screens
Screenltem
Represents the "f(x)FunctionTrendView" object. The FunctionTrendControl object is an
element of the ScreenItems list.
Type identifier in VBS
HMIFunctionTrendControl
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1591
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderColor (Page 1646)
BorderWidth (Page 1649)
Caption (Page 1650)
Closable (Page 1652)
ConnectTrendWindows (Page 1654)
Enabled (Page 1659)
ExportDirectoryChangeable (Page 1661)
ExportDirectoryname (Page 1662)
ExportFileExtension (Page 1662)
ExportFilename (Page 1663)
ExportFilenameChangeable (Page 1663)
ExportFormatGuid (Page 1664)
ExportFormatName (Page 1664)
ExportParameters (Page 1664)
ExportSelection (Page 1665)
ExportShowDialog (Page 1665)
ExportXML (Page 1666)
Font (Page 1668)
GraphDirection (Page 1671)
Height (Page 1672)
Left (Page 1678)
LineColor (Page 1681)
LineWidth (Page 1681)
LoadDataImmediately (Page 1681)
Movable (Page 1685)
ObjectName (Page 1688)
Online (Page 1690)
Parent (Page 1690)
PrintJobName (Page 1694)
RTPersistence (Page 1695)
RTPersistencePasswordLevel (Page 1696)
RTPersistenceType (Page 1696)
ShowRuler (Page 1711)
ShowRulerInAxis (Page 1711)
ShowScrollbars (Page 1712)
ShowTitle (Page 1715)
ShowTrendIcon (Page 1715)
SkinName (Page 1716)
StatusbarBackColor (Page 1719)
StatusbarElementAdd (Page 1720)
StatusbarElementAutoSize (Page 1720)
StatusbarElementCount (Page 1720)
StatusbarElementIconId (Page 1721)
StatusbarElementID (Page 1721)
StatusbarElementIndex (Page 1721)
StatusbarElementName (Page 1721)
StatusbarElementRemove (Page 1722)
ToolbarButtonRemove (Page 1729)
ToolbarButtonRename (Page 1729)
ToolbarButtonRepos (Page 1730)
ToolbarButtonTooltipText (Page 1730)
ToolbarButtonUserDefined (Page 1730)
ToolbarShowTooltips (Page 1731)
ToolbarUseBackColor (Page 1731)
ToolbarUseHotKeys (Page 1732)
ToolbarVisible (Page 1732)
Top (Page 1733)
TrendActualize (Page 1735)
TrendAdd (Page 1736)
TrendBeginTime (Page 1736)
TrendColor (Page 1736)
TrendCount (Page 1737)
TrendEndTime (Page 1737)
TrendExtendedColorSet (Page 1737)
TrendFill (Page 1738)
TrendFillColor (Page 1738)
TrendIndex (Page 1738)
TrendLabel (Page 1739)
TrendLineStyle (Page 1739)
TrendLineType (Page 1740)
TrendLineWidth (Page 1740)
TrendLowerLimit (Page 1740)
TrendLowerLimitColor (Page 1741)
TrendLowerLimitColoring (Page 1741)
TrendMeasurePoints (Page 1741)
TrendName (Page 1742)
TrendPointColor (Page 1742)
TrendPointStyle (Page 1742)
TrendPointWidth (Page 1743)
TrendProvider (Page 1743)
TrendRangeType (Page 1744)
TrendRemove (Page 1745)
TrendRename (Page 1745)
TrendRepos (Page 1745)
TrendSelectTagNameX (Page 1746)
TrendSelectTagNameY (Page 1746)
TrendTagNameY (Page 1747)
TrendTimeRangeBase (Page 1747)
TrendTimeRangeFactor (Page 1748)
TrendTrendWindow (Page 1748)
TrendUncertainColor (Page 1748)
TrendUncertainColoring (Page 1749)
TrendUpperLimit (Page 1749)
TrendTagNameX (Page 1746)
TrendUpperLimitColor (Page 1749)
TrendUpperLimitColoring (Page 1750)
TrendVisible (Page 1750)
TrendWindowAdd (Page 1751)
TrendWindowCoarseGrid (Page 1751)
TrendWindowCoarseGridColor (Page 1751)
TrendWindowFineGrid (Page 1752)
TrendWindowFineGridColor (Page 1752)
TrendWindowForegroundTrendGrid (Page 1752)
TrendWindowGridInTrendColor (Page 1753)
TrendWindowHorizontalGrid (Page 1753)
TrendWindowIndex (Page 1754)
TrendWindowName (Page 1754)
TrendWindowRemove (Page 1754)
TrendWindowRename (Page 1755)
TrendWindowRepos (Page 1755)
TrendWindowRulerColor (Page 1755)
TrendWindowRulerLayer (Page 1756)
TrendWindowRulerStyle (Page 1756)
TrendWindowRulerWidth (Page 1757)
TrendWindowSpacePortion (Page 1757)
TrendWindowVerticalGrid (Page 1757)
TrendWindowVisible (Page 1758)
TrendXAxis (Page 1758)
TrendYAxis (Page 1758)
Type (Page 1758)
UseTrendNameAsLabel (Page 1762)
Visible (Page 1764)
Width (Page 1768)
XAxisAdd (Page 1771)
XAxisAlign (Page 1771)
XAxisAutoPrecisions (Page 1771)
XAxisAutorange(i) (Page 1772)
XAxisBeginValue (Page 1773)
XAxisColor (Page 1773)
XAxisCount (Page 1773)
XAxisEndValue (Page 1774)
XAxisExponentialFormat (Page 1774)
XAxisIndex (Page 1774)
XAxisInTrendColor (Page 1775)
XAxisLabel(i) (Page 1775)
XAxisName (Page 1776)
XAxisPrecisions (Page 1776)
XAxisRemove (Page 1776)
XAxisRepos (Page 1777)
XAxisScalingType(i) (Page 1777)
XAxisTrendWindow (Page 1778)
XAxisVisible (Page 1778)
YAxisAdd (Page 1779)
YAxisAlign (Page 1779)
YAxisAutoPrecisions (Page 1780)
YAxisAutoRange (Page 1780)
YAxisBeginValue (Page 1781)
YAxisColor (Page 1781)
YAxisCount (Page 1781)
YAxisEndValue (Page 1782)
YAxisExponentialFormat (Page 1782)
YAxisIndex (Page 1782)
YAxisInTrendColor (Page 1783)
YAxisLabel (Page 1783)
YAxisName (Page 1784)
YAxisPrecisions (Page 1784)
YAxisRemove (Page 1784)
YAxisRename (Page 1785)
YAxisRepos (Page 1785)
YAxisScalingType (Page 1786)
YAxisTrendWindow (Page 1786)
YAxisVisible (Page 1786)
AttachDB method (Page 1792)
DetachDB (Page 1792)
Export (Page 1793)
GetStatusbarElement (Page 1793)
GetStatusbarElementCollection (Page 1794)
GetToolbarButton (Page 1796)
GetToolbarButtonCollection (Page 1797)
GetTrend (Page 1798)
GetTrendCollection (Page 1799)
GetTrendWindow (Page 1800)
GetTrendWindowCollection (Page 1801)
GetXAxis (Page 1802)
GetXAxisCollection (Page 1803)
GetYAxis (Page 1805)
GetYAxisCollection (Page 1806)
MoveAxis (Page 1807)
NextTrend (Page 1808)
OneToOneView (Page 1808)
PreviousTrend (Page 1809)
Print (Page 1809)
ShowHelp (Page 1810)
ShowPropertyDialog (Page 1810)
ShowTagSelection (Page 1811)
ShowTimeSelection (Page 1811)
ShowTrendSelection (Page 1812)
StartStopUpdate (Page 1812)
ZoomArea (Page 1813)
ZoomInOut (Page 1813)
ZoomInOutX (Page 1814)
ZoomInOutY (Page 1814)
ZoomMove (Page 1815)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1592 System Manual, 08/2011,
Gauge
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Gauge" object. The Gauge object is an element of the ScreenItems list.
Type identifier in VBS
HMIGauge
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1593
See also
Activate (Page 1787)
AngleMax (Page 1639)
AngleMin (Page 1640)
BackColor (Page 1640)
CaptionColor (Page 1651)
CaptionText (Page 1651)
CenterColor (Page 1652)
DangerRangeColor (Page 1655)
DangerRangeStart (Page 1656)
DangerRangeVisible (Page 1656)
DialColor (Page 1657)
Enabled (Page 1659)
Gradation (Page 1670)
Height (Page 1672)
Left (Page 1678)
MaximumValue (Page 1683)
MinimumValue (Page 1683)
NormalRangeColor (Page 1686)
NormalRangeVisible (Page 1687)
ObjectName (Page 1688)
Parent (Page 1690)
PointerColor (Page 1693)
Processvalue (Page 1694)
ScaleLabelColor (Page 1702)
ScaleTickColor (Page 1703)
ShowPeakValuePointer (Page 1710)
Top (Page 1733)
Type (Page 1758)
UnitColor (Page 1761)
UnitText (Page 1761)
Visible (Page 1764)
WarningRangeColor (Page 1767)
WarningRangeStart (Page 1767)
WarningRangeVisible (Page 1768)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1594 System Manual, 08/2011,
GraphicIOField
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Graphic I/O field" object. The GraphicIOField object is an element of the
ScreenItems list.
The availability of the following object properties depends on the selected mode:
Property "Input" "Output" "Input/Output" "Two-States"
BorderColor -- -- -- x
BorderStyle3D x x x --
Enabled x -- x --
FocusColor x -- x --
FocusWidth x -- x --
HelpText x -- x --
TransparentColor x x x --
UseTransparentC
olor
x x x --
Type identifier in VBS
HMIGraphicIOField
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1595
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderStyle3D (Page 1649)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
Height (Page 1672)
HelpText (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
TransparentColor (Page 1735)
Top (Page 1733)
Type (Page 1758)
UseTransparentColor (Page 1762)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1596 System Manual, 08/2011,
GraphicView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Graphic view" object. The GraphicView object is an element of the
ScreenItems list.
Type identifier in VBS
HMIGraphicView
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1597
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderStyle3D (Page 1649)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
TransparentColor (Page 1735)
Type (Page 1758)
UseTransparentColor (Page 1762)
Visible (Page 1764)
Width (Page 1768)
Top (Page 1733)
HTMLBrowser
Description
Screen
Screenltems
Screens
Screenltem
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1598 System Manual, 08/2011,
Represents the object "HTML Browser". The HTMLBrowser-object is an element of the
ScreenItems-list.
Type identifier in VBS
HMIHTMLBrowser
See also
ScreenItem (Page 1571)
Activate (Page 1787)
Address (Page 1638)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1599
IOField
Description
Screen
Screenltems
Screens
Screenltem
Represents the "I/O field" object. The IOField object is an element of the ScreenItems list.
Type identifier in VBS
HMIIOField
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1600 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderColor (Page 1646)
BorderStyle3D (Page 1649)
EdgeStyle (Page 1658)
Enabled (Page 1659)
ForeColor (Page 1669)
Height (Page 1672)
HelpText (Page 1674)
HorizontalAlignment (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Processvalue (Page 1694)
Top (Page 1733)
Type (Page 1758)
VerticalAlignment (Page 1763)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1601
Line
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Line" object. The Line object is an element of the ScreenItems list.
Type identifier in VBS
HMILine
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1602 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
Color (Page 1653)
Enabled (Page 1659)
EndStyle (Page 1661)
FillStyle (Page 1666)
Height (Page 1672)
Left (Page 1678)
LineWidth (Page 1681)
ObjectName (Page 1688)
Parent (Page 1690)
StartStyle (Page 1719)
Style (Page 1722)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1603
AlarmView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "AlarmView" object. The MessageView object is an element of the ScreenItems
list.
If you change the settings for this object with a user-defined function, the changed settings are
retained even after the screen is called again.
Note
The object "Simple AlarmView" cannot be dynamized with a user-defined function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1604 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
SelectionBackColor (Page 1706)
SelectionForeColor (Page 1707)
ShowMessagesAtDate (Page 1709)
TableBackColor (Page 1723)
TableForeColor (Page 1723)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
GridLineColor (Page 1671)
ShowAlarmsFromDate (Page 1708)
SortByTimeDirection (Page 1717)
SortByTimeEnable (Page 1717)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1605
Polygon
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Polygon" object. The Polygon object is an element of the ScreenItems list.
Type identifier in VBS
HMIPolygon
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1606 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
BackFillStyle (Page 1642)
BorderColor (Page 1646)
BorderWidth (Page 1649)
EdgeStyle (Page 1658)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Polyline
Description
Screen
Screenltems
Screens
Screenltem
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1607
Represents the "Polyline" object. The Polyline object is an element of the ScreenItems list.
Type identifier in VBS
HMIPolyline
See also
Activate (Page 1787)
BackColor (Page 1640)
Color (Page 1653)
Enabled (Page 1659)
EndStyle (Page 1661)
FillStyle (Page 1666)
Height (Page 1672)
Left (Page 1678)
LineWidth (Page 1681)
ObjectName (Page 1688)
Parent (Page 1690)
StartStyle (Page 1719)
Style (Page 1722)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1608 System Manual, 08/2011,
ProtectedAreaName
Description
Screen
Screensltems
Screenltem
Represents the "EffectiveRangeName" (RFID)" object. The ProtectedAreaName object is an
element of the ScreenItems list.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1609
RangeLabelView
Description
Screen
Screensltems
Screenltem
Represents the "EffectiveRangeName" object. The RangeLabelView object is an element of
the ScreenItems list.
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Left (Page 1678)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1610 System Manual, 08/2011,
RangeQualityView
Description
Screen
Screensltems
Screenltem
Represents the "EffectiveRangeSignal" object. The RangeQualityView object is an element of
the ScreenItems list.
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1611
RecipeView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "RecipeView" object. The RecipeView object is an element of the ScreenItems
list.
If you change the settings for this object with a user-defined function, the changed settings are
retained even after the screen is called again.
Note
The object "Simple RecipeView" cannot be dynamized with a user-defined function.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1612 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
ForeColor (Page 1669)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
RecipeName (Page 1698)
RecipeNumber (Page 1699)
RecordName (Page 1699)
RecordNumber (Page 1699)
SelectionBackColor (Page 1706)
SelectionForeColor (Page 1707)
TableBackColor (Page 1723)
TableForeColor (Page 1723)
TableGridLineColor (Page 1724)
TableHeaderBackColor (Page 1725)
TableHeaderForeColor (Page 1726)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1613
Rectangle
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Rectangle" object. The Rectangle object is an element of the ScreenItems
list.
Type identifier in VBS
HMIRectangle
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1614 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
BackFillStyle (Page 1642)
BorderColor (Page 1646)
BorderWidth (Page 1649)
EdgeStyle (Page 1658)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Slider
Description
Screen
Screenltems
Screens
Screenltem
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1615
Represents the "Slider" object. The Slider object is an element of the ScreenItems list.
Type identifier in VBS
HMISlider
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1616 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
BarBackColor (Page 1643)
BarColor (Page 1644)
BorderBrightColor3D (Page 1646)
BorderInnerWidth3D (Page 1647)
BorderOuterWidth3D (Page 1648)
BorderShadeColor3D (Page 1648)
BorderWidth (Page 1649)
Caption (Page 1650)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
ForeColor (Page 1669)
Height (Page 1672)
LabelColor (Page 1677)
Left (Page 1678)
MinimumValue (Page 1683)
MaximumValue (Page 1683)
ObjectName (Page 1688)
Parent (Page 1690)
Processvalue (Page 1694)
ShowBar (Page 1708)
ShowPosition (Page 1710)
ShowThumb (Page 1713)
ShowTickLabels (Page 1714)
ShowTicks (Page 1714)
ThumbBackColor (Page 1728)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Font (Page 1668)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1617
SmartClientView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Sm@rtClient View" object. The SmartClientView object is an element of the
ScreenItems list.
Type identifier in VBS
HMISmartClientView
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1618 System Manual, 08/2011,
See also
Activate (Page 1787)
AllowMenu (Page 1639)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
MachineName (Page 1682)
ObjectName (Page 1688)
Parent (Page 1690)
Password (Page 1693)
Top (Page 1733)
Type (Page 1758)
ViewOnly (Page 1764)
Visible (Page 1764)
Width (Page 1768)
StatusForce
Description
Screen
Screenltems
Screens
Screenltem
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1619
Represents the "Status/Force" object. The StatusForce object is an element of the
ScreenItems list.
If you change the settings for this object with a user-defined function, the changed settings are
retained even after the screen is called again.
Type identifier in VBS
HMIStatusForce
See also
Activate (Page 1787)
BackColor (Page 1640)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
SelectionBackColor (Page 1706)
ShowTableGridlines (Page 1713)
TableBackColor (Page 1723)
TableForeColor (Page 1723)
TableHeaderBackColor (Page 1725)
TableHeaderForeColor (Page 1726)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1620 System Manual, 08/2011,
Switch
Description
Screen
Screenltems
Screens
Screenltem
Represents the "Switch" object. The Switch object is an element of the ScreenItems list.
The availability of the following object properties depends on the selected mode:
Property "Switch with text" "Switch with graphic" "Switch"
CaptionColor -- -- x
CaptionText -- -- x
HorizontalAlignment X -- --
InnerBackColorOff -- -- x
InnerBackColorOn -- -- x
TextOn x -- x
TextOff x -- x
VerticalAlignment x -- --
Type identifier in VBS
HMISwitch
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1621
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderStyle3D (Page 1649)
CaptionColor (Page 1651)
CaptionText (Page 1651)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
ForeColor (Page 1669)
Height (Page 1672)
HelpText (Page 1674)
HorizontalAlignment (Page 1674)
InnerBackColorOff (Page 1676)
InnerBackColorOn (Page 1677)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
TextOff (Page 1727)
TextOn (Page 1727)
Top (Page 1733)
Type (Page 1758)
VerticalAlignment (Page 1763)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1622 System Manual, 08/2011,
SymbolicIOField
Description
Screen
Screenltems
Screens
Screenltem
Represents the "SymbolicIOField" object. The SymbolicIOField object is an element of the
ScreenItems list.
The availability of the following object properties depends on the selected mode:
Property "Input" "Output" "Input/Output" "Two-States"
BackColor x x x x
BorderColor -- x -- x
BorderWidth -- -- -- x
BorderStyle3D -- x -- --
Enabled x -- x --
HelpText x -- x --
VerticalAlignment -- x -- x
HorizontalAlignment -- x -- x
Type identifier in VBS
HMISymbolicIOField
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1623
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderColor (Page 1646)
BorderStyle3D (Page 1649)
BorderWidth (Page 1649)
Enabled (Page 1659)
ForeColor (Page 1669)
Height (Page 1672)
HelpText (Page 1674)
HorizontalAlignment (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
VerticalAlignment (Page 1763)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1624 System Manual, 08/2011,
SymbolLibrary
Description
Screen
Screenltems
Screens
Screenltem
Represents the "SymbolLibrary" object. The SymbolLibrary object is an element of the
ScreenItems list.
Type identifier in VBS
HMISymbolLibrary
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1625
See also
Activate (Page 1787)
BackColor (Page 1640)
BlinkColor (Page 1645)
Enabled (Page 1659)
ForeColor (Page 1669)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
SystemDiagnoseView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "System diagnostic view" object. The SystemDiagnoseView object is an
element of the ScreenItems list.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1626 System Manual, 08/2011,
Type identifier in VBS
HMISysDiagView
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
SystemDiagnoseWindow
Description
Screen
Screenltems
Screens
Screenltem
Represents the "System diagnostic window" object. The SystemDiagnoseWindow object is an
element of the ScreenItems list.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1627
Type identifier in VBS
HMISysDiagWindow
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
TextField
Description
Screen
Screenltems
Screens
Screenltem
Represents the "TextField" object. The TextField object is an element of the ScreenItems list.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1628 System Manual, 08/2011,
Type identifier in VBS
HMITextField
See also
Activate (Page 1787)
BackColor (Page 1640)
BorderColor (Page 1646)
BorderStyle3D (Page 1649)
BorderWidth (Page 1649)
EdgeStyle (Page 1658)
Enabled (Page 1659)
ForeColor (Page 1669)
Height (Page 1672)
HorizontalAlignment (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Text (Page 1726)
Top (Page 1733)
Type (Page 1758)
VerticalAlignment (Page 1763)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1629
TrendView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "TrendView" object. The TrendView object is an element of the ScreenItems
list.
Type identifier in VBS
HMITrendView
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1630 System Manual, 08/2011,
See also
Activate (Page 1787)
BackColor (Page 1640)
Enabled (Page 1659)
FocusColor (Page 1667)
FocusWidth (Page 1668)
Height (Page 1672)
HelpText (Page 1674)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
RulerColor (Page 1700)
ScaleColor (Page 1700)
ShowRuler (Page 1711)
TableBackColor (Page 1723)
TableGridLineColor (Page 1724)
TableHeaderBackColor (Page 1725)
TableHeaderForeColor (Page 1726)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1631
UserView
Description
Screen
Screenltems
Screens
Screenltem
Represents the "UserView" object. The UserView object is an element of the ScreenItems list.
Note
The object "Simple UserView" cannot be dynamized with a user-defined function.
Type identifier in VBS
HMIUserView
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1632 System Manual, 08/2011,
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
SelectionBackColor (Page 1706)
SelectionForeColor (Page 1707)
TableBackColor (Page 1723)
TableForeColor (Page 1723)
TableGridLineColor (Page 1724)
TableHeaderBackColor (Page 1725)
TableHeaderForeColor (Page 1726)
BackColor (Page 1640)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1633
WLanQualityView
Description
Screen
Screensltems
Screenltem
Represents the "WLAN reception" object. The WLanQualityView object is an element of the
ScreenItems list.
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1634 System Manual, 08/2011,
ZoneLabelView
Description
Screen
Screensltems
Screenltem
Represents the "Zone name" object. The ZoneLabelView object is an element of the
ScreenItems list.
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1635
ZoneQualityView
Description
Screen
Screensltems
Screenltem
Represents the "ZoneSignal" object. The ZoneQualityView object is an element of the
ScreenItems list.
See also
Activate (Page 1787)
Enabled (Page 1659)
Height (Page 1672)
Left (Page 1678)
ObjectName (Page 1688)
Parent (Page 1690)
Top (Page 1733)
Type (Page 1758)
Visible (Page 1764)
Width (Page 1768)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1636 System Manual, 08/2011,
Properties
A-G
AboveUpperLimitColor
Description
Defines the color of the specified object for the case "High limit exceeded".
ActiveScreen
Description
Returns a "Screen" type object, which represents the screen which has the focus at the
moment.
Note
If you query the "ActiveScreen" property in a user-defined function, it may be due to a screen
saver that the property does not return a valid "screen" object but "Nothing". A system
message will be issued.
Access in Runtime: Read
Syntax
Object.ActiveScreen
Object
Required An object of the "HMIRuntime" type.
Comments
Which screen is returned depends on whether the root screen or the permanent window has
the focus.
The ActiveScreen property returns NOTHING if no screen has the focus. That is the case, for
example, when another window has the focus. With the statement "If not [expression] is
nothing" you are able to interrogate whether a screen is to be returned:
VBS example ActiveScreen
Dim objActiveScreen
Set objActiveScreen = HmiRuntime.ActiveScreen
If not objActiveScreen is nothing then
'found an active screen
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1637
HmiRuntime.Trace("There is an active screen." & vbCrLf)
Else
'found NO active screen
HmiRuntime.Trace("There is NO active screen." & vbCrLf)
End if
ActiveScreenItem
Description
References the screen object which currently has the focus.
The "ActiveScreenItem" property of the "Screen" object is only assigned a valid "ScreenItem"
object if the screen of the corresponding "Screen" object is active and has an input field. In all
other cases, for example, with a different screen from the "Screens" list, an independent
window within WinCC or a different application will be selected, this property will not apply to
the screens and will be occupied with "Nothing".
Application
The "ActiveScreenItem" object is used to address the object property which has the focus in
runtime.
Address
Description
Defines the Web address which is opened in the HTML browser.
Access during runtime: Read and Write
Syntax
Object.Address [=STRING]
Object
Required. An object of the "HTMLBrowser" type.
STRING
Optional. A value or constant which contains the Web address.
See also
HTMLBrowser (Page 1598)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1638 System Manual, 08/2011,
AllowMenu
Description
Establishes whether the shortcut menu should be enabled to control the Sm@rtClient view.
Syntax
Object.AllowMenu
Object
Required A "ScreenItem" object with the format "SmartClientView".
See also
SmartClientView (Page 1618)
AngleMax
Description
Specifies the angle of the scale end of the "Gauge" object.
Access in Runtime: Read and write
Syntax
Object.AngleMax[= DOUBLE]
Object
Required A "ScreenItem" object with the format "Gauge".
DOUBLE
Optional A value or a constant that specifies the angle in degrees.
Comments
The start and end of the scale gradations are described with the properties "AngleMin" and
"AngleMax" in angle degrees.
The value of the AngleMin property must always be less than the value of the AngleMax
property. The zero degree angle is located at the 3 oclock position on the scale. Positive angle
values are counted clockwise.
See also
Gauge (Page 1593)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1639
AngleMin
Description
Specifies the angle of the scale start of the "Gauge" object.
Access in Runtime: Read and write
Syntax
Object.AngleMin[= DOUBLE]
Object
Required A "ScreenItem" object with the format "Gauge".
DOUBLE
Optional A value or a constant that specifies the angle in degrees.
Comments
The start and end of the scale gradations are described with the properties "AngleMin" and
"AngleMax" in angle degrees.
The value of the AngleMin property must always be less than the value of the AngleMax
property.
The zero degree angle is located at the 3 oclock position on the scale. Positive angle values
are counted clockwise.
See also
Gauge (Page 1593)
BackColor
Description
Determines the background color of the given object.
Access during runtime: Read and Write
Syntax
Object.BackColor [= Color]
Object
Required An object of type "ScreenItem" with the characteristic "Line", "Polyline", "Ellipse",
"Circle", "Rectangle", "Polygon", "TextField", "IOField", "SymbolicIOField", "Button", "Switch",
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1640 System Manual, 08/2011,
"GraphicIOField", "GraphicView", "Bar", "RecipeView", "StatusForce", "Gauge", "Slider",
"SymbolLibrary", "TrendView", "MessageView" or "UserView" or an object of type "Screen".
Color
Optional A value or constant which determines the background color.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
The background color is not visible if the "BorderStyle" property has the value of "0."
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1641
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Gauge (Page 1593)
FunctionTrendControl (Page 1591)
Button (Page 1581)
BackFillStyle
Description
Determines the fill style of the specified object.
Access during runtime: Read and Write
Syntax
Object.BackFillStyle [= THmiFillStyle]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1642 System Manual, 08/2011,
Object
Required. An object of the "ScreenItem" type with the characteristic "Ellipse," "Circle",
"Rectangle" or "Polygon".
THmiFillStyle
Optional. A value or constant which determines the fill style.
hmiFillStyleTransparent (65536): Transparent fill
hmiFillStyleTransparent (0): Object is filled with the specified color
Default setting: Solid
See also
Ellipse (Page 1589)
Circle (Page 1583)
Polygon (Page 1606)
Rectangle (Page 1614)
BarBackColor
Description
Specifies the color of the bar background for the selected object.
Access during runtime: Read and write
Syntax
Object.BarBackColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "Bar," or "Slider".
Color
Optional A value or a constant that specifies the color of the bar background.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1643
See also
Bar (Page 1578)
Slider (Page 1615)
BarColor
Description
Specifies the color of the slider in the "Slider" object.
Access during runtime: Read and Write
Syntax
Object.BarColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Slider".
Color
Optional A value or a constant that specifies the color of the slider.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
The range extends from "RangeMin" to the position of the controller.
See also
Slider (Page 1615)
BaseScreenName
Description
Reads the name of the current root screen or triggers a root screen change by setting a new
screen name.
Access in Runtime: Read and write
Syntax
Object.BaseScreenName[= STRING]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1644 System Manual, 08/2011,
Object
Required An "HMIRuntime" object.
STRING
Optional A value or a constant that contains the screen name.
Comments
You can also use the property to establish which screen is currently being displayed.
BelowLowerLimitColor
Description
Defines the color of the specified object for the case "Low limit exceeded".
BlinkColor
Description
Specifies the color in which the "SymbolLibrary" object will flash.
Access during runtime: Read and Write
Syntax
Object.BlinkColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "SymbolLibrary".
Color
Optional A value or a constant that specifies the flash color.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
SymbolLibrary (Page 1625)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1645
BorderBrightColor3D
Description
Determines the frame color of the following frame parts in the 3D display of the given object:
Outer frame parts above and below
Inner frame parts below and right
Access during runtime: Read and Write
Syntax
Object.BorderBrightColor3D [= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Slider".
Color
Optional A value or constant which determines the frame color. Default setting is white.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
Slider (Page 1615)
BorderColor
Description
Determines the line color of the given object.
Access during runtime: Read and Write
Syntax
Object.BorderColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "Ellipse", "Circle",
"Rectangle", "Polygon", "TextField", "IOField" or "SymbolicIOField".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1646 System Manual, 08/2011,
Color
Optional A value or constant which determines the line color.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
IOField (Page 1600)
Ellipse (Page 1589)
Circle (Page 1583)
DateTimeField (Page 1587)
Polygon (Page 1606)
Rectangle (Page 1614)
SymbolicIOField (Page 1623)
TextField (Page 1628)
FunctionTrendControl (Page 1591)
BorderInnerWidth3D
Description
Specifies the width of the inner border for the 3D presentation of the selected object.
Access in Runtime: Read and write
Syntax
Object.BorderInnerWidth3D[= LONG]
Object
Required A "ScreenItem" object with the format "Slider".
LONG
Optional A value or a constant that specifies the width in pixels of the inner border.
See also
Slider (Page 1615)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1647
BorderOuterWidth3D
Description
Specifies the width of the outer border for the 3D presentation of the selected object.
Access in Runtime: Read and write
Syntax
Object.BorderOuterWidth3D[= LONG]
Object
Required A "ScreenItem" object with the format "Slider".
LONG
Optional A value or a constant that specifies the width in pixels of the outer border.
See also
Slider (Page 1615)
BorderShadeColor3D
Description
Determines the frame color of the following frame parts in the 3D display of the given object:
Inner frame parts above and below
Outer frame parts below and right
Access during runtime: Read and Write
Syntax
Object.BorderShadeColor3D [= Color]
Object
Required. An object of the "ScreenItem" type with the characteristic "Slider."
Color
Optional. A value or constant which determines the shade color. Default setting is
Remarks
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the corresponding decimal values (value range from 0 to 255) for each of the
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1648 System Manual, 08/2011,
three RGB values. For example, the color "red" is represented as follows: RGB(255, 0, 0).
Furthermore, you can use the VBS color constants such as vbRedor vbGreen.
See also
Slider (Page 1615)
BorderStyle3D
Description
Determines whether the given object has 3D border shading.
Access during runtime: Read and Write
Syntax
Object.BorderStyle3D [= BOOLEAN]
Object
Required. An object of the type "ScreenItem" with the characteristic "TextField", "IOField",
"SymbolicIOField", "Button", "Switch", "GraphicView", "GraphicIOField" or "Bar".
BOOLEAN
Optional. TRUE, if the object has 3D border shading.
See also
IOField (Page 1600)
Bar (Page 1578)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
Switch (Page 1621)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Button (Page 1581)
BorderWidth
Description
Determines the LineWidth of the given object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1649
Access during runtime: Read and Write
Syntax
Object.BorderWidth [= LONG]
Object
Required. An object of the type "ScreenItem" with the characteristic "Ellipse", "Circle", "Gauge",
"Rectangle", "Polygon" or "TextField".
LONG
Optional. A value or constant which determines the line width in pixels.
See also
Ellipse (Page 1589)
Circle (Page 1583)
Polygon (Page 1606)
Rectangle (Page 1614)
Slider (Page 1615)
SymbolicIOField (Page 1623)
TextField (Page 1628)
FunctionTrendControl (Page 1591)
Caption
Description
Determines the text which is displayed in the caption line of the given object.
Access during runtime: Read and Write
Syntax
Object.Caption [= STRING]
Object
Required. An object of the "ScreenItem" type with the characteristic "Slider."
STRING
Optional. A value or a constant which contains the text which is displayed in the caption.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1650 System Manual, 08/2011,
See also
Slider (Page 1615)
FunctionTrendControl (Page 1591)
CaptionColor
Description
Determines the color of the text which is displayed in the title bar of the given object.
Access during runtime: Read and Write
Syntax
Object.CaptionColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "Switch," or "Gauge".
Color
Optional A value or constant which determines the text color.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
Switch (Page 1621)
Gauge (Page 1593)
CaptionText
Description
Specifies the text that will be displayed in the title line of the selected object.
Access in Runtime: Read and write
Syntax
Object.CaptionText[= STRING]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1651
Object
Required A "ScreenItem" object with the formats "Switch" or "Gauge".
STRING
Optional A value or a constant that contains the text that will be shown in the title line.
See also
Switch (Page 1621)
Gauge (Page 1593)
CenterColor
Description
Specifies the color of the center of the "Gauge" object.
Access during runtime: Read and Write
Syntax
Object.CenterColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Gauge".
Color
Optional A value or a constant that specifies the color of the center.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Gauge (Page 1593)
Closable
Description
Specifies whether the window can be closed in Runtime.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1652 System Manual, 08/2011,
Access in Runtime: Read and write
Syntax
Object.Closable[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "UserArchiveControl".
BOOLEAN
Optional TRUE, if the window can be closed in Runtime.
See also
FunctionTrendControl (Page 1591)
Color
Description
Determines the line color of the given object.
Access during runtime: Read and Write
Syntax
Object.Color [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "Line," or "Polyline".
Color
Optional A value or constant which determines the line color.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
Line (Page 1602)
Polyline (Page 1607)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1653
ConnectTrendWindows
Description
Specifies whether the configured trend views are connected. The requirement is that you have
configured several trend views.
The connected trend views have the following properties:
A common X axis
A scrollbar
A ruler
Access in Runtime: Read
Syntax
Object.ConnectTrendWindows[=Boolean]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
Boolean
TRUE = All configured trend views are connected.
FALSE = The trend views are displayed separately.
See also
FunctionTrendControl (Page 1591)
Count
Description
Returns the number of elements in the specified list.
Access in Runtime: Read
Syntax
Object.Count
Object
Required A "Collection" object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1654 System Manual, 08/2011,
CountSubDivisions
Description
Specifies the number of scale marking lengths between two main marking lengths of the "Bar"
object.
Access in Runtime: Read and write
Syntax
Object.CountSubDivisions[= LONG]
Object
Required A "ScreenItem" object with the format "Bar".
LONG
Optional A value or a constant that specifies the number of scale segments.
See also
Bar (Page 1578)
DangerRangeColor
Description
Specifies the color of the danger range of the scale of the "Gauge" object.
The "DangerRangeVisible" property must have the value TRUE so that the danger range is
displayed.
Access during runtime: Read and write
Syntax
Object.DangerRangeColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Gauge".
Color
Optional A value or a constant that specifies the color of the danger range.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1655
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Gauge (Page 1593)
DangerRangeStart
Description
Specifies at which scale value the danger range of the "Gauge" object will start.
The "DangerRangeColor" property must have the value TRUE so that the danger range is
displayed.
Access in Runtime: Read and write
Syntax
Object.DangerRangeStart[= DOUBLE]
Object
Required A "ScreenItem" object with the format "Gauge".
DOUBLE
Optional A value or a constant that specifies the scale value for the start of the danger range.
Comments
The range extends from the value "Gefahr" through to the end of the scale.
See also
Gauge (Page 1593)
DangerRangeVisible
Description
Specifies whether the danger range in the scale of the "Gauge" object will be displayed.
Access in Runtime: Read and write
Syntax
Object.DangerRangeVisible[= BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1656 System Manual, 08/2011,
Object
Required A "ScreenItem" object with the format "Gauge".
BOOLEAN
Optional TRUE, if the danger range will be displayed in the scale.
Comments
Specifies the color of the danger range with the "DangerRangeColor" property.
Specifies the start of the danger range with the "DangerRangeStart" property.
See also
Gauge (Page 1593)
DialColor
Description
Specifies the color of the dial for the selected object.
Access during runtime: Read and Write
Syntax
Object.DialColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "Clock," or "Gauge".
Color
Optional A value or a constant that specifies the color of the dial.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Clock (Page 1585)
Gauge (Page 1593)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1657
EdgeStyle
Description
Determines the line style of the given object.
Access during runtime: Read and Write
Syntax
Object.EdgeStyle [= THmiLineStyle]
Object
Required. An object of the type "ScreenItem" with the characteristic "Ellipse", "Circle",
"Rectangle", "Polygon", "TextField" or "IOField".
THmiLineStyle
Optional. A value or constant that defines the line style. Value range from -1 to 4.
The objects "Ellipse", "Circle", "Rectangle" and "Polygon" support the line style:
hmiLineStyleSolid (0): solid line
hmiLineStyleDash (1): dashed line
hmiLineStyleDot (2): dotted line
hmiLineStyleDashDot (3): dash dot line
hmiLineStyleDashDotDot (4): dash dot dot line
The objects "TextField" and "IOField" support only the line style:
hmiLineStyleNone (-1): no line
hmiLineStyleSolid (0): solid line
Default setting: hmiLineStyleSolid
See also
IOField (Page 1600)
Ellipse (Page 1589)
Circle (Page 1583)
Polygon (Page 1606)
Rectangle (Page 1614)
TextField (Page 1628)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1658 System Manual, 08/2011,
Enabled
Description
Determines whether the given object can be operated in runtime.
Access during runtime: Read and Write
Syntax
Object.Enabled [= BOOLEAN]
Object
Required. An object of the type "ScreenItem" with the characteristic "IOField",
"SymbolicIOField", "Button", "Switch", "GraphicIOField", "Bar", "RecipeView", "StatusForce",
"Slider", "SymbolLibrary", "TrendView", "MessageView", "UserView" or "BrowserView".
BOOLEAN
Optional. TRUE, if the given object can be operated.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1659
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1660 System Manual, 08/2011,
EndStyle
Description
Determines how the line end of the given object is displayed.
Access during runtime: Read and Write
Syntax
Object.EndStyle [= THmiLineEndStyle]
Object
Required. An object of the "ScreenItem" type with the characteristic "Line," or "Polyline".
THmiLineEndStyle
Optional. A value or constant which determines the line end.
hmiLineEndStyleNone (0): The line has no end symbol.
hmiLineEndStyleFilledArrow (2): The line ends with a filled arrow.
See also
Line (Page 1602)
Polyline (Page 1607)
ExportDirectoryChangeable
Description
Enables changing of the directory for data export in Runtime.
Syntax
Object.ExportDirectoryChangeable=[Boolean]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
Boolean
TRUE, the directory for the data export can be changed in Runtime.
FALSE, the directory for the data export cannot be changed in Runtime.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1661
See also
FunctionTrendControl (Page 1591)
ExportDirectoryname
Description
Defines the directory to which the exported Runtime data is written.
Access in Runtime: Read and write
Syntax
Object.ExportDirectoryname[=String]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
String
Optional A value or a constant which specifies the directory.
See also
FunctionTrendControl (Page 1591)
ExportFileExtension
Description
Specifies the file extension of the export file. Only the file extension "csv" is supported.
Syntax
Object.ExportFileExtension
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1662 System Manual, 08/2011,
ExportFilename
Description
Defines the name of the file which is to receive the exported Runtime data.
Syntax
Object.ExportFilename
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
See also
FunctionTrendControl (Page 1591)
ExportFilenameChangeable
Description
Enables renaming of the export file in Runtime.
Syntax
Object.ExportFilenameChangeable=[Boolean]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
Boolean
TRUE, , the file name of the export file can be changed in Runtime.
FALSE, , the file name of the export file cannot be changed in Runtime.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1663
ExportFormatGuid
Description
Default assignment of the ID number and export provider.
Syntax
Object.ExportFormatGuid
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
See also
FunctionTrendControl (Page 1591)
ExportFormatName
Description
Defines the export file format. Only the "csv" file format is currently available for the export.
See also
FunctionTrendControl (Page 1591)
ExportParameters
Description
Specifies the parameters of the selected format by means of the properties dialog.
Access in Runtime: Read and write
Syntax
Object.ExportParameters
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1664 System Manual, 08/2011,
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
See also
FunctionTrendControl (Page 1591)
ExportSelection
Description
Specifies the file extension of the export file. Only the file extension "csv" is supported.
Syntax
Object.ExportSelection=[Boolean]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
Boolean
Value Description Explanation
0 all All Runtime data of the control is exported.
1 Selection Selected Runtime data of the control is exported.
See also
FunctionTrendControl (Page 1591)
ExportShowDialog
Description
Enables the display of the export dialog during runtime.
Access in Runtime: Read and write
Syntax
Object.ExportShowDialog [=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1665
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchivControl", "FunctionTrendControl",
"OnlineTrendControl".
BOOLEAN
Optional TRUE, if the dialog box is shown in Runtime.
.
See also
FunctionTrendControl (Page 1591)
ExportXML
ExportXML
Only used internally.
The attribute can be assigned dynamic properties by means of the name ExportXML.
See also
FunctionTrendControl (Page 1591)
FillStyle
Description
Determines the fill style of the specified object.
Access during runtime: Read and Write
Syntax
Object.FillStyle [= THmiLineFillStyle]
Object
Required. An object of the "ScreenItem" type with the characteristic "Line," or "Polyline".
THmiLineFillStyle
Optional. A value or constant which determines the fill style.
hmiLineFillStyleTransparent (0): Transparent fill
hmiLineFillStyleSolid (1): Object is filled with the specified color
Default setting: hmiLineFillStyleSolid
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1666 System Manual, 08/2011,
See also
Line (Page 1602)
Polyline (Page 1607)
FocusColor
Description
Determines the color for the focus frame of the given object that has the focus.
Access during runtime: Read and Write
Syntax
Object.FocusColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "Button", "Switch",
"GraphicIOField", "RecipeView", "StatusForce", "Slider", "TrendView" or "MessageView".
Color
Optional A value or constant which determines the frame color.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
GraphicIOField (Page 1595)
AlarmView (Page 1604)
RecipeView (Page 1612)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
StatusForce (Page 1619)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1667
FocusWidth
Description
Determines the border width of the given object if the object has a focus.
Access during runtime: Read and Write
Syntax
Object.FocusWidth [= LONG]
Object
Required. An object of type "ScreenItem" with the characteristic "SymbolicIOField", "Button",
"Switch", "GraphicIOField", "RecipeView", "StatusForce", "Slider", "TrendView" or
"MessageView".
LONG
Optional. A value or constant which determines the border width in pixels. Value range from
1 to 10.
See also
GraphicIOField (Page 1595)
AlarmView (Page 1604)
RecipeView (Page 1612)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
StatusForce (Page 1619)
BatteryView (Page 1580)
Button (Page 1581)
Font
Description
Defines or returns the font.
The font object has the following sub-properties
Size (Font Size)
Bold (yes/no)
Name (font name)
Italic (yes/no)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1668 System Manual, 08/2011,
Underline (underline yes/no)
StrikeThrough (yes/no)
If two font properties are directly assigned, only the default property "Name" is assumed.
Access in Runtime: Read and write
Syntax
Object.Font [=Font]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "UserArchiveControl", "MediaPlayer",
"FunctionTrendControl" or "Slider".
Font
Font
Example:
'VBS74
Dim objControl1
Dim objControl2
Set objControl1 = ScreenItems("Control1")
Set objControl2 = ScreenItems("Control2")
objControl2.Font = objControl1.Font ' take over only the type of font
See also
FunctionTrendControl (Page 1591)
Slider (Page 1615)
ForeColor
Description
Determines the text color of the given object.
Access during runtime: Read and Write
Syntax
Object.ForeColor [= Color]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1669
Object
Required An object of the "ScreenItem" type with the characteristics "TextField", "IOField",
"SymbolicIOField", "Button", "Switch", "Bar", "RecipeView", "Slider" or "SymbolLibrary".
Color
Optional A value or constant which determines the text color.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
IOField (Page 1600)
Bar (Page 1578)
DateTimeField (Page 1587)
RecipeView (Page 1612)
Switch (Page 1621)
Slider (Page 1615)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Button (Page 1581)
Gradation
Description
Specifies the value difference between two main marking lengths of the "Gauge" object.
Access in Runtime: Read and write
Syntax
Object.Gradation[= LONG]
Object
Required A "ScreenItem" object with the format "Gauge".
LONG
Optional A value or a constant that specifies the value difference.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1670 System Manual, 08/2011,
See also
Gauge (Page 1593)
GraphDirection
Description
Specifies at which border of the trend view the current values are displayed.
Access in Runtime: Read and write
Syntax
Object.GraphDirection[=Direction]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
Direction
0: Positive values run to the right and upwards.
-1: Positive values run to the left and upwards.
-2: Positive values run to the right and upwards.
-3: Positive values run to the right and downwards.
See also
FunctionTrendControl (Page 1591)
GridLineColor
Color of the row divider / content - GridLineColor
Defines the color of row/column dividers in table contents. The button opens the "Color
selection" dialog.
The attribute can be assigned dynamic properties by means of the name GridLineColor.
See also
AlarmView (Page 1604)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1671
H-P
Height
Description
Specifies the height of the selected objects "Ellipse", "Circle" and "Rectangle".
Access in Runtime: Read and write
The other objects only have read access to the property.
Syntax
Object.Height[= LONG]
Object
Required A "Screen" object or an object of type "ScreenItem". This property is a standard
property of the ScreenItem-Objekts and is therefore available for all formats.
LONG
Optional A value or a constant that specifies the height in pixels. This parameter can be set
only for the objects "Ellipse", "Circle" and "Rectangle".
Example
The following example halves the height of all objects of the image "NewPDL1", whose name
starts with "Circle":
'VBS75
Dim objScreen
Dim objCircle
Dim lngIndex
Dim strName
lngIndex = 1
Set objScreen = HMIRuntime.Screens("NewPDL1")
For lngIndex = 1 To objScreen.ScreenItems.Count
'
'Searching all circles
strName = objScreen.ScreenItems.Item(lngIndex).ObjectName
If "Circle" = Left(strName, 6) Then
'
'to halve the height of the circles
Set objCircle = objScreen.ScreenItems(strName)
objCircle.Height = objCircle.Height / 2
End If
Next
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1672 System Manual, 08/2011,
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1673
HelpText
Description
Returns the tooltip that is shown in Runtime as an operating aid for the specified object.
Access in Runtime: Read
Syntax
Object.HelpText
Object
Required An object of the type "ScreenItem" with the characteristic "IOField",
"SymbolicIOField", "Button", "Switch", "GraphicIOField" or "TrendView".
See also
IOField (Page 1600)
DateTimeField (Page 1587)
GraphicIOField (Page 1595)
TrendView (Page 1630)
Switch (Page 1621)
SymbolicIOField (Page 1623)
Button (Page 1581)
HorizontalAlignment
Description
Determines the horizontal alignment of the text within the given object.
Access during runtime: Read and Write
Syntax
Object.HorizontalAlignment [= THmiHorizontalAlignment]
Object
Required An object of the "ScreenItem" type with the characteristics "TextField", "IOField",
"SymbolicIOField", "Button" or "Switch".
THmiHorizontalAlignment
Optional A value or constant which determines the horizontal alignment of the text.
hmiAlignmentLeft (0): The text is aligned left justified in the object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1674 System Manual, 08/2011,
hmiAlignmentCentered (1): The text is centered horizontally in the object.
hmiAlignmentRight (2): The text is aligned right justified in the object.
See also
IOField (Page 1600)
DateTimeField (Page 1587)
Switch (Page 1621)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Button (Page 1581)
HourNeedleHeight
Description
Specifies the length of the hour hand in the "Clock" object.
Access in Runtime: Read and write
Syntax
Object.HourNeedleHeight[= LONG]
Object
Required A "ScreenItem" object with the format "Clock".
LONG
Optional A value or a constant that specifies the length of the hour hand.
Specify the length of the hour hand as a percentage relating to the radius of the clock face.
See also
Clock (Page 1585)
HourNeedleWidth
Description
Specifies the width of the hour hand in the "Clock" object.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1675
Syntax
Object.HourNeedleWidth[= LONG]
Object
Required A "ScreenItem" object with the format "Clock".
LONG
Optional A value or a constant that specifies the width of the hour hand.
Specify the width of the hour hand as a percentage relating to double the length of the clock
face.
See also
Clock (Page 1585)
InnerBackColorOff
Description
Specifies the color under the slider of the "Switch" object if the object is in OFF status.
Access during runtime: Read and Write
Syntax
Object.InnerBackColorOff[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Switch".
Color
Optional A value or a constant that specifies the color for the OFF status.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Switch (Page 1621)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1676 System Manual, 08/2011,
InnerBackColorOn
Description
Specifies the color under the slider of the "Switch" object if the object is in ON status.
Access during runtime: Read and Write
Syntax
Object.InnerBackColorOn[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Switch".
Color
Optional A value or a constant that specifies the color for the ON status.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Switch (Page 1621)
LabelColor
Description
Specifies the color of the scale label in the "Slider" object.
Access in Runtime: Read and write
Syntax
Object.LabelColor[= Color]
Object
Required A "ScreenItem" object with the format "Slider".
Color
Optional A value or a constant that specifies the color of the scale label.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1677
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
See also
Slider (Page 1615)
Language
Description
Determines the current Runtime language.
Access in Runtime: Read and write
Syntax
Object.Language[= LONG]
Object
Required A "HMIRuntime" object.
LONG
Optional A value or a constant that specifies the national code.
Comments
Specify the Runtime language in VBS with a national code, e.g. 1031 for German, 2057 for
English etc.. Refer to the VBScript basics under the topic "Current local ID (LCID) diagram"
for an overview of all the national codes.
Left
Description
Specifies the value of the X coordinate of the selected object.
Access in Runtime: Read and write
Syntax
Object.Left[= DOUBLE]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1678 System Manual, 08/2011,
Object
Required A "ScreenItem" object. This property is a standard property of the ScreenItem-
Objekts and is therefore available for all formats.
DOUBLE
Optional A value or a constant that contains the value of the X coordinate in pixels (measured
from the top left edge of the screen).
Comments
The X coordinate refers to the top left corner of the rectangle that surrounds the object. The
screen limits are also monitored in Runtime. If the assigned coordinate value exceeds the
display size, the user-defined function is interrupted with an error message.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1679
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1680 System Manual, 08/2011,
LineColor
Description
Specifies the color of the window dividers. The button opens the "Color selection" dialog.
See also
FunctionTrendControl (Page 1591)
LineWidth
Description
Determines the LineWidth of the given object.
Access during runtime: Read and Write
Syntax
Object.LineWidth [= LONG]
Object
Required. An object of the "ScreenItem" type with the characteristic "Line," or "Polyline".
LONG
Optional. A value or constant which determines the line width in pixels.
See also
Line (Page 1602)
Polyline (Page 1607)
FunctionTrendControl (Page 1591)
LoadDataImmediately
Description
Specifies whether in the event of a screen impact the tag values should be downloaded from
the archives for the time range that is to be shown.
Access in Runtime: Read and write
Syntax
Object.LoadDataImmediately[=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1681
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl" or "OnlineTableControl".
BOOLEAN
Optional TRUE, if in the event of a screen impact the tag values should be downloaded from
the archives for the time range that is to be shown.
See also
FunctionTrendControl (Page 1591)
LocalCursor
Description
Establishes whether the cursor data is transferred separately in order to increase the
performance.
Syntax
Object.LocalCursor
Object
Required A "ScreenItem" object with the format "SmartClientView".
MachineName
Description
Specifies the network code of the device that is to be monitored.
Enter the name or the port of the device as the network code.
Access in Runtime: Read and write
Syntax
Object.MachineName= [STRING]
Object
Required A "ScreenItem" object with the format "SmartClientView".
STRING
Optional A value or a constant that contains the network code.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1682 System Manual, 08/2011,
See also
SmartClientView (Page 1618)
MaximumValue
Description
Determines the maximum value of the scale in the given object.
Access during runtime: Read and Write
Syntax
Object.MaximumValue [= DOUBLE]
Object
Required. An object of the type "ScreenItem" with the characteristic "Bar", "Gauge" or "Slider".
DOUBLE
Optional. A value or constant which determines the maximum value.
See also
Bar (Page 1578)
Slider (Page 1615)
Gauge (Page 1593)
MinimumValue
Description
Determines the minimum value of the scale in the given object.
Access during runtime: Read and Write
Syntax
Object.MinimumValue [= DOUBLE]
Object
Required. An object of the type "ScreenItem" with the characteristic "Bar", "Gauge" or "Slider".
DOUBLE
Optional. A value or constant which determines the minimum value.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1683
See also
Bar (Page 1578)
Slider (Page 1615)
Gauge (Page 1593)
MinuteNeedleHeight
Description
Specifies the length of the minute hand in the ""Clock" object.
Access in Runtime: Read and write
Syntax
Object.MinuteNeedleHeight[= LONG]
Object
Required A "ScreenItem" object with the format "Clock".
LONG
Optional A value or a constant that specifies the length of the minute hand.
Specify the length of the minute hand as a percentage relating to the radius of the clock face.
See also
Clock (Page 1585)
MinuteNeedleWidth
Description
Specifies the width of the minute hand in the "Clock" object.
Access in Runtime: Read and write
Syntax
Object.MinuteNeedleWidth[= LONG]
Object
Required A "ScreenItem" object with the format "Clock".
LONG
Optional A value or a constant that specifies the width of the minute hand.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1684 System Manual, 08/2011,
Specify the width as a percentage relating to double the length of the minute hand.
See also
Clock (Page 1585)
Movable
Description
Specifies whether the window can be moved in Runtime.
Access in Runtime: Read and write
Syntax
Object.Movable[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "UserArchiveControl".
BOOLEAN
Optional. TRUE, if the window can be moved in Runtime.
See also
FunctionTrendControl (Page 1591)
NeedleBorderColor
Description
Specifies the line color of the pointer in the ""Clock"" object.
Access in Runtime: Read and write
Syntax
Object.NeedleBorderColor[= Color]
Object
Required A "ScreenItem" object with the format "Clock".".
Color
Optional A value or a constant that specifies the line color of the pointer.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1685
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen .
See also
Clock (Page 1585)
NeedleColor
Description
Specifies the hand color of the "Clock" object.
You must have configured the "NeedleFillStyle" property as "Transparent" for the pointer color
to be shown.
Access in Runtime: Read and write
Syntax
Object.NeedleColor[= Color]
Object
Required A "ScreenItem" object with the format "Clock".".
Color
Optional A value or a constant that specifies the pointer color.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
See also
Clock (Page 1585)
NormalRangeColor
Description
Specifies the color of the normal range on the scale of the "Gauge" object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1686 System Manual, 08/2011,
The "NormalRangeVisible" property must have the value TRUE so that the normal range is
displayed.
Access during runtime: Read and write
Syntax
Object.NormalRangeColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Gauge".
Color
Optional A value or a constant that specifies the color of the normal range.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Gauge (Page 1593)
NormalRangeVisible
Description
Specifies whether the normal range in the scale of the ""Gauge" object will be displayed.
Access in Runtime: Read and write
Syntax
Object.NormalRangeVisible[= BOOLEAN]
Object
Required A "ScreenItem" object with the format "Gauge".
BOOLEAN
Optional TRUE, if the normal range will be displayed in the scale.
Comments
Specify the color of the normal range with the ""NormalRangeColor" property.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1687
See also
Gauge (Page 1593)
Object
Description
If you use a Control that is not a standard WinCC control, it could be that the properties provided
by the Control have the same names as the general ScreenItem properties. In this case, the
ScreenItem properties take priority. You can access the "hidden" properties of an outside
provider Controls via the additional ""object" property.
Syntax
Object.Object
Object
Required A "ScreenItem" object with the format ""ForeignControl".
Application example
To do this, address the properties of an outside provider control in the following way:
Control.object.type
If you are using only the form Control.type, the properties of the ScreenItem object will be used
in case of identical names.
ObjectName
Description
Returns the name of the specified object.
Access in Runtime: Read
Syntax
Object.ObjectName
Object
Required A "ScreenItem" object. This property is a standard property of the ScreenItem object
and is therefore available for all formats.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1688 System Manual, 08/2011,
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1689
Online
Description
Specifies start and stop of the updating.
Access in Runtime: Read and write
Syntax
Object.Online[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl" or "OnlineTableControl".
BOOLEAN
Optional TRUE, if the updated display should be stopped. The values are stored in the cache
and when the button is reactivated they are added . FALSE, if the updated display is to be
continued.
See also
FunctionTrendControl (Page 1591)
Parent
Description
Returns the screen in which the specified object is embedded.
Access in Runtime: Read
Syntax
Object.Parent
Object
Required A "ScreenItem" object. This property is a standard property of the ScreenItem object
and is therefore available for all formats.
Application example
The following example writes the name of the root screen in "BaseScreenName" tag:
'VBS_Example_Parent
Dim objScrItem, BaseScreenName
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1690 System Manual, 08/2011,
Set objScrItem = HMIRuntime.Screens(1).ScreenItems(1)
BaseScreenName = "Name of BaseScreen: " & objScrItem.Parent.ObjectName
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1691
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1692 System Manual, 08/2011,
Password
Description
Determines the password for the loading of the remote monitor.
Access during runtime: Read and Write
Syntax
Object.Password = [STRING]
Object
Required. An object of the "ScreenItem" type with the characteristic "SmartClientView."
STRING
Optional. A value or constant which contains the password.
See also
SmartClientView (Page 1618)
PointerColor
Description
Specifies the pointer color of the "Gauge" object.
Access during runtime: Read and Write
Syntax
Object.PointerColor[= Color]
Object
Required An object of the ""ScreenItem" type with the characteristic "Gauge".
Color
Optional A value or a constant that specifies the pointer color.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1693
See also
Gauge (Page 1593)
PrintJobName
Description
Defines the print job triggered by the print function of the "Print" toolbar button. The
recommended print job is set for the control by default.
Open the "Select Print Job" dialog using the selection button.
Syntax
Object.PrintJobName]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"FunctionTrendControl", "OnlineTableControl", "OnlineTrendControl", "TrendRulerControl",
"UserArchiveControl".
See also
FunctionTrendControl (Page 1591)
Processvalue
Description
Defines the presetting for the value to be displayed.
This value is used in runtime when a screen is started and the associated tag has not been
connected nor updated.
Access during runtime: Read and Write
Syntax
Object.Processvalue [=DOUBLE]
Object
Required. An object of the "ScreenItem" type with the characteristic "Bar," "Gauge", "IOField"
or "Slider".
DOUBLE
Optional. A value or constant which contains preset the Web address.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1694 System Manual, 08/2011,
Remarks
To assign SmartTags to the "ProcessValue" property, you must formulate the assignment as
follows:
Examples of the assignment of SmartTags
'Example 1
IOField.ProcessValue = SmartTags("TagName").Value
'Example 2
HmiRuntime.Screens("Screen_1").ScreenItems("IOField_1").ProcessValue
= SmartTags("Tag_1").Value
See also
IOField (Page 1600)
Bar (Page 1578)
Slider (Page 1615)
Gauge (Page 1593)
RTPersistence
Description
Specifies how online configurations of WinCC are retained.
Syntax
Object.RTPersistence[=RTPersistence]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"OnlineTrendControl", "TrendRulerControl" or "OnlineTableControl".
RTPersistence
Value Description Explanation
0 Discard The current online configurations are discarded at the next picture change.
1 Retain The current online configurations are retained at the next picture change.
2 Reset All online configurations made are lost. The picture is set to the contents
found in the configuration system.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1695
RTPersistencePasswordLevel
Description
Displays the authorization for online configuration. You can edit the authorization using the
selection button. Authorizations are configured in the user administration.
Syntax
Object.RTPersistencePasswordLevel
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"OnlineTrendControl", "TrendRulerControl" or "OnlineTableControl".
See also
FunctionTrendControl (Page 1591)
RTPersistenceType
Description
Defines how to retain online configurations of WinCC.
Syntax
Object.RTPersistenceType[=RTPersistenceType]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"OnlineTrendControl", "TrendRulerControl" or "OnlineTableControl".
RTPersistenceType
Value Description Explanation
0 Do not retain Online configurations are not retained. These are lost at
the next picture change.
1 Retain during runtime Online configurations are retained during runtime. These
are lost on exiting.
2 Retain permanently Online configurations are retained permanently. These
are also available after restart.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1696 System Manual, 08/2011,
R-S
Radius
Description
Determines the radius of the given object "Circle."
Access during runtime: Read and Write
Syntax
Object.Radius [= LONG]
Object
Required. An object of the "ScreenItem" type with the characteristic "Circle".
LONG
Optional. A value or constant which determines the radius in pixels.
See also
Circle (Page 1583)
RadiusHeight
Description
Determines the secondary axis of the object "Ellipse".
Access during runtime: Read and Write
Syntax
Object.RadiusHeight
Object
Required. An object of the "ScreenItem" type with the characteristic "Ellipse."
LONG
Optional. A value or constant which determines the secondary axis in pixels.
See also
Ellipse (Page 1589)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1697
RadiusWidth
Description
Determines the main axis of the object "Ellipse".
Access during runtime: Read and Write
Syntax
Object.RadiusWidth
Object
Required. An object of the "ScreenItem" type with the characteristic "Ellipse."
LONG
Optional. A value or constant which determines the main axis in pixels.
See also
Ellipse (Page 1589)
RecipeName
Description
Returns the name of the recipe that is currently being displayed in the "RecipeView".
Access in Runtime: Read
Syntax
Object.RecipeName
Object
Required A "ScreenItem" object with the format "RecipeView".
See also
RecipeView (Page 1612)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1698 System Manual, 08/2011,
RecipeNumber
Description
Returns the number of the recipe that is currently being displayed in the "RecipeView".
Access in Runtime: Read
Syntax
Object.RecipeNumber
Object
Required A "ScreenItem" object with the format "RecipeView"".
See also
RecipeView (Page 1612)
RecordName
Description
Returns the name of the recipe data record that is currently being displayed in the
"RecipeView".
Access in Runtime: Read
Syntax
Object.RecordName
Object
Required A "ScreenItem" object with the formats "RecipeView" or "PrintRecipe".
See also
RecipeView (Page 1612)
RecordNumber
Description
Returns the number of the recipe data record that is currently being displayed in the
"RecipeView".
Access in Runtime: Read
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1699
Syntax
Object.RecordNumber
Object
Required A "ScreenItem" object with the format "RecipeView".
See also
RecipeView (Page 1612)
RulerColor
Description
Specifies the color of the scale gradation (help line) of the axis label in the "OnlineTrendControl"
object.
Access during runtime: Read and Write
Syntax
Object.RulerColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "OnlineTrendControl".
Color
Optional A value or a constant that specifies the color of the scale gradation.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
TrendView (Page 1630)
ScaleColor
Description
Specifies the color of the scale of the selected object.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1700 System Manual, 08/2011,
Syntax
Object.ScaleColor[= Color]
Object
Required An object of type"ScreenItem" with the formats "Bar" or "OnlineTrendControl".
Color
Optional A value or a constant that specifies the color of the scale.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
ScreenItem object with the format "Bar": For the color to be displayed, the property
""ShowScale" must have the value TRUE.
See also
Bar (Page 1578)
TrendView (Page 1630)
ScaleDenumerator
Description
Defines the counter for scaling on the client.
Syntax
Object.ScaleDenumerator=[Int]
Object
Required A "ScreenItem" object with the format "SmartClientView".
Int
Optional A value or a constant that specifies the value.
ScaleGradation
Description
Specifies the distance between two large marking lengths of the scale.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1701
Access in Runtime: Read and write
Syntax
Object.ScaleGradation[=Double]
Object
Required A "ScreenItem" object with the format "Bar".
Double
Optional A value or a constant that specifies the distance between two large marking lengths
of the scale.
See also
Bar (Page 1578)
ScaleLabelColor
Description
Specifies the color of the label for the scale gradation of the "Gauge" object.
Access during runtime: Read and Write
Syntax
Object.ScaleLabelColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Gauge".
Color
Optional A value or a constant that specifies the label color of the scale gradation.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Gauge (Page 1593)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1702 System Manual, 08/2011,
ScaleNumerator
Description
Defines the counter for scaling on the client.
Syntax
Object.ScaleNumerator =[Int]
Object
Required A "ScreenItem" object with the format "SmartClientView".
Int
Optional A value or a constant that specifies the value.
ScaleTickColor
Description
Specifies the color of the scale gradation of the "Gauge" object.
Access in Runtime: Read and write
Syntax
Object.ScaleTickColor[= Color]
Object
Required A "ScreenItem" object with the format "Gauge".
Color
Optional A value or a constant that specifies the color of the scale gradation.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
See also
Gauge (Page 1593)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1703
ScreenItems
Description
Returns the ScreenItems list.
Access in Runtime: Read
Syntax
Object.ScreenItems
Object
Required A "ScreenItems"." object.
Screens
Description
Returns the Screens list. The Screens list contains two elements: The first element with the
index 0 represents the permanent window. The second element with the index 1 represents
the root screen. Alternatively, the two elements can be addressed by means of their names.
Use "Overview" for the permanent window and "Base" for the root screen.
Note
The alarm window and the alarm indicator are not contained in the Screens list, even if they
have the focus in Runtime.
Access in Runtime: Read
Syntax
Object.Screens
Object
Required A "Screens" object.
SecondNeedleHeight
Description
Specifies the length of the second hand in the "Clock" object.
Access in Runtime: Read and write
Syntax
Object.SecondNeedleHeight[= LONG]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1704 System Manual, 08/2011,
Object
Required A ""ScreenItem" object with the format "Clock".
LONG
Optional A value or a constant that specifies the length of the second hand.
Specify the length of the second hand as a percentage relating to the radius of the clock face.
See also
Clock (Page 1585)
SecondNeedleWidth
Description
Specifies the width of the second hand in the "Clock" object.
Access in Runtime: Read and write
Syntax
Object.SecondNeedleWidth[= LONG]
Object
Required An object of the type "ScreenItem" with the definition "Clock".
LONG
Optional A value or a constant that specifies the width of the second hand. Specify the width
as a percentage relating to double the length of the second hand.
See also
Clock (Page 1585)
SegmentColoring
Description
Specifies the type of color change that should be displayed in the "Bar" if the limits are
exceeded.
Access in Runtime: Read and write
Syntax
Object.SegmentColoring[= THmiBarColorType]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1705
Object
Required A "ScreenItem" object with the format "Bar".
THmiBarColorType
Optional A value or a constant that specifies the type of color change. Value range from 0 to
1.
hmiBarColorEntire (0): Color change applied to the entire bar.
hmiBarColorSegmented (1): Color change applied to segments.
See also
Bar (Page 1578)
SelectionBackColor
Description
Determines the background color of the selected cells.
Access during runtime: Read and Write
Syntax
Object.SelectionBackColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView,"
"StatusForce", "MessageView" or "UserView".
Color
Optional A value or constant which determines the background color of the selected row.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
AlarmView (Page 1604)
UserView (Page 1632)
RecipeView (Page 1612)
StatusForce (Page 1619)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1706 System Manual, 08/2011,
SelectionForeColor
Description
Determines the foreground color of the selected cells.
Access during runtime: Read and Write
Syntax
Object.SelectionForeColor
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView,"
"StatusForce", "MessageView" or "UserView".
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
AlarmView (Page 1604)
UserView (Page 1632)
RecipeView (Page 1612)
ServerScale
Description
Establishes whether the Sm@rtClient view should be zoomed in or out.
Syntax
Object.ServerScale =[Int]
Object
Required A "ScreenItem" object with the format "SmartClientView".
Int
Optional A value or a constant that specifies the value.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1707
Shared
Description
Specifies that an HMI device is shared by several Sm@rtClient Views.
Syntax
Object.Shared[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "SmartClientView".
ShowAlarmsFromDate
Description
Specifies that only those message events are displayed that are saved in this tag.
Access in Runtime: Read and write
Syntax
Object.ShowAlarmsFromDate[=Tag]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl".
Tag
Optional A value or a constant which specifies that only those message events are displayed
that are saved in this tag.
See also
AlarmView (Page 1604)
ShowBar
Description
Specifies whether the displayed process value in the "Slider" object is also shown by a filled
bar.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1708 System Manual, 08/2011,
Syntax
Object.ShowBar
Object
Required A "ScreenItem" object with the format "Slider".
Optional TRUE, if the process value is also shown by a filled bar.
See also
Slider (Page 1615)
ShowInputControls
Description
Establishes whether additional fields exist for entering the address and password.
Syntax
Object.ShowInputControls
Object
Required A "ScreenItem" object with the format "SmartClientView".
ShowMessagesAtDate
Description
Determines at which time the alarms will be displayed.
Note
This function does not filter out alarms, it positions the display range of the alarm list as of
the specified date.
Access during runtime: Read and Write
Syntax
Object.ShowMessagesAtDate [= DATE]
Object
Required. An object of the "MessageView" type.
Remarks
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1709
To assign SmartTags to the "ShowMessagesAtDate" property, you must formulate the
assignment as follows:
'Example 1
HmiRuntime.Screens("Screen_1").ScreenItems("Alarm
view_1").ShowMessagesAtDate = SmartTags("intern_1").Value
'Example 2
HmiRuntime.Screens("Screen_1").ScreenItems("Alarm
view_1").ShowMessagesAtDate = CDate(SmartTags("intern_1"))
SmartTag "intern_1" must be of the "DateTime" type.
See also
AlarmView (Page 1604)
ShowPeakValuePointer
Description
Determines whether a pointer for the given object is to be used.
The pointer shows the maximum hand deflection in runtime as long as the process screen is
loaded. When you reload the process screen, the pointer is reset.
Access during runtime: Read and Write
Syntax
Object.ShowPeakValuePointer [= BOOLEAN]
Object
Required. An object of the "ScreenItem" type with the characteristic "Gauge".
BOOLEAN
Optional. TRUE, if the pointer is used.
See also
Gauge (Page 1593)
ShowPosition
Description
Specifies whether the value of the current slider position should also be displayed numerically.
The value is then displayed beneath the slider.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1710 System Manual, 08/2011,
Access in Runtime: Read and write
Syntax
Object.ShowPosition[= BOOLEAN]
Object
Required A "ScreenItem" object with the format "Slider".
BOOLEAN
Optional TRUE, if the value is also shown.
See also
Slider (Page 1615)
ShowRuler
Description
Determines whether a scale gradation (help lines) is expanded for the axis label of the object
"TrendView".
Access during runtime: Read and Write
Syntax
Object.ShowRuler [= BOOLEAN]
Object
Required. An object of the "ScreenItem" type with the characteristic "TrendView".
BOOLEAN
Optional. TRUE, if the scale gradation is shown.
See also
TrendView (Page 1630)
FunctionTrendControl (Page 1591)
ShowRulerInAxis
Description
Enables the display of rulers in the time axis.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1711
Access in Runtime: Read and write
Syntax
Object.ShowRulerInAxis[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
BOOLEAN
TRUE: The rulers are also displayed in the time axes.
FALSE: The rulers are not displayed in the time axes.
See also
FunctionTrendControl (Page 1591)
ShowScrollbars
Description
Scroll bars - ShowScrollbars
Enables the display of scroll bars.
Access in Runtime: Read and write
Syntax
Object.ShowScrollbars[=ShowScrollbars]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
ShowScrollbars
Value Description Description
0 no The display of scroll bars is disabled.
1 as required Scroll bars are displayed if space requirements of the control are greater
than the actual display area.
2 always The scroll bars are always displayed.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1712 System Manual, 08/2011,
ShowTableGridlines
Description
Determines whether gridlines are shown in the table of the given object.
Access during runtime: Read and Write
Syntax
Object.ShowTableGridlines [= BOOLEAN]
Object
Required. An object of the "ScreenItem" type with the characteristic "StatusForce".
BOOLEAN
Optional. TRUE, if gridlines are displayed.
See also
StatusForce (Page 1619)
ShowThumb
Description
Specifies whether the slider of the "Slider" object will be displayed.
Access in Runtime: Read and write
Syntax
Object.ShowThumb[= BOOLEAN]
Object
Required A "ScreenItem" object with the format "Slider".
BOOLEAN
Optional TRUE, if the slider is shown.
See also
Slider (Page 1615)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1713
ShowTickLabels
Description
Specifies whether the label is shown in the scale.
Access in Runtime: Read and write
Syntax
Object.ShowTickLabels[= BOOLEAN]
Object
Required A "ScreenItem" object with the formats "Bar" or "Slider".
BOOLEAN
Optional TRUE, if the label is shown.
Comments
The increments for the measured value are automatically established dependent upon the
specified measurement range and the size of the object.
See also
Slider (Page 1615)
ShowTicks
Description
Specifies whether the marking lengths are shown in the scale of the selected object.
Access in Runtime: Read and write
Syntax
Object.ShowTicks[= BOOLEAN]
Object
Required A "ScreenItem" object with the formats "Clock" or "Slider".
BOOLEAN
Optional TRUE, if the marking lengths are shown.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1714 System Manual, 08/2011,
See also
Slider (Page 1615)
Clock (Page 1585)
ShowTitle
Description
Defines representation the Control window header.
Access in Runtime: Read and write
Syntax
Object.ShowTitle[=WindowHeaderStyle]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl", "UserArchiveControl",
"TrendRulerControl".
WindowHeaderStyle
Value Designation Description
0 No No window title.
1 Normal The window title consists of a WinCC icon and text. The text is entered in the
"Text" field.
2 Narrow The window title consists only of text. The text is entered in the "Text" field.
See also
FunctionTrendControl (Page 1591)
ShowTrendIcon
Description
Enables the display of an icon below the value axes. The icon indicates the trend currently
displayed in the foreground.
Access in Runtime: Read and write
Syntax
Object.ShowTrendIcon[=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1715
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
BOOLEAN
TRUE: The icon is displayed.
FALSE: The icon is not displayed.
See also
FunctionTrendControl (Page 1591)
SkinName
Description
The control style can be defined in this selection field.
Access in Runtime: Read and write
Syntax
Object.SkinName[=SkinName]
Object
Required An object of the "ScreenItem" type with the format "MessageView",
"OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl", "RecipeView",
"RulerControl".
SkinName
The following settings are available:
Value Designation Description
Project setting The style corresponds to the project settings in WinCC
Explorer.
0 Classic "Classic" WinCC style
1 Standard New WinCC V7 style
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1716 System Manual, 08/2011,
SmartTags
Description
Returns the SmartTags list.
Access in Runtime: Read
Syntax
Object.SmartTags
Object
Required A ""HMIRuntime" object.
SortByTimeDirection
Description
Specifies whether the last incoming message is shown at the top of the "AlarmControl" object
(ascending sorting order).
Access in Runtime: Read and write
Syntax
Object.SortByTimeDirection[= BOOLEAN]
Object
Required A "ScreenItems" object with the format "AlarmControl".
BOOLEAN
Optional TRUE, if the last incoming alarm is shown at the top.
See also
AlarmView (Page 1604)
SortByTimeEnable
Description
Specifies whether the sorting direction can be altered in Runtime.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1717
Syntax
Object.SortByTimeEnable[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl".
BOOLEAN
Optional TRUE, if the sorting direction can be altered in Runtime.
See also
AlarmView (Page 1604)
SortTimeAscending
Description
Determines whether the last message received is displayed on top (ascending sorting order)
in the "MessageView" object.
Access during runtime: Read and Write
Syntax
Object.SortTimeAscending [= BOOLEAN]
Object
Required. An object of the "MessageView" type.
BOOLEAN
Optional. TRUE, if the last message received is displayed on top.
SortTimeEnable
Description
Determines whether the sorting of messages can be changed according to time in the
"MessageView" object.
Access during runtime: Read and Write
Syntax
Object.SortTimeEnable [= BOOLEAN]
Object
Required. An object of the "MessageView" type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1718 System Manual, 08/2011,
BOOLEAN
Optional. TRUE, if the sorting can be changed by the operator on the device.
StartStyle
Description
Determines how the line start of the given object is displayed.
Access in Runtime: Read and write
Syntax
Object.StartStyle [= THmiLineEndStyle]
Object
Required An object of the "ScreenItem" type with the characteristic "Line," or "Polyline".
THmiLineEndStyle
Optional A value or constant which determines the line start. Value range from 0 to 2.
hmiLineEndStyleNone (0): The line has no start symbol.
hmiLineEndStyleFilledArrow (2): The line starts with a filled arrow.
See also
Line (Page 1602)
Polyline (Page 1607)
StatusbarBackColor
Description
Defines the background color of the status bar. You open a color selection dialog box with the
button. Enable the "Display" option to active the setting.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1719
StatusbarElementAdd
Description
Defines a new, user-defined status bar element. You can change the name assigned by WinCC
in the "Object name" field.
See also
FunctionTrendControl (Page 1591)
StatusbarElementAutoSize
Description
Enables autosizing of the width of a status bar element selected.
Access in Runtime: Read and write
Syntax
Object.StatusbarElementAutoSize
Object
Required An object of the "ScreenItem" type with the format "MessageView",
"OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl", "RecipeView",
"RulerControl".
BOOLEAN
TRUE: The width of the selected element is set automatically.
FALSE: The width of the selected element is not set automatically.
.
See also
FunctionTrendControl (Page 1591)
StatusbarElementCount
Description
Defines the number of configurable status bar elements.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1720 System Manual, 08/2011,
StatusbarElementIconId
Description
Default assignment of the ID number and icon of a status bar element.
The property can be dynamized for customized elements of the status bar with the
StatusbarElementIconId name.
See also
FunctionTrendControl (Page 1591)
StatusbarElementID
Description
Unique ID of the status bar element selected. WinCC sets this read only ID.
See also
FunctionTrendControl (Page 1591)
StatusbarElementIndex
Description
References a status bar element. You can assign the values of other properties to a specific
element of the status bar by using this property.
Values between 0 and "StatusbarElementCount" minus 1 are valid for
"StatusbarElementIndex". Attribute "StatusbarElementCount" defines the number of
configurable status bar elements.
See also
FunctionTrendControl (Page 1591)
StatusbarElementName
Description
Displays the object name of the status bar element selected. You can rename the objects of
custom status bar elements. The "StatusbarElementName" property for customized elements
can be dynamized by the " StatusbarElementRename" property.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1721
See also
FunctionTrendControl (Page 1591)
StatusbarElementRemove
Description
Removes the selected status bar element. Only customized elements of the status bar can be
removed from the list.
See also
FunctionTrendControl (Page 1591)
Style
Description
Determines the line style of the given object.
Access during runtime: Read and Write
Syntax
Object.Style [= THmiLineStyle]
Object
Required. An object of the "screen item" type with the characteristic "Line," or "Polyline".
THmiLineStyle
Optional. A value or constant that defines the line style. Value range from 0 to 4.
hmiLineStyleSolid (0): solid line
hmiLineStyleDash (1): dashed line
hmiLineStyleDot (2): dotted line
hmiLineStyleDashDot (3): dash dot line
hmiLineStyleDashDotDot (4): dash dot dot line
Default setting: hmiLineStyleSolid
See also
Line (Page 1602)
Polyline (Page 1607)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1722 System Manual, 08/2011,
T-TrendR
TableBackColor
Description
Determines the background color of the table cells of the given object.
Access during runtime: Read and Write
Syntax
Object.TableBackColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView",
"StatusForce", "TrendView", "MessageView" or "UserView".
Color
Optional A value or constant which determines the background color of the table cells.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
AlarmView (Page 1604)
UserView (Page 1632)
RecipeView (Page 1612)
TrendView (Page 1630)
StatusForce (Page 1619)
TableForeColor
Description
Determines the text color in the table cells of the given object.
Access during runtime: Read and Write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1723
Syntax
Object.TableForeColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView,"
"StatusForce", "MessageView" or "UserView".
Color
Optional A value or constant which determines the text color of the table cells.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
AlarmView (Page 1604)
UserView (Page 1632)
RecipeView (Page 1612)
StatusForce (Page 1619)
TableGridLineColor
Description
Determines the color of the gridlines in the table of the given object.
Access during runtime: Read and Write
Syntax
Object.TableGridLineColor [= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView,"
"MessageView", "TrendView" or "UserView".
Color
Optional A value or constant which determines the color of the gridlines of the table.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1724 System Manual, 08/2011,
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
UserView (Page 1632)
RecipeView (Page 1612)
TrendView (Page 1630)
TableHeaderBackColor
Description
Specifies the background color in the header of the table of the selected object.
Access during runtime: Read and Write
Syntax
Object.TableHeaderBackColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView",
"StatusForce", "TrendView", "MessageView," or "UserView".
Color
Optional A value or a constant that specifies the background color in the header.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
UserView (Page 1632)
RecipeView (Page 1612)
TrendView (Page 1630)
StatusForce (Page 1619)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1725
TableHeaderForeColor
Description
Specifies the text color in the header of the table of the selected object.
Access during runtime: Read and Write
Syntax
Object.TableHeaderForeColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristics "RecipeView",
"StatusForce", "TrendView", "MessageView" or "UserView".
Color
Optional A value or a constant that specifies the text color in the header.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
UserView (Page 1632)
RecipeView (Page 1612)
TrendView (Page 1630)
StatusForce (Page 1619)
Text
Description
Determines the labeling of the text field.
Access during runtime: Read and Write
Syntax
Object.Text [= STRING]
Object
Required. An object of the "ScreenItem" type with the characteristic "TextField".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1726 System Manual, 08/2011,
STRING
Optional. A value or constant which determines the label text color.
See also
TextField (Page 1628)
TextOff
Description
Determines the text which is displayed in the "Off" status of the given object.
Access during runtime: Read and Write
Syntax
Object.TextOff[= STRING]
Object
Required. An object of the "ScreenItem" type with the characteristic "Button," and "Switch".
STRING
Optional. A value or constant which determines the label for the "Off" status.
Remarks
The property is only available if the referenced "Button" or "Switch" object is of the "Text" type.
See also
Switch (Page 1621)
Button (Page 1581)
TextOn
Description
Determines the text which is displayed in the "On" status of the given object.
Access during runtime: Read and Write
Syntax
Object.TextOn[= STRING]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1727
Object
Required. An object of the "ScreenItem" type with the characteristic "Button," and "Switch".
STRING
Optional. A value or constant which determines the label for the "On" status.
Remarks
The property is only available if the referenced "Button" or "Switch" object is of the "Text" type.
See also
Switch (Page 1621)
Button (Page 1581)
ThumbBackColor
Description
Determines the background color of the slider in the "Slider" object.
Access during runtime: Read and Write
Syntax
Object.ThumbBackColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Slider".
Color
Optional A value or constant which determines the background color of the slider.
Comments
You can use the "RGB" function to establish the colors in the RGB format (red, green, blue).
To do this, enter the appropriate decimal value for each of the three RGB values (range from
0 to 255). For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the
VBScript color constants such as vbRed or vbGreen.
See also
Slider (Page 1615)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1728 System Manual, 08/2011,
TicksColor
Description
Specifies the color of the hour markers on the face of the "Clock" object.
Access during runtime: Read and Write
Syntax
Object.TicksColor[= Color]
Object
Required An object of the "ScreenItem" type with the characteristic "Clock".
Color
Optional A value or a constant that specifies the color of the hour markers.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as: RGB(255, 0, 0). You can also use the VBScript color
constants such as vbRed or vbGreen.
See also
Clock (Page 1585)
ToolbarButtonRemove
Description
Removes the selected button function from the list. Only user-defined button functions can be
removed.
See also
FunctionTrendControl (Page 1591)
ToolbarButtonRename
Description
Changes the name of the customized element of the toolbar which is referenced by the
"ToolbarButtonIndex" property.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1729
With "ToolbarButtonRename" you also dynamize the "ToolbarButtonName" property.
See also
FunctionTrendControl (Page 1591)
ToolbarButtonRepos
Description
Changes the sorting order of button functions. "Up" and "Down" move the button function
selected up or down in the list. This moves the button function in the toolbar of a Control towards
the front or towards the back.
See also
FunctionTrendControl (Page 1591)
ToolbarButtonTooltipText
Description
Specifies the tooltip text for the button.
See also
FunctionTrendControl (Page 1591)
ToolbarButtonUserDefined
Description
Indicates whether the project engineer has added a new user-defined toolbar button.
Syntax
Object.ToolbarButtonUserDefined[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"FunctionTrendControl", "TrendRulerControl", "UserArchiveControl".
Boolean
TRUE: The key of the toolbar is customized.
FALSE: The key of the toolbar is specified by the system.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1730 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
ToolbarShowTooltips
Description
Enables the display of tooltips for the button functions in Runtime. The property can be
dynamized with the ToolbarShowTooltips name. The property for specifying the tooltip text is
"ToolbarButtonTooltipText".
Access in Runtime: Read and write
Syntax
Object.ToolbarShowTooltips[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl",
"RecipeView".
BOOLEAN
TRUE: The tooltips are displayed.
FALSE: The tooltips are not displayed.
See also
FunctionTrendControl (Page 1591)
ToolbarUseBackColor
Description
Enables the display of the background color for a toolbar.
Access in Runtime: Read and write
Syntax
Object.ToolbarUseBackColor[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl",
"RecipeView".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1731
BOOLEAN
TRUE: The background color of the toolbar is displayed.
FALSE: The background color of the toolbar is not displayed.
See also
FunctionTrendControl (Page 1591)
ToolbarUseHotKeys
Description
Activates the hotkeys for button functions in Runtime. Insert the hotkeys for button functions
in the "Hotkey" field.
Access in Runtime: Read and write
Syntax
Object.ToolbarUseHotKeys[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "AlarmControl",
"TrendRulerControl", "OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl",
"RecipeView".
BOOLEAN
TRUE: The hotkeys are activated.
FALSE: The hotkeys are not activated.
See also
FunctionTrendControl (Page 1591)
ToolbarVisible
Description
Enables the display of the Control toolbar.
Access in Runtime: Read and write
Syntax
Object.ToolbarVisible[=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1732 System Manual, 08/2011,
Object
Required An object of the "ScreenItem" type with the format "MessageView", "RulerControl",
"OnlineTableControl", "OnlineTrendControl", "FunctionTrendControl", "RecipeView".
BOOLEAN
TRUE: The toolbar is displayed.
FALSE: The toolbar is not displayed.
See also
FunctionTrendControl (Page 1591)
Top
Description
Specifies the value of the Y coordinate of the selected object.
Access in Runtime: Read and write
Syntax
Object.Top[= DOUBLE]
Object
Required A "ScreenItem" object. This property is a standard property of the ScreenItem object
and is therefore available for all formats.
DOUBLE
Optional A value or a constant that contains the value of the Y coordinate in pixels (measured
from the top left edge of the screen).
Comments
The Y coordinate refers to the top left corner of the rectangle that surrounds the object. The
screen limits are also monitored in Runtime. If the assigned coordinate value exceeds the
display size, the user-defined function is interrupted with an error message.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1733
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1734 System Manual, 08/2011,
TransparentColor
Description
Specifies which color of the allocated graphic (*.bmp, *dib) of the specified object will be set
to "transparent".
The "UseTransparentColor" property must have the value TRUE so that the color will be shown
as transparent.
Access in Runtime: Read and write
Syntax
Object.TransparentColor[= Color]
Object
Required An object of type "ScreenItem" with the formats "GraphicView" or "GraphicIOField".
Color
Optional A value or a constant that specifies the color that will be shown transparent.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
See also
GraphicView (Page 1597)
GraphicIOField (Page 1595)
TrendActualize
Description
Enables the update of a selected trend.
Access in Runtime: Read and write
Syntax
Object.TrendActualize[=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1735
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The selected trend is always actualized.
FALSE: The selected trend is not actualized. This setting is useful when a logged trend is
compared with a current trend.
See also
FunctionTrendControl (Page 1591)
TrendAdd
Description
Creates a new trend.
See also
FunctionTrendControl (Page 1591)
TrendBeginTime
Description
Defines the start time of the time range for data transfer to the selected trend. .
See also
FunctionTrendControl (Page 1591)
TrendColor
Description
Determines the color of the trend display or returns it.
The trend display indicates the tendency (rising or falling) of the measuring value being
monitored by a small arrow. In order to activate the trend display, the Trend property must be
set to "True". LONG write-read access.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1736 System Manual, 08/2011,
TrendCount
Description
Defines the number of configured trends.
See also
FunctionTrendControl (Page 1591)
TrendEndTime
Description
Defines the end of the time range for data connections of a selected trend.
.
See also
FunctionTrendControl (Page 1591)
TrendExtendedColorSet
Description
Enables configuration of the point and fill colors and the display of colors in Runtime.
Access in Runtime: Read and write
Syntax
Object.TrendExtendedColorSet[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The settings in the "Point color" and "Fill color" fields are configurable and effective in
Runtime.
FALSE: The settings in the "Point color" and "Fill color" fields are not configurable and effective
in Runtime.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1737
TrendFill
Description
Specifies if the area beneath the trend is to be filled.
Access in Runtime: Read and write
Syntax
Object.TrendFill[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The area beneath the trend is shown filled. You can define the trend color as fill color
if the "Advanced" option is deactivated.
FALSE: The trend is not shown filled.
See also
FunctionTrendControl (Page 1591)
TrendFillColor
Description
Specifies the fill color of the trend. The settings are only active if the "Filled" option is enabled.
Open the "Color selection" dialog by clicking the button.
The settings are only active if the "Advanced" option is enabled.
See also
FunctionTrendControl (Page 1591)
TrendIndex
Description
References a configured trend. You can assign the values of other properties to a specific
trend by using the property. The index must always be set before you change the properties
of a trend in runtime.
Valid values for "TrendIndex" are between 0 and "TrendCount" minus 1. The "TrendCount"
property indicates the number of configured trends.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1738 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
TrendLabel
Description
Defines the label of the trend selected. The label is displayed in Runtime if the value at attribute
"UseTrendNameAsLabel" is "FALSE".
See also
FunctionTrendControl (Page 1591)
TrendLineStyle
Example
Defines the line style for trend visualization.
Access in Runtime: Read and write
Syntax
Object.TrendLineStyle[=LineStyle]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
LineStyle
Value Description Explanation
0 Solid The trend is visualized as solid line.
1 Dashed The trend is visualized as dashed line.
2 Dotted The trend is visualized as dotted line.
3 Dash dot The trend is visualized as dot-dash line.
4 Dash Dot Dot The trend is visualized as dash-dot-dot line.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1739
TrendLineType
Description
Defines how to visualize a trend.
Access in Runtime: Read and write
Syntax
Object.TrendLineType[=LineType]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
LineType
Value Description Explanation
0 None Only the dots are displayed.
1 Line Visualizes a trend with linear interconnection of points.
2 Stepped Visualizes a stepped trend and its interconnected points.
See also
FunctionTrendControl (Page 1591)
TrendLineWidth
Description
Defines the line weight of the line displayed.
See also
FunctionTrendControl (Page 1591)
TrendLowerLimit
Description
Specifies the low limit of a tag. If the tag drops below the value of "TrendLowerLimit", the values
are marked with the color set in "TrendLowerLimitColor". The specification is effective if the
"TrendLowerLimitColoring" property has the value "TRUE".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1740 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
TrendLowerLimitColor
Description
Specifies the color which marks tag values which are below the value of "TrendLowerLimit".
The setting is effective if the "TrendLowerLimitColoring" attribute has the value "TRUE".
See also
FunctionTrendControl (Page 1591)
TrendLowerLimitColoring
Description
Enables the "TrendLowerLimitColor" attribute for identifying tag values which are less than the
value at "TrendLowerLimitValue".
Syntax
Object.TrendLowerLimitColoring[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
Boolean
TRUE: The "TrendLowerLimitColor" property is effective.
FALSE: The "TrendLowerLimitColor" property is not effective.
See also
FunctionTrendControl (Page 1591)
TrendMeasurePoints
Number of measurement points - TrendMeasurePoints
Defines the number of measurement points for visualization of selected trends.
Defines the number of value pairs provided to the trend from a user archive.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1741
The attribute can be assigned dynamic properties by means of the name
TrendMeasurePoints.
See also
FunctionTrendControl (Page 1591)
TrendName
Description
Displays the name of the selected trend. The name is defined on the "Trends" tab. The
"TrendName" property can be dynamized by the TrendRename property.
Access in Runtime: Read and write
Syntax
Object.TrendName
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
TrendPointColor
Description
Defines the color of trend points. Open the "Color selection" dialog by clicking the button.
The settings are only active if the "Advanced" option is enabled.
See also
FunctionTrendControl (Page 1591)
TrendPointStyle
Description
Defines the dot style for trend visualization.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1742 System Manual, 08/2011,
Syntax
Object.TrendPointStyle[=PointStyle]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
PointStyle
Value Description Explanation
0 None The points are not displayed.
1 Dots The trend points are visualized with a size of one pixel. The setting
in the "Dot width" field is deactivated.
2 Squares The dots are displayed as square. The setting in the "Dot width"
field is active.
3 Circles The dots are displayed as circles. The setting in the "Dot width" field
is active.
See also
FunctionTrendControl (Page 1591)
TrendPointWidth
Description
Sets the dot width in pixels. You can only define the dot width for the "square" and "circular"
type.
See also
FunctionTrendControl (Page 1591)
TrendProvider
Description
Specifies the data source for a selected trend.
Access in Runtime: Read and write
Syntax
Object.TrendProvider[=Provider]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1743
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
Provider
Value Description Description
0 None No data source configured for implementation in Runtime by means of
a user-defined function.
1 Archive tags Data source with archive tags of a process value archive.
2 HMI tags Data supply with tag values of HMI tags
3 Recipe data Data supply with columns of a recipe
See also
FunctionTrendControl (Page 1591)
TrendRangeType
Description
Defines the time range for providing data to the selected trend.
You can only define the number of measuring points if you select user archives as the data
source.
Access in Runtime: Read and write
Syntax
Object.TrendRangeType[=RangeType]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
RangeType
Value Description Description
0 Time range Defines the start time and the time range for the data
connection.
1 Start to end time Defines the start and end time for the data connection.
2 Number of measurement
points
Defines the start time and the number of measurement points
for the data connection.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1744 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
TrendRemove
Description
Removes selected trends from the list.
See also
FunctionTrendControl (Page 1591)
TrendRename
Description
Changes the name of the trend which is referenced by the "TrendIndex" property.
With "TrendRename" you also dynamize the "TrendName" property.
See also
FunctionTrendControl (Page 1591)
TrendRepos
Description
Repositions the trend in the trend window. "Up" and "Down" move the selected trend up or
down in the list. This moves the trend towards the foreground or background for visualization
in Runtime.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1745
TrendS-Ty
TrendSelectTagNameX
Description
Opens the dialog box for selecting the tag name for the data supply of the X axis in the f(x)
trend view. Programmers can use the property to let the user select a tag name with a button
for example.
See also
FunctionTrendControl (Page 1591)
TrendSelectTagNameY
Description
Opens the dialog box for selecting the tag name for the data supply of the Y axis in the f(x)
trend view. Programmers can use the property to let the user select a tag name with a button
for example.
See also
FunctionTrendControl (Page 1591)
TrendTagNameX
Description
Shows the name of the bound HMI tag or column for the X axis. You select an HMI tag or a
column with the selection button.
Access in Runtime: Read and write
Syntax
Object.TrendTagNameX
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1746 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
TrendTagNameY
Description
Shows the name of the bound HMI tag or column for the Y axis. You select an HMI tag or a
column with the selection button.
Access in Runtime: Read and write
Syntax
Object.TrendTagNameX
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
TrendTimeRangeBase
Description
Defines the time unit for calculating the time range.
Access in Runtime: Read and write
Syntax
Object.TrendTimeRangeBase[=TimeRangeBase]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
TimeRangeBase
Value Description
500 500 ms
1000 1 second
60000 1 minute
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1747
Value Description
3600000 1 hour
86400000 1 day
See also
FunctionTrendControl (Page 1591)
TrendTimeRangeFactor
Description
Defines the factor for calculating the time range. Only integer factors are valid. .
See also
FunctionTrendControl (Page 1591)
TrendTrendWindow
Description
Defines the trend window for visualizing the trend selected. Define the available trend windows
in the "Trend window" tab.
See also
FunctionTrendControl (Page 1591)
TrendUncertainColor
Description
Value are in uncertain state if the initial value is unknown after runtime has been activated, or
if a substitute value is used. With the "TrendUncertainColor" property you specify the color
which is used for marking these values. Whether the information is evaluated depends on the
"TrendUncertainColoring" property.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1748 System Manual, 08/2011,
TrendUncertainColoring
Description
Value are in uncertain state if the initial value is unknown after runtime has been activated, or
if a substitute value is used. The "TrendUncertainColoring" attribute is used to enable
identification of such values based on the color set in "TrendUncertainColor".
Access in Runtime: Read and write
Syntax
Object.TrendUncertainColoring[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
BOOLEAN
TRUE: The setting of the "TrendUncertainColor" property is effective.
FALSE: The setting of the "TrendUncertainColor" property is not effective.
See also
FunctionTrendControl (Page 1591)
TrendUpperLimit
Description
Specifies the high limit of a tag. If the tag drops below the value of "TrendUpperLimit", the
values are marked by the color set in "TrendUpperLimitColor". The specification is effective if
the "TrendUpperLimitColoring" attribute has the value "TRUE".
See also
FunctionTrendControl (Page 1591)
TrendUpperLimitColor
TrendUpperLimitColor
Specifies the color of tag values which are less than the value at "TrendLowerLimit". This
setting is only active if the value at attribute "TrendUpperLimitColoring" is "TRUE".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1749
The attribute can be assigned dynamic properties by means of the name
TrendUpperLimitColor.
See also
FunctionTrendControl (Page 1591)
TrendUpperLimitColoring
Description
Specifies whether the selection frame is shown with the specified color.
Access in Runtime: Read and write
Syntax
Object.TrendUpperLimitColoring[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl",
"OnlineTrendControl".
BOOLEAN
TRUE: The setting of the "TrendUpperLimitColor" attribute is effective.
FALSE: The setting of the "TrendUpperLimitColor" attribute is not effective.
See also
FunctionTrendControl (Page 1591)
TrendVisible
Description
The list shows all trends you created.
Select the trends to be displayed in the trend window from the list.
Click a trend entry in the list to adapt the properties and to assign axes and trend windows to
the trend.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1750 System Manual, 08/2011,
TrendWindowAdd
Description
Create a new trend view.
See also
FunctionTrendControl (Page 1591)
TrendWindowCoarseGrid
Description
Enables the display of grid lines for the main scale.
Access in Runtime: Read and write
Syntax
Object.TrendWindowCoarseGrid[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The grid lines for the main scaling are displayed.
FALSE: The grid lines for the main scaling are not displayed.
See also
FunctionTrendControl (Page 1591)
TrendWindowCoarseGridColor
Description
Specifies the grid color of the main scale. Open the "Color selection" dialog by clicking the
button.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1751
TrendWindowFineGrid
Description
Enables the display of grid lines for the secondary scale.
Access in Runtime: Read and write
Syntax
Object.TrendWindowFineGrid[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The grid lines for the auxiliary scaling are displayed.
FALSE: The grid lines for the auxiliary scaling are not displayed.
See also
FunctionTrendControl (Page 1591)
TrendWindowFineGridColor
Description
Specifies the grid color of the main scale. Open the "Color selection" dialog by clicking the
button.
See also
FunctionTrendControl (Page 1591)
TrendWindowForegroundTrendGrid
Description
Enables the display of grid lines only for the foreground trend in the trend window.
Access in Runtime: Read and write
Syntax
Object.TrendWindowForegroundTrendGrid[=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1752 System Manual, 08/2011,
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The grid lines for the foreground trend are displayed.
FALSE: The grid lines for the foreground trend are not displayed.
See also
FunctionTrendControl (Page 1591)
TrendWindowGridInTrendColor
Description
Sets the trend color for the visualization of the grid lines for the main scale.
Access in Runtime: Read and write
Syntax
Object.AutoSelectionRectColors [=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The grid lines are displayed in the trend color.
FALSE: The grid lines are displayed with the color set in the "Color" field.
See also
FunctionTrendControl (Page 1591)
TrendWindowHorizontalGrid
Description
Enables the display of horizontal grid lines.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1753
Syntax
Object.TrendWindowHorizontalGrid[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The horizontal grid lines are displayed.
FALSE: The horizontal grid lines are not displayed.
See also
FunctionTrendControl (Page 1591)
TrendWindowIndex
Description
References a configured trend view. You can assign the values of other properties to a specific
trend window by using the property.
Valid values for "TrendWindowIndex" are between 0 and "TrendWindowCount" minus 1. The
"TrendWindowCount" property indicates the number of configured trend windows.
See also
FunctionTrendControl (Page 1591)
TrendWindowName
Description
Defines the name of the trend window selected.
See also
FunctionTrendControl (Page 1591)
TrendWindowRemove
Description
Removes the selected trend view from the list.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1754 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
TrendWindowRename
Description
Changes the name of the trend window which is referenced by the "TrendWindowIndex"
property.
With "TrendWindowRename" you also dynamize the "TrendWindowName" property.
See also
FunctionTrendControl (Page 1591)
TrendWindowRepos
Description
Changes the order of the trend view. "Up" and "Down" move the selected trend up or down in
the list.
The sorting order in the list defines the position in the Control. The first trend view is shown in
the lowest position, the last trend view in the highest position.
See also
FunctionTrendControl (Page 1591)
TrendWindowRulerColor
Description
Specifies the ruler color. Open the "Color selection" dialog by clicking the button.
The color can be configured and displayed if "1 - graphic" is set for visualization.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1755
TrendWindowRulerLayer
Description
Specifies the display layer of the ruler in the trend view.
Access in Runtime: Read and write
Syntax
Object.TrendWindowRulerLayer[=RulerLayer]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
RulerLayer
Value Description Explanation
0 Under grid The ruler is visualized on a layer under the grid.
1 Between grid and
trend
The ruler is positioned on top of the trend and under the grid.
2 On top of trend The ruler is positioned on top of the trend.
See also
FunctionTrendControl (Page 1591)
TrendWindowRulerStyle
Description
Defines the appearance of the ruler.
Access in Runtime: Read and write
Syntax
Object.TrendWindowRulerStyle[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The ruler is displayed as a single black line.
FALSE: The ruler is is displayed in the configured "Color" and "Width".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1756 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
TrendWindowRulerWidth
Description
Defines the width of the ruler in pixels.
The width can be configured and displayed if "1 - graphic" is set for visualization.
See also
FunctionTrendControl (Page 1591)
TrendWindowSpacePortion
Description
Specifies the proportion of the trend widow to be used for the selected curve.
See also
FunctionTrendControl (Page 1591)
TrendWindowVerticalGrid
Description
Enables the display of vertical grid lines.
Access in Runtime: Read and write
Syntax
Object.TrendWindowVerticalGrid[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The vertical grid lines are displayed.
FALSE: The vertical grid lines are not displayed.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1757
See also
FunctionTrendControl (Page 1591)
TrendWindowVisible
Description
The trend lines which you have created are listed in the list.
Activate the trend views in the list which you want to display in the control.
Click a list entry to adapt the ruler and grid line properties.
See also
FunctionTrendControl (Page 1591)
TrendXAxis
Description
Defines the X axis to be used for the trend selected. Define the available X axes inn the "X
Axes" tab.
See also
FunctionTrendControl (Page 1591)
TrendYAxis
Description
Defines the Y axis to be used for the trend selected. Define the available Y axes inn the "Y
Axes" tab.
See also
FunctionTrendControl (Page 1591)
Type
Description
Returns the type of the specified object as STRING. Name diagram: Hmi<ObjectName>, e.g.
HmiCircle for the "circle" screen object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1758 System Manual, 08/2011,
Access in Runtime: Read
Syntax
Object.Type
Object
Required A "ScreenItem" object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1759
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1760 System Manual, 08/2011,
U-XAxis
UnitColor
Description
Specifies the text color for the label of the measurement unit in the "Gauge" object
Access in Runtime: Read and write
Syntax
Object.UnitColor[= Color]
Object
Required A "ScreenItem" object with the format "Gauge".
Color
Optional A value or a constant that specifies the text color for the measurement unit.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
See also
Gauge (Page 1593)
UnitText
Description
Specifies the text for the measurement unit of the selected object.
Access in Runtime: Read and write
Syntax
Object.UnitText[= STRING]
Object
Required A "ScreenItem" object with the format ""Gauge".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1761
STRING
Optional A value or a constant that specifies the text for the measurement unit.
Comments
Enter a text to show, for example, the physical unit of the displayed value. It is standard for no
text to be set as a default.
See also
Gauge (Page 1593)
UseTransparentColor
Description
Specifies whether the color described with the property "TransparentColor" will be shown as
transparent for the selected object.
Access in Runtime: Read and write
Syntax
Object.UseTransparentColor[= BOOLEAN]
Object
Required A "ScreenItem" object with the formats "GraphicView" or "GraphicIOField".
BOOLEAN
Optional TRUE, if the specified color is to be shown as transparent.
See also
GraphicView (Page 1597)
GraphicIOField (Page 1595)
UseTrendNameAsLabel
Description
Specifies whether the "Name" or "Label" property is used as a designation for the trend in
Runtime.
Access in Runtime: Read and write
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1762 System Manual, 08/2011,
Syntax
Object.UseTrendNameAsLabel[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "OnlineTrendControl",
"FunctionTrendControl".
BOOLEAN
TRUE: The name configured under "Properties > Properties > Trends > Name" is used.
FALSE: The name configured under "Properties > Properties > Trends > Label" is used.
See also
FunctionTrendControl (Page 1591)
VerticalAlignment
Description
Determines the vertical alignment of the text within the given object.
Access during runtime: Read and Write
Syntax
Object.VerticalAlignment [= THmiVerticalAlignment]
Object
Required An object of the "ScreenItem" type with the characteristics "TextField", "IOField",
"SymbolicIOField", "Button" or "Switch".
THmiVerticalAlignment
Optional A value or constant which determines the vertical alignment of the text.
hmiAlignmentTop (0): The text is aligned at the top of the object.
hmiAlignmentMiddle (1): The text is centered vertically in the object.
hmiAlignmentBottom (2): The text is aligned at the bottom in the object.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1763
See also
IOField (Page 1600)
DateTimeField (Page 1587)
Switch (Page 1621)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Button (Page 1581)
ViewOnly
Description
Specifies whether the Sm@rtClient display will be used for remote monitoring or remote
maintenance.
Remote maintenance means that settings can be changed on the monitored device.
Remote monitoring means that settings of the monitored device cannot be changed.
Access in Runtime: Read and write
Syntax
Object.ViewOnly[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "SmartClientView".
BOOLEAN
Optional TRUE, if the Sm@rtClient display is to be used only for remote monitoring.
See also
SmartClientView (Page 1618)
Visible
Description
Specifies whether the selected object will be visible.
Access in Runtime: Read and write
Syntax
Object.Visible[=BOOLEAN]
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1764 System Manual, 08/2011,
Object
Required A "ScreenItem"." object.
BOOLEAN
Optional TRUE, if the object is visible.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1765
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1766 System Manual, 08/2011,
WarningRangeColor
Description
Specifies the color of the warning range on the scale of the "Gauge" object.
The "WarningRangeVisible" property must have the value TRUE so that the warning range is
displayed.
Access in Runtime: Read and write
Syntax
Object.WarningRangeColor[= Color]
Object
Required A "ScreenItem" object with the format "Gauge".
Color
Optional A value or a constant that specifies the color of the warning range.
Comments
Use the "RGB" function to establish the colors in RGB format (red, green blue). To do this,
enter the appropriate decimal value for each of the three RGB values (range from 0 to 255).
For example, the color "red" is shown as such: RGB(255, 0, 0). You can also use the VBS
color constants like vbRed or vbGreen.
See also
Gauge (Page 1593)
WarningRangeStart
Description
Specifies at which scale value the warning range of the "Gauge" object will start.
The "WarningRangeVisible" property must have the value TRUE so that the warning range is
displayed.
Access in Runtime: Read and write
Syntax
Object.WarningRangeStart[= DOUBLE]
Object
Required A "ScreenItem" object with the format "Gauge".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1767
DOUBLE
Optional A value or a constant that contains the scale value for the start of the warning range.
Comments
The range extends from the value "Warning" through to the value "Danger". If no range is
activated for "Danger", then the range for "Warning" extends to the end of the scale.
See also
Gauge (Page 1593)
WarningRangeVisible
Description
Specifies whether the warning range in the scale of the "Gauge" object will be displayed.
Access in Runtime: Read and write
Syntax
Object.WarningRangeVisible[= BOOLEAN]
Object
Required A "ScreenItem" object with the format "Gauge".
BOOLEAN
Optional TRUE, if the warning range will be displayed in the scale.
Comments
Specifies the color of the warning range with the ""WarningRangeColor" property.
Specifies the start of the warning range with the "WarningRangeStart"" property.
See also
Gauge (Page 1593)
Width
Description
Specifies the width of the selected objects "Ellipse", "Circle" and "Rectangle".
Access in Runtime: Read and write.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1768 System Manual, 08/2011,
The other objects only have read access to the property.
Syntax
Object.Width[=LONG]
Object
Required A "Screen" object or an object of type "ScreenItem". This property is a standard
property of the ScreenItem-object and is therefore available for all formats.
LONG
Optional A value or a constant that specifies the width in pixels. This parameter can only be
set for the objects "Ellipse", Circle" and "Rectangle".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1769
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1770 System Manual, 08/2011,
XAxisAdd
Description
Creates a new X axis.
Syntax
Object.XAxisAdd
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
XAxisAlign
Description
Defines the alignment mode for a selected axis.
Syntax
Object.XAxisAlign[=Alignement]
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
Alignment
Value Description Description
0 Bottom The X axis selected is displayed below the trend.
1 Top The X axis selected is displayed above the trend.
See also
FunctionTrendControl (Page 1591)
XAxisAutoPrecisions
Description
Enables automatic setting of the decimal precision.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1771
Access in Runtime: Read and write
Syntax
Object.XAxisAutoPrecisions[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
BOOLEAN
TRUE: The number of decimal places is specified automatically.
FALSE: The value configured under "Properties > X axis > Format > Decimal places" is
effective.
See also
FunctionTrendControl (Page 1591)
XAxisAutorange(i)
Description
Specifies whether the value range of the X axis is determined automatically or via the attributes
"XAxisBegin(i)" and "XAxisEnd(i)".
Access in Runtime: Read and write
Syntax
Object.XAxisAutorange(i)[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "FunctionTrendView".
BOOLEAN
Optional TRUE, if the value range of the X axis is determined automatically or via the values
"XAxisBegin(i)" and "XAxisEnd(i)".
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1772 System Manual, 08/2011,
XAxisBeginValue
Description
Specifies the lower range of values of the axis selected. To configure the value, deactivate the
"Automatic" option in "Value range".
See also
FunctionTrendControl (Page 1591)
XAxisColor
Description
Use this attribute to define the color for the common X-axis.
Access in Runtime: Read and write
Syntax
Object.XAxisColor[=COLOR]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl" or
"OnlineTrendControl".
Color
The color is defined as an RGB value.
See also
FunctionTrendControl (Page 1591)
XAxisCount
Description
Defines the number of X axes configured.
Syntax
Object.XAxisCount
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl"..
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1773
See also
FunctionTrendControl (Page 1591)
XAxisEndValue
Description
Specifies the upper range of values of the axis selected. To configure the value, deactivate
the "Automatic" option in "Value range".
See also
FunctionTrendControl (Page 1591)
XAxisExponentialFormat
Description
Enables the exponential notation for visualization of a selected axis.
Access in Runtime: Read and write
Syntax
Object.XAxisExponentialFormat [=BOOLEAN]
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
BOOLEAN
TRUE: The values are displayed in exponential format.
FALSE: The values are displayed in exponential format.
See also
FunctionTrendControl (Page 1591)
XAxisIndex
Description
References a configured X axis. You can assign the values of other properties to a specific X
axis by using the property.
Valid values for "Index" are between 0 and "XAxisCount" minus 1. The "ToolbarButtonCount"
property specifies the number of configured X axes.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1774 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
XAxisInTrendColor
Description
Enables the display of an axis selected in the trend color. The color of the first trend is activated
if several trends are displayed in the trend window. The order of the trends is determined in
the "Trends" properties.
Access in Runtime: Read and write
Syntax
Object.XAxisInTrendColor[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl".
BOOLEAN
TRUE: The selected axis is displayed in the trend color. The setting in the "Color" field is
disabled.
FALSE: The selected axis is displayed in the color which is set in the "Color" field.
See also
FunctionTrendControl (Page 1591)
XAxisLabel(i)
Description
Specifies the labeling of the X axis of a trend that has been referenced with the property
"CurrentCurveIndex", dependent upon the value of "XAxisMode(i)".
Access in Runtime: Read and write
Syntax
Object.XAxisLabel(i)[=String]
Object
Required A "ScreenItem" object with the format "FunctionTrendView".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1775
String
Optional A value or a constant that specifies the labeling of the X axis of a trend that has been
referenced with the property "CurrentCurveIndex".
See also
FunctionTrendControl (Page 1591)
XAxisName
Description
Specifies the name of a selected axis.
Syntax
Object.XAxisName
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
XAxisPrecisions
Description
Specifies the decimal precision for displaying the axis selected. To configure the value,
deactivate the "Automatic" option in "Format".
See also
FunctionTrendControl (Page 1591)
XAxisRemove
Description
Removes the selected axis from the list.
Syntax
Object.XAxisRemove
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1776 System Manual, 08/2011,
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
XAxisRepos
Description
Changes the sorting order of the axes. "Up" and "Down" move the axis selected up or down
in the list. The order in the list determines the position of the axis in the trend view in Runtime.
If the alignment is identical and the axis is further up in the list, it is shown at a position further
away from the trend.
Syntax
Object.XAxisRepos
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
XAxisScalingType(i)
Description
Specifies the type of scaling for the X axis. Whether the information is evaluated depends on
the value of the property "XAxisMode(i)".".
Access in Runtime: Read and write
Syntax
Object.XAxisScalingType(i)[=AxisScalingType]
Object
Required A "ScreenItem" object with the format "FunctionTrendView".
AxisScalingType
hmiBarScalingLinear ( 0): Linear axis scaling.
hmiBarScalingLogarithmic ( 1): Logarithmic axis scaling
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1777
hmiBarScalingNegativeLogarithmic ( 2): Negative logarithmic axis scaling
Comments
The parameter i indicates the number of the trend.
See also
FunctionTrendControl (Page 1591)
XAxisTrendWindow
Description
Specifies in which trend view the selected axis is used. The available trend views are specified
in the properties in "Trends".
Access in Runtime: Read and write
Syntax
Object.XAxisTrendWindow
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
XAxisVisible
Description
The list shows all axes you created.
Activate the axes which are to be displayed in the trend views in the list.
Click an axis in the list to adapt the properties and to assign the axis to a trend view.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1778 System Manual, 08/2011,
YAxis-Z
YAxisAdd
Description
Creates a new X axis.
Syntax
Object.YAxisAdd
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
YAxisAlign
Description
Specifies how the selected axis is aligned.
Syntax
Object.YAxisAlign[=Alignement]
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
Alignment
Value Description Explanation
0 Left The X axis selected is displayed on left side of the trend.
1 Right The selected Y axis is displayed to the right of the trend.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1779
YAxisAutoPrecisions
Description
Enables automatic setting of the decimal precision.
Access in Runtime: Read and write
Syntax
Object.YAxisAutoPrecisions[=BOOLEAN]
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
BOOLEAN
TRUE: The number of decimal places is specified automatically.
FALSE: The value configured under "Properties > Y axis > Format > Decimal places" is
effective.
See also
FunctionTrendControl (Page 1591)
YAxisAutoRange
Value range automatic - X/YAxisAutoRange
Enables automatic calculation of the value range of the axis selected.
Value Description
TRUE The range of values is calculated automatically.
FALSE The range of values is calculated based in the values configured in the "from" and "to" fields.
The X axis attribute can be assigned dynamic properties by means of the name
XAxisAutoRange.
The Y axis attribute can be assigned dynamic properties by means of the name
YAxisAutoRange.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1780 System Manual, 08/2011,
YAxisBeginValue
Description
Specifies the lower value range of the selected axis. To configure the value, deactivate the
"Automatic" option in "Value range".
See also
FunctionTrendControl (Page 1591)
YAxisColor
Description
Specifies the color of the axis selected. Open the "Color selection" dialog by clicking the
button. . The setting is only active if the "Use trend color" field is disabled.
Syntax
Object.YAxisColor[=COLOR]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl" or
"OnlineTrendControl".
Color
The color is defined as an RGB value.
See also
FunctionTrendControl (Page 1591)
YAxisCount
Description
Defines the number of Y axes configured.
Syntax
Object.YAxisCount
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1781
See also
FunctionTrendControl (Page 1591)
YAxisEndValue
Description
Specifies the upper value range of the selected axis. To configure the value, deactivate the
"Automatic" option in "Value range".
See also
FunctionTrendControl (Page 1591)
YAxisExponentialFormat
Description
Enables the exponential notation for visualization of a selected axis.
Access in Runtime: Read and write
Syntax
Object.YAxisExponentialFormat [=BOOLEAN]
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
BOOLEAN
TRUE: The values are displayed in exponential format.
FALSE: The values are displayed in exponential format.
See also
FunctionTrendControl (Page 1591)
YAxisIndex
Description
References a configured Y axis. You can assign the values of other properties to a specific Y
axis by using the property.
Valid values for "Index" are between 0 and "YAxisCount" minus 1. The "ToolbarButtonCount"
property specifies the number of configured Y axes.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1782 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
YAxisInTrendColor
Description
Enables the display of an axis selected in the trend color. The color of the first trend is activated
if several trends are displayed in the trend window. The order of the trends is determined in
the "Trends" properties.
Access in Runtime: Read and write
Syntax
Object.YAxisInTrendColor[=BOOLEAN]
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl".
BOOLEAN
TRUE: The selected axis is displayed in the trend color. The setting in the "Color" field is
disabled.
FALSE: The selected axis is displayed in the color which is set in the "Color" field.
See also
FunctionTrendControl (Page 1591)
YAxisLabel
Description
Defines the label text for a selected axis.
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1783
YAxisName
Description
Specifies the name of the selected axis.
Syntax
Object.XAxisName
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
YAxisPrecisions
Description
Specifies the decimal precision for displaying the axis selected. To configure the value,
deactivate the "Automatic" option in "Format".
See also
FunctionTrendControl (Page 1591)
YAxisRemove
Description
Removes the selected axis from the list.
Syntax
Object.YAxisRemove
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1784 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
YAxisRename
Description
Changes the name of the Y axis which is referenced by the "YAxisIndex" property.
Syntax
Object.YAxisRename
Object
Required An object of the "ScreenItem" type with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
YAxisRepos
Description
Changes the order of the axes. "Up" and "Down" move the selected axis up or down in the list.
The order in the list determines the position of the axis in the trend view in Runtime. The axis
output position is moved away from the trend if the axis is moved further up in the list and the
orientation is the same.
Syntax
Object.YAxisRepos
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1785
YAxisScalingType
Scaling - X/YAxisScalingType
Defines the scaling mode for a selected axis.
The following settings are available:
Value Description
0 Linear
1 Logarithmic
2 Logarithmically negated
The X axis attribute can be assigned dynamic properties by means of the name
XAxisScalingType.
The Y axis attribute can be assigned dynamic properties by means of the name
YAxisScalingType.
See also
FunctionTrendControl (Page 1591)
YAxisTrendWindow
Description
Specifies in which trend view the selected axis is used. The available trend views are specified
in the properties in "Trends".
Access in Runtime: Read and write
Syntax
Object.YAxisTrendWindow
Object
Required A "ScreenItem" object with the format "FunctionTrendControl".
See also
FunctionTrendControl (Page 1591)
YAxisVisible
Description
The list shows all axes you created.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1786 System Manual, 08/2011,
Activate the axes which are to be displayed in the trend views in the list.
Click an axis in the list to adapt the properties and to assign the axis to a trend view.
See also
FunctionTrendControl (Page 1591)
Methods
Activate
Description
Activates the permanent window or the root screen.
To activate a not selected screen, use the "BaseScreenName" property.
It only makes sense to use the activate method with the following operable screen objects. An
error message is output at screen objects which cannot be operated, for example rectangles.
I/O field
Switch
Symbol library
Trend view
f(x) trend view
HTML browser
Slider
Graphic I/O field
Symbolic I/O field
Button
Alarm view
User view
Recipe view
Sm@rtClient View
Status/Force
Syntax
Expression.Activate
Expression
Required An output which returns an object of the "Screen" or "ScreenItem" type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1787
Parameters
--
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1788 System Manual, 08/2011,
See also
Line (Page 1602)
IOField (Page 1600)
Ellipse (Page 1589)
Bar (Page 1578)
Circle (Page 1583)
DateTimeField (Page 1587)
GraphicView (Page 1597)
GraphicIOField (Page 1595)
HTMLBrowser (Page 1598)
AlarmView (Page 1604)
Polygon (Page 1606)
Polyline (Page 1607)
UserView (Page 1632)
RecipeView (Page 1612)
Rectangle (Page 1614)
TrendView (Page 1630)
Switch (Page 1621)
Slider (Page 1615)
SmartClientView (Page 1618)
StatusForce (Page 1619)
SymbolLibrary (Page 1625)
SymbolicIOField (Page 1623)
TextField (Page 1628)
Clock (Page 1585)
Gauge (Page 1593)
BatteryView (Page 1580)
RangeLabelView (Page 1610)
RangeQualityView (Page 1611)
WLanQualityView (Page 1634)
ZoneLabelView (Page 1635)
ZoneQualityView (Page 1636)
SystemDiagnoseWindow (Page 1627)
SystemDiagnoseView (Page 1626)
FunctionTrendControl (Page 1591)
Button (Page 1581)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1789
Item
Description
Returns an element from a list.
Syntax
Expression.Item(Index)
Expression
Required An expression which returns a list.
Parameters
Index
The name or the index number of an element of the list:
ScreenItems (list) Use the object names, e.g.
"HmiRuntime.Screens(1).ScreenItems("Circle")" or the index number.
Screen list Use either the name or the index number.
SmartTags list: Therefore you can use only the tag names as index in the SmartTags list.
A counting of all tags is not possible.
If the transferred value does not correspond with an element in the list, an error occurs. The
return value has the value "Nothing".
On Error Resume Next
Dim screen
Set screen = HmiRuntime.Screens("Screen_1")
If (screen is Nothing)
then
Else...
End If
To achieve an optimum support using auto-completion, it is preferable to use a combined
addressing via the screen name and object name .e. g.
"HmiRuntime.Screens("Screen").ScreenItems("Circle")".
Example
The item method is the default method for lists. Therefore, the results are the same for the
following two examples:
'VBS_Example_ItemHMIRuntime.Screens.Item(1)HMIRuntime.Screens(1)
Both instructions reference the respective base screen.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1790 System Manual, 08/2011,
Stop
Description
Closes WinCC Runtime.
Syntax
Expression.Stop
Expression
Required An expression which returns an "HMIRuntime" type object.
Parameters
--
Trace
Description
Returns a user-defined text through the operating system channel for debug alarms.
The methods HMIRuntime.Trace works only in a PC-based environment. The text-based
parameter can be viewed with any freeware debugger, such as, DebugView
(www.sysinternals.com). You can use the "ShowSystemAlarm" system function if you need to
run a trace without using external tools.
Syntax
Expression.Trace"STRING"
Expression
Required An expression which returns an "HMIRuntime" type object.
Parameters
STRING
The text which is issued as a debug alarm. The text can be displayed with a freely available
debugger, like for example, DebugView (www.sysinternals.com). You can use the
"ShowSystemAlarm" system function if you need to run a trace without using external tools.
Example
In the following example a debug alarm is issued:
'VBS example trace
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1791
HMIRuntime.Trace "Customized error message"
See also
SmartTag (Page 1576)
SmartTags (Page 1574)
Get methods
AttachDB method
Description
Executes the "Connect backup" key function of the control.
Syntax
Ausdruck.AttachDB()
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
DetachDB
Description
Executes the "Disconnect backup" key function of the control.
Syntax
Ausdruck.DetachDB()
Expression
Required An expression that returns an object of the "ScreenItem" type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1792 System Manual, 08/2011,
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Export
Description
Executes the "Export archive" or "Export data" key function of the control.
Syntax
Ausdruck.Export()
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
See also
FunctionTrendControl (Page 1591)
GetStatusbarElement
Description
Returns the element of the control status bar designated as name or index as type
"ICCAxStatusbarElement".
Syntax
Ausdruck.GetStatusbarElement(ByVal vIndex As Variant)
Expression
Required An expression that returns an object of the "ScreenItem" type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1793
Parameters
VARIANT
Parameters Description
vIndex Index or name of status bar element.
Example
'VBS331
Dim ctrl
Dim objStatusBar
Set ctrl = ScreenItems( "Control1" )
Set objStatusBar = ctrl.GetStatusbarElement(1)
objStatusBar.Visible = FALSE
Set objStatusBar = ctrl.GetStatusbarElement(3)
objStatusBar.Width = 10
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "StatusbarElement" listing, for example, you write "objStatusBar.Visible" instead of
"objStatusBar.StatusbarElementVisible".
See also
FunctionTrendControl (Page 1591)
GetStatusbarElementCollection
Description
Returns the list of all status bar elements of the control as type "ICCAxCollection".
Syntax
Ausdruck.GetStatusbarElementCollection()
Expression
Required An expression that returns an object of the "ScreenItem" type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1794 System Manual, 08/2011,
Parameters
- -
Features and functions of the ICCAxCollection
The following properties are available for the ICCAxCollection:
Count
Item
The following functions are available for the ICCAxCollection:
AddItem(vName) As Object
RemoveItem(vIndex)
Example
'VBS332
Dim ctrl
Dim coll
Dim statelement
Set ctrl = ScreenItems.Item("Control1")
Set coll = ctrl.GetStatusbarElementCollection
HMIRuntime.Trace "Number of statusbar elements:" & coll.Count & vbCrLf
For Each statelement In coll
HMIRuntime.Trace statelement.Name & vbCrLf
HMIRuntime.Trace statelement.Width & vbCrLf
HMIRuntime.Trace statelement.Text & vbCrLf
Next
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "StatusbarElement" listing, for example, you write "statelement.Name" instead of
"statelement.StatusbarElementName".
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1795
GetToolbarButton
Description
Returns the name or index designated toolbar button function of the control as type
"ICCAxToolbarButton".
Syntax
Ausdruck.GetToolbarButton(ByVal vIndex As Variant)
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
Parameters Description
vIndex Index or name of toolbar button function.
Example
'VBS337
Dim ctrl
Set ctrl = ScreenItems( "Control1" )
Dim toolbu
Set toolbu = ctrl.GetToolbarButton ("ShowHelp")
HMIRuntime.Trace "Name: " & toolbu.Name & vbCrLf
HMIRuntime.Trace "Index: " & toolbu.Index & vbCrLf
HMIRuntime.Trace "Hotkey: " & toolbu.HotKey & vbCrLf
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "ToolbarButton" listing, for example, you write "toolbu.Index" instead of
"toolbu.ToolbarButtonIndex".
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1796 System Manual, 08/2011,
GetToolbarButtonCollection
Description
Returns the list of all toolbar button functions of the control as type "ICCAxCollection".
Syntax
Ausdruck.GetToolbarButtonCollection()
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
- -
Features and functions of the ICCAxCollection
The following properties are available for the ICCAxCollection:
Count
Item
The following methods are available for the ICCAxCollection:
AddItem(vName) As Object
RemoveItem(vIndex)
Example
'VBS338
Dim ctrl
Dim coll
Dim toolbu
Set ctrl = ScreenItems( "Control1" )
Set coll = ctrl.GetToolbarButtonCollection
HMIRuntime.Trace "Number of toolbar buttons:" & coll.Count & vbCrLf
For Each toolbu In coll
HMIRuntime.Trace toolbu.Name & vbCrLf
HMIRuntime.Trace "Hotkey: " & toolbu.HotKey & vbCrLf
HMIRuntime.Trace "Authorization: " & toolbu.PasswordLevel & vbCrLf
Next
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1797
GetTrend
Description
Returns the trend object of the f(t) trend view or the f(x) trend view designated by name or
index as "ICCAxTrend" or "ICCAxFunctionTrend" type.
Syntax
Ausdruck.GetTrend(ByVal vIndex As Variant)
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
Parameters Description
vIndex Index or name of curve.
Example
'VBS339
Dim ctrl
Dim objTrend
Set ctrl = ScreenItems("OnlineTrendControl")
Set objTrend = ctrl.GetTrend( "Trend 1" )
objTrend.PointStyle = 1
objTrend.LineWidth = 4
Set objTrend = ctrl.GetTrend(2)
objTrend.Provider = 1
objTrend.TagName = "Archive\ArchiveTag2"
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "Trend" listing, for example, you write "objTrend.PointStyle" instead of
"objTrend.TrendPointStyle".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1798 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
GetTrendCollection
Description
Returns the list of all trend objects of the f(t) trend display or the f(x) trend display as
"ICCAxCollection" type.
Syntax
Ausdruck.GetTrendCollection()
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
- -
Features and functions of the ICCAxCollection
The following properties are available for the ICCAxCollection:
Count
Item
The following functions are available for the ICCAxCollection:
AddItem(vName) As Object
RemoveItem(vIndex)
Example
'VBS340
Dim ctrl
Dim objTrendWnd
Dim objTimeAxis
Dim objValAxis
Dim objTrend
Set ctrl = ScreenItems("OnlineTrendControl")
Set objTrendWnd = ctrl.GetTrendWindowCollection.AddItem("myWindow")
Set objTimeAxis = ctrl.GetTimeAxisCollection.AddItem("myTimeAxis")
Set objValAxis = ctrl.GetValueAxisCollection.AddItem("myValueAxis")
objTimeAxis.TrendWindow = objTrendWnd.Name
objValAxis.TrendWindow = objTrendWnd.Name
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1799
Set objTrend = ctrl.GetTrendCollection.AddItem("myTrend1")
objTrend.Provider = 1
objTrend.TagName = "Archive\ArchiveTag1"
objTrend.TrendWindow = objTrendWnd.Name
objTrend.TimeAxis = objTimeAxis.Name
objTrend.ValueAxis = objValAxis.Name
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "Trend" listing, for example, you write "objTrend.TagName" instead of
"objTrend.TrendTagName".
See also
FunctionTrendControl (Page 1591)
GetTrendWindow
Description
Returns the trend view object of the f(t) trend view or the f(x) trend view designated by name
or index as "ICCAxTrendWindow" type.
Syntax
Ausdruck.GetTrendWindow(ByVal vIndex As Variant)
Expression
Required An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
Parameters Description
vIndex Index or name of curve window.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1800 System Manual, 08/2011,
Example
'VBS341
Dim ctrl
Dim objTrendWnd
Set ctrl = ScreenItems("OnlineTrendControl")
Set objTrendWnd = ctrl.GetTrendWindow(1)
objTrendWnd.Visible = FALSE
Set objTrendWnd = ctrl.GetTrendWindow("trend window 2")
objTrendWnd.VerticalGrid = TRUE
objTrendWnd.FineGrid = TRUE
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "TrendWindow" listing, for example, you write "objTrendWnd.Visible" instead of
"objTrendWnd.TrendWindowVisible".
See also
FunctionTrendControl (Page 1591)
GetTrendWindowCollection
Description
Returns the list of all trend window objects of the f(t) trend display or the f(x) trend display as
"ICCAxCollection" type.
Syntax
Ausdruck.GetTrendWindowCollection()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1801
Features and functions of the ICCAxCollection
The following properties are available for the ICCAxCollection:
Count
Item
The following functions are available for the ICCAxCollection:
AddItem(vName) As Object
RemoveItem(vIndex)
Example
'VBS342
Dim ctrl
Dim objTrendWnd
Dim objTimeAxis
Dim objValAxis
Set ctrl = ScreenItems("OnlineTrendControl")
Set objTrendWnd = ctrl.GetTrendWindowCollection.AddItem("myWindow")
Set objTimeAxis = ctrl.GetTimeAxisCollection.AddItem("myTimeAxis")
Set objValAxis = ctrl.GetValueAxisCollection.AddItem("myValueAxis")
objTimeAxis.TrendWindow = objTrendWnd.Name
objValAxis.TrendWindow = objTrendWnd.Name
See also
FunctionTrendControl (Page 1591)
GetXAxis
Description
Returns the X axis object of the f(x) trend view designated by name or index as
"ICCAxValueAxis" type.
Syntax
Ausdruck.GetXAxis(ByVal vIndex As Variant)
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1802 System Manual, 08/2011,
Parameters
VARIANT
Parameters Description
vIndex Index or name of X axis.
Example
'VBS347
Dim ctrl
Dim objXAx
Set ctrl = ScreenItems("FunctionTrendControl")
Set objXAx = ctrl.GetXAxis(1)
objXAx.Visible = FALSE
Set objXAx = ctrl.GetXAxis("axis 2")
objXAx.Label = "X axis 2"
objXAx.ScalingType = 0
objXAx.Precisions = 2
objXAx.Color = RGB(109,109,109)
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "XAxis" listing, for example, you write "objXAx.Visible" instead of
"objXAx.XAxisVisible".
See also
FunctionTrendControl (Page 1591)
GetXAxisCollection
Description
Returns the list of all X axis objects of the f(x) trend view as "ICCAxCollection" type.
Syntax
Ausdruck.GetXAxisCollection()
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1803
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
Features and functions of the ICCAxCollection
The following properties are available for the ICCAxCollection:
Count
Item
The following functions are available for the ICCAxCollection:
AddItem(vName) As Object
RemoveItem(vIndex)
Example
'VBS348
Dim ctrl
Dim objXAxis1
Dim objXAxis2
Dim coll
Dim axes
Set ctrl = ScreenItems("FunctionTrendControl")
Set objXAxis1 = ctrl.GetXAxisCollection.AddItem("myXAxis1")
objXAxis1.Label = "temperature"
Set objXAxis2 = ctrl.GetXAxisCollection.AddItem("myXAxis2")
objXAxis2.Label = "pressure"
Set coll = ctrl.GetXAxisCollection
HMIRuntime.Trace "Number of XAxis:" & coll.Count & vbCrLf
For Each axes In coll
HMIRuntime.Trace axes.Name & vbCrLf
HMIRuntime.Trace axes.Label & vbCrLf
Next
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "XAxis" listing, for example, you write "objXAxis1.Label" instead of
"objXAxis1.XAxisLabel".
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1804 System Manual, 08/2011,
See also
FunctionTrendControl (Page 1591)
GetYAxis
Description
Returns the Y axis object of the f(x) trend view designated by name or index as
"ICCAxValueAxis" type.
Syntax
Ausdruck.GetYAxis(ByVal vIndex As Variant)
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
Parameters Description
vIndex Index or name of Y axis.
Example
'VBS349
Dim ctrl
Dim objYAx
Set ctrl = ScreenItems("FunctionTrendControl")
Set objYAx = ctrl.GetYAxis(1)
objYAx.Visible = FALSE
Set objYAx = ctrl.GetYAxis("axis 2")
objYAx.Label = "Y axis 2"
objYAx.Align = 0
objYAx.Precisions = 3
objYAx.EndValue = 90.000
objYAx.BeginValue = 10.000
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1805
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "YAxis" listing, for example, you write "objYAx.Visible" instead of
"objYAx.YAxisVisible".
See also
FunctionTrendControl (Page 1591)
GetYAxisCollection
Description
Returns the list of all Y axis objects of the f(x) trend view as "ICCAxCollection" type.
Syntax
Ausdruck.GetYAxisCollection()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
Features and functions of the ICCAxCollection
The following properties are available for the ICCAxCollection:
Count
Item
The following functions are available for the ICCAxCollection:
AddItem(vName) As Object
RemoveItem(vIndex)
Example
'VBS350
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1806 System Manual, 08/2011,
Dim ctrl
Dim objYAxis1
Dim objYAxis2
Dim coll
Dim axes
Set ctrl = ScreenItems("FunctionTrendControl")
Set objYAxis1 = ctrl.GetXAxisCollection.AddItem("myYAxis1")
objYAxis1.Label = "temperature"
Set objYAxis2 = ctrl.GetXAxisCollection.AddItem("myYAxis2")
objYAxis2.Label = "pressure"
Set coll = ctrl.GetYAxisCollection
HMIRuntime.Trace "Number of YAxis:" & coll.Count & vbCrLf
For Each axes In coll
HMIRuntime.Trace axes.Name & vbCrLf
HMIRuntime.Trace axes.Label & vbCrLf
Next
Note
When you use the "Get..." methods to access properties from the Control object list rather
than with the Control object, you have to omit the prefix of the property with the name of the
list.
For the "YAxis" listing, for example, you write "objYAxis1.Label" instead of
"objYAxis1.YAxisLabel".
See also
FunctionTrendControl (Page 1591)
MoveAxis
Description
Executes the "Move axis area" key function of the f(t) trend view and the f(x) trend view.
Syntax
Expression.MoveAxis()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameter
- -
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1807
See also
FunctionTrendControl (Page 1591)
NextTrend
Description
Executes the "Next trend" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.NextTrend()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
OneToOneView
Description
Executes the "Original view" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.OneToOneView()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1808 System Manual, 08/2011,
PreviousTrend
Description
Executes the "Previous trend" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.PreviousTrend()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Print
Description
Executes the "Print" key function of the control.
Syntax
Ausdruck.Print()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1809
ShowHelp
Description
Executes the "Help" key function of the control.
Syntax
Ausdruck.ShowHelp()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
See also
FunctionTrendControl (Page 1591)
ShowPropertyDialog
Description
Executes the "Configuration dialog" key function of the control.
Syntax
Ausdruck.ShowPropertyDialog()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
VARIANT
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1810 System Manual, 08/2011,
ShowTagSelection
Description
Executes the "Select data connection" key function of the control.
Syntax
Ausdruck.ShowTagSelection()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
ShowTimeSelection
Description
Executes the "Select time range" key function of the control.
Syntax
Ausdruck.ShowTimeSelection()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1811
ShowTrendSelection
Description
Executes the "Select trends" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.ShowTrendSelection()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
-- -
See also
FunctionTrendControl (Page 1591)
StartStopUpdate
Description
Executes the "Start" or "Stop" key function of the control.
Syntax
Ausdruck.StartStopUpdate()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1812 System Manual, 08/2011,
ZoomArea
Description
Executes the "Zoom area" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.ZoomArea()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
ZoomInOut
Description
Executes the "Zoom +/-" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.ZoomInOut()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1813
ZoomInOutX
Description
Executes the "X axis zoom +/-" key function of the f(t) trend view.
Syntax
Ausdruck.ZoomInOutX()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
ZoomInOutY
Description
Executes the "Y axis zoom +/-" key function of the f(t) trend view.
Syntax
Ausdruck.ZoomInOutY()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
1814 System Manual, 08/2011,
ZoomMove
Description
Executes the "Move trend area" key function of the f(t) trend view and the f(x) trend view.
Syntax
Ausdruck.ZoomMove()
Expression
Necessary. An expression that returns an object of the "ScreenItem" type.
Parameters
- -
See also
FunctionTrendControl (Page 1591)
Visualizing processes (Advanced)
9.8 Working with system functions and Runtime scripting
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1815
9.9 Mobile Wireless
9.9.1 Field of application of the Mobile Panel Wireless
Introduction
The Mobile Panel Wireless enables you to move through the plant without restrictions and with
or without security technology. You can operate and monitor moving machine parts or the
entire plant depending on the situation. You can plan, configure, simulate and extend wireless
networks quickly and reliably.
The Mobile Panels Wireless are based on standardized WLAN technology and are specially
tailored to the requirements of automation.
WLAN area
A WLAN area is the area of the plant in which the HMI device communicates with the PLC
over a wireless local area network. The wireless coverage of the network has a sufficient signal
strength in this area.
The WLAN of a plant is formed by the radio area of one or more Access Points.
Access Point
The Access Point serves as a gateway between the wireless and hard-wired network. The
HMI device communicates with an Access Point via WLAN. You can operate the different
machines or plants without annoying cables. The HMI device is connected to a network in
which it communicates with a PLC via the access point.
Effective range
Safety-related operator input is only possible in a limited part of a WLAN area upstream of a
machine or plant known as the effective range. One exception to this rule is the emergency
stop, which works in the entire WLAN area.
The configured effective ranges are stored in the HMI device. The HMI device can only log on
to a machine within the effective range. This also requires there no other HMI device is logged
on in the same effective range.
To ensure clear logon and machine operator inputs, one effective range must not overlap
another effective range.
Tags
Effective ranges are formed by the spatial assignment of tags to a machine or plant. Tags
create a geometrical space which is relevant for logon to a machine. After logon you operate
the machine using acknowledgement buttons.
A distinction is made between two types of tags:
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1816 System Manual, 08/2011,
Transponder
RFID tag
Transponder
After successful logon to a machine, the spanned geometrical area will be monitored. The
distance between the HMI device and the transponder can only be measured if the two devices
are in the reception range of each other. When you leave the effective range, safety-related
operator input of the machine with acknowledgment buttons is prevented.
Zones in the transponder system
Zones are configurable objects within a transponder system. A zone is defined by the maximum
distance from one or more transponders. In a hard-wired Mobile Panel, the length of the
connection cable defines a zone around a connection box.
Zones are operating areas in which safety-related operator input is not possible. To enter a
zone, you have to configure a screen change to the correct process picture.
RFID tag
After successful logon to a machine, the spanned geometrical area is not monitored. Monitoring
therefore calls for an additional organizational measure, for example: a light barrier or a
protective fence. The protection area is separated from the plant by a security system. The
protection area is the area in the plant in which you operate one or more machines in fail-safe
operation. One or more RFID Tags are distributed within protection zones. The protection area
is not a configurable object.
9.9.2 How does the transponder system work?
Overview
To give a basic understanding of all this, the following section describes the interaction
between:
HMI device
Zone
Effective range
Transponder
NOTICE
You should always assign administrator rights or set up encryption to protect the project
containing a Mobile Panel Wireless for fail-safe operation against unauthorized access.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1817
Principle of operation in the transponder system
9
3
5
6
7
8
4
2 1
Access Point
WLAN of the Access Point
PLC
Plant
Effective range "Robot 1" with a transponder
Effective range "Robot 2" with two transponders
Zone "Zone 1" with a transponder
Radio area of the HMI device
HMI device
Example:
A screen change is configured for "Zone 1".
Transponder1 is assigned to the "Robot 2" effective range.
The operator enters the radio cone of the transponder to receive the transponder ID.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1818 System Manual, 08/2011,
To log onto the machine "Robot 2", the operator presses the object "Effective range - Name".
The "Effective range - Logon" dialog box opens. The operator enters the effective range ID
and confirms with "OK". The dialog is closed.
If the logon was successful, then the acknowledgement buttons will be active.
The HMI device measures the distance from the transponder which is less than the
configured distance of the effective range.
Result:
The operator is logged onto the machine "Robot 2". The operating element "Effective range -
Name" is green and shows the name of the effective range "Robot 2".
If the HMI device is logged onto the effective range, then the following will apply:
The operator may not leave the effective range without logging off. If the operator leaves
the effective range without logging off for more than 30 seconds, a local rampdown will
occur.
No other HMI device can log onto the machine.
To log off from the machine, the operator presses the operating element "Effective range -
Name". A logoff dialog is displayed. The operator confirms the dialog.
After successful logoff, another operator can log on to the machine "Robot2".
When the operator enters "Zone 1", a screen change will take place.
9.9.3 How does the RFID system work?
Overview
RFID stands for radio frequency identification. RFID allows wireless identification of objects
without contact or visual sighting.
For a basic understanding, the following section describes the interaction between:
HMI device
Effective range (RFID)
RFID tag
NOTICE
RFID Tags in the plant area
You may only affix RFID Tags in restricted plant areas that are protected by additional
protective measures, for example, protective railings.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1819
Principle of operation in the RFID system
9
2 1
6
10
5
8
7
3
4
5
Access Point
WLAN of the Access Point
PLC
RFID tag with effective range (RFID) for logon to "Robot 1"
RFID tag with effective range (RFID) for logon to "Robot 2"
Plant
Protective area limit of the machine "Robot1"
Protective area limit of the machine "Robot2"
Radio area of the HMI device
HMI device
Example:
"RFID Tag1" is assigned to the effective range (RFID) "Robot1".
An operator enters the restricted plant area. The operator manually switches to the screen
with the configured operating element "Effective range - Name (RFID)".
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1820 System Manual, 08/2011,
At "RFID Tag1", he presses the "Scan" button.
During the logon operation, the button is yellow and displays the text "Scanning".
The "Effective range - Logon" dialog box opens. The operator enters the effective range
(RFID) ID and confirms it with "OK". The dialog is closed.
The "Confirmation of logon" dialog box opens. The operator confirms logon with the
acknowledgment button.
If logon was successful, the acknowledgement buttons are active.
Result:
The operator is logged on to the machine "Robot 1" and operates the machine within the
protection area in fail-safe operation. The operating element "Effective range - Name (RFID)"
is green and shows the name of the effective range (RFID) "Robot1".
If the HMI device is logged on to the machine, the following applies:
The user may not leave the protection area without logging off from the machine. If the
operator leaves the protection area without logging off, a local rampdown occurs.
No other HMI device can log on to this machine.
To log off from the machine, the operator presses the operating element "Effective range -
Name (RFID)". A logoff dialog is displayed. The operator confirms the dialog.
After successful logoff, another operator can log on to the machine "Robot 1".
9.9.4 Basics
9.9.4.1 Zones
Introduction
The following section applies only to the Mobile Panels Wireless, e.g. Mobile Panel 277 IWLAN
V2 and Mobile Panel 277F IWLAN V2. The "Zones" work area is only visible for these HMI
devices.
Note
For more information refer to the operating instructions for the HMI device:
Complete documentation for Mobile Wireless (http://support.automation.siemens.com/WW/
view/en/26268960)
Open
Depending on the HMI device selected, open the work area in the project window by double-
clicking on "Zones" or "Zones and effective ranges".
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1821
Work area
The "Zones" work area displays the zones that have been set up and the transponders
assigned to them.
Inspector window
When a zone is selected, you can edit the names, display names and the limits of the zone
under the "General" category. The zone has the "On entry" and "On exit" zones. Assign the
"ActivateScreen" system function to the events.
9.9.4.2 Zones working area
Introduction
The "Zones" work area displays the zones and the transponders assigned to them in table
format. You create a list of transponders and assign certain transponders to a zone. The limit
of the zone is defined by the maximum distance from the transponders.
Principle
The work area consists of the "Zones" and "Transponders" tables.
If you select a zone in the "Zones" table, the "Transponder" table displays the following:
Transponder enabled: The transponder is assigned to the selected zone.
Transponder deactivated: The transponder is not yet assigned to any zone.
Transponder not available: The transponder has already been assigned to another zone.
To undo the assignment, switch to the relevant zone and deactivate the transponder.
The zone and transponder IDs are initially assigned automatically. They can be changed,
however.
Please note the following:
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1822 System Manual, 08/2011,
A maximum of 254 zones may be configured.
The zone ID must be unique and fall within the range from 1 - 254.
You can initially configure transponders without assigning them to a zone.
There may be no more than 255 transponders assigned to a zone, an effective range or
both.
The transponder ID must be unique and fall within the range from 1 - 65534.
The transponder IDs are set on the transponder.
9.9.4.3 Effective ranges
Introduction
The following section applies only to the Mobile Panels Wireless that support fail-safe
operation, e.g. Mobile Panel 277F IWLAN V2. The "Effective ranges" work area is only visible
for these HMI devices.
You set up effective ranges in order to control safety related operations. An effective range is
defined by the maximum distance from one or more transponders.
Note
For more information refer to the operating instructions for the HMI device:
Complete documentation for Mobile Wireless (http://support.automation.siemens.com/WW/
view/en/26268960)
Open
Open the work area in the project window by double-clicking on "Zones & effective ranges".
Click the "Effective ranges" tab.
Work area
The "Effective ranges" work area displays the effective ranges that have been set up and the
transponders assigned to them.
Inspector window
When an effective range is selected, you can edit the names, display names and the limits of
the effective range under the "General" category.
When you select a transponder, you can see both the effective range and the zone that are
assigned to that transponder. You can only assign a transponder to one effective range so
that the effective ranges do not overlap.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1823
9.9.4.4 Effective ranges working area
Introduction
The "Effective ranges" work area displays the effective ranges and their transponders in table
format. You create a list of transponders and assign certain transponders to an effective range.
The limit of the effective range is defined by the maximum distance from the transponders.
Principle
The work area consists of the "Effective ranges" and "Transponders" tables.
The HMI device calculates a checksum from the local data so that the configured effective
ranges and transponders reliably match those locally on the machine. The project cannot be
started on the HMI device unless the local checksum agrees with the checksum stored in the
"Effective ranges" editor.
When you select an effective range from the "Effective ranges" table, the "Transponder" table
displays the following:
Transponder enabled: The transponder is assigned to the selected effective range.
Transponder deactivated: The transponder is not yet assigned to any effective range.
Transponder not available: The transponder has already been assigned to another effective
range. To undo the assignment, switch to the relevant effective range and deactivate the
transponder.
The zone assigned to the transponder is displayed in addition to the effective range.
The effective range and transponder IDs are initially assigned automatically. They can be
changed, however.
Please note the following:
A maximum of 127 effective ranges may be configured.
The effective range ID must be unique and fall within the range from 1 - 127.
The display name of an effective range must not be the same as its ID.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1824 System Manual, 08/2011,
You can initially configure transponders without assigning them to an effective range.
There may be no more than 127 transponders assigned to a zone, an effective range or
both.
The transponder ID must be unique and fall within the range from 1 - 65534.
The transponder IDs are set on the transponder.
Effective range in Runtime
To log on to the effective range in Runtime, only the display name of the effective range appears
to the operator in the Runtime language. The operator reads the effective range ID in the plant
and enters it on the HMI device. This ensures that the right machine operated. The
acknowledgment buttons are activated after successful logon.
9.9.4.5 Effective ranges (RFID)
Introduction
The following section only applies to the Mobile Panel 277F IWLAN (RFID tag) which supports
fail-safe operation with RFID. The "Effective ranges (RFID)" work area is only visible with these
HMI devices.
To monitor safety-related operator inputs, you set up effective ranges (RFID).
Note
For more information, refer to the operating instructions of the HMI device:
Complete documentation for Mobile Wireless (http://support.automation.siemens.com/WW/
view/en/26268960)
Open
Open the work area in the project window by double-clicking on "Effective ranges (RFID)".
Work area
The "Effective ranges (RFID)" work area displays the effective ranges that have been set up
and the RFID Tags assigned to them.
Inspector window
When an effective range (RFID) is selected, you can edit the name, display name and ID of
the effective range under the "General" category.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1825
9.9.4.6 Work area for effective ranges (RFID)
Introduction
The "Effective ranges (RFID)" work area displays the effective ranges (RFID) and their
RFID Tags in table format. You create a list of RFID Tags and assign specific RFID Tags to
an effective range.
Principle
The work area consists of the "Effective ranges (RFID)" and "RFID Tags" tables.
The HMI device calculates a checksum from the local data so that the configured effective
ranges (RFID) and RFID Tags reliably match those locally on the machine. The project cannot
be started on the HMI device unless the local checksum agrees with the checksum stored in
the "Effective ranges (RFID)" editor.
When you select an effective range (RFID) in the "Effective ranges (RFID)" table, the
"RFID Tags" table displays the following:
RFID Tag enabled: The RFID Tag is assigned to the selected effective range (RFID).
RFID Tag disabled: The RFID Tag is not yet assigned to any effective range (RFID).
RFID Tag not available: The RFID Tag has already been assigned to another effective
range (RFID). To undo the assignment, switch to the relevant effective range (RFID) and
deactivate the RFID Tag.
The IDs of the effective ranges (RFID) and RFID Tags are initially assigned automatically.
They can be changed, however.
Please note the following:
A maximum of 127 effective ranges (RFID) may be configured.
The effective range (RFID) ID must be unique and fall within the range from 1 - 127.
The display name of an effective range (RFID) must not be the same as its ID.
You can initially configure RFID Tags without assigning them to an effective range (RFID).
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1826 System Manual, 08/2011,
A maximum of 127 RFID Tags is available to assign to an effective range (RFID).
The RFID Tag ID must be unique and fall within the range 1-65534.
The RFID Tag ID is written to the RFID Tag by the HMI device.
Effective range in Runtime
To log on to the effective range (RFID) in Runtime, only the display name of the effective range
(RFID) is displayed to the operator in the Runtime language. The operator reads the effective
range (RFID) ID in the plant and enters it on the HMI device. This ensures that the right machine
operated. The acknowledgment buttons are activated after successful logon.
9.9.5 Working with zones
9.9.5.1 Configuring a zone
Validity
The next section applies to all Mobile Panels Wireless, e.g. Mobile Panel 277 IWLAN.
Introduction
You will have to set up a zone in order to carry out plant-specific operator control and monitoring
tasks.
Requirements
A suitable editing language, e.g. English, must have been set in the "Project languages"
editor.
The "Zones" work area is open.
Procedure
1. Double-click "Add..." in the "Zones" table.
2. Enter the "MixingPlant" zone in the "Name" field.
3. Enter "MixingSystem" as the "Display name" for the zone at runtime. Enter zone "1" in the
"ID" field.
4. Enter "8" meters as the zone "Limit".
5. Double-click "Add..." in the "Transponders" table.
6. Enter "Transponder 1" as the "Name" of the transponder.
7. Enter transponder "1" in the "ID" field.
Then set transponder IDs on the transponder.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1827
8. Enable the assignment of "Transponder 1".
"Transponder 1" is assigned to the "MixingPlant" zone.
9. Repeat steps 6 to -9 accordingly for "Transponder 2".
"Transponder 2" is assigned to the "MixingPlant" zone.
Result
The "MixingPlant" zone is configured as two conical areas arranged at a distance of 8 meters,
regardless of the effective ranges: one area around "Transponder 1" and one around
"Transponder 2".
The display name designates the zone in the set editing language. An overview of the display
names can be found in the "Project texts" editor.
9.9.5.2 Displaying the screen on entering a zone
Introduction
Configure a screen change when entering and leaving the zone.
Requirements
A Mobile Panel which supports zones has been created, for example, Mobile
Panel 277 IWLAN.
The "MixingPlant" zone is configured.
The "Plant_1" screen has been created and opened.
The "MixingPlant_1" screen has been created and opened.
The "Zones" work area is open.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1828 System Manual, 08/2011,
Procedure
1. Select the "MixingPlant" zone from the "Zones" table.
2. Click "Properties> Events" in the Inspector window.
3. Click the event "On entry".
4. Select the "ActivateScreen" system function in the "function list".
5. Select "MixingPlant_1" as the "Screen name".
6. Click the event "On exit".
7. Select the "ActivateScreen" system function in the function list.
8. Select "Plant_1" as the "Screen name".
Result
The "MixingPlant_1" screen is displayed on the HMI device when you enter the "MixingPlant"
zone. When you exit the zone, the "Plant_1" screen appears once more.
9.9.5.3 Displaying an object in relation to the zone
Validity
The following example is independent of the WLAN and applies to all Mobile Panels.
Introduction
You configure an I/O field that is only visible within a specific zone.
Requirements
A Mobile Panel which supports zones has been created, for example, Mobile
Panel 277 IWLAN.
The "Zone_id" variable of the "Int" data type has been created.
A "Plant_1_Overview" screen has been created.
Procedure
1. Open the "Runtime Settings > General" editor.
2. Select the "Zone_id" tag as the "ID Zone/ Effective range".
3. Open the screen "Plant_1_Overview".
4. Drag and drop the "I/O box" object from the toolbox into the screen.
5. Click "Properties > Animations" in the Inspector window.
6. Click "Layout > Visibility."
7. Select "Zone_id" as the "tag".
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1829
8. Select "from" 1 "to" 1 as the "Range".
9. Enable "Visible".
Result
The IO field is only visible at runtime under the following conditions:
The hard-wired Mobile Panel is connected to a connection box with ID = 1.
The Mobile Panel Wireless is located in a zone with ID = 1, for example, the "MixingPlant"
zone.
9.9.6 Working with effective ranges
9.9.6.1 Overview
Introduction
The following configuration guide describes the steps needed to set up an effective range for
fail-safe operation on a Mobile Panel Wireless.
Procedures overview
1. Configuring the effective range:
You configure the "MixingAxisControl" effective range as a conical area around
"Transponder1 " at a distance of 5 meters.
2. Configuring the name of the effective range:
To ensure logon to the effective range, configure the object "Effective range - Name".
3. Configuring additional effective range objects:
Configure additional objects for displaying the position and signal strength within an
effective range.
4. Set parameters for loading:
PROFIsafe communication
WLAN network
Power management
Interface
5. Configure the data channel
6. Configure network operation
7. Set the transponder
8. Commissioning effective ranges
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1830 System Manual, 08/2011,
9. Switching on and Testing the HMI device
10.Start loading manually
11.Acknowledging the effective range at the plant:
You acknowledge the effective ranges and their transponders.
12.Determine the checksum
13.Load the project once again with checksum:
Enter the checksum you have determined in the project and load the project once again.
14.Test effective range
Note
For detailed information on items 5 to 14, refer to the operating instructions of the HMI
device.
Complete documentation for Mobile Wireless (http://support.automation.siemens.com/
WW/view/en/26268960)
9.9.6.2 Configure effective range
Introduction
You set up an effective range in order to control safety related operator input upstream of a
machine or plant.
Requirements
A suitable editing language, e.g. English, must have been set in the "Project languages"
editor.
The "Effective ranges" work area is open.
Procedure
1. Double-click "Add..." in the "Effective Ranges" table.
2. Enter "MixingAxisControl" as the "Name" of the effective range.
3. Enter "Mixing_axis_PLC" as the "Display name" for the effective range at runtime.
4. Enter effective range "1" in the "ID" field.
Make sure that the effective range ID matches the ID on the machine.
5. Enter "5" meters as the "Limit" of the effective range.
6. Double-click "Add..." in the "Transponders" table.
7. Enter "Transponder 1" as the "Name" of the transponder.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1831
8. Enter transponder "1" in the "ID" field.
Then set transponder IDs on the transponder.
9. Enable the assignment of "Transponder 1".
"Transponder 1" is assigned to the "MixingAxisControl" effective range.
Result
You configure the "MixingAxisControl" effective range as a conical area around "Transponder
1" at a distance of 5 meters, regardless of the zones.
The display name designates the effective range in the set editing language. An overview of
the display names can be found in the "Project texts" editor.
9.9.6.3 Configuring the effective range name
Introduction
Configure at least the "Effective range - Name" object so that an operator can log on and off
a machine using an effective range. If you do not configure an effective range object for a
Mobile Panel Wireless for fail-safe operation, a warning appears during generation.
Requirements
A screen has been created and opened.
Procedure
1. Select the "Effective range - Name" object from the "Advanced objects" category in the
toolbox.
2. Drag and drop the "Effective range - Name" object from the toolbox into the screen.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1832 System Manual, 08/2011,
Result
If the operator clicks an object during runtime, he initiates logon or logoff of the HMI device to
a machine that is assigned to an effective range.
See also
Effective range name (Page 854)
9.9.6.4 Configuring additional Mobile Wireless objects
Introduction
You will need to configure other objects in order to display further information about the
effective range during testing, for example.
Requirements
A screen has been created and opened.
Procedure
1. Select the "Effective range - Signal" object from the "Advanced objects" category in the
toolbox.
2. Drag and drop the "Effective range - Signal" object from the toolbox into the screen.
3. Repeat steps 1 and 2 with the "WLAN - Reception" object.
Result
The "Effective range - Signal" object indicates how accurately the Mobile Panel Wireless is
within an effective range. The "WLAN - Reception Quality" object displays the signal strength
of the WLAN wireless connection.
See also
Effective range signal (Page 858)
WLAN reception (Page 859)
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1833
9.9.7 Working with effective ranges (RFID)
9.9.7.1 Overview
Validity
The next section applies only to Mobile Panels Wireless with RFID, for example,
Mobile Panel 277F IWLAN (RFID Tag).
Introduction
The following configuration guide describes the steps required to set up an effective range
(RFID) for fail-safe operation on a Mobile Panel Wireless with RFID.
Procedures overview
1. Configure effective range (RFID):
You configure the effective range (RFID) "MixingAxisControl".
2. Configuring the name of the effective range (RFID):
To ensure logon to the effective range, configure the object "Effective range - Name (RFID)".
3. Set parameters for loading
4. Configure the data channel
5. Configure network operation
6. Install RFID Tag in the plant
7. Turn on the HMI device and enable loading mode
8. Loading a project
9. Write the suitable IDs to the RFID Tags in the plant
10.Determine the checksum
11.Load the project once again with checksum:
Enter the checksum you have determined in the project and load the project once again.
12.Test effective range (RFID)
Note
For detailed information on items 4 to 12, refer to the operating instructions of the HMI
device.
Complete documentation for Mobile Wireless (http://support.automation.siemens.com/
WW/view/en/26268960)
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1834 System Manual, 08/2011,
9.9.7.2 Configuring effective range (RFID)
Introduction
You set up an effective range (RFID) to control safety-related operator input upstream of a
machine or plant.
Requirements
A suitable editing language, e.g. English, must have been set in the "Project languages"
editor.
The "Effective ranges (RFID)" work area is open.
Procedure
1. Double-click "Add..." in the "Effective Ranges (RFID)" table.
2. Enter "MixingAxisControl" as the "Name" of the effective range (RFID).
3. Enter "MixingAxisControl" in the "Display name" field of the effective range (RFID).
4. Enter "1" in the "ID" field of the effective range (RFID).
Make sure that the effective range (RFID)-ID matches the ID on the machine.
5. Double-click "Add..." in the "RFID Tag table.
6. Enter "RFID Tag 1" as the "Name" of the RFID Tag.
7. Enter "1" as the "ID" of the RFID Tag. Then set the RFID Tag-ID for the RFID Tag.
8. Enable the assignment of "RFID Tag 1".
"RFID Tag 1" is assigned to the effective range (RFID) "MixingAxisControl".
Result
The effective range (RFID) "MixingAxisControl" is configured.
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1835
The display name describes the effective range (RFID) in the set editing language. An overview
of the display names can be found in the "Project texts" editor.
9.9.7.3 Configuring the effective range name (RFID)
Introduction
Configure the "Effective range - Name" object so that an operator can log on and off a machine
using an effective range (RFID). If you do not configure the "Effective range-Name" object for
a Mobile Panel Wireless RFID with (RFID), a warning will appear during generation.
Requirements
A screen has been created and opened.
Procedure
1. Select the "Effective range - Name (RFID)" object from "Advanced objects" in the toolbox.
2. Drag and drop the "Effective range - Name (RFID)" object from the toolbox into the screen.
Result
If the operator clicks an object during runtime, he will initiate logon or logoff of the HMI device
to a machine which has been assigned to an effective range (RFID).
See also
Effective range name (RFID) (Page 856)
9.9.8 Reference
9.9.8.1 PROFIsafe address
Validity
The PROFIsafe address is only available for fail-safe operation for the Mobile Panel Wireless.
Note
Additional information on fail-safe operation can be found in the operating instructions for the
HMI device:
Complete documentation for Mobile Wireless (http://support.automation.siemens.com/WW/
view/en/26268960)
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1836 System Manual, 08/2011,
PROFIsafe address
The PROFIsafe address used for fail-safe I/Os in PROFIsafe communication is unique on the
entire network and on all stations. On the Mobile Panel Wireless, you create a default value
in the project and load it to the HMI device. You can also store a PROFIsafe address on the
HMI device.
The PROFIsafe address fall within the range from 1 to 65534. The two PROFIsafe addresses
(in the Engineering System and on the HMI device) are checked for formal validity.
The PROFIsafe address is loaded as follows at the start of Runtime:
You programmed a valid PROFIsafe address in the Control Panel.
The HMI loads the PROFIsafe address set in the Control Panel.
You did not program a valid PROFIsafe address in the Control Panel.
The HMI loads the PROFIsafe address set in the project.
NOTICE
The invalid address 65.535 is programmed by default in the Control Panel of the HMI
device. The HMI loads the address set in the project.
See also
Power Management (Page 1837)
Zone ID / connection point ID (Page 1838)
9.9.8.2 Power Management
Validity
In the "Runtime Settings > Power Management" editor, configure the energy-saving mode of
a Mobile Panel.
Power Management
The Mobile Panel Wireless can save energy in the following ways:
Reduce brightness - minimal saving
Switch off display - significant saving
You can also indicate after how long without operator input the power management function
is enabled. The communication link is maintained. The time for "Switch monitor off" is longer
than the time for "Reduce brightness".
See also
PROFIsafe address (Page 1836)
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1837
9.9.8.3 Zone ID / connection point ID
Validity
In the "Runtime Settings > General" configure an internal tag which, depending on the value,
shows specific information on the display of the HMI device.
Note
Mobile Panels Wireless with RFID
For Mobile Panels Wireless with RFID, the area "Zone ID / Connection point ID" is not
available.
Zone ID / connection point ID
This field is used to configure an internal tag that contains the following value at runtime in
relation to the type of HMI device:
The ID of the connection box or effective range to which the hard-wired Mobile Panel is
connected.
The ID of the zone in which the Mobile Panel Wireless is located. If the value is set to 255,
then the HMI device is not in any zone.
See also
PROFIsafe address (Page 1836)
Visualizing processes (Advanced)
9.9 Mobile Wireless
WinCC Advanced V11.0 SP1
1838 System Manual, 08/2011,
9.10 Planning tasks
9.10.1 Field of application of the Scheduler
Definition
You can use the Scheduler to configure tasks to run independent of the screen in the
background. You create tasks by linking system functions or scripts to a trigger. The linked
functions will be called when the triggering event occurs.
Example of an application
The Scheduler is used to execute event-controlled tasks automatically. For example, you use
a task to automate the following:
Regular swap out of log data
Printout of an alarm report when an alarm buffer overflow occurs
Printout of a report at shift end
Monitoring a tag
Monitoring of a user change
Note
The availability of the listed examples is determined by the HMI device.
See also
Work area of the "Scheduler" editor (Page 1840)
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1839
9.10.2 Working with tasks and triggers
Introduction
A task consists of a trigger and a task type.
Starting a task
Controlled by a trigger, the Scheduler starts the task linked to the trigger.
9.10.3 Basics
9.10.3.1 Work area of the "Scheduler" editor
Introduction
Double-click on "Scheduler" to open it in the project view. The work area shows the scheduled
tasks, which consist of the trigger and the task type, for example, the function list.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1840 System Manual, 08/2011,
Structure
The work area consists of the table of jobs.
The table of tasks shows specified tasks with their properties, such as triggers. You select a
task type and a trigger. You assign a name and a comment to the task. The description provides
a written summary of the task including the timing for the task.
Inspector window
The "Properties" tab of the Inspector window is split into two parts.
The "Job" area lists the name of the job and the job type. The "Starting time" area shows the
trigger. The area is different depending on the trigger selected.
In the "Events" tab use the function list with system functions that will be executed in the task.
Note
You can obtain more detailed information about the elements of the user interface using the
tooltips. To do so, move the mouse pointer to the relevant object or press <F1> if the object
has already been selected.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1841
See also
Field of application of the Scheduler (Page 1839)
Trigger (Basic) (Page 1843)
9.10.3.2 Function list
Function list
A trigger starts the function list. The function list is executed line-for-line. Each line contains a
system function. You can configure exactly one function list for each task.
Note
The choice of configurable system functions in a function list depends on the selected trigger
and the HMI device.
9.10.3.3 Function list
Function list
A trigger starts the function list. The function list is executed line-for-line. Each line contains a
system function or a local script. You can configure exactly one function list for each task.
Note
The choice of configurable system functions in a function list depends on the selected trigger
and the HMI device.
Processing of system functions and scripts
System functions and scripts in a function list are processed in Runtime sequentially from top
to bottom.
Basics of the function list (Page 1226)
Use a script with loops, conditional statements and abort conditions to program non-sequential
and conditional procedures.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1842 System Manual, 08/2011,
9.10.3.4 Triggers
Trigger (Basic)
Introduction
A trigger is linked to a task and forms the triggering event which will call this task. The task is
executed when the trigger occurs.
Event trigger
When a task is linked to a system event, the task will be triggered by the event. System events
include, for example, Runtime stop, screen change, user change, etc.
Each system event can only be configured once for each HMI device.
Deactivating job
If you do not need a certain job temporarily, deactivate the job in the Engineering System. You
also use the trigger "Deactivated" to make a previously configured system event available once
again.
Example: Task "A" is planned with the system event "Shutdown". This system event is then
no longer available for another task "B". Select "Disabled" as the trigger for task "A" to make
the "Runtime stop" system event available again.
Note
The available triggers depend on the HMI device.
See also
Work area of the "Scheduler" editor (Page 1840)
Triggers
Introduction
A trigger is linked to a task and forms the triggering event which will call this task. The task is
executed when the trigger occurs.
Types of triggers
The Scheduler recognizes different types of triggers:
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1843
Acyclic triggers
They consist of a specification for the date and time of day. Tasks with an acyclic trigger are
performed once by the Scheduler on the specified date and at the specified time.
Cyclic triggers
Tasks linked to a cyclic trigger occur regularly at a specific point in time.
Standard cycle: With a standard cycle, the beginning of the first interval coincides with the
start of Runtime. The length of the interval is determined by the cycle.
Trigger with defined starting time: You specify a start time and a time interval. You can use
cyclic triggers to perform tasks on a daily or weekly basis, for example. For example, you
can select a "Weekly" trigger to specify a week as the interval. You specify the beginning
of the interval with the day of the week and the time of day.
Event trigger
When a task is linked to a system event, the task will be triggered by the event. In contrast to
cyclic triggers, system events usually occur acyclically. A Runtime stop is a system event, for
example.
Each system event can only be configured once for each HMI device.
Deactivating job
If you do not need a certain job temporarily, deactivate the job in the Engineering System. You
also use the trigger "Deactivated" to make a previously configured system event available once
again.
Example: Task "A" is planned with the "User change" system event. This system event is then
no longer available for another task "B". Select "Disabled" as the trigger for task "A" to make
the "User change" system event available again.
Note
The available triggers depend on the HMI device.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1844 System Manual, 08/2011,
Timers for cyclic triggers
Timers for cyclic and acyclic triggers
You have the option to change the start time of a task dynamically in Runtime. You can select
an HMI variable as the timer. The value of the tag determines the start time for the task during
Runtime.
Note
An HMI tag must be of the type "DateTime". A PLC tag must be of the type "Date and Time"
or "DTL".
As long as the operator does not change the tag after Runtime starts, the start time configured
in the task is valid. As soon as the operator enters a change to the tag, the current value of
the tag is always the start time. To reset the configured time as the start time, the operator has
to enter the configured time again.
9.10.4 Planning jobs
9.10.4.1 Planning tasks with acyclic triggers
Introduction
You are planning a one-time Runtime stop for maintenance work. The task starts a function
which requires Runtime to stop.
Requirements
The "Scheduler" editor is open.
The Inspector window is open.
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Maintenance at end of year" as the "Name."
3. Select "Once" as the "Trigger".
4. Select "31.12.2008" in the "Properties > Properties > General > on" field of the Inspector
window.
5. Enter the time "18:00" in the "at" field.
6. Click "Properties > Events" in the Inspector window.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1845
7. Select the "StopRuntime" system function in the function list.
8. Select "Runtime" as the "Mode".
Result
The task is executed once. Runtime will be stopped at 18:00 on December 31, 2008.
Note
"StopRuntime" event on RT Professional
Please note that the "StopRuntime" event means runtime is in the process of ending and that
some functionalities are therefore no longer available.
9.10.4.2 Planning tasks with cyclic triggers
Introduction
You plan a job that provides a weekly printout of a report.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1846 System Manual, 08/2011,
Requirements
A "Weekly report" report has been created.
The "Scheduler" editor is open.
The Inspector window is open.
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Weekly report printout for end of shift" as the "Name."
3. Select "Weekly" as the "Event".
4. Open the "Properties" tab in the Inspector window.
5. Select "Friday" in the "on day" field of the "Starting point" area.
6. Enter the time "18:00" in the "at" field in the "Starting point" area.
7. Click in the "Events" tab of the "Function list" on the entry "No function."
8. Select "Print/PrintReport" as the function.
9. Select "Weekly report" report.
Result
The task is executed weekly. The report "Weekly report" will be printed every Friday at 18:00
hours.
9.10.4.3 Planning tasks with event triggers
Introduction
You plan a task that generates a screen change when the user changes.
Requirements
The "Scheduler" work area is open.
You have created the "Start" screen.
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Screen change at user change" as the "Name."
3. Select "User change" as the "Trigger."
4. In the Inspector window, select "Properties > Events".
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1847
5. Select the "Screen/ActivateScreen" system function in the function list.
6. Select the "Start" screen in the screen name field.
Result
The task is executed with the "User change" event. When a new user logs on successfully,
the "Start" screen is called up.
9.10.4.4 Administer task
Changing the designation
1. In the work area, double-click the field in the "Name" column.
2. Change the name of the task.
3. Confirm your entry with <Return>.
As an alternative, you can change the designation in the "Job > Name" box of the Inspector
window.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1848 System Manual, 08/2011,
Changing triggers
1. In the work area, mark the field in the "Trigger" column.
2. Open the drop-down list using the button and select the trigger you require.
You can alternatively change the trigger in the "Starting time" area of the Inspector window.
Deleting a task
1. Select one or more lines for the tasks to be deleted.
2. Open the shortcut menu with the right button and select the menu command "Delete".
As an alternative, delete one or more tasks by using the <Del> button.
9.10.5 Examples
9.10.5.1 Example: Terminating Runtime every day
Task
You plan a job that terminates Runtime every day at the end of work.
Requirements
The "Scheduler" work area is open.
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Runtime stop at end of work" as the "Name."
3. Select "Daily" as the "Event."
4. Open the "Properties" tab in the Inspector window.
5. Enter the time "21:00" in the "at" field in the "Starting point" area.
6. Open the "Events" tab in the Inspector window.
7. Click the "No function" entry in the "Function list".
8. Select "System functions/System/StopRuntime" as the function.
Result
Runtime is terminated every day at 21:00.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1849
9.10.5.2 Example: Update user following change of user
Task
Configure an I/O field which displays the logged on user. Configure a task which updates the
I/O field when the logged on user changes.
Requirements
A "CurrentUser" tag of the "String" type is created.
A screen has been created and opened.
An I/O field is created in the screen.
Procedure
1. Click on the "I/O field" object.
2. In the Inspector window, select "Properties > Events > General":
Select "Character string" as the "Display format."
Select "CurrentUser" as the "Variable."
Select "Output" as the mode.
3. Change to the work area of the Scheduler.
4. Click "Add..." in the table of the task area.
5. Enter "CurrentUser" as the "Name".
6. Select "User change" as the "Trigger."
7. In the Inspector window, select "Properties > Events".
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1850 System Manual, 08/2011,
8. Select the system function "ReadUserName" from the "User Management" group in the
function list.
9. Select "CurrentUser" as the "Variable."
Result
When a new user logs on successfully, the "ReadUserName" function is called up. The
"CurrentUser" tag is updated and displayed in the I/O field of the newly logged on user.
If a user does not log on successfully, the logged on user is logged off. The I/O field continues
to display the user previously logged on until a new user logs on successfully.
9.10.5.3 Example: Changing the starting point of a job in Runtime
Example: Changing the starting point of a task in Runtime
Introduction
A cyclic trigger, for example "Starting daily at 18:00," is configured in the Engineering System.
The time "18:00" is fixed as a constant. To change the start time in Runtime, select a tag as
the "Timer." The value of the tag determines the start time of the task during Runtime.
Task
You plan a task that swaps out log data daily and has the "LogTime" tag as the timer. You
configure a "LogTime" tag in an input field.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1851
Requirements
The "DataLogSource" source log has been created as a data log.
The "DataLogDestination" destination log has been created as a data log.
A "ChangeLogTime" screen has been created.
Procedures overview
1. Creating a timer tag: You create a tag with which you change the starting point of the log
data swap in Runtime.
2. Configuring a Date/time field: The operator changes the starting point of the task by using
the Date/Time field in Runtime.
3. Configure the task with a timer tag: You create a task whose start time can be changed
dynamically in Runtime.
Result
If nothing is entered in the "LogDataTimeField" input field, then the task starts daily at 18:00
by default. The log data are swapped out. If an operator enters 19:00 in the "LogDataTimeField"
input field, then the log data are swapped out at 19:00. Provided the value of the tag is not
changed again before the task starts.
Example: 1. Configuring a tag for Runtime
Task
In the following example you configure the "LogTime" variable.
Procedure
1. Open the "HMI tags" editor.
2. Click "Add..." in the table of the task area.
3. Enter "LogTime" as the "Name" of the variable.
4. Select "Internal variable" in the "Connection" column.
5. Select "DateTime" in the "Date type" column.
Result
A variable of the "DateTime" type has been created.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1852 System Manual, 08/2011,
Example: 2. Configuring a Date/time field
Task
In the following example you configure a Date/time field. To change the starting point of the
task in Runtime, link the "LogTime" variable to the Date/time field.
Requirements
The "LogTime" variable of the "DateTime" type has been created.
The "ChangeLogTime" screen is open.
Procedure
1. In the toolbox view, drag-and-drop a "Date/time field" from the "Basic objects" category to
the screen.
2. In the Inspector window, click "Properties >Properties > General".
3. Disable the "System time."
4. Click "Variable" and select "LogTime."
5. Disable "Display date" and enable "Display time."
6. Select "Input/output" as the "Mode."
7. Click "Properties > Miscellaneous."
8. Enter "LogDataTimeField" as the "Name".
Result
The operator enters a time using the created date/time field.
Example: 3. Configuring a swap to archive with a timer variable
Task
In the following example you configure a task with a timer tag with which you change the starting
point of the task in Runtime.
Requirements
The "LogTime" tag has been created.
The "DataLogSource" source log has been created as a data log.
The "DataLogDestination" destination log has been created as a data log.
The Scheduler work area is open.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1853
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Swap out log daily at a tag time" as the "Name".
3. Select "Daily" as the "Trigger".
4. In the Inspector window "Properties >Properties > General > at" enter the time "18:00".
5. Select the "LogTime" tag as the "Standard timer".
6. In the Inspector window, open "Properties > Events".
7. Select the "System functions/Logs/CopyLog" system function in the function list.
8. Select these settings:
Select "Data log" as the "Log type".
Select "DataLogDestination" as the "Destination log".
Select "DataLogSource" as the "Source log".
Select "Overwrite" as the "Mode".
Select "Yes" for "Delete source log".
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
1854 System Manual, 08/2011,
Result
If nothing is entered in the "LogDataTimeField" input field, then the task starts daily at 18:00
by default. The log data are swapped out. If an operator enters 19:00 in the "LogDataTimeField"
input field, then the log data are swapped out at 19:00. Provided the value of the tag is not
changed again before the task starts.
Visualizing processes (Advanced)
9.10 Planning tasks
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1855
9.11 Communicating with PLCs
9.11.1 Basics of communication
9.11.1.1 Communication between devices
Communication
The data exchange between two devices is known as communication. The devices can be
interconnected directly or via a network. The interconnected devices in communication are
referred to as communication partners.
HMl device 1
HMl device 2
PLC
Data transferred between the communication partners may serve different purposes:
Display processes
Operate processes
Output alarms
Archive process values and alarms
Document process values and alarms
Administer process parameters and machine parameters
Communication partners
Communication between the following devices is described in more detail in this section:
PLC
The PLC controls a process by means of a user program.
HMI device
You use the HMI device to operate and monitor the process.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1856 System Manual, 08/2011,
Basic information for all communication
The basis for all types of communication is a network configuration. In a network configuration,
you specify the connection that exists between the configured devices.
With the network configuration, you also ensure the necessary prerequisites for
communication, in other words:
Every device in a network is assigned a unique address.
The devices carry out communication with consistent transmission characteristics.
Automation system
The following characteristics describe an automation system:
The PLC and HMI device are interconnected
The network between the PLC and HMI device is configured
Communication between HMI devices
The HTTP protocol is available for communication between HMI devices.
For more detailed information, refer to the documentation on the SIMATIC HMI HTTP protocol.
Communication via a uniform and vendor-neutral interface
With OPC (Openess Productivity Collaboration), WinCC has a uniform and manufacturer-
neutral software interface. This interface enables standardized data exchange between
industrial, office, and manufacturing applications.
For more detailed information, refer to the documentation for OPC.
9.11.1.2 Devices and networks in the automation system
Introduction
To set up an automation system, you must configure, parameterize, and interconnect the
individual devices.
You insert PLCs and HMI devices into the project in the same way. Likewise, you configure
the two devices in the same way.
Automation system setup:
1. Insert PLC into the project.
2. Insert HMI device into the project.
3. Network the devices together.
4. Interconnect the devices.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1857
Inserting devices
If you have created a project, you can add a device in the portal view or project view.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1858 System Manual, 08/2011,
Portal view
Project view
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1859
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1860 System Manual, 08/2011,
Networking devices
You can network the interfaces of the communication-capable devices conveniently in the
"Devices & Networks" editor. In the networking step, you configure the physical device
connections.
The tabular network overview supplements the graphical network view with the following
additional functions:
You obtain detailed information on the structure and parameter settings of the devices.
Using the "Subnet" column, you can connect communication-capable components to
subnets that have been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1861
Connecting devices
After you network the devices together, you configure the connection. You configure the "HMI
connection" connection type for communication with the HMI device.
9.11.1.3 Data exchange using tags
Communication using tags
Process values are forwarded in runtime using tags. Process values are data which is stored
in the memory of one of the connected automation systems. They represent the status of a
plant in the form of temperatures, fill levels or switching states, for example. Define external
tags for processing the process values in WinCC.
WinCC works with two types of tag:
External tags
Internal tags
Working with tags
See the chapter "Working with tags" for further information about configuring tags.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1862 System Manual, 08/2011,
9.11.1.4 Data exchange using area pointers
Communication using area pointers
Area pointers are parameter fields. WinCC receives information about the location and size of
data areas in the PLC from these parameter fields in runtime.
During communication, the PLC and the HMI device alternately access these data areas for
read and write operations.
Based on the evaluation of data stored in the data areas, the PLC and HMI device initiate
mutually defined actions.
The area pointers are managed centrally in the "Connections" editor. Area pointers are used
to exchange data from specific user data areas.
You use the following area pointers in WinCC:
Data record
Date/time
Coordination
Job mailbox
Date/time PLC
Project ID
Screen number
The availability of the various area pointers is determined by the HMI device used.
9.11.1.5 Communication drivers
Communication drivers
A communication driver is a software component that establishes a connection between a PLC
and an HMI device. The communication driver thus enables the assignment of process values
to HMI tags.
The interface as well as the profile and transmission speed can be chosen, depending on the
HMI device used and the connected communication partner.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1863
9.11.2 Networks and connections
9.11.2.1 SIMATIC communication networks
Communication networks
Overview
Communication networks are a central component of modern automation solutions. Industrial
networks have to fulfill special requirements, for example:
Coupling of automation systems as well as simple sensors, actuators, and computers.
The information has to be correct and has to be transferred at the right moment.
Robust against electromagnetic disturbances, mechanical stresses and soiling
Flexible adaptation to the production requirements
Industrial networks belong to the LANs (Local Area Networks) and allow communication within
a limited area.
Industrial networks fulfill the following communication functions:
Process and field communication of the automation systems including sensors and
actuators
Data communication between automation systems
IT communication for integrating the modern information technology
Overview of the networks
This section examines the following networks:
Industrial Ethernet
The industrial network standard for all levels
PROFINET
The open Industrial Ethernet standard for automation
PROFIBUS
The international standard for the field area and market leader at the field busses
MPI
The integrated interface of the SIMATIC products
PPI
The integrated interface specially for the S7-200
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1864 System Manual, 08/2011,
PROFINET
Industrial Ehernet
PROFIBUS
PROFINET and Ethernet
Industrial Ethernet
Industrial Ethernet, which is based on IEEE 802.3, enables you to connect your automation
system to your office networks. Industrial Ethernet provides IT services that you can use to
access production data from the office environment.
Ethernet network
An Ethernet network allows you to interconnect all devices that are connected to the network
via an integrated Ethernet interface or a communication module. You can thereby connect
multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI
device. The maximum number of communication partners that you can connect to an HMI
device is dependent on the HMI device used. Additional information is available in the
documentation for the respective HMI device.
PROFINET
PROFINET is an open standard for industrial automation defined by IEEE 61158 and based
on Industrial Ethernet. PROFINET makes use of IT standards all the way to the field level and
enables plant-wide engineering.
With PROFINET, you can realize high-performance automation solutions for applications with
stringent real-time requirements.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1865
PROFIBUS
PROFIBUS DP
PROFIBUS DP (distributed I/O) is used to connect the following devices:
PLCs, PCs, HMI devices
Distributed I/O devices, e.g., SIMATIC ET 200
Valves
Drives
PROFIBUS DP's fast response times make it ideally suited for the manufacturing industry.
Its basic functionality includes cyclic exchange of process data between the master and
PROFIBUS DP slaves, as well as diagnostics.
PROFIBUS network
You can connect an HMI device within the PROFIBUS network to any SIMATIC S7 module
that has an integrated PROFIBUS or PROFIBUS DP interface. You can thereby connect
multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI
device.
The maximum number of communication partners that you can connect to an HMI device is
dependent on the HMI device used. Additional information is available in the documentation
for the respective HMI device.
You configure the SIMATIC S7-200 PLC as a passive device in the network. You connect the
SIMATIC S7-200 using the DP connector or a PROFIBUS communication module.
MPI
MPI
MPI (Multi-Point Interface) is the integrated interface for SIMATIC products:
PLCs
HMI devices
Programming device/PC
Small subnets with the following characteristics are set up with MPI:
Short distances
Few devices
Small data quantities
MPI network
You connect the HMI device to the MPI interface of the SIMATIC S7 PLC. You can connect
multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1866 System Manual, 08/2011,
device. The maximum number of communication partners that you can connect to an HMI
device is dependent on the HMI device used. Additional information is available in the
documentation for the respective HMI device.
Network architectures
MPI is based on the PROFIBUS standard (IEC 61158 and EN 50170) and supports the
following bus topologies:
Line
Star
Tree
An MPI subnet contains a maximum of 127 devices and consists of multiple segments. Each
segment contains a maximum of 32 devices and is limited by terminating resistors. Repeaters
are used to connect segments. The maximum cable length without a repeater is 50 m.
PPI
Introduction
PPI (point-to-point interface) is an integrated interface that was developed specially for the
SIMATIC S7-200. A PPI network typically connects S7-200 PLCs. However, other
SIMATIC PLCs (e.g., S7-300 and S7-400) or HMI devices can communicate with a SIMATIC
S7-200 in the PPI network.
PPI network
A PPI connection is a point-to-point connection. The HMI device is the master. The SIMATIC
S7-200 is the slave.
You can connect a maximum of one SIMATIC S7-200 to an HMI device. You use the serial
connector of the CPU to connect the HMI device. You can connect multiple HMI devices to
one SIMATIC S7-200. From the perspective of the SIMATIC S7-200, only one connection at
a time is possible.
Note
The PPI network can contain a maximum of four masters in addition to the HMI device. For
performance reasons, do not configure more than four devices at a time as a master in the
PPI network.
Network architectures
PPI is based on the PROFIBUS standard (IEC 61158 and EN 50170) and supports the
following bus topologies:
Line
Star
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1867
Multi-master networks with a maximum of 32 masters are set up with PPI:
An unlimited number of masters can communicate with each slave.
A slave can be assigned to multiple masters.
The RS 485 repeater can be used to extend the PPI network. Modems can also be connected
to the PPI network.
9.11.2.2 Configuring networks and connections
Networking devices
Introduction
The "Devices & Networks" editor is provided for configuring connections. You can network
devices in the editor. You can also configure and assign parameters to devices and interfaces.
You then configure the required connections between the networked devices.
In the "Devices & Networks" editor you configure HMI connections with the PLCs:
SIMATIC S7 1200
SIMATIC S7 300
SIMATIC S7 400
You configure the HMI connections to other PLCs in the "Connections" editor of the respective
HMI device.
Networking devices
The network view of the "Devices & Networks" editor includes a graphical area and a tabular
area. You can use the graphical area to network the devices in the project with drag-and-drop.
The tabular area provides an overview of the devices and their components.
You can network the following PLCs together with HMI devices in the "Devices & Networks"
area.
SIMATIC S7 1200
SIMATIC S7 300
SIMATIC S7 400
All other PLCs are available in the TIA-Portal and are configured "not integrated". You configure
"not integrated" connections in the "Connections" editor of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1868 System Manual, 08/2011,
With the networking step, you configure the physical connection of the communication
partners. The networking of devices is depicted by lines that are colored according to the
interface.
Configuring an integrated connection in the "Devices & Networks" editor
Introduction
You configure an HMI connection between the HMI device and a SIMATIC S7 1200 in the
"Devices & Networks" editor. This HMI connection is the direct connection between the
communication partners that you have created in a project.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1869
Integrated connections
Connections of devices within a project are referred to as integrated connections. In the case
of integrated connections, you can directly configure addresses of PLC tags.
Note
An HMI connection can be configured in the "Devices & Networks" editor for the following
PLCs only:
SIMATIC S7 1200
SIMATIC S7 300
SIMATIC S7 400
You configure the HMI connections to all other PLCs in the "Connections" editor of the HMI
device.
Configuring an HMI connection in the "Devices & Networks" editor
1. Insert an HMI device and a SIMATIC S7 1200 into your project.
2. Switch to "Connections" mode.
3. Select the "HMI connection" connection type.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1870 System Manual, 08/2011,
4. Use a drag-and-drop operation to interconnect the two PROFINET interfaces.
5. Change the IP address and subnet mask address parameters according to the
requirements of your project.
Special considerations of the "Devices & Networks" editor
Introduction
If you are configuring or have already configured networks or HMI connections, the "Devices
& Networks" editor supports you with the following functions:
Highlighting of communication partners
Highlighting of HMI connections
Automatic creation of subnets
Highlighting of communication partners
All communication partners for which an HMI connection is possible are highlighted in turquoise
if you have selected the "HMI connection" type.
Starting from the interface of a device create an HMI connection to the device of another device
using a drag-and-drop operation. During the drag-and-drop operation all potential
communication partners are highlighted in turquoise.
Use the ESC key to stop connecting interfaces using a drag-and-drop operation.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1871
When the mouse pointer is moved over the interface of a device, the following icons indicate
whether a connection is possible:
A connection is possible.
A connection is not possible.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1872 System Manual, 08/2011,
Highlighting of HMI connections
A turquoise highlighting of the connection indicates that a HMI connection was created. If
several HMI connections are created, you can select one of the already created HMI
connections in a dialog.
Then you can configure the parameters of the selected HMI connection and the communication
partners in the inspector window.
Automatic creation of subnets
A subnet is created automatically when you configure a HMI connection.
Configuring a non-integrated connection in the "Connections" editor
Introduction
You use the "Connections" editor of the HMI device to configure a connection between an HMI
device and a PLC that cannot be configured in the "Devices & Networks" editor.
These connections are referred to as non-integrated connections.
Requirements
A project is open.
An HMI device has been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1873
Configuring a connection in the "Connections" editor
1. Open the "Connections" editor of the HMI device.
2. Create a new connection.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1874 System Manual, 08/2011,
3. Select the communication driver.
4. Set the connection parameters.
Integrated connections in the "Connections" editor
If you have already configured the integrated connections of the HMI device in the "Devices
& Networks" editor, they are also displayed in the "Connections" editor.
Meaning of the icons used:
Integrated connection
Non-integrated connection
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1875
9.11.3 Data exchange
9.11.3.1 Data exchange using tags
Basics of tags
Introduction
Process values are forwarded in runtime using tags. Process values are data which is stored
in the memory of one of the connected automation systems. They represent the status of a
plant in the form of temperatures, fill levels or switching states, for example. Define external
tags for processing the process values in WinCC.
WinCC works with two types of tag:
External tags
Internal tags
The external tags form the link between WinCC and the automation systems. The values of
external tags correspond to the process values from the memory of an automation system.
The value of an external tag is determined by reading the process value from the memory of
the automation system. It is also possible to rewrite a process value in the memory of the
automation system.
External tag
WinCC Automation system
Process value
Internal tags do not have a process link and only convey values within the WinCC.
Tags in WinCC
For external tags, the properties of the tag are used to define the connection that the WinCC
uses to communicate with the automation system and form of data exchange.
Tags that are not supplied with values by the process - the internal tags - are not connected
to the automation system. In the tag's "Connection" property, this is identified by the "Internal
tag" entry.
You can create tags in different tag tables for greater clarity. You then directly access the
individual tag tables in the "HMI tags" node in the project tree. The tags from all tag tables can
be displayed with the help of the table "Show all tags".
With structures you bundle a number of different tags that form one logical unit. Structures are
project-associated data and are available for all HMI devices of the project. You use the "Types"
editor in the project library to create and edit a structure.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1876 System Manual, 08/2011,
Overview of HMI tag tables
Introduction
HMI tag tables contain the definitions of the HMI tags that apply across all devices. A tag table
is created automatically for each HMI device created in the project.
In the project tree there is an "HMI tags" folder for each HMI device. The following tables can
be contained in this folder:
Default tag table
User-defined tag tables
Table of all tags
In the project tree you can create additional tag tables in the HMI tags folder and use these to
sort and group tags and constants. You can move tags to a different tag table using a drag-
and-drop operation or with the help of the "Tag table" field. Activate the "Tags table" field using
the shortcut menu of the column headings.
Default tag table
There is one default tag table for each HMI device of the project. It cannot be deleted or moved.
The default tag table contains HMI tags and, depending on the HMI device, also system tags.
You can declare all HMI tags in the standard tags table or, as necessary, additional user-
defined tables of tags.
User-defined tag tables
You can create multiple user-defined tag tables for each HMI device in order to group tags
according to your requirements. You can rename, gather into groups, or delete user-defined
tag tables. To group tag tables, create additional subfolders in the HMI tags folder.
All tags
The "All tags" table shows an overview of all HMI tags and system tags of the HMI device in
question. This table cannot be deleted, renamed or moved. This table also contains the "Tags
table" column, which indicates the tag table of where a tag is included. Using the "Tags table"
field, the assignment of a tag to a tags table can be changed.
With devices for Runtime Professional, the table "All tags" contain an additional tab "System
tags". The system tags are created by the system and used for internal management of the
project. The names of the system tags begin with the "@" character. System tags cannot be
deleted or renamed. You can evaluate the value of a system tag, but cannot modify it.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1877
Additional tables
The following tables are also available in an HMI tag table:
Discrete alarms
Analog alarms
Logging tags
With the help of these tables you configure alarms and logging tags for the currently selected
HMI tag.
Discrete alarms table
In the "Discrete alarms" table, you configure discrete alarms to the HMI tag selected in the
HMI tag table. When you configure a discrete alarm, multiple selection in the HMI tag table is
not possible. You configure the discrete alarms for each HMI tag separately.
Analog alarms table
In the "Analog alarms" table, you configure analog alarms to the HMI tag selected in the HMI
tag table. When you configure an analog alarm, multiple selection in the HMI tag table is not
possible. You configure the analog alarms for each HMI tag separately.
Logging tags table
In the "Logging tags" table, you configure logging tags to the HMI tag selected in the HMI tag
table. When you configure a logging tag, multiple selection in the HMI tag table is not possible.
You configure the logging tags for each HMI tag separately. The "Logging tags" table is only
available if the HMI device used supports logging.
If WinCC Runtime Professional is used, you can also assign several log tags to a tag. With
the other HMI devices, you can only assign one log tag to a tag.
External tags
Introduction
External tags allow communication (exchange of data) between the components of an
automation system, such as between the HMI device and the PLC.
Principle
An external tag is the image of a defined memory location in the PLC. You have read and write
access to this storage location from both the HMI device and from the PLC.
Since external tags are the image of a storage location in the PLC, the applicable data types
depend on the PLC which is connected to the HMI device.
In STEP 7, if you write a PLC control program, the PLC tags created in the control program
will be added to the PLC tag table. If you want to connect an external tag to a PLC tag, access
the PLC tags directly via the PLC tag table and connect them to the external tag.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1878 System Manual, 08/2011,
Data types
All the data types which are available at the connected PLC are available at an external tag
in WinCC. Information about data types which are available for connection to other PLCs can
be found in the documentation about the respective communication drivers.
See "Communication between devices (Page 1856)" for additional information.
Note
As well as external tags, area pointers are also available for communication between the HMI
device and PLC. You can set up and enable the area indicators in the "Connections" editor.
Update of tag values
For external tags, the current tag values are transmitted in runtime via the communication
connection between WinCC and the connected automation systems and then saved in the
runtime memory. Next, the tag value will be updated to the set cycle time. For use in the runtime
project, WinCC accesses tag values in the runtime memory that were read from the PLC at
the previous cycle time. As a result, the value in the PLC can already change whilst the value
from the runtime memory is being processed.
See also
Communication between devices (Page 1856)
Addressing external tags
Introduction
The options for addressing external tags depend on the type of connection between WinCC
and the PLC in question. A distinction must be made between the following connection
types:
Integrated connection
Connections of devices which are within a project and were created with "Devices &
Networks" editor are referred to as integrated connections.
Non-integrated connection
Connections of devices which were created with the "Connections" editor are referred to
as non-integrated connections. It is not necessary that all of the devices be within a single
project.
The connection type can also be recognized by its symbol.
Integrated connection
Non-integrated connection
You can find additional details on this in the section "Basics of communication (Page 1856)".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1879
Addressing with integrated connections
An integrated connection offers the advantage that you can address a tag both symbolically
and absolutely.
For symbolic addressing, you select the PLC tag via its name and connect it to the HMI tag.
The valid data type for the HMI tag is automatically selected by the system. You have to
distinguish between the following cases when you address elements in data blocks:
Symbolic addressing of data blocks with optimized access
For symbolic addressing of a data block with optimized access, the address of an element
in the data block is assigned dynamically and automatically applied to the HMI tag in case
of a change. You do not need to compile the connected data block or the WinCC project
for this step.
For data blocks with optimized access, only symbolic addressing is available.
Symbolic addressing of data blocks with standard access
For symbolic addressing of a data block with standard access, the address of an element
in the data block is assigned permanently. The valid data type for the HMI tag is
automatically selected by the system. Any change in the address of an element in the data
block is applied directly to the HMI tag. You do not need to compile the connected data
block or the WinCC project for this step.
For data blocks with standard access, you can use symbolic addressing as well as absolute
addressing.
For symbolic addressing of elements in a data block, you only need to recompile and reload
the WinCC project in case of the following changes:
If the name or the data type of the connected data block has changed.
If the name or the data type of a higher-level structure node of the connected element in
the data block has changed.
If the name of the connected data block has changed.
Symbolic addressing is currently only available on PLCs of the SIMATIC S7 1200 type.
Addressing with optimized access is only available in an integrated connection.
You can also use absolute addressing with an integrated connection. You have to use absolute
addressing for PLC tags from a SIMATIC S7 300/400 PLC. If you have connected an HMI tag
with a PLC tag and the address of the PLC tag changes, you only have to recompile the control
program to update the new address in WinCC. Then you recompile the WinCC project and
load it onto the HMI device.
In WinCC, symbolic addressing is the default method. To change the default setting, select
the menu command "Options > Settings". Select "Visualization > Tags" in the "Settings" dialog.
If required, disable the "Symbolic access" option.
The availability of an integrated connection depends on the PLC used. The following table
shows the availability:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1880 System Manual, 08/2011,
PLC Integrated connection Comments
S7 300/400 Yes The linking of tags is not checked in Runtime. If
the tag address changes in the PLC and the HMI
device is not compiled again and loaded, the
change is not registered in runtime.
S7 1200 Yes A validity check of the tag connection is
performed in runtime during symbolic
addressing. If an address is changed in the PLC,
the change is registered and an error message
is issued. The reaction described for S7 300/400
applies whilst addressing with standard access.
Create an integrated connection in the "Devices & Networks" editor. If the PLC is contained in
the project and integrated connections are supported, you can then also have the connection
created automatically. To do this, when configuring the HMI tag, simply select an existing PLC
tag to which you want to connect the HMI tag. The integrated connection is then automatically
created by the system.
Addressing with non-integrated connections
In the case of a project with a non-integrated connection, you always configure a tag connection
with absolute addressing. Select the valid data type yourself. If the address of a PLC tag
changes in a project with a non-integrated connection during the course of the project, you
also have to make the change in WinCC. The tag connection cannot be checked for validity
in Runtime, an error message is not issued.
A non-integrated connection is available for all supported PLCs.
Symbolic addressing is not available in a non-integrated connection.
With a non-integrated connection, the control program does not need to be part of the WinCC
project. You can perform the configuration of the PLC and the WinCC project independently
of each other. For configuration in WinCC, only the addresses used in the PLC and their
function have to be known.
See also
Basics of communication (Page 1856)
Internal Tags
Introduction
Internal tags do not have any connection to the PLC.
Principle
Internal tags are stored in the memory of the HMI device. Therefore, only this HMI device has
read and write access to the internal tags. You can create internal tags to perform local
calculations, for example.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1881
You can use the HMI data types for internal tags. Availability depends on the HMI device being
used.
The following HMI data types are available:
HMI data type Data format
Array One-dimensional array
Bool Binary tag
DateTime Date/time format
DInt Signed 32-bit value
Int Signed 16-bit value
LReal Floating-point number 64-bit IEEE 754
Real Floating-point number 32-bit IEEE 754
SInt Signed 8-bit value
UDInt Unsigned 32-bit value
UInt Unsigned 16-bit value
USInt Unsigned 8-bit value
WString Text tag, 16-bit character set
9.11.3.2 Data exchange using area pointers
Basic information on area pointers
Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC
and the HMI device alternately access these data areas for read and write operations. The
PLC and the HMI device trigger defined interactions based on the evaluation of stored data.
For example, area pointers are required for the following data:
Recipes
Job mailboxes
Sign-of-life monitoring
Area pointers
The following area pointers are supported:
Area pointer
Area pointers can be configured for connections.
Data record
Date/time
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1882 System Manual, 08/2011,
Coordination
Job mailbox
Global area pointers of the HMI device
Global area pointers can be configured for separate connections.
Screen number
Date/time PLC
Project ID
Area pointers for connections
Introduction
Using the "Area pointer" tab of the "Connections" editor, you can configure the usage of the
available area pointers.
To configure the area pointers, open the "Connections" editor and open the "Area pointer" tab.
Structure
The "Area pointer" tab contains two tables of area pointers. The top part of the table contains
the area pointers you can create and enable separately for each available connection.
The "Global area pointers of HMI device" table contains the area pointers which are created
only once in the project and can be used for only one connection.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1883
Use of area pointers
"Area pointer" tab
Before you use an area pointer, you enable it under "Connections > Area pointer". You then
assign the area pointer parameters.
You assign the following parameters in the "Area pointer" tab:
Active
Enables the area pointer.
Pointer name
Name of the area pointer specified by WinCC.
PLC tag
Here you select the PLC tag or the tag array that you have configured as the data area for
the area pointer.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1884 System Manual, 08/2011,
Access mode
Here you can select from the following access modes:
Symbolic access
Absolute access
Address
If you selected "Symbolic access", no address is entered in this field.
If you selected "Absolute access", enter the address of a tag in the "Address" field.
Length
WinCC specifies the length of the area pointer.
Acquisition cycle
You specify the acquisition cycle in this field for area pointers that are read by the HMI
device. Note that a very short acquisition time may have a negative impact on HMI device
performance.
Comment
Enter a comment, for example, to describe the purpose of the area pointer.
Accessing data areas
Accessing data areas
The following table shows how HMI devices and PLCs access individual data areas for read
(R) or write (W) operations.
Data area Required for HMI device PLC
Screen number Evaluation by the PLC in order to determine the active screen. W R
Data record Transfer of data records with synchronization R/W R/W
Date/time Transfer of the date and time from the HMI device to the PLC W R
Date/time PLC Transfer of the date and time from the PLC to the HMI device R W
Coordination Requesting the HMI device status in the PLC program W R
Project ID Runtime checks for consistency between the WinCC project
ID and the project in the PLC
R W
Job mailbox Triggering of HMI device functions by the PLC program R/W R/W
Configuring area pointers
Configuration of area pointers
Introduction
You use an area pointer to access a data area in the PLC. The data area is stored in the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1885
Prior to configuring area pointers
Before you use the area pointer, you must enable and parameterize it under "Connections >
Area Pointer".
Global data block
To access the data area in the PLC, you have to create a global data block in the PLC program.
The following example shows the use of a data block.
Length of area pointers
For area pointers with a length >= 1, you set up the data area as a tag array in a global data
block or instance data block.
You also have the option to use a PLC tag for area pointers with a length = 1.
The configuration of the tags in a data block is dependent on the length of the area pointer you
want to use. The unit for the length of an area pointer is a 16-bit word.
If, for example, you want to use an area pointer with a length of "5", you must create an array
with 5 array elements in the data block.
Alternative procedure
Alternatively, you can also use the absolute access mode to access area pointers.
Parameterizing a global data block
Introduction
To access the data area in the PLC, a global data block for the area pointer must be
parameterized in the PLC program.
Requirements
A PLC is created in the project.
A connection is configured between the PLC and the HMI device.
The PLC program contains a global data block.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1886 System Manual, 08/2011,
Procedure
1. Open "PLC > Program blocks" in the project tree.
2. Double-click the global data block you created previously.
The data block opens.
3. Enter a tag name in the "Name" column.
4. Select "Array[lo .. hi] of type" as the data type in the "Data type" column.
5. Replace the "lo" entry by the low value for the dimension of the array.
6. Replace the "hi" entry by the high value for the dimension of the array.
Example: If you configure an area pointer with the length "4", enter the value "0" for "lo"
and the value "3" for "hi" inside the brackets.
7. Replace the "type" designation with the "word" data type.
The full data type for an array of 4 tags appears as follows: "Array[0 .. 3] of word".
The tag array is created after the entry is confirmed.
8. Click "Compile".
The project is compiled.
Configuring an area pointer for a connection
Introduction
After you have parameterized the global data block, you now create the area pointer for the
connection.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1887
Requirements
The global data block has been parameterized in the PLC program.
Procedure
1. Open "HMI >Connections" in the project tree.
2. Click the "Area pointer" tab.
3. Enable the required area pointer.
You enable a global area pointer by selecting the connection in the "Connection" field.
4. Click the navigation button in the "PLC tag" field.
The object list opens.
5. Navigate to the data block in the object list, and select the tag in the right window.
You do not need an array tag to configure an area pointer with the length of "1".
6. Select the "Word" data type when creating the tag in the data block.
If required, set additional parameters, such as the acquisition cycle, during configuration.
Result
The area pointer is enabled and connected to the PLC tag in the global data block.
9.11.4 Device dependency
9.11.4.1 Basic Panel
Communication drivers for Basic Panels
Device dependency of the Basic Panels
The following table shows which communication drivers you can configure with the various
Basic Panels.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1888 System Manual, 08/2011,
Communication drivers
HMI
devices
SIMATI
C S7
1200
SIMATI
C S7
300/40
0
SIMATI
C S7
200
SIMATI
C
HTTP
protoco
l
OPC Allen-
Bradley
EtherN
et/IP
Allen-
Bradley
DF1
Mitsubi
shi MC
TCP/IP
Mitsubi
shi FX
Modico
n
Modbu
s TCP/
IP
Modico
n
Modbu
s RTU
Omron
Host
Link
KP300
Basic
Yes Yes Yes No No Yes No Yes No Yes No No
KTP40
0 Basic
mono
PN
Yes Yes Yes No No Yes No Yes No Yes No No
KTP40
0 Basic
mono
PN
Portrait
Yes Yes Yes No No Yes No Yes No Yes No No
KTP60
0 Basic
DP
Yes Yes Yes No No No Yes
2)
No Yes No yes
1)
Yes
KTP60
0 Basic
DP
Portrait
Yes Yes Yes No No No Yes
2)
No Yes No yes
1)
Yes
KTP60
0 Basic
PN
Yes Yes Yes No No Yes No Yes No Yes No No
KTP60
0 Basic
PN
Portrait
Yes Yes Yes No No Yes No Yes No Yes No No
KTP60
0 Basic
mono
PN
Yes Yes Yes No No Yes No Yes No Yes No No
KTP60
0 Basic
mono
PN
Portrait
Yes Yes Yes No No Yes No Yes No Yes No No
KTP10
00
Basic
DP
Yes Yes Yes No No No Yes
2)
No Yes No yes
1)
Yes
KTP10
00
Basic
PN
Yes Yes Yes No No Yes No Yes No Yes No No
TP150
0 Basic
PN
Yes Yes Yes No No Yes No Yes No Yes No No
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1889
1)
only with RS 422-RS232 converter
Order number: 6AV6 671-8XE00-0AX0
2)
Direct communication with PLC 5 or KF2 module, otherwise only approved with
RS422-RS232 converter (option).
Order number: 6AV6 671-8XE00-0AX0
Interfaces of the Basic Panels
Device dependency of the Basic Panels
The following table shows which HMI device interfaces are available for the communication
driver protocols.
Table 9-18 Basic Panels
KTP300
Basic
KTP400
Basic PN
KTP600
Basic DP
KTP600
Basic PN
KTP1000
Basic DP
KTP1000
Basic PN
TP1500
Basic PN
SIMATIC S7 -
PPI
1)
MPI/DP (X2) MPI/DP (X2)
SIMATIC S7 -
MPI
MPI/DP (X2) MPI/DP (X2)
SIMATIC S7 -
PROFIBUS
MPI/DP (X2) MPI/DP (X2)
SIMATIC S7 -
PROFINET
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
SIMATIC HMI
HTTP protocol
OPC
Allen-Bradley
EtherNet/IP
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
Allen-Bradley
DF1
MPI/DP (X2)
2)
MPI/DP (X2)
2)
Mitsubishi TCP/
IP
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
Mitsubishi FX MPI/DP (X2)
(RS422)
MPI/DP (X2)
(RS422)
Modicon
Modbus TCP
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
PROFINET
(X1)
Modicon
Modbus RTU
MPI/DP (X2)
3)
MPI/DP (X2)
3)
Omron Host
Link
MPI/DP (X2)
(RS422)
MPI/DP (X2)
(RS422)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1890 System Manual, 08/2011,
1)
For SIMATIC S7-200 only
2)
Direct communication with PLC5 or KF2 module, otherwise only approved with RS422-
RS232 converter (option).
Order number: 6AV6 671-8XE00-0AX0
3)
only approved with RS 422-RS232 converter
Order number: 6AV6 671-8XE00-0AX0
Area pointers for Basic Panels
Introduction
Area pointers are parameter fields from which the HMI device obtains information about the
location and size of data areas in the PLC. During communication, the PLC and the HMI device
alternately access these data areas for read and write operations. Based on the evaluation of
data stored in the data areas, the PLC and HMI device initiate mutually defined actions.
WinCC uses the following area pointers:
Job mailbox
Project ID
Screen number
Data record
Date/time
Date/time PLC
Coordination
Availability of the area pointers
The following table shows the availability of the area pointers on the HMI devices. Note that
the area pointers can be used only for available communication drivers.
Area pointer
KP300 Basic KTP400
Basic PN
KTP600
Basic PN
KTP600
Basic DP
KTP1000
Basic PN
KTP1000
Basic DP
TP1500
Basic PN
Screen number Yes Yes Yes Yes Yes Yes Yes
Data record Yes Yes Yes Yes Yes Yes Yes
Date/time Yes Yes Yes Yes Yes Yes Yes
Date/time PLC Yes Yes Yes Yes Yes Yes Yes
Coordination Yes Yes Yes Yes Yes Yes Yes
Project ID Yes Yes Yes Yes Yes Yes Yes
Job mailbox Yes Yes Yes Yes Yes Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1891
9.11.4.2 Panel
Communication drivers for Panels
Device dependency of Panels
The following table shows which communication drivers you can configure with the various
Panels.
Communication drivers
HMI
devices
SIMATI
C S7
1200
SIMATI
C S7
300/40
0
SIMATI
C S7
200
SIMATI
C
HTTP
protoco
l
OPC Allen-
Bradley
EtherN
et/IP
Allen-
Bradley
DF1
Mitsubi
shi MC
TCP/IP
Mitsubi
shi FX
Modico
n
Modbu
s TCP/
IP
Modico
n
Modbu
s RTU
Omron
Host
Link
OP 73 No Yes Yes No No No No No No No No No
OP 77A Yes Yes Yes No No No Yes
2) 3)
No Yes No Yes
1)
Yes
3)
OP 77B Yes Yes Yes No No No Yes
2) 3)
No Yes No Yes Yes
3)
TP 177
A
Yes Yes Yes No No No Yes
2) 3)
No Yes No Yes
1)
Yes
3)
TP
177A
Portrait
Yes Yes Yes No No No Yes
2) 3)
No Yes No Yes
1)
Yes
3)
TP
177B 4"
Yes Yes Yes Yes No Yes Yes
2) 3)
Yes Yes Yes Yes
1) 3)
Yes
3)
TP
177B
6"
mono
Yes Yes Yes No No No Yes
2) 3)
No Yes No Yes
1) 3)
Yes
3)
TP
177B 6"
Yes Yes Yes Yes No Yes Yes
2) 3)
Yes Yes Yes Yes
1) 3)
Yes
3)
OP
177B
6"
mono
Yes Yes Yes No No No Yes
2) 3)
No Yes No Yes
1) 3)
Yes
3)
OP
177B 6"
Yes Yes Yes Yes No Yes Yes
2) 3)
Yes Yes Yes Yes
1) 3)
Yes
3)
TP 277
6"
Yes Yes Yes Yes No Yes Yes
2) 3)
Yes Yes Yes Yes
1) 3)
Yes
3)
OP
277 6"
Yes Yes Yes Yes No Yes Yes
2) 3)
Yes Yes Yes Yes
1) 3)
Yes
3)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1892 System Manual, 08/2011,
1)
only approved with RS 422-RS232 converter
Order number: 6AV6 671-8XE00-0AX0
2)
Direct communication with PLC 5 or KF2 module, otherwise only approved with
RS422-RS232 converter (option).
Order number: 6AV6 671-8XE00-0AX0
3)
"PROFINET IO Enabled" must be disabled.
Interfaces of Panels
Device dependency of Panels
The following table shows which HMI device interfaces are available for the communication
driver protocols.
Table 9-19 Panels
OP 73 OP 77A OP 77B
3)
TP 177A TP 177B
3)
OP 177B
3)
TP 277
3)
OP 277
3)
SIMATIC S7 - PPI
1)
IF1B IF1B IF1B IF1B IF1B IF1B
SIMATIC S7 - MPI IF1B IF1B IF1B IF1B IF1B IF1B
SIMATIC S7 - PROFIBUS IF1B IF1B IF1B IF1B IF1B IF1B
SIMATIC S7 - PROFINET ETHERNE
T
2)
ETHERNE
T
2)
SIMATIC HMI HTTP protocol ETHERNE
T
2)
ETHERNE
T
OPC
Allen-Bradley Ethernet IP ETHERNE
T
2)
ETHERNE
T
Allen-Bradley DF1 IF1B
5)
IF1A
3)
,
IF1B
3)4)
IF1B
5)
IF1B
3) 5) 8)
IF1B
3) 5) 8)
Mitsubishi MC TCP/IP ETHERNE
T
2)
ETHERNE
T
Mitsubishi FX IF1B IF1A
3)
,
IF1B
3)
IF1B IF1B
3) 8)
IF1B
3) 8)
Modicon Modbus TCP ETHERNE
T
2)
ETHERNE
T
Modicon Modbus RTU IF1B
7)
IF1A
3)
,
IF1B
3)6)
IF1B
7)
IF1B
7)
3) 8)
IF1B
7) 3) 8)
Omron Host Link IF1B IF1A
3)
,
IF1B
3)
IF1B IF1B
3) 8)
IF1B
3) 8)
1)
For SIMATIC S7-200 only
2)
Not approved for TP 177B DP, OP 177B DP.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1893
3)
For serial communication, deselect "Remote Control" of "Channel 1" in the "File >
Transfer >Options" menu.
4)
Only with PLC5 or KF2 module.
5)
Direct communication with PLC5 or KF2 module, otherwise only approved with RS422-
RS232 converter 6AV6 671-8XE00-0AX0 (option)
6)
Can be selected and used, but not approved.
7)
Only with RS 422-RS 232 converter 6AV6 671-8XE00-0AX0 (option)
8)
"PROFINET IO Enabled" must be disabled.
Area pointers for Panels
Introduction
Area pointers are parameter fields from which the HMI device obtains information about the
location and size of data areas in the PLC. During communication, the PLC and the HMI device
alternately access these data areas for read and write operations. Based on the evaluation of
data stored in the data areas, the PLC and HMI device initiate mutually defined actions.
WinCC uses the following area pointers:
Job mailbox
Project ID
Screen number
Data record
Date/time
Date/time PLC
Coordination
Availability of the area pointers
The following table shows the availability of the area pointers on the HMI devices. Note that
the area pointers can be used only for available communication drivers.
Area pointers
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
Screen number Yes Yes Yes Yes Yes Yes
Data record No Yes Yes Yes Yes Yes
Date/time Yes Yes Yes Yes Yes Yes
Date/time PLC Yes Yes Yes Yes Yes Yes
Coordination Yes Yes Yes Yes Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1894 System Manual, 08/2011,
OP 73 OP 77A OP 77B TP 177A TP 177B
OP 177B
TP 277
OP 277
Project ID Yes Yes Yes Yes Yes Yes
Job mailbox Yes Yes Yes Yes Yes Yes
9.11.4.3 Comfort Panel
Communication drivers for Comfort Panels
Device dependency of Comfort Panels
The following table shows which communication drivers you can configure with the various
Comfort Panels.
Communication drivers
HMI
devices
SIM
ATI
C
S7
120
0
SIMATI
C S7
300/40
0
SIMATI
C S7
200
SIMATI
C
HTTP
protoco
l
OPC
1)
Allen-
Bradley
EtherN
et/IP
Allen-
Bradley
DF1
Mitsubi
shi MC
TCP/IP
Mitsubi
shi FX
Modico
n
Modbu
s TCP/
IP
Modico
n
Modbu
s RTU
Omron
Host
Link
KP400
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
KTP400
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
KTP400
Comfort
Portrait
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
KP700
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
TP700
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
TP700
Comfort
Portrait
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
KP900
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
TP900
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
TP900
Comfort
Portrait
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
KP1200
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1895
HMI
devices
SIM
ATI
C
S7
120
0
SIMATI
C S7
300/40
0
SIMATI
C S7
200
SIMATI
C
HTTP
protoco
l
OPC
1)
Allen-
Bradley
EtherN
et/IP
Allen-
Bradley
DF1
Mitsubi
shi MC
TCP/IP
Mitsubi
shi FX
Modico
n
Modbu
s TCP/
IP
Modico
n
Modbu
s RTU
Omron
Host
Link
TP1200
Comfort
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
TP1200
Comfort
Portrait
Yes Yes Yes Yes Yes Yes Yes
2)3)
Yes Yes
3)
Yes yes
3)4)
Yes
3)
1)
OPC-UA (DA only) Client
OPC-XML DA Server
2)
Direct communication with PLC 5 or KF2 module, otherwise only approved with RS422-
RS232 converter (option).
Order number: 6AV6 671-8XE00-0AX0
3)
"PROFINET IO Enabled" must be disabled.
4)
Only approved with RS 422-RS232 converter
Order number: 6AV6 671-8XE00-0AX0
Interfaces of Comfort Panels
Device dependency of Comfort Panels
The following table shows which HMI device interfaces are available for the communication
driver protocols.
Table 9-20 Comfort Panels
KP400
Comfort
KTP400
Comfort
KP700
Comfort
TP700
Comfort
KP900
Comfort
TP900
Comfort
KP1200
Comfort
TP1200
Comfort
SIMATIC S7 -
PPI
1)
IF1B IF1B IF1B IF1B IF1B IF1B IF1B IF1B
SIMATIC S7 -
MPI
IF1B IF1B IF1B IF1B IF1B IF1B IF1B IF1B
SIMATIC S7 -
PROFIBUS
IF1B IF1B IF1B IF1B IF1B IF1B IF1B IF1B
SIMATIC S7 -
PROFINET
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
SIMATIC HMI
HTTP protocol
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
OPC ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
Allen-Bradley
EtherNet/IP
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1896 System Manual, 08/2011,
KP400
Comfort
KTP400
Comfort
KP700
Comfort
TP700
Comfort
KP900
Comfort
TP900
Comfort
KP1200
Comfort
TP1200
Comfort
Allen-Bradley
DF1
IF1B
1)3)4)
IF1B
1)3)4)
IF1B
1)3)4)
IF1B
1)3)4)
IF1B
1)3)4)
IF1B
1)3)4)
IF1B
1)3)4)
IF1B
1)3)4)
Mitsubishi
MC TCP/IP
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
Mitsubishi FX IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
Modicon
Modbus TCP/
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
ETHERNE
T
Modicon
Modbus RTU
IF1B
2)3)4)
IF1B
2)3)4)
IF1B
2)3)4)
IF1B
2)3)4)
IF1B
2)3)4)
IF1B
2)3)4)
IF1B
2)3)4)
IF1B
2)3)4)
Omron Host
Link
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
IF1B
3)4)
1)
Direct communication with PLC5 or KF2 module, otherwise only with RS422-RS232
converter.
Order number: 6AV6 671-8XE00-0AX0
2)
only with RS422-RS232 converter (option)
Order number: 6AV6 671-8XE00-0AX0
3)
For serial communication, deselect "Remote Control" of "Channel 1" in the "File >
Transfer >Options" menu.
4)
"PROFINET IO Enabled" must be disabled.
Area pointers for Comfort Panel
Introduction
Area pointers are parameter fields from which the HMI device obtains information about the
location and size of data areas in the PLC. During communication, the PLC and the HMI device
alternately access these data areas for read and write operations. Based on the evaluation of
data stored in the data areas, the PLC and HMI device initiate mutually defined actions.
WinCC uses the following area pointers:
Job mailbox
Project ID
Screen number
Data record
Date/time
Date/time PLC
Coordination
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1897
Availability of the area pointers
The following table shows the availability of the area pointers on the HMI devices. Note that
the area pointers can be used only for available communication drivers.
Area pointer
KP400
Comfort
KTP400
Comfort
KP700
Comfort
TP700
Comfort
KP900
Comfort
TP900
Comfort
KP1200
Comfort
TP1200
Comfort
Screen number Yes Yes Yes Yes Yes Yes Yes Yes
Data record Yes Yes Yes Yes Yes Yes Yes Yes
Date/time Yes Yes Yes Yes Yes Yes Yes Yes
Date/time PLC Yes Yes Yes Yes Yes Yes Yes Yes
Coordination Yes Yes Yes Yes Yes Yes Yes Yes
Project ID Yes Yes Yes Yes Yes Yes Yes Yes
Job mailbox Yes Yes Yes Yes Yes Yes Yes Yes
9.11.4.4 Multi Panel
Communication drivers for Multi Panels
Device dependency of Multi Panels
The following table shows which communication drivers you can configure with the various
Multi Panels.
Communication drivers
HMI
devices
SIM
ATI
C S
7 12
00
SIMATI
C S7 30
0/400
SIMATI
C S7 20
0
SIMATI
C
HTTP
protoco
l
OPC
1)
Allen-
Bradley
EtherN
et/IP
Allen-
Bradley
DF1
Mitsubi
shi MC
TCP/IP
Mitsubi
shi FX
Modico
n
Modbu
s TCP/
IP
Modico
n
Modbu
s RTU
Omron
Host
Link
MP 177 6"
Touch
Yes Yes Yes Yes No Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
MP 277 8"
Key
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
MP 277
10" Key
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
MP 277
10" Touch
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
MP 377
12" Key
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1898 System Manual, 08/2011,
HMI
devices
SIM
ATI
C S
7 12
00
SIMATI
C S7 30
0/400
SIMATI
C S7 20
0
SIMATI
C
HTTP
protoco
l
OPC
1)
Allen-
Bradley
EtherN
et/IP
Allen-
Bradley
DF1
Mitsubi
shi MC
TCP/IP
Mitsubi
shi FX
Modico
n
Modbu
s TCP/
IP
Modico
n
Modbu
s RTU
Omron
Host
Link
MP 377
12" Touch
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
MP 377
15" Touch
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
MP 377
19" Touch
Yes Yes Yes Yes Yes Yes yes
3)4)
Yes Yes
4)
Yes yes
2)4)
Yes
4)
1)
OPC-XML DA Server
OPC-DA Client (Inproc)
2)
only approved with RS 422-RS232 converter
Order number: 6AV6 671-8XE00-0AX0
3)
Direct communication with PLC 5 or KF2 module, otherwise only with RS422-RS232
converter (option).
Order number: 6AV6 671-8XE00-0AX0
4)
"PROFINET IO Enabled" must be disabled.
Interfaces of Multi Panels
Device dependency of Multi Panels
The following table shows which HMI device interfaces are available for the communication
driver protocols.
Table 9-21 Multi Panels
MP 177
3)
MP 277
3)
MP 377
3)
SIMATIC S7 - PPI
1)
IF1B IF1B IF1B
SIMATIC S7 - MPI IF1B IF1B IF1B
SIMATIC S7 - PROFIBUS IF1B IF1B IF1B
SIMATIC S7 - PROFINET ETHERNET ETHERNET ETHERNET
SIMATIC HMI HTTP protocol ETHERNET ETHERNET ETHERNET
OPC - ETHERNET ETHERNET
Allen-Bradley EtherNet/IP ETHERNET ETHERNET ETHERNET
Allen-Bradley DF1 IF1B
3) 4) 5)
IF1B
3) 4) 5)
IF1B
3) 4) 5)
Mitsubishi MC TCP/IP ETHERNET ETHERNET ETHERNET
Mitsubishi FX IF1B
3)5)
IF1B
3)5)
IF1B
3)5)
Modicon Modbus TCP ETHERNET ETHERNET ETHERNET
Modicon Modbus RTU IF1B
2) 3) 5)
IF1B
2) 3) 5)
IF1B
2) 3) 5)
Omron Host Link IF1B
3)5)
IF1B
3)5)
IF1B
3)5)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1899
1)
For SIMATIC S7-200 only
2)
only with RS 422-RS232 converter (option)
Order number: 6AV6 671-8XE00-0AX0
3)
For serial communication, deselect "Remote Control" of "Channel 1" in the "File >
Transfer >Options" menu.
4)
Direct communication with PLC5 or KF2 module, otherwise only approved with RS422-
RS232 converter (option).
Order number: 6AV6 671-8XE00-0AX0
5)
"PROFINET IO Enabled" must be disabled.
Area pointers for Multi Panel
Introduction
Area pointers are parameter fields from which the HMI device obtains information about the
location and size of data areas in the PLC. During communication, the PLC and the HMI device
alternately access these data areas for read and write operations. Based on the evaluation of
data stored in the data areas, the PLC and HMI device initiate mutually defined actions.
WinCC uses the following area pointers:
Job mailbox
Project ID
Screen number
Data record
Date/time
Date/time PLC
Coordination
Availability of the area pointers
The following table shows the availability of the area pointers on the HMI devices. Note that
the area pointers can be used only for available communication drivers.
Area pointers
MP 177 MP 277 MP 377
Screen number Yes Yes Yes
Data record Yes Yes Yes
Date/time Yes Yes Yes
Date/time PLC Yes Yes Yes
Coordination Yes Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1900 System Manual, 08/2011,
MP 177 MP 277 MP 377
Project ID Yes Yes Yes
Job mailbox Yes Yes Yes
9.11.4.5 Mobile Panel
Communication drivers for Mobile Panels
Device dependency of Mobile Panels
The following table shows which communication drivers you can configure with the various
Mobile Panels.
Communication drivers
HMI
devices
SIM
ATIC
S7
1200
SIMA
TIC
S7
300/4
00
SIMA
TIC
S7
200
SIMA
TIC
HTTP
protoc
ol
OPC Allen-
Bradle
y
Ether
Net/IP
Allen-
Bradle
y DF1
Mitsubis
hi MC
TCP/IP
Mitsu
bishi
FX
Modicon
Modbus
TCP/IP
Modicon
Modbus
RTU
Omron Host
Link
Mobile
Panel
177 6"
DP
Yes Yes Yes No No No Yes
1)
No Yes
1)
No Yes
1)
Yes
1)
Mobile
Panel
177 6"
PN
Yes Yes Yes Yes No Yes No Yes No Yes No No
Mobile
Panel
277 8"
Yes Yes Yes Yes No Yes Yes
1)
Yes Yes
1)
Yes Yes
1)
Yes
1)
Mobile
Panel
277 8"
IWLAN
V2
Yes Yes Yes Yes No Yes No Yes No Yes No No
Mobile
Panel
277F 8"
IWLAN
V2
Yes Yes Yes Yes No Yes No No No No No No
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1901
HMI
devices
SIM
ATIC
S7
1200
SIMA
TIC
S7
300/4
00
SIMA
TIC
S7
200
SIMA
TIC
HTTP
protoc
ol
OPC Allen-
Bradle
y
Ether
Net/IP
Allen-
Bradle
y DF1
Mitsubis
hi MC
TCP/IP
Mitsu
bishi
FX
Modicon
Modbus
TCP/IP
Modicon
Modbus
RTU
Omron Host
Link
Mobile
Panel
277F 8"
IWLAN
V2
(RFID
tag)
Yes Yes Yes Yes No Yes No No No No No No
Mobile
Panel
277 10"
Yes Yes Yes Yes No Yes Yes
1)
Yes Yes
1)
Yes Yes
1)
Yes
1)
1)
"PROFINET IO Enabled" must be disabled.
Interfaces of Mobile Panels
Device dependency of Mobile Panels
The following table shows which HMI device interfaces are available for the communication
driver protocols.
Table 9-22 Mobile Panels
Mobile Panel
177 DP
3)
Mobile Panel
177 PN
Mobile Panel
277
2)3)
Mobile Panel
277 IWLAN V2
Mobile Panel
277F V2
IWLAN
Mobile Panel
277F IWLAN
V2 (RFID tag)
SIMATIC S7 - PPI
1)
IF1B IF1B
SIMATIC S7 - MPI IF1B IF1B
SIMATIC S7 -
PROFIBUS
IF1B IF1B
SIMATIC S7 -
PROFINET
ETHERNET ETHERNET ETHERNET ETHERNET ETHERNET
SIMATIC HMI
HTTP protocol
ETHERNET ETHERNET ETHERNET ETHERNET ETHERNET
OPC ETHERNET ETHERNET ETHERNET
Allen-Bradley DF1 IF1A
3)
, IF1B
3)
4)
6)
(terminal
box)
IF1A
3)
, IF1B
3)
4)
6)
(terminal
box)
Allen-Bradley
EtherNet/IP
--- ETHERNET ETHERNET ETHERNET ETHERNET ETHERNET
Mitsubishi MC TCP/
IP
-- ETHERNET ETHERNET ETHERNET
Mitsubishi FX IF1A
3)
, IF1B
3)
6)
(terminal box)
IF1A
3)
, IF1B
3)
6)
(terminal box)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1902 System Manual, 08/2011,
Mobile Panel
177 DP
3)
Mobile Panel
177 PN
Mobile Panel
277
2)3)
Mobile Panel
277 IWLAN V2
Mobile Panel
277F V2
IWLAN
Mobile Panel
277F IWLAN
V2 (RFID tag)
Modicon
Modbus RTU
IF1A
3)
, IF1B
3)
5)
6)
(terminal
box)
IF1A
3)
, IF1B
3)
5)
6)
(terminal
box)
Modicon
Modbus TCP/IP
ETHERNET ETHERNET ETHERNET
Omron Host Link IF1A
3)
, IF1B
3)
6)
(terminal box)
IF1A
3)
, IF1B
3)6)
(terminal
box)
1)
For SIMATIC S7-200 only
2)
Depending on the terminal box used
3)
For serial communication, deselect "Remote Control" of "Channel 1" in the "File >
Transfer >Options" menu.
4)
With PLC5 and KF2 module only
5)
Can be selected and used, but not approved.
6)
"PROFINET IO Enabled" must be disabled.
Area pointers for Mobile Panel
Introduction
Area pointers are parameter fields from which the HMI device obtains information about the
location and size of data areas in the PLC. During communication, the PLC and the HMI device
alternately access these data areas for read and write operations. Based on the evaluation of
data stored in the data areas, the PLC and HMI device initiate mutually defined actions.
WinCC uses the following area pointers:
Job mailbox
Project ID
Screen number
Data record
Date/time
Date/time PLC
Coordination
Availability of the area pointers
The following table shows the availability of the area pointers on the HMI devices. Note that
the area pointers can be used only for available communication drivers.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1903
Area pointer
Mobile
Panel 177
Mobile
Panel 277
Mobile
Panel 277
IWLAN V2
Mobile
Panel 277F
IWLAN V2
Mobile
Panel 277F
IWLAN V2
(RFID tag)
Mobile
Panel 277
Screen number Yes Yes Yes Yes Yes Yes
Data record Yes Yes Yes Yes Yes Yes
Date/time Yes Yes Yes Yes Yes Yes
Date/time PLC Yes Yes Yes Yes Yes Yes
Coordination Yes Yes Yes Yes Yes Yes
Project ID Yes Yes Yes Yes Yes Yes
Job mailbox Yes Yes Yes Yes Yes Yes
9.11.4.6 PC systems
Communication drivers for PC systems
Device dependency
The following table shows which communication drivers you can configure with the various
Runtimes on a PC.
Communication drivers
HMI
devices
SIM
ATIC
S7
1200
SIMA
TIC
S7
300/4
00
SIMA
TIC
S7
200
SIMA
TIC
HTTP
protoc
ol
OPC Allen-
Bradle
y
Ether
Net/IP
Allen-
Bradle
y DF1
Mitsubis
hi MC
TCP/IP
Mitsu
bishi
FX
Modicon
Modbus
TCP/IP
Modicon
Modbus
RTU
Omron Host
Link
WinCC
RT
Advance
d
Yes Yes Yes Yes Yes
1)
Yes Yes Yes Yes Yes Yes Yes
WinCC
RT
Professi
onal
Yes Yes No No Yes
2)
Yes No Yes No Yes No No
1)
OPC-DA-Client, OPC-XML-DA-Client, OPC-UA(DA only) Client and OPC-DA-Server
2)
OPC-DA-Client, OPC-XML-DA-Client and OPC-DA-Server, OPC-XML-DA-Server
(optional),
OPC-HDA-Server (optional), OPC-AE-Server (optional) , OPC-UA(DA only)-Server
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1904 System Manual, 08/2011,
Interfaces for PC systems
Device dependency
The following table shows which HMI device interfaces are available for the communication
driver protocols.
WinCC RT Advanced WinCC RT Professional
SIMATIC S7 - PPI MPI/DP
2)
--
SIMATIC S7 - MPI MPI/DP
2)
MPI/DP
2)
SIMATIC S7 - PROFIBUS MPI/DP
2)
MPI/DP
2)
SIMATIC S7 - PROFINET ETHERNET ETHERNET
SIMATIC HMI HTTP protocol ETHERNET ETHERNET
OPC ETHERNET ETHERNET
Allen-Bradley EtherNet/IP ETHERNET ETHERNET
Allen-Bradley DF1 COM1 to COM4
1)
--
Mitsubishi MC TCPI/IP ETHERNET ETHERNET
Mitsubishi FX COM1 to COM4
1)
--
Modicon Modbus TCP/IP ETHERNET ETHERNET
Modicon Modbus RTU COM1 to COM4
1)
--
Omron Host Link COM1 to COM4
1)
--
1)
COM2 is blocked for Panel PC 477
2)
in SIMATIC PC via integrated interface
in Standard PC e.g. SIMATIC NET CP 5611 A2
Area pointers for PC systems
Introduction
Area pointers are parameter fields from which WinCC RT Advanced obtains information about
the location and size of data areas in the PLC. During communication, the PLC and the HMI
device alternately access these data areas for read and write operations. Based on the
evaluation of data stored in the data areas, the PLC and HMI device initiate mutually defined
actions.
WinCC uses the following area pointers:
Job mailbox
Project ID
Screen number
Data record
Date/time
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1905
Date/time PLC
Coordination
Availability of the area pointers
The following table shows the availability of the area pointers on the HMI devices. Note that
the area pointers can be used only for available communication drivers.
Table 9-23 WinCC RT Advanced
WinCC RT Advanced
Screen number Yes
Data record Yes
Date/time Yes
Date/time PLC Yes
Coordination Yes
Project ID Yes
Job mailbox Yes
9.11.4.7 Parallel communication
Parallel communication of communication drivers
The following table shows an overview of which communication drivers you can use
simultaneously on one HMI device.
Note
Parallel communication is not approved for Basic Panels.
Parallel communication over Ethernet interfaces
The approved combinations can be operated via the same Ethernet interface. Several Ethernet
interfaces are not required.
Parallel communication only concerns the Ethernet-based communication drivers.
Allen-
Bradley
EtherNet/
IP
Mitsubishi
MC TCP/
IP
Modicon
Modbus
TCPIP
OPC (DA/
XML DA)
OPC UA
(DA)
SIMATIC
S7 300/40
0
SIMATIC
S7 1200
SIMATIC
HTTP
protocol
Sinumerik
NC
Allen-
Bradley
EtherNet/
IP
-- No No Yes Yes Yes Yes Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1906 System Manual, 08/2011,
Mitsubishi
MC TCP/
IP
No -- No Yes Yes No No Yes No
Modicon
Modbus
TCPIP
No No -- Yes Yes No No Yes No
OPC (DA/
XML DA)
Yes Yes Yes -- Yes Yes Yes Yes Yes
OPC UA
(DA)
Yes Yes Yes Yes -- Yes Yes Yes Yes
SIMATIC
S7 300/40
0
Yes No No Yes Yes -- Yes Yes Yes
SIMATIC
S7 1200
Yes No No Yes Yes Yes -- Yes Yes
SIMATIC
HTTP
protocol
Yes Yes Yes Yes Yes Yes Yes -- Yes
Sinumerik
NC
Yes No No Yes Yes Yes Yes Yes --
Parallel communication over serial interfaces
The following applies for parallel communication over serial interfaces:
One communication driver per interface.
One interface per communication driver.
9.11.5 Communicating with SIMATIC S7 1200
9.11.5.1 Communication with SIMATIC S7 1200
Introduction
This section describes the communication between an HMI device and the SIMATIC S7 1200
PLC.
You can configure the following communication channels for the SIMATIC S7 1200 PLC:
PROFINET
PROFIBUS
HMI connection for communication
You configure connections between the HMI device and a SIMATIC S7 1200 in the "Devices
& Networks" editor. If you have configured a HMI device with a serial port, you must configure
a PROFIBUS-capable communication module to the SIMATIC S7 1200.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1907
9.11.5.2 Communication via PROFINET
Configuring an HMI connection
Communication via PROFINET
HMI connections via PROFINET
If you have inserted an HMI device and a SIMATIC S7 1200 into the project, you interconnect
the two PROFINET interfaces in the "Devices & Networks" editor.
You can also connect multiple HMI devices to one SIMATIC S7 1200 and multiple SIMATIC
S7 1200s to one HMI device. The maximum number of communication partners that you can
connect to an HMI device is dependent on the HMI device used.
Additional information is available in the documentation for the respective HMI device.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFINET in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via PROFINET
in the "Connections" editor of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1908 System Manual, 08/2011,
Configuring an HMI connection via PROFINET
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via
PROFINET or Ethernet in the "Devices & Networks" editor.
CAUTION
Communication via Ethernet
In Ethernet-based communication, the end user is responsible for the security of his data
network.
Targeted attacks can overload the device and interfere with proper functioning.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 1200
HMI device with PROFINET or Ethernet interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed graphically in the network
view.
2. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
3. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFINET or Ethernet interface of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1909
4. Click the connecting line.
5. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
6. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFINET parameters (Page 1916)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created a connection between an HMI device and a SIMATIC S7 1200. The IP
address and subnet mask connection parameters are configured.
Configuring an HMI connection
Communication via PROFINET
Communication via PROFINET
This section describes the communication between a WinCC Runtime and the SIMATIC
S7 1200 PLC via PROFINET.
You can use the following WinCC Runtimes as an HMI device:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1910 System Manual, 08/2011,
WinCC RT Advanced
WinCC Runtime as HMI device
You configure the HMI connections between WinCC Runtime and SIMATIC S7 1200 in the
"Devices & Networks" editor.
If you want to use a WinCC Runtime as an HMI device, you have the following options:
1. You create a SIMATIC PC and configure a WinCC Runtime on this SIMATIC PC.
In this way you use the SIMATIC PC with a WinCC Runtime as an HMI device.
2. You create a Runtime and configure a communication processor to the Runtime.
In this way you use your configuration PC as an HMI device.
You can also connect multiple HMI devices to one SIMATIC S7 1200 and multiple SIMATIC
S7 1200s to one HMI device. The maximum number of communication partners that you can
connect to an HMI device is dependent on the HMI device used.
Additional information is available in the documentation for the respective HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1911
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFINET in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via PROFINET
in the "Connections" editor of the HMI device.
Configuring an HMI connection via PROFINET with a SIMATIC PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via
PROFINET or Ethernet in the "Devices & Networks" editor.
CAUTION
Communication via Ethernet
In Ethernet-based communication, the end user is responsible for the security of his data
network.
Targeted attacks can overload the device and interfere with proper functioning.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 1200
SIMATIC PC with PROFINET interface
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1912 System Manual, 08/2011,
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a WinCC Runtime from the hardware catalog to
the PC.
3. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
4. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFINET interface of the PC.
5. Click the connecting line.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1913
6. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
7. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFINET parameters (Page 1916)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created a connection between an HMI device and a SIMATIC S7 1200. The IP
address and subnet mask connection parameters are configured.
Configuring an HMI connection via PROFINET with a PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via
PROFINET or Ethernet in the "Devices & Networks" editor.
CAUTION
Communication via Ethernet
In Ethernet-based communication, the end user is responsible for the security of his data
network.
Targeted attacks can overload the device and interfere with proper functioning.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 1200
PC station with WinCC RT Advanced
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1914 System Manual, 08/2011,
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a communication processor from the hardware
catalog to the WinCC Runtime.
3. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1915
4. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFINET interface of the communication processor.
5. Click the connecting line.
6. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
7. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFINET parameters (Page 1916)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created a connection between an HMI device and a SIMATIC S7 1200. The IP
address and subnet mask connection parameters are configured.
PROFINET parameters
PROFINET parameters for the HMI connection
PROFINET parameters for the HMI connection
An overview of the configured HMI connection parameters can be found in the properties for
the HMI connection.
Only limited changes are possible in this Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1916 System Manual, 08/2011,
Displaying and changing the HMI connection parameters
1. Click the HMI connection in the "Devices & Networks" editor.
2. Change the parameters of the HMI connection in the Inspector window under "Properties
> General > General".
"Connection"
Displays whether the devices are networked together.
- displayed if the devices are networked together.
- displayed if the devices are not networked together.
"Connection path"
The communication partners of the selected HMI connection and the associated PROFINET
parameters are displayed in the "Connection path" area. Some of the areas displayed cannot
be edited in this dialog.
"End point"
Displays the device name. This area is not editable.
"Interface"
Displays the selected interface of the device. You can choose between several interfaces,
depending on the device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1917
"Interface type"
Displays the selected interface type. This area cannot be edited.
"Subnet"
Displays the selected subnet. This area cannot be edited.
"Address"
Displays the selected IP address of the device. This area cannot be edited.
"Find connection path" button
Enables the subsequent specification of connections.
PROFINET parameters for the HMI device
PROFINET parameters for the HMI device
An overview of the configured HMI device parameters can be found in the properties for the
HMI device.
Displaying and changing PROFINET parameters of the HMI device
1. Click the HMI device in the "Devices & Networks" editor.
2. Change the parameters of the HMI device in the Inspector window under "Properties >
General > General".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1918 System Manual, 08/2011,
"Interface networked with"
In the "Interface networked with" area, select the subnet of the HMI connection via which the
HMI device is connected to the network. You use the "Add new subnet" button to create a new
subnet.
"IP protocol"
"Set IP address in the project"
When you transfer the WinCC project to the HMI device, this IP address is set up directly
in the HMI device.
Note
The device is automatically restarted in the case of HMI devices with the Windows CE 3.0
operating system.
HMI devices with Windows CE 3.0:
OP 77B
TP 177B color PN/DP
TP 177B mono DP
OP 177B color PN/DP
OP 177B mono DP
Mobile Panel 177 PN
Mobile Panel 177 DP
TP 277 6"
OP 277 6"
"Subnet mask"
You assign data of the subnet mask in the "Subnet mask" area.
"Use IP router"
If you are using an IP router, select "Use IP router" and enter the router address in the
"Router address" field.
"Set IP address using a different method"
If the function "Set IP address using a different method" is activated, the IP address is not
taken from the project. You have to enter the IP address directly in the Control Panel of the
HMI device.
PROFINET parameters for the PLC
PROFINET parameters for the PLC
An overview of the configured parameters can be found in the properties for the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1919
Displaying and changing PROFINET parameters of the PLC
1. Click the PLC in the "Devices & Networks" editor.
2. Change the parameters of the PLC in the Inspector window under "Properties > General >
General".
"Interface networked with"
In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected
to the network. You use the "Add new subnet" button to create a new subnet.
"IP protocol"
"Interface type"
Depending on the HMI device type, you have various interfaces to choose from.
"IP address"
You assign the IP address of the HMI device in the "IP address" area.
"Subnet mask"
You assign data of the subnet mask in the "Subnet mask" area.
If you are using an IP router, select "Use IP router" and enter the router address in the field.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1920 System Manual, 08/2011,
Configuring Industrial Ethernet
Rules for the network configuration
The Ethernet interfaces of the devices have a default IP address that you can change.
IP address
The IP parameters are visible if the communication-capable devices support the TCP/IP
protocol.
The IP address consists of 4 decimal figures in the range of 0 to 255. The decimal figures are
separated from one another by a dot.
Example: 140.80.0.2
The IP address consists of the following:
The address of the (sub) net
The address of the node (generally also called host or network node)
Subnet mask
The subnet mask splits these two addresses. It determines which part of the IP address
addresses the network and which part of the IP address addresses the node.
The set bits of the subnet mask determine the network part of the IP address.
Example:
Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000
In the example given for the above IP address, the subnet mask shown here has the following
meaning:
The first 2 bytes of the IP address identify the subnet - i.e. 140.80. The last two bytes address
the node, thus 0.2.
It is generally true that:
The network address results from AND linking the IP address and subnet mask.
The node address results from AND NOT linking the IP address and subnet mask.
Relation between IP address and default subnet mask
An agreement exists relating to the assignment of IP address ranges and so-called "Default
subnet masks". The first decimal number (from the left) in the IP address determines the
structure of the default subnet mask. It determines the number of "1" values (binary) as follows:
IP address (decimal) IP address (binary) Address class Default subnet mask
0 to 126 0xxxxxxx.xxxxxxxx.... A 255.0.0.0
128 to 191 10xxxxxx.xxxxxxxx... B 255.255.0.0
192 to 223 110xxxxx.xxxxxxxx... C 255.255.255.0
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1921
Note
Range of values for the first decimal point
A value of between 224 and 255 is also possible for the first decimal number of the IP address
(address class D etc). This is, however, not recommended because there is no address check
for these values.
Masking other subnets
You can use the subnet mask to add further structures and form "private" subnets for a subnet
that is assigned one of the address classes A, B or C. This is done by setting other lower points
of the subnet mask to "1". For each bit set to "1", the number of "private" networks doubles
and the number of nodes they contain is halved. Externally, the network functions like an
individual network as it did previously.
Example:
You have a subnet of address class B (e.g. IP address 129.80.xxx.xxx) and change the default
subnet mask as follows:
Masks Decimal Binary
Default subnet mask 255.255.0.0 11111111.11111111.00000000.
00000000
Subnet mask 255.255.128.0 11111111.11111111.10000000.
00000000
Result:
All nodes with addresses between 129.80.001.xxx and 129.80.127.xxx are on one subnet, all
nodes with addresses between 129.80.128.xxx and 129.80.255.xxx are on another subnet.
Router
The job of the routers is to connect the subnets. If an IP datagram is to be sent to another
network, it first has to be conveyed to a router. To make this possible, in this case you have
to enter the address of the router for each node in the subnet.
The IP address of a node in the subnet and the address of the router may only differ at the
points at which there is a "0" in the subnet mask.
Configuring time synchronization for integrated connections
Introduction
You configure time synchronization for an integrated connection in the "Devices & Networks"
editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1922 System Manual, 08/2011,
Requirements
An HMI connection between an HMI device and a SIMATIC S7 1200 has been configured.
The HMI device must support the "time synchronization" function.
The "Devices & Networks" editor is open.
Procedure
1. Click the line of the HMI connection in the "Devices & networks" editor.
2. Select the following in the inspector window under "General > Time synchronization >
Settings":
None: No time synchronization is used.
Master: The HMI device sets the time.
Slave: The PLC sets the time.
Setting port options
Setting the port options
Changing connection settings for the PROFINET IO port
You can change the network settings for the PROFINET IO port as required. By default, the
settings are made automatically. In normal situations, this guarantees problem-free
communication.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1923
Possible settings for transmission rate / duplex
Depending on the selected device, you can make the following settings for "Transmission rate /
duplex":
Automatic setting
Recommended default setting of the port. The transmission settings are automatically
"negotiated" with the peer port. The "Enable autonegotiation" option is also enabled as a
default, in other words, you can use cross cables or patch cables for the connection.
TP/ITP at x Mbps full duplex (half duplex)
Setting of the transmission rate and the full duplex/half duplex mode. The effectiveness
depends on the "Enable autonegotiation" setting:
Autonegotiation enabled
You can use both cross cable and patch cable.
Autonegotiation disabled
Make sure that you use the correct cable (patch cable or cross cable)! The port is also
monitored with this setting.
Deactivated
Depending on the module type, the drop down list box can contain the "- Disabled -" option.
This option, for example, allows you to prevent access to an unused port for security
reasons. With this setting, diagnostic events are not generated.
"Monitor" option
This option enables or disables port diagnostics. Examples of port diagnostics: The link status
is monitored, in other words, the diagnostics are generated during link-down and the system
reserve is monitored in the case of fiber optic ports.
Option "Enable autonegotiation "
The autonegotiation setting can only be changed if a concrete medium (for example, TP 100
Mbps full duplex) is selected. Whether or not a concrete medium can be set depends on the
properties of the module.
If autonegotiation is disabled, this causes the port to be permanently specified, as for example,
is necessary for a prioritized startup of the IO device.
You must make sure the partner port has the same settings because with this option the
operating parameters of the connected network are not detected and the data transmission
rate and transmission mode can accordingly not be optimally set.
Note
When a local port is connected, STEP 7 makes the setting for the partner port if the partner
port supports the setting. If the partner port does not accept the setting, an error message is
generated.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1924 System Manual, 08/2011,
Wiring rules for disabled autonegotiation
Requirements
You have made the following settings for the port in question, for example, to accelerate the
startup time of the IO device:
Fixed transmission rate
Autonegotiation incl. autocrossing disabled
The time for negotiating the transmission rate during startup has been saved.
If you have disabled autonegotiation, you must observe the wiring rules.
Wiring rules for disabled autonegotiation
PROFINET devices have the following two types of ports:
Type of port PROFINET devices Note
Switch port with crossed pin
assignment
For IO devices: Port 2
For S7 CPUs with 2 ports: Ports
1 and 2
Crossed pin assignment means
that the pin assignment for the
ports for sending and receiving
between the respective
PROFINET devices is
exchanged internally.
End device port with uncrossed
pin assignment
For IO devices: Port 1
For S7 CPUs with one port: Port
1
-
Validity of the wiring rules
The cabling rules described in the following paragraph apply exclusively for the situation in
which you have specified a fixed port setting.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1925
Rules for cabling
You can connect several IO devices in line using a single cable type (patch cable). To do this,
you connect port 2 of the IO device (distributed I/O) with port 1 of the next IO device. The
following graphic gives an example with two IO devices.
P2 P2
Patch cables
Switch or
PROFlNET device
P2
Patch cables
lO device lO device
End device port
Switch port
P1 P1 P1
Boundaries at the port
Requirements
To use boundaries, the respective device must have more than one port. If the PROFINET
does not support boundary settings, they are not shown.
Enable boundaries
"Boundaries" are limits for transmission of certain Ethernet frames. The following boundaries
can be set at a port:
"End of discovery of accessible devices"
No forwarding of DCP frames to identify accessible devices. Devices downstream from this
port cannot be reached by the project tree under "Accessible devices". Devices downstream
from this port cannot be reached by the CPU.
"End of topology discovery"
LLDP frames (Link Layer Discovery Protocol) are not forwarded for topology detection.
"End of sync domain"
No forwarding of sync frames transmitted to synchronize nodes within a sync domain.
If you operate, for example, a PROFINET device with more than two ports in a ring, you
should prevent the sync frame from being fed into the ring by setting a sync boundary (at
the ports not inside the ring).
Additional example: If you want to use several sync domains, configure a sync domain
boundary for the port connected to a PROFINET device from the other sync domain.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1926 System Manual, 08/2011,
Restrictions
The following restrictions must be observed:
The individual check boxes can only be used if the port supports the function in question.
If a partner port has been determined for the port, the following check boxes cannot be
used:
"End of discovery of accessible devices"
"End of topology discovery"
If autonegotiation is disabled, none of the check boxes can be used.
9.11.5.3 Communication via PROFIBUS
Configuring an HMI connection
Communication via PROFIBUS
HMI connections via PROFIBUS
If you want to connect a SIMATIC S7 1200 to a HMI device via PROFIBUS, you must configure
a PROFIBUS-capable communication module to a slot of the controller first.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the
"Devices & Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1927
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device in the
"Connections" editor of the HMI device.
Configuring an HMI connection via PROFIBUS
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via
PROFIBUS in the "Devices & Networks" editor.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
HMI device with MPI/DP interface
SIMATIC S7 1200
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed graphically in the network
view.
2. Click the "Connections" button.
The devices available for connection are highlighted in color.
3. Use a drag-and-drop operation to move a PROFIBUS-capable communication module from
the hardware catalog to the PLC.
4. Click the HMI device interface.
5. Select the "PROFIBUS" interface type in the Inspector window under "Properties > General
> PROFIBUS address/ MPI address > Parameters".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1928 System Manual, 08/2011,
6. Click the interface of the communication module and use a drag-and-drop operation to draw
a connection to the HMI device.
7. Click the name of the connection.
The connection is displayed graphically in the Inspector window.
8. Click "Highlight HMI connection" and select the HMI connection.
9. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFIBUS parameters (Page 1935)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 1200 via
PROFIBUS.
Configuring an HMI connection
Communication via PROFIBUS
Communication via PROFIBUS
This section describes the communication between a WinCC Runtime and the SIMATIC S7
1200 PLC via PROFIBUS.
You can use the following WinCC Runtimes as an HMI device:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1929
WinCC RT Advanced
If you want to connect a SIMATIC S7 1200 to an HMI device via PROFIBUS, you must
configure a PROFIBUS-capable communication module in a slot of the PLC.
WinCC Runtime as HMI device
You configure the HMI connections between WinCC Runtime and SIMATIC S7 1200 in the
"Devices & Networks" editor.
If you want to use a WinCC Runtime as an HMI device, you have the following options:
1. You create a SIMATIC PC and configure a WinCC Runtime on this SIMATIC PC.
In this way you use the SIMATIC PC with a WinCC Runtime as an HMI device.
2. You create a WinCC Runtime and configure a communication processor to the Runtime.
In this way you use your configuration PC with a WinCC Runtime as an HMI device.
You can also connect multiple HMI devices to one SIMATIC S7 1200 and multiple SIMATIC
S7 1200s to one HMI device. The maximum number of communication partners that you can
connect to an HMI device is dependent on the HMI device used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1930 System Manual, 08/2011,
Additional information is available in the documentation for the respective HMI device.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via PROFIBUS
in the "Connections" editor of the HMI device.
Configuring an HMI connection via PROFIBUS with a SIMATIC PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via
PROFIBUS in the "Devices & Networks" editor.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 1200
SIMATIC PC with PROFIBUS interface
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1931
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a WinCC Runtime from the hardware catalog to
the PC.
3. Use a drag-and-drop operation to move a PROFIBUS-capable communication module from
the hardware catalog to the PLC.
4. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1932 System Manual, 08/2011,
5. Click the PROFIBUS interface of the communication module and use a drag-and-drop
operation to draw a connection to the PROFIBUS interface of the PC.
6. Click the connecting line.
7. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
8. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFIBUS parameters (Page 1935)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 1200 via
PROFIBUS.
Configuring an HMI connection via PROFIBUS with a PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 1200 via
PROFIBUS in the "Devices & Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1933
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 1200
PC station with WinCC RT Advanced
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a PROFIBUS-capable communication processor
from the hardware catalog to the WinCC Runtime.
3. Use a drag-and-drop operation to move a PROFIBUS-capable communication module from
the hardware catalog to the PLC.
4. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1934 System Manual, 08/2011,
5. Click the PROFIBUS interface of the communication module and use a drag-and-drop
operation to draw a connection to the PROFIBUS interface of the communication processor.
6. Click the connecting line.
7. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
8. Click the communication partners in the "Network view" and change the PROFIBUS
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFIBUS parameters (Page 1935)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 1200 via
PROFIBUS.
PROFIBUS parameters
PROFIBUS parameters for the HMI connection
PROFIBUS parameters for the HMI connection
An overview of the configured HMI connection parameters can be found in the properties for
the HMI connection.
Only limited changes are possible in this Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1935
Displaying and changing the HMI connection parameters
1. Click the HMI connection in the "Devices & Networks" editor.
2. Change the parameters of the HMI connection in the Inspector window under "Properties
> General > General".
"Connection"
Displays whether the devices are networked together.
- displayed if the devices are networked together.
- displayed if the devices are not networked together.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1936 System Manual, 08/2011,
"Connection path"
The communication partners of the selected HMI connection and the associated PROFIBUS
parameters are displayed in the "Connection path" area. Some of the areas displayed cannot
be edited in this dialog.
"End point"
Displays the device name. This area is not editable.
"Interface"
Displays the selected interface of the device. You can choose between several interfaces,
depending on the device.
"Interface type"
Displays the selected interface type. This area is not editable.
"Subnet"
Displays the selected subnet. This area is not editable.
"Address"
Displays the PROFIBUS address of the device. This area is not editable.
"Find connection path" button
Enables the subsequent specification of connections.
PROFIBUS parameters for the HMI device
PROFIBUS parameters for the HMI device
An overview of the configured HMI device parameters can be found in the properties for the
HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1937
Displaying and changing PROFIBUS parameters of the HMI device
1. Click the HMI device in the "Devices & Networks" editor.
2. Change the parameters of the HMI device in the Inspector window under "Properties >
General > General".
"Interface networked with"
In the "Interface networked with" area, select the subnet of the HMI connection via which the
HMI device is connected to the network. You use the "Add new subnet" button to create a new
subnet.
"Parameters"
"Interface type"
Depending on the HMI device type, you have various interfaces to choose from.
"Address"
You assign the PROFIBUS address of the HMI device in the "Address" area. The
PROFIBUS address must be unique throughout the PROFIBUS network.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1938 System Manual, 08/2011,
"Highest address"
The "Highest address" area displays the highest address of the PROFIBUS network.
"Transmission speed"
The "Transmission speed" is determined by the slowest device connected to the network.
The setting is identical throughout the network.
PROFIBUS parameters for the PLC
PROFIBUS parameters for the PLC
An overview of the configured parameters can be found in the properties for the PLC.
Displaying and changing PROFIBUS parameters of the PLC
1. Click the PLC in the "Devices & Networks" editor.
2. Change the parameters of the PLC in the Inspector window under "Properties > General >
General".
"Interface networked with"
In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected
to the network. You use the "Add new subnet" button to create a new subnet.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1939
"Parameters"
"Interface type"
Depending on the HMI device type, you have various interfaces to choose from.
"Address"
You assign the PROFIBUS address of the HMI device in the "Address" area. The
PROFIBUS address must be unique throughout the PROFIBUS network.
"Highest address"
The "Highest address" area displays the highest address of the PROFIBUS network.
"Transmission speed"
The "Transmission speed" is determined by the slowest device connected to the network.
The setting is identical throughout the network.
Bus profiles with PROFIBUS
Introduction
Depending on the device types connected and protocols used on the PROFIBUS, different
profiles are available. The profiles differ in terms of the setting options and calculation of bus
parameters. The profiles are explained below.
Devices with different profiles on the same PROFIBUS subnet
The PROFIBUS subnet only functions without problem if the bus parameters of all devices
have the same values.
Profiles and transmission rates
Profiles Supported transmission speeds in Kbits/s
DP 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000
Standard 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000
Universal 9,6 19,2 93,75 187,5 500 1500
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1940 System Manual, 08/2011,
Meaning of profiles
Profile Meaning
DP Select the "DP" bus profile when the only devices connected to the PROFIBUS
subnet are those which satisfy the requirements of standard EN 50170 Volume
2/3, Part 8-2 PROFIBUS. The bus parameter setting is optimized on these
devices.
This includes devices with DP master and DP slave interfaces of the SIMATIC
S7 and distributed I/Os of other manufacturers.
Standard Compared to the "DP" profile, the "Standard" profile also offers scope for
devices of another project or devices which have not been configured here to
be taken into account when calculating the bus parameters. The bus
parameters are then calculated following a simple, non-optimized algorithm.
Universal Select the "Universal" bus profile when individual devices on the PROFIBUS
subnet use the PROFIBUS-FMS service.
This includes the following devices for example:
CP 343-5
PROFIBUS-FMS devices of other manufacturers
As with the "Standard" profile, this profile allows you to take other devices into
account when calculating the bus parameters.
9.11.5.4 Data exchange
Data exchange using area pointers
General information on area pointers
Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC
and the HMI device alternately access these data areas for read and write operations.
The PLC and the HMI device trigger defined interactions based on the evaluation of stored
data.
Configuration of area pointers
Before you use an area pointer, you enable it under "Connections > Area pointer". You then
assign the area pointer parameters.
You can find more detailed information on configuring area pointers in:
Configuring area pointers (Page 1885)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1941
Area pointer "Date/time"
Function
This area pointer is used to transfer the date and time from the HMI device to the PLC.
The PLC writes control job "41" to the job mailbox.
When it evaluates the control job, the HMI device writes its current date and the time in the
data area configured in the "Date/time" area pointer.
The date/time data area has the following structure:
Data word Most significant byte Least significant byte
7 0 7 0
n+0 Reserved Hour (0-23)
Time
n+1 Minute (0-59) Second (0 to 59)
n+2 Reserved Reserved
n+3 Reserved Weekday (1 to 7, 1=Sunday)
Date
n+4 Day (1 to 31) Month (1 to 12)
n+5 Year (80 to 99/0 to 29) Reserved
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29 result in the years 2000 through 2029.
Permissible data types
You can use the following data types when you configure the "Date/Time" area pointer.
Word
UInt
DTL
Use of the "DTL" data type
Use data type "DTL" with communication driver S7 1200. A tag of the "DTL" data type has a
length of 12 bytes and saves information on date and time in a predefined structure.
The "DTL" data type has the following structure:
Byte Component Data type Value range
0 Year UINT 1970 to 2554
1
2 Month USINT 0 to 12
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1942 System Manual, 08/2011,
Byte Component Data type Value range
3 Tag USINT 1 to 31
4 Day of week USINT 1(Sunday) to 7(Saturday)
The weekday is not considered in the value entry.
5 Hour USINT 0 to 23
6 Minute USINT 0 to 59
7 Second USINT 0 to 59
8 Nanoseconds UDINT 0 to 999 999 999
9
10
11
"Date/time PLC" area pointer
Function
This area pointer is used to transfer the date and time from the PLC to the HMI device. Use
this area pointer if the PLC is the time master.
The PLC loads the data area of the area pointer.
The HMI device reads the data cyclically within the configured acquisition cycle and
synchronizes itself.
Note
Set an acquisition cycle of sufficient length for the date/time area pointer PLC to avoid any
negative impact on HMI device performance.
Recommended: Acquisition cycle of 1 minute, if the process allows this.
Date/time PLC is a global area pointer and can be configured only once in a project.
The date/time data area has the following structure:
DATE_AND_TIME format (in BCD code)
Data word Most significant byte Least significant byte
7 . . . . . . 0 7 . . . . . . 0
n+0 Year (80-99/0-29) Month (1 to 12)
n+1 Day (1 to 31) Hour (0 to 23)
n+2 Minute (0 to 59) Second (0 to 59)
n+3 Reserved Reserved Weekday
(1 to 7,
1=Sunday)
n+4
1)
Reserved Reserved
n+5
1)
Reserved Reserved
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1943
1) The two data words must exist in the data area to ensure that the data format matches
WinCC flexible and to avoid reading false information.
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29 result in the years 2000 through 2029.
Permitted data types
You can use the following data types when you configure the "Date/Time PLC" area pointer:
Word
UInt
DTL
Use of the "DTL" data type
Use data type "DTL" with communication driver S7 1200. A tag of the "DTL" data type has a
length of 12 bytes and saves information on date and time in a predefined structure.
The "DTL" data type has the following structure:
Byte Component Data type Value range
0 Year UINT 1970 to 2554
1
2 Month USINT 0 to 12
3 Day USINT 1 to 31
4 Day of week USINT 1(Sunday) to 7(Saturday)
The weekday is not considered in the value entry.
5 Hour USINT 0 to 23
6 Minute USINT 0 to 59
7 Second USINT 0 to 59
8 Nanoseconds UDINT 0 to 999 999 999
9
10
11
The HMI devices do not support the use of nanoseconds. Values in the nanosecond range will
be ignored during processing in Runtime.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1944 System Manual, 08/2011,
Area pointer "Coordination"
Function
The "Coordination" area pointer is used to implement the following functions:
Detecting the startup of the HMI device in the control program
Detecting the current operating mode of the HMI device in the control program
Detecting whether the HMI device is ready to communicate in the control program
The "Coordination" area pointer has a length of one word.
Application
Note
Each time the area pointer is updated by the HMI device, the entire coordination area is
always written.
For this reason, the PLC program must not make any changes in the coordination area.
Assignment of the bits in the "Coordination" area pointer
0 1 2 7 8 15
X X X
More significant byte
1st word
= reserved
x = assigned .
Less significant byte
Startup bit
Operating mode
Life bit
Startup bit
The startup bit is set briefly to "0" by the HMI device during startup. After startup, the bit is set
permanently to "1".
Operating mode
As soon as the HMI device is switched offline by the user, the operating mode bit is set to 1.
In normal operation of the HMI device, the state of the operating mode bit is "0". You can find
out the current operating mode of the HMI device by querying this bit.
Life bit
The life bit is inverted by the HMI device at intervals of approximately one second. By querying
this bit in the PLC program, you can check whether or not the connection to the HMI device
still exists.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1945
Processing in the PLC
For a simpler evaluation in the PLC program, use a Bool array for this area pointer when using
the SIMATIC S7 1200 communication driver. You will have to map the complete 16-bit word
of the area pointer. Configure a tag of the data type "Array [0 .. 15] of bool" for this purpose.
Permitted data types
You can use the following data types when you configure the "Coordination" area pointer.
Word
UInt
Bool
Area pointer "Screen number"
Function
The HMI devices store information about the screen called up on the HMI device in the "Screen
number" area pointer.
This allows the transfer of the current screen contents from the HMI device to the PLC. Certain
reactions can be triggered in the PLC, such as the call of a different screen.
Use
Before the "Screen number" area pointer can be used, it must be set up and activated by
selecting "Communication Area pointer". You can create only one instance of the "Screen
number" area pointer and only on one PLC.
The screen number is always transferred to the PLC when a new screen is activated or when
the focus within a screen changes from one screen object to another.
Structure
The area pointer is a data area in the memory of the PLC with a fixed length of 5 words.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1. Word Current screen type
2. Word Current screen number
3. Word Reserved
4th word Current field number
5. Word Reserved
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1946 System Manual, 08/2011,
Current screen type
"1" for root screen or
"4" for permanent window
Current screen number
1 to 32767
Current field number
1 to 32767
Note
Device dependency
Permanent windows are not available on Basic Panels.
Permitted data types
You can use the following data types when you configure the "Screen number" area pointer.
Word
UInt
Area pointer "Project ID"
Function
When runtime starts it can check to see if the HMI device is connected to the correct PLC. This
check is important when operating with several HMI devices.
The HMI device compares a value stored on the PLC with the value specified in the
configuration data. This ensures the compatibility of the configuration data and the PLC
program.
A missing compatibility results in a corresponding alarm and Runtime will not be started.
Use
In order to use this area pointer you must set up the following during the configuration:
Define the version of configuration. Possible values between 1 and 255.
You enter the version in the editor "Runtime settings > General" in the "Identification" area.
This is where you select the PLC tag or the tag array that you have configured as the data
area for the area pointer.
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in
all the other connections in the project being switched to "offline".
This behavior has the following prerequisites:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1947
You have several connections configured in a project.
You are using the "project ID" area pointer in at least one connection.
Causes which may set connections "offline":
The PLC is not available.
The connection has been switched offline in the engineering system.
Permitted data types
You can use the following data types when you configure the "Project ID" area pointer.
Word
UInt
Area pointer "Job mailbox"
Function
The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding
actions on the HMI device. These functions include, for example:
Display screen
Set date and time
Data structure
The first word of the job mailbox contains the job number. Depending on the job mailbox, up
to three parameters can be transferred.
Word Most significant byte Least significant byte
n+0 0 Job number
n+1 Parameter 1
n+2 Parameter 2
n+3 Parameter 3
The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This
means that the parameters must be entered in the job mailbox first, followed by the job number.
When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution
of the job mailbox is generally not completed at this point in time.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1948 System Manual, 08/2011,
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job
number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI
device is online.
No
.
Function
14 Set time (BCD-coded)
Parameter 1 Left byte: -
Right byte: hours (0-23)
Parameter 2 Left byte: minutes (0-59)
Right byte: seconds (0-59)
Parameter 3 -
15 Set date (BCD-coded)
Parameter 1 Left byte: -
Right byte: weekday
(1-7: Sunday-Saturday)
Parameter 2 Left byte: day (1-31)
Right byte: month (1-12)
Parameter 3 Left byte: year
23 User logon
Logs the user on with the name "PLC user" at the HMI device with the group number transferred
in parameter 1.
The logon is possible only when the transferred group number exists in the project.
Parameter 1 Group number 1 to 255
Parameter 2, 3 -
24 User logoff
Logs off the current user.
(The function corresponds to the "logoff" system function)
Parameter 1, 2, 3 -
40 Transferring date/time to PLC
An interval of at least 5 seconds must be maintained between two successive jobs to prevent
overload of the HMI device.
Parameter 1, 2, 3 -
41 Transfer date/time to the PLC
An interval of at least 5 seconds must be maintained between two successive jobs to prevent
overload of the HMI device.
Parameter 1, 2, 3 -
46 Updating tags
Causes the HMI device to read the current value of the tags from the PLC whose update ID
matches the value transferred in parameter 1.
(Function corresponds to the "UpdateTag" system function.)
Parameter 1 1 - 100
49 Clear event buffer
Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer.
Parameter 1, 2, 3 -
50 Clear error alarm buffer
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1949
No
.
Function
14 Set time (BCD-coded)
Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer.
Parameter 1, 2, 3 -
51 Display selection
Parameter 1 Screen number
Parameter 2 -
Parameter 3 Field number
69 Reading data record from PLC
1)
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Parameter 3 0: Do not overwrite existing data record
1: Overwrite existing data record
70 Writing data record from PLC
1)
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Parameter 3 -
1)
Only devices supporting recipes
2)
OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if
the on-screen keyboard is active.
3)
The weekday is ignored on HMI device KTP 600 BASIC PN.
Permitted data types
You can use the following data types when you configure the "Screen number" area pointer.
Word
UInt
"Data record" area pointer
"Data mailbox" area pointer
Function
When data records are transferred between the HMI device and PLC, both partners access
common communications areas on the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1950 System Manual, 08/2011,
Data transfer types
There are two ways of transferring data records between the HMI device and PLC:
Transfer without synchronization
Transfer with synchronization over the data mailbox
Data records are always transferred directly. That is, the tag values are read from an address
or written to an address configured for this tag directly, without redirecting the values by means
of interim memory.
Initiating the transfer of data records
There are three ways of triggering the transfer:
Operator input in the recipe view
Job mailboxes
The transfer of data records can also be triggered by the PLC.
Triggering by configured functions
If the transfer of data records is triggered by a job mailbox, the data in the recipe view will be
updated as well. Avoid operating the recipe view while job mailboxes for transfer of data records
are being triggered. If you have already started editing a data record and a job mailbox is
triggered for transfer of data records, then this job mailbox will be rejected.
Permitted data types
You can use the following data types when you configure the "Data record" area pointer.
Word
UInt
Transfer without synchronization
If you select asynchronous transfer of data records between the HMI device and PLC, there
is no coordination over the common data areas. It is therefore unnecessary to set up a data
area during configuration.
Asynchronous data record transfer can be a useful alternative, for example, when:
The system is capable of excluding the risk of uncontrolled overwriting of data by the
communication peer.
The PLC does not require information about the recipe number and data record number.
The transfer of data records is triggered by the operator of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1951
Reading values
When a read job is triggered, the values are read from the PLC addresses and transferred to
the HMI device.
Triggering by the operator in the recipe view:
The values are downloaded to the HMI device. You can then process, edit, or save these
values, for example.
Triggering by a function or job mailbox:
The values are saved immediately to the data volume.
Writing values
When a write job is triggered, the values are written to the PLC addresses.
Triggering by the operator in the recipe view:
The current values are written to the PLC.
Triggering by a function or job mailbox:
The current values are written to the PLC from the data medium.
Transfer with synchronization
If you select synchronous transfer, both communication partners set status bits in the common
data area. Use this mechanism to prevent uncontrolled overwriting of data in either direction
of your control program.
Application
Synchronous data record transfer can be a useful solution, for example, when:
The PLC is the "active partner" in the transfer of data records.
The PLC evaluates the information about the recipe number and data record number.
The transfer of data records is triggered by means of a Job mailbox.
Requirements
In order to synchronize transfer of data records between the HMI device and the PLC, the
following requirements must be met during configuration:
An area pointer has been set up: "Connections Area pointer" editor.
The PLC with which the HMI device synchronizes transfer of data records is specified in
the recipe:
"Recipes" editor in the inspector window the option "Coordinated transfer of data records"
under "General > Synchronization > Settings"
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1952 System Manual, 08/2011,
Structure of the data area
The data area has a fixed length of 5 words. Structure of the data area:
15 0
1. Word Current recipe number (1 - 999)
2. Word Current data record number (0 - 65535)
3. Word Reserved
4. Word Status (0, 2, 4, 12)
5. Word Reserved
Status
The status word (word 4) can adopt the following values:
Value Meaning
Decimal Binary
0 0000 0000 Transfer permitted, data record free
2 0000 0010 Transfer is busy
4 0000 0100 Transfer completed without error
12 0000 1100 Transfer completed with error
Sequence of a transfer started by the operator in the recipe display
Reading from the PLC started by the operator in the recipe view
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe number to be read and the status
"Transferring" in the data mailbox and sets the data record number
to 0.
Abort with system
alarm.
3 The HMI device reads the values from the PLC and displays them in
the recipe view.
If the recipes have synchronized tags, the values from the PLC are
also written to the tags.
4 The HMI device sets the status "Transfer completed."
5 The control program must reset the status word to zero in order to
enable further transfers.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1953
Writing to the PLC started by the operator in the recipe view
Step Action
Check: Status word = 0?
1 Yes No
The HMI device enters the recipe and data record number to be
written and the status "Transferring" in the data mailbox.
Abort with system
alarm.
2 The HMI device writes the current values to the PLC.
If the recipes have synchronized tags, the changed values are
synchronized between the recipe view and tags and then written to
the PLC.
3 The HMI device sets the status "Transfer completed."
4 If required, the control program can now evaluate the transferred
data.
5 The control program must reset the status word to zero in order to
enable further transfers.
Note
The status word may only be set by the HMI device. The PLC may only reset the status word
to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency is
detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Sequence of the transfer triggered by a job mailbox
The transfer of data records between the HMI device and the PLC can be initiated by either
one of these stations.
The two job mailboxes No. 69 and No. 70 are available for this type of transfer.
No. 69: Read data record from PLC ("PLC DAT")
Job mailbox no. 69 transfers data mailboxes from the PLC to the HMI device. The job mailbox
is structured as follows:
Most significant byte Least significant byte
Word 1 0 69
Word 2 Recipe number (1-999)
Word 3 Data record number (1-65,535)
Word 4 Do not overwrite existing data record: 0
Overwrite existing data record: 1
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1954 System Manual, 08/2011,
No. 70: Write data record to PLC ("DAT PLC")
Job mailbox no. 70 transfers data mailboxes from the HMI device to the PLC. The job mailbox
is structured as follows:
Most significant byte Least significant byte
Word 1 0 70
Word 2 Recipe number (1-999)
Word 3 Data record number (1-65,535)
Word 4
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified
in the job and the status "Transferring" in the data mailbox.
Abort without
return message.
3 The HMI device reads the values and stores the values in the data
record specified in the job mailbox.
4 If "Overwrite" was selected in the job, an existing data record is
overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed".
If "Do not overwrite" was selected in the job, and the data record
already exists, the HMI device aborts the job and enters 0000
1100 in the status word of the data mailbox.
5 The control program must reset the status word to zero in order to
enable further transfers.
Sequence writing to the PLC with job mailbox "DAT PLC" (no. 70)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified
in the job and the status "Transferring" in the data mailbox.
Abort without
return message.
3 The HMI device fetches the values of the data record specified in the
job from the data medium and writes the values to the PLC.
4 The HMI device sets the status "Transfer completed."
5 The PLC program can now evaluate the transferred data.
To allow further transfers, the PLC program must set the status word
to 0 again.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1955
Sequence of the transfer when triggered by a configured function
Reading from the PLC using a configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
mailbox.
Abort with system
alarm.
3 The HMI device reads the values from the PLC and stores them
in the data record specified in the function.
4 If "Yes" was selected for the "Overwrite" function, an existing
data record is overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "No" was selected for the "Overwrite" function and the data
record already exists, the HMI device aborts the job and
enters 0000 1100 in the status word of the data mailbox.
5 The control program must reset the status word to zero in order
to enable further transfers.
Writing to the PLC by means of configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
mailbox.
Abort with system
alarm.
3 The HMI device fetches the values of the data record specified
in the function from the data medium and transfers the values to
the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order
to enable further transfers.
Possible causes of error when transferring data records
Possible causes of error
The section below shows possible error causes which lead to the cancellation of data record
transfer:
Tag address not set up on the PLC
Overwriting data records not possible
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1956 System Manual, 08/2011,
Recipe number does not exist
Data record number does not exist
Note
The status word may only be set by the HMI device. The PLC may only reset the status
word to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency
is detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Reaction to an aborted transfer due to errors
If the transfer of data records is aborted due to errors, the HMI device reacts as follows:
Triggering by the operator in the recipe view
Information in the status bar of the recipe view and output of system alarms
Triggered by function
Output of system alarms
Triggering by job mailbox
No return message on the HMI device
You can nonetheless evaluate the status of the transfer by querying the status word in the data
mailbox.
Note
Availability for specific devices
Notes in the status bar of the recipe view are not available in Basic Panels.
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
For additional information see:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1957
Displaying tags with Runtime Advanced and Panels (Page 940)
Note
The value is read out time-triggered for Basic Panels.
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
See also
Trends (Page 940)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1958 System Manual, 08/2011,
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
The following picture shows the structure of a trend transfer area.
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Permitted data types for trends
For SIMATIC S7
You assign one bit to each trend during configuration. Tags and array tags of the "Word" or
"Int" data type are permitted.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1959
Alarms
Configuring alarms
Configure alarms
Several steps are needed to configure alarms, such as operational messages, error alarms,
and acknowledgement.
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Data types
For connections with a SIMATIC communication driver, the following data types are supported:
PLC Permitted data types
Discrete alarms Analog alarms
SIMATIC S7 PLCs WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT,
REAL, TIMER
How the bit positions are counted
For connections with a SIMATIC communication driver, the following counting method applies:
How the bit positions are
counted
Byte 0 Byte 1
Most significant byte Least significant byte
In SIMATIC S7
PLCs
7 0 7 0
In WinCC you configure: 15 8 7 0
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1960 System Manual, 08/2011,
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1961
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1962 System Manual, 08/2011,
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
9.11.5.5 Performance features of communication
Permitted data types for SIMATIC S7 1200 - V1
Permitted data types for connections with SIMATIC S7 1200 (V1)
V1: Firmware Version V1.0
The table lists the data types that can be used when configuring tags and area pointers.
Data type Length
BOOL 1 bit
SINT 1 byte
INT 2 bytes
DINT 4 bytes
USINT 1 byte
UINT 2 bytes
UDINT 4 bytes
REAL 4 bytes
LREAL 8 bytes
TIME 4 bytes
DTL 12 bytes
STRING (2+n) bytes, n = 0 to 254
CHAR 1 byte
Array of CHAR --
BYTE 1 byte
WORD 2 bytes
DWORD 4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1963
Permitted data types for SIMATIC S7 1200 - V2
Permitted data types for connections with SIMATIC S7 1200 (V2)
The table lists the user data types that can be used when configuring tags and area pointers.
Data type Length
BOOL 1-bit
SINT 1 byte
INT 2 bytes
DINT 4 bytes
USINT 1 byte
UINT 2 bytes
UDINT 4 bytes
REAL 4 bytes
LREAL 8 bytes
TIME 4 bytes
DATE 2 bytes
DTL 12 bytes
TIME_OF_DAY, TOD 4 bytes
STRING (2+n) bytes, n = 0 to 254
CHAR 1 byte
BYTE 1 byte
WORD 2 bytes
DWORD 4 bytes
9.11.5.6 Creating connections in the "Connections" editor
Creating a PROFINET connection
Requirements
A project is open.
An HMI device with a PROFINET interface has been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1964 System Manual, 08/2011,
Procedure
1. Open the "Connections" editor of the HMI device.
2. Double-click "<Add>".
3. In the "Communication drivers" column, select the "SIMATIC S7 1200" driver.
4. Click the name of the connection.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1965
5. Select a PROFINET interface of the HMI device in the Inspector window under "Parameters
> Interface".
6. Set the IP addresses of the communication partners in the Inspector window:
HMI device: "Parameters > HMI device > Address"
PLC: "Parameters > PLC > Address"
Creating a PROFIBUS DP connection
Requirements
A project is open.
An HMI device with a PROFIBUS interface has been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1966 System Manual, 08/2011,
Procedure
1. Open the "Connections" editor of the HMI device.
2. Double-click "<Add>".
3. In the "Communication drivers" column, select the "SIMATIC S7 1200" driver.
4. Click the name of the connection.
5. Select the "MPI/DP" interface in the Inspector window under "Parameters".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1967
6. Select the "DP" profile in the Inspector window under "Parameters > Network".
7. Set the addresses of the communication partners in the Inspector window:
HMI device: "Parameters > HMI device > Address"
PLC: "Parameters > PLC > Address"
Parameters for the connection
Parameters for the connection (SIMATIC S7 1200)
Parameters to be set
To assign the connection parameters, such as addresses and profiles, click the connection
that you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning
parameters according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1968 System Manual, 08/2011,
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1969
Ethernet parameters
Parameters for the HMI device
You set the parameters for the HMI device in the network under "HMI device".. The changes
are not transferred automatically to the HMI device. You must change the settings in the Control
Panel of the HMI device.
"Interface"
If you are directly connected to the HMI device during configuration, you can set up the IP
address of the HMI device in WinCC.
Note
The IP address in the Control Panel will be overwritten upon subsequent loading if you
have already set up the IP address in the HMI device control panel.
The IP address already set up in the Control Panel will be retained upon subsequent
loading if you activate "Set IP address using a different method".
The IP address is transferred to the HMI device during project transfer.
To set up the IP address of the HMI device:
Click the HMI device.
Open the "Device configuration" editor.
Click the Ethernet interface.
Assign the IP address in the inspector window under:
"General > PROFINET interface > Ethernet addresses"
"Address"
You assign the IP address of the HMI device in the "Address" area.
When you transfer the WinCC project to the HMI device, this IP address is set up directly
in the HMI device.
"Access point"
The access point defines a logical device name through which the communication partner
can be reached.
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
Under "Address", set the IP address of the S7 module to which the HMI device is connected.
"Expansion slot"
Defines the number of the expansion slot of the CPU to be addressed.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1970 System Manual, 08/2011,
"Rack"
Defines the rack number of the CPU to be addressed.
"Cyclic mode"
Note
The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC.
When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This increases system performance.
Disable cyclic mode if you are operating several HMI devices in parallel.
PROFIBUS parameters
Parameters for the HMI device
You assign the parameters for the HMI device in the network once under "HMI device". The
change applies to each communication partner.
"Type"
Specifies the physical connection used.
"Interface"
For "Interface", you select the HMI device interface via which the HMI device is connected
to the PROFIBUS network.
"Baud rate"
For "Baud rate", you set the transmission speed of the data in the network. The baud rate
is determined by the slowest HMI device connected to the network. The setting must be
identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must
be less than or equal to 63.
"Address"
You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS
address must be unique in the PROFIBUS network.
"Sole master on bus"
Disables an additional safety feature against bus faults when the HMI device is connected
to the network. A passive station (slave) can only send data if it is requested to do so by
an active station (master).
In S7 200, you must set an HMI device as the master.
"Access point"
The access point defines a logical device name through which the communication partner
can be reached.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1971
Parameters for the network
Under "Network", you set the parameters for the PROFIBUS network to which the HMI device
is linked.
"Profile"
For "Profile", you select the network profile that is used in the network. In "Profile", set "DP",
"Universal", or "Standard". The setting must be identical throughout the network.
"Highest address"
For "Highest station address", set the highest station address. The highest station address
must be greater than or equal to the highest actual PROFIBUS address. The setting must
be identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address
must be less than or equal 63.
"Number of masters"
For "Number of masters", set the number of masters in the PROFIBUS network. This
information is necessary to correctly calculate the bus parameters.
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which
the HMI device is connected.
"Cyclic operation"
Note
The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC.
When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This increases system performance. Disable cyclic mode if you are
operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200
PLCs.
9.11.5.7 Time synchronization
Time synchronization
Introduction
To have the same time of day throughout the plant, you can synchronize the time on various
plant components using time synchronization. WinCC time synchronization is operated as a
master-slave system.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1972 System Manual, 08/2011,
One system component must be a clock for all components of a plant to work with identical
time. The component functioning as the clock is referred to as the time master. The
components that receive the time are time slaves.
Properties of time synchronization
An update time of 60 seconds is set in master mode.
The first update takes place 60 seconds after the start of runtime.
The first time synchronization is performed on the HMI device immediately after the start
of runtime.
Time synchronization is only performed on the HMI device during operation of runtime.
The HMI device can define the time as master or can accept the time of the PLC as slave.
Time synchronization restrictions
Approved HMI devices
You can configure the time synchronization between a SIMATIC S7 1200 and an HMI device
with the following HMI devices:
Device Operating system
TP177 4" Windows CE 5.0
Multi Panel 177 Windows CE 5.0
Multi Panel 277 Windows CE 5.0
Multi Panel 377 Windows CE 5.0
Mobile Panel 277 Windows CE 5.0
Mobile 277 IWLAN V2 Windows CE 5.0
Comfort Panels Windows CE 6.0
PC systems with WinCC RT Advanced Microsoft Windows XP
Microsoft Windows 7
Configuration restrictions
If an HMI device has several connections to SIMATIC S7 1200, you can only configure one
connection as "slave".
If you have enabled time synchronization for the HMI device as "slave", you can no longer
use the global area pointer "Date/time PLC".
If you use Basic Panels for the configuration, it is not possible to use time synchronization
via NTP and the "Date/time PLC" area pointer simultaneously.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1973
Configuring time synchronization for integrated connections
Introduction
You configure time synchronization for an integrated connection in the "Devices & Networks"
editor.
Requirements
An HMI connection between an HMI device and a SIMATIC S7 1200 has been configured.
The HMI device must support the "time synchronization" function.
The "Devices & Networks" editor is open.
Procedure
1. Click the line of the HMI connection in the "Devices & networks" editor.
2. Select the following in the inspector window under "General > Time synchronization >
Settings":
None: No time synchronization is used.
Master: The HMI device sets the time.
Slave: The PLC sets the time.
Configuring time synchronization for non-integrated connections
Introduction
You configure time synchronization for a non-integrated connection in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1974 System Manual, 08/2011,
Requirements
An HMI device which supports the "time synchronization" function has been created.
"Connections" editor is open.
Procedure
1. Double-click "<Add>".
2. In the "Communication drivers" column, select the "SIMATIC S7 1200" PLC.
3. Select the following in the "HMI time synchronization mode" column:
None: No time synchronization is used.
Master: The HMI device sets the time.
Slave: The PLC sets the time.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1975
9.11.6 Communicating with SIMATIC S7 300/400
9.11.6.1 Communication with SIMATIC S7 300/400
Introduction
This section describes the communication between an HMI device and the SIMATIC S7 300
and S7 400 PLCs. These two PLCs will be referred to jointly as SIMATIC S7 300/400.
You can configure the following communication channels for the SIMATIC S7 300/400 PLC:
PROFINET
PROFIBUS
MPI
HMI connection for communication
You configure connections between the HMI device and a SIMATIC S7 300/400 in the "Devices
& Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1976 System Manual, 08/2011,
9.11.6.2 Communication via PROFINET
Configuring an HMI connection
Communication via PROFINET
HMI connections via PROFINET
If you have inserted an HMI device and a SIMATIC S7 300/400 into the project, you
interconnect the two PROFINET interfaces in the "Devices & Networks" editor.
You can also connect multiple HMI devices to one SIMATIC S7 300/400 and multiple SIMATIC
S7 300/400s to one HMI device. The maximum number of communication partners that you
can connect to an HMI device is dependent on the HMI device used.
Additional information is available in the documentation for the respective HMI device.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFINET in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via PROFINET
in the "Connections" editor of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1977
Configuring an HMI connection via PROFINET
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFINET or Ethernet in the "Devices & Networks" editor.
CAUTION
Communication via Ethernet
In Ethernet-based communication, the end user is responsible for the security of his data
network.
Targeted attacks can overload the device and interfere with proper functioning.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
HMI device with PROFINET or Ethernet interface
SIMATIC S7 300/400 with PROFINET interface.
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed graphically in the network
view.
2. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1978 System Manual, 08/2011,
3. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFINET or Ethernet interface of the HMI device.
4. Click the connecting line.
5. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
6. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFINET parameters (Page 1986)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created a connection between an HMI device and a SIMATIC S7 300/400. The IP
address and subnet mask connection parameters are configured.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1979
Configuring an HMI connection
Communication via PROFINET
Communication via PROFINET
This section describes the communication between a WinCC Runtime and the SIMATIC S7
300/400 PLC via PROFINET.
You can use the following WinCC Runtimes as an HMI device:
WinCC RT Advanced
WinCC Runtime as HMI device
You configure the HMI connections between WinCC Runtime and SIMATIC S7 300/400 in the
"Devices & Networks" editor.
If you want to use a WinCC Runtime as an HMI device, you have the following options:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1980 System Manual, 08/2011,
1. You create a SIMATIC PC and configure a WinCC Runtime on this SIMATIC PC.
In this way you use the SIMATIC PC with a WinCC Runtime as an HMI device.
2. You create a WinCC Runtime and configure a communication processor to the Runtime.
In this way you use your configuration PC with a WinCC Runtime as an HMI device.
You can also connect multiple HMI devices to one SIMATIC S7 300/400 and multiple SIMATIC
S7 300/400s to one HMI device. The maximum number of communication partners that you
can connect to an HMI device is dependent on the HMI device used.
Additional information is available in the documentation for the respective HMI device.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFINET in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via PROFINET
in the "Connections" editor of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1981
Configuring an HMI connection via PROFINET with a SIMATIC PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFINET or Ethernet in the "Devices & Networks" editor.
CAUTION
Communication via Ethernet
In Ethernet-based communication, the end user is responsible for the security of his data
network.
Targeted attacks can overload the device and interfere with proper functioning.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 300/400 with PROFINET interface
SIMATIC PC with PROFINET interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a WinCC Runtime from the hardware catalog to
the PC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1982 System Manual, 08/2011,
3. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
4. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFINET or Ethernet interface of the PC.
5. Click the connecting line.
6. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
7. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFINET parameters (Page 1986)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created a connection between an HMI device and a SIMATIC S7 300/400. The IP
address and subnet mask connection parameters are configured.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1983
Configuring an HMI connection via PROFINET with a PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFINET or Ethernet in the "Devices & Networks" editor.
CAUTION
Communication via Ethernet
In Ethernet-based communication, the end user is responsible for the security of his data
network.
Targeted attacks can overload the device and interfere with proper functioning.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 300/400 with PROFINET interface
PC station with WinCC RT Advanced
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1984 System Manual, 08/2011,
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed graphically in the network
view.
2. Use a drag-and-drop operation to move a PROFINET-capable communication processor
from the hardware catalog to the WinCC Runtime.
3. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
4. Click the PROFINET interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFINET interface of the communication processor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1985
5. Click the connecting line.
The connection is displayed graphically in the Inspector window.
6. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
7. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFINET parameters (Page 1986)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created a connection between an HMI device and a SIMATIC S7 300/400. The IP
address and subnet mask connection parameters are configured.
PROFINET parameters
PROFINET parameters for the HMI connection
PROFINET parameters for the HMI connection
An overview of the configured HMI connection parameters can be found in the properties for
the HMI connection.
Only limited changes are possible in this Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1986 System Manual, 08/2011,
Displaying and changing the HMI connection parameters
1. Click the HMI connection in the "Devices & Networks" editor.
2. Change the parameters of the HMI connection in the Inspector window under "Properties
> General > General".
"Connection"
Displays whether the devices are networked together.
- displayed if the devices are networked together.
- displayed if the devices are not networked together.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1987
"Connection path"
The communication partners of the selected HMI connection and the associated PROFINET
parameters are displayed in the "Connection path" area. Some of the areas displayed cannot
be edited in this dialog.
"End point"
Displays the device name. This area cannot be edited.
"Interface"
Displays the selected interface of the device. You can choose between several interfaces,
depending on the device.
"Interface type"
Displays the selected interface type. This area cannot be edited.
"Subnet"
Displays the selected subnet. This area cannot be edited.
"Address"
Displays the selected IP address of the device. This area cannot be edited.
"Find connection path" button
Enables the subsequent specification of connections.
PROFINET parameters for the HMI device
PROFINET parameters for the HMI device
An overview of the configured HMI device parameters can be found in the properties for the
HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1988 System Manual, 08/2011,
Displaying and changing PROFINET parameters of the HMI device
1. Click the HMI device in the "Devices & Networks" editor.
2. Change the parameters of the HMI device in the Inspector window under "Properties >
General".
"Interface networked with"
In the "Interface networked with" area, select the subnet of the HMI connection via which the
HMI device is connected to the network. You use the "Add new subnet" button to create a new
subnet.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1989
"IP protocol"
"Set IP address in the project"
When you transfer the WinCC project to the HMI device, this IP address is set up directly
in the HMI device.
Note
The device is automatically restarted in the case of HMI devices with the Windows CE 3.0
operating system.
HMI devices with Windows CE 3.0:
OP 77B
TP 177B color PN/DP
TP 177B mono DP
OP 177B color PN/DP
OP 177B mono DP
Mobile Panel 177 PN
Mobile Panel 177 DP
TP 277 6"
OP 277 6"
"Subnet mask"
You assign data of the subnet mask in the "Subnet mask" area.
"Use IP router"
If you are using an IP router, select "Use IP router" and enter the router address in the
"Router address" field.
"Set IP address using a different method"
If the function "Set IP address using a different method" is activated, the IP address is not
taken from the project. You have to enter the IP address directly in the Control Panel of the
HMI device.
PROFINET parameters for the PLC
PROFINET parameters for the PLC
An overview of the configured parameters can be found in the properties for the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1990 System Manual, 08/2011,
Displaying and changing PROFINET parameters of the PLC
1. Click the PLC in the "Devices & Networks" editor.
2. Change the parameters of the PLC in the Inspector window under "Properties > General >
General".
"Interface networked with"
In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected
to the network. You use the "Add new subnet" button to create a new subnet.
"IP protocol"
"Interface type"
Depending on the HMI device type, you have various interfaces to choose from.
"IP address"
You assign the IP address of the HMI device in the "IP address" area.
"Subnet mask"
You assign data of the subnet mask in the "Subnet mask" area.
If you are using an IP router, select "Use IP router" and enter the router address in the field.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1991
Configuring Industrial Ethernet
Rules for the network configuration
The Ethernet interfaces of the devices have a default IP address that you can change.
IP address
The IP parameters are visible if the communication-capable devices support the TCP/IP
protocol.
The IP address consists of 4 decimal figures in the range of 0 to 255. The decimal figures are
separated from one another by a dot.
Example: 140.80.0.2
The IP address consists of the following:
The address of the (sub) net
The address of the node (generally also called host or network node)
Subnet mask
The subnet mask splits these two addresses. It determines which part of the IP address
addresses the network and which part of the IP address addresses the node.
The set bits of the subnet mask determine the network part of the IP address.
Example:
Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000
In the example given for the above IP address, the subnet mask shown here has the following
meaning:
The first 2 bytes of the IP address identify the subnet - i.e. 140.80. The last two bytes address
the node, thus 0.2.
It is generally true that:
The network address results from AND linking the IP address and subnet mask.
The node address results from AND NOT linking the IP address and subnet mask.
Relation between IP address and default subnet mask
An agreement exists relating to the assignment of IP address ranges and so-called "Default
subnet masks". The first decimal number (from the left) in the IP address determines the
structure of the default subnet mask. It determines the number of "1" values (binary) as follows:
IP address (decimal) IP address (binary) Address class Default subnet mask
0 to 126 0xxxxxxx.xxxxxxxx.... A 255.0.0.0
128 to 191 10xxxxxx.xxxxxxxx... B 255.255.0.0
192 to 223 110xxxxx.xxxxxxxx... C 255.255.255.0
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1992 System Manual, 08/2011,
Note
Range of values for the first decimal point
A value of between 224 and 255 is also possible for the first decimal number of the IP address
(address class D etc). This is, however, not recommended because there is no address check
for these values.
Masking other subnets
You can use the subnet mask to add further structures and form "private" subnets for a subnet
that is assigned one of the address classes A, B or C. This is done by setting other lower points
of the subnet mask to "1". For each bit set to "1", the number of "private" networks doubles
and the number of nodes they contain is halved. Externally, the network functions like an
individual network as it did previously.
Example:
You have a subnet of address class B (e.g. IP address 129.80.xxx.xxx) and change the default
subnet mask as follows:
Masks Decimal Binary
Default subnet mask 255.255.0.0 11111111.11111111.00000000.
00000000
Subnet mask 255.255.128.0 11111111.11111111.10000000.
00000000
Result:
All nodes with addresses between 129.80.001.xxx and 129.80.127.xxx are on one subnet, all
nodes with addresses between 129.80.128.xxx and 129.80.255.xxx are on another subnet.
Router
The job of the routers is to connect the subnets. If an IP datagram is to be sent to another
network, it first has to be conveyed to a router. To make this possible, in this case you have
to enter the address of the router for each node in the subnet.
The IP address of a node in the subnet and the address of the router may only differ at the
points at which there is a "0" in the subnet mask.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1993
Setting port options
Setting the port options
Changing connection settings for the PROFINET IO port
You can change the network settings for the PROFINET IO port as required. By default, the
settings are made automatically. In normal situations, this guarantees problem-free
communication.
Possible settings for transmission rate / duplex
Depending on the selected device, you can make the following settings for "Transmission rate /
duplex":
Automatic setting
Recommended default setting of the port. The transmission settings are automatically
"negotiated" with the peer port. The "Enable autonegotiation" option is also enabled as a
default, in other words, you can use cross cables or patch cables for the connection.
TP/ITP at x Mbps full duplex (half duplex)
Setting of the transmission rate and the full duplex/half duplex mode. The effectiveness
depends on the "Enable autonegotiation" setting:
Autonegotiation enabled
You can use both cross cable and patch cable.
Autonegotiation disabled
Make sure that you use the correct cable (patch cable or cross cable)! The port is also
monitored with this setting.
Deactivated
Depending on the module type, the drop down list box can contain the "- Disabled -" option.
This option, for example, allows you to prevent access to an unused port for security
reasons. With this setting, diagnostic events are not generated.
"Monitor" option
This option enables or disables port diagnostics. Examples of port diagnostics: The link status
is monitored, in other words, the diagnostics are generated during link-down and the system
reserve is monitored in the case of fiber optic ports.
Option "Enable autonegotiation "
The autonegotiation setting can only be changed if a concrete medium (for example, TP 100
Mbps full duplex) is selected. Whether or not a concrete medium can be set depends on the
properties of the module.
If autonegotiation is disabled, this causes the port to be permanently specified, as for example,
is necessary for a prioritized startup of the IO device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1994 System Manual, 08/2011,
You must make sure the partner port has the same settings because with this option the
operating parameters of the connected network are not detected and the data transmission
rate and transmission mode can accordingly not be optimally set.
Note
When a local port is connected, STEP 7 makes the setting for the partner port if the partner
port supports the setting. If the partner port does not accept the setting, an error message is
generated.
Wiring rules for disabled autonegotiation
Requirements
You have made the following settings for the port in question, for example, to accelerate the
startup time of the IO device:
Fixed transmission rate
Autonegotiation incl. autocrossing disabled
The time for negotiating the transmission rate during startup has been saved.
If you have disabled autonegotiation, you must observe the wiring rules.
Wiring rules for disabled autonegotiation
PROFINET devices have the following two types of ports:
Type of port PROFINET devices Note
Switch port with crossed pin
assignment
For IO devices: Port 2
For S7 CPUs with 2 ports: Ports
1 and 2
Crossed pin assignment means
that the pin assignment for the
ports for sending and receiving
between the respective
PROFINET devices is
exchanged internally.
End device port with uncrossed
pin assignment
For IO devices: Port 1
For S7 CPUs with one port: Port
1
-
Validity of the wiring rules
The cabling rules described in the following paragraph apply exclusively for the situation in
which you have specified a fixed port setting.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1995
Rules for cabling
You can connect several IO devices in line using a single cable type (patch cable). To do this,
you connect port 2 of the IO device (distributed I/O) with port 1 of the next IO device. The
following graphic gives an example with two IO devices.
P2 P2
Patch cables
Switch or
PROFlNET device
P2
Patch cables
lO device lO device
End device port
Switch port
P1 P1 P1
Boundaries at the port
Requirements
To use boundaries, the respective device must have more than one port. If the PROFINET
does not support boundary settings, they are not shown.
Enable boundaries
"Boundaries" are limits for transmission of certain Ethernet frames. The following boundaries
can be set at a port:
"End of discovery of accessible devices"
No forwarding of DCP frames to identify accessible devices. Devices downstream from this
port cannot be reached by the project tree under "Accessible devices". Devices downstream
from this port cannot be reached by the CPU.
"End of topology discovery"
LLDP frames (Link Layer Discovery Protocol) are not forwarded for topology detection.
"End of sync domain"
No forwarding of sync frames transmitted to synchronize nodes within a sync domain.
If you operate, for example, a PROFINET device with more than two ports in a ring, you
should prevent the sync frame from being fed into the ring by setting a sync boundary (at
the ports not inside the ring).
Additional example: If you want to use several sync domains, configure a sync domain
boundary for the port connected to a PROFINET device from the other sync domain.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1996 System Manual, 08/2011,
Restrictions
The following restrictions must be observed:
The individual check boxes can only be used if the port supports the function in question.
If a partner port has been determined for the port, the following check boxes cannot be
used:
"End of discovery of accessible devices"
"End of topology discovery"
If autonegotiation is disabled, none of the check boxes can be used.
9.11.6.3 Communication via PROFIBUS
Configuring an HMI connection
Communication via PROFIBUS
HMI connections via PROFIBUS
If you have inserted an HMI device and a SIMATIC S7 300/400 into the project, you
interconnect the two PROFIBUS interfaces in the "Devices & Networks" editor.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the
"Devices & Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1997
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device in the
"Connections" editor of the HMI device.
Configuring an HMI connection via PROFIBUS
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFIBUS in the "Devices & Networks" editor.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
HMI device with MPI/DP interface
SIMATIC S7 300/400 with PROFIBUS interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed graphically in the network
view.
2. Click the "Connections" button.
The devices available for connection are highlighted in color.
3. Click the HMI device interface.
4. Select the "PROFIBUS" interface type in the Inspector window under "Properties > General
> HMI MPIDP > Parameters".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
1998 System Manual, 08/2011,
5. Click the interface of the PLC and use a drag-and-drop operation to draw a connection to
the HMI device.
6. Click the connecting line.
7. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
8. Click the communication partners in the "Network view" and change the PROFINET
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFIBUS parameters (Page 2005)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via
PROFIBUS.
Configuring an HMI connection
Communication via PROFIBUS
Communication via PROFIBUS
This section describes the communication between a WinCC Runtime and the SIMATIC S7
300/400 PLC via PROFIBUS.
You can use the following WinCC Runtimes as an HMI device:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 1999
WinCC RT Advanced
WinCC RT Professional
WinCC Runtime as HMI device
You configure the HMI connections between WinCC Runtime and SIMATIC S7 300/400 in the
"Devices & Networks" editor.
If you want to use a WinCC Runtime as an HMI device, you have the following options:
1. You create a SIMATIC PC and configure a WinCC Runtime on this SIMATIC PC.
In this way you use the SIMATIC PC with a WinCC Runtime as an HMI device.
2. You create a WinCC Runtime and configure a communication processor to the Runtime.
In this way you use your configuration PC with a WinCC Runtime as an HMI device.
You can also connect multiple HMI devices to one SIMATIC S7 300/400 and multiple SIMATIC
S7 300/400s to one HMI device. The maximum number of communication partners that you
can connect to an HMI device is dependent on the HMI device used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2000 System Manual, 08/2011,
Additional information is available in the documentation for the respective HMI device.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via PROFIBUS
in the "Connections" editor of the HMI device.
Configuring an HMI connection via PROFIBUS with a SIMATIC PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFIBUS in the "Devices & Networks" editor.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 300/400 with PROFIBUS interface
SIMATIC PC with PROFIBUS interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Click the MPI interface of the PC and select "PROFIBUS" for the interface type in the
Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2001
3. Use a drag-and-drop operation to move a WinCC Runtime from the hardware catalog to
the PC.
4. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
5. Click the PROFIBUS interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFIBUS interface of the PC.
6. Click the connecting line.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2002 System Manual, 08/2011,
7. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
8. Click the communication partners in the "Network view" and change the PROFIBUS
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFIBUS parameters (Page 2005)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via
PROFIBUS.
Configuring an HMI connection via PROFIBUS with a PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFIBUS in the "Devices & Networks" editor.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 300/400
PC station with WinCC RT Advanced
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2003
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a PROFIBUS-capable communication processor
from the hardware catalog to the WinCC Runtime.
3. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
4. Click the PROFIBUS interface of the PLC and use a drag-and-drop operation to draw a
connection to the PROFIBUS interface of the communication processor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2004 System Manual, 08/2011,
5. Click the connecting line.
6. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
7. Click the communication partners in the "Network view" and change the PROFIBUS
parameters in the Inspector window according to the requirements of your project.
See the chapter "PROFIBUS parameters (Page 2005)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 1200 via
PROFIBUS.
PROFIBUS parameters
PROFIBUS parameters for the HMI connection
PROFIBUS parameters for the HMI connection
An overview of the configured HMI connection parameters can be found in the properties for
the HMI connection.
Only limited changes are possible in this Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2005
Displaying and changing the HMI connection parameters
1. Click the HMI connection in the "Devices & Networks" editor.
2. Change the parameters of the HMI connection in the Inspector window under "Properties
> General > General".
"Connection"
Displays whether the devices are networked together.
- displayed if the devices are networked together.
- displayed if the devices are not networked together.
"Connection path"
The communication partners of the selected HMI connection and the associated PROFIBUS
parameters are displayed in the "Connection path" area. Some of the areas displayed cannot
be edited in this dialog.
"End point"
Displays the device name. This area is not editable.
"Interface"
Displays the selected interface of the device. You can choose between several interfaces,
depending on the device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2006 System Manual, 08/2011,
"Interface type"
Displays the selected interface type. This area is not editable.
"Subnet"
Displays the selected subnet. This area is not editable.
"Address"
Displays the PROFIBUS address of the device. This area is not editable.
"Find connection path" button
Enables the subsequent specification of connections.
PROFIBUS parameters for the HMI device
PROFIBUS parameters for the HMI device
An overview of the configured HMI device parameters can be found in the properties for the
HMI device.
Displaying and changing PROFINET parameters of the HMI device
1. Click the HMI device in the "Devices & Networks" editor.
2. Change the parameters of the HMI device in the Inspector window under "Properties >
General > General".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2007
"Interface networked with"
In the "Interface networked with" area, select the subnet of the HMI connection via which the
HMI device is connected to the network. You use the "Add new subnet" button to create a new
subnet.
"Parameters"
"Interface type"
You assign the interface type in the "Interface type" area. Depending on the HMI device
type, you have various interfaces to choose from.
"Address"
You assign the PROFIBUS address of the HMI device in the "Address" area. The
PROFIBUS address must be unique throughout the PROFIBUS network.
"Highest address"
The "Highest address" area displays the highest address of the PROFIBUS network.
"Transmission speed"
The "Transmission speed" is determined by the slowest device connected to the network.
The setting is identical throughout the network.
PROFIBUS parameters for the PLC
PROFIBUS parameters for the PLC
An overview of the configured parameters can be found in the properties for the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2008 System Manual, 08/2011,
Displaying and changing PROFIBUS parameters of the PLC
1. Click the PLC in the "Devices & Networks" editor.
2. Change the parameters of the PLC in the Inspector window under "Properties > General >
General".
"Interface networked with"
In the "Subnet" area, select the subnet of the HMI connection via which the PLC is connected
to the network. You use the "Add new subnet" button to create a new subnet.
"Parameters"
"Interface type"
Depending on the HMI device type, you have various interfaces to choose from.
"Address"
You assign the PROFIBUS address of the HMI device in the "Address" area. The
PROFIBUS address must be unique throughout the PROFIBUS network.
"Highest address"
The "Highest address" area displays the highest address of the PROFIBUS network.
"Transmission speed"
The "Transmission speed" is determined by the slowest device connected to the network.
The setting is identical throughout the network.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2009
Bus profiles with PROFIBUS
Introduction
Depending on the device types connected and protocols used on the PROFIBUS, different
profiles are available. The profiles differ in terms of the setting options and calculation of bus
parameters. The profiles are explained below.
Devices with different profiles on the same PROFIBUS subnet
The PROFIBUS subnet only functions without problem if the bus parameters of all devices
have the same values.
Profiles and transmission rates
Profiles Supported transmission speeds in Kbits/s
DP 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000
Standard 9,6 19,2 45,45 93,75 187,5 500 1500 3000 6000 12000
Universal 9,6 19,2 93,75 187,5 500 1500
Meaning of profiles
Profile Meaning
DP Select the "DP" bus profile when the only devices connected to the PROFIBUS
subnet are those which satisfy the requirements of standard EN 50170 Volume
2/3, Part 8-2 PROFIBUS. The bus parameter setting is optimized on these
devices.
This includes devices with DP master and DP slave interfaces of the SIMATIC
S7 and distributed I/Os of other manufacturers.
Standard Compared to the "DP" profile, the "Standard" profile also offers scope for
devices of another project or devices which have not been configured here to
be taken into account when calculating the bus parameters. The bus
parameters are then calculated following a simple, non-optimized algorithm.
Universal Select the "Universal" bus profile when individual devices on the PROFIBUS
subnet use the PROFIBUS-FMS service.
This includes the following devices for example:
CP 343-5
PROFIBUS-FMS devices of other manufacturers
As with the "Standard" profile, this profile allows you to take other devices into
account when calculating the bus parameters.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2010 System Manual, 08/2011,
9.11.6.4 Communication via MPI
Configuring an HMI connection
Communication via MPI
HMI connections via MPI
If you have inserted an HMI device and a SIMATIC S7 300/400 into the project, you
interconnect the two MPI interfaces in the "Devices & Networks" editor.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via PROFIBUS in the
"Devices & Networks" editor.
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device in the
"Connections" editor of the HMI device.
Configuring an HMI connection via MPI
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via MPI
in the "Devices & Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2011
Requirements
The following communication partners are created in the "Devices & Networks" editor:
HMI device with MPI/DP interface
SIMATIC S7 300/400 with MPI/DP interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed graphically in the network
view.
2. Click the "Connections" button.
The devices available for connection are highlighted in color.
3. Click the interface of the PLC and use a drag-and-drop operation to draw a connection to
the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2012 System Manual, 08/2011,
4. Click the connecting line.
The connection is displayed graphically in the Inspector window.
5. Click "Highlight HMI connection" and select the HMI connection.
6. Click the communication partners in the "Network view" and change the MPI parameters
in the Inspector window according to the requirements of your project.
See the chapter "MPI parameters (Page 2018)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. Use the table to monitor the connection parameters and change the
connection partner. You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via
MPI.
Configuring an HMI connection
Communication via MPI
Communication via MPI
This section describes the communication between a WinCC Runtime and the SIMATIC S7
300/400 PLC via MPI.
You can use the following WinCC Runtimes as an HMI device:
WinCC RT Advanced
WinCC Runtime as HMI device
You configure the HMI connections between WinCC Runtime and SIMATIC S7 300/400 in the
"Devices & Networks" editor.
If you want to use a WinCC Runtime as an HMI device, you have the following options:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2013
1. You create a SIMATIC PC and configure a WinCC Runtime on this SIMATIC PC.
In this way you use the SIMATIC PC with a WinCC Runtime as an HMI device.
2. You create a WinCC Runtime and configure a communication processor to the Runtime.
In this way you use your configuration PC with a WinCC Runtime as an HMI device.
You can also connect multiple HMI devices to one SIMATIC S7 300/400 and multiple SIMATIC
S7 300/400s to one HMI device. The maximum number of communication partners that you
can connect to an HMI device is dependent on the HMI device used.
Additional information is available in the documentation for the respective HMI device.
HMI connection in the "Devices & Networks" editor
You configure the HMI connection between the PLC and the HMI device via MPI in the "Devices
& Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2014 System Manual, 08/2011,
Connection in the "Connections" editor
Alternatively, you configure the connection between the PLC and HMI device via MPI in the
"Connections" editor of the HMI device.
Configuring an HMI connection via MPI with a SIMATIC PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via
PROFIBUS in the "Devices & Networks" editor.
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 300/400 with MPI interface
SIMATIC PC with MPI interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a WinCC Runtime from the hardware catalog to
the PC.
3. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2015
4. Click the MPI interface of the PLC and use a drag-and-drop operation to draw a connection
to the MPI interface of the PC.
5. Click the connecting line.
6. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
7. Click the communication partners in the "Network view" and change the MPI parameters
in the Inspector window according to the requirements of your project.
See the chapter "MPI parameters (Page 2018)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via
MPI.
Configuring an HMI connection via MPI with a PC
Introduction
You configure an HMI connection between HMI devices and a SIMATIC S7 300/400 via MPI
in the "Devices & Networks" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2016 System Manual, 08/2011,
Requirements
The following communication partners are created in the "Devices & Networks" editor:
SIMATIC S7 300/400 with MPI interface
PC station with WinCC RT Advanced
Procedure
1. Double-click the "Devices & Networks" item in the project tree.
The available communication partners in the project are displayed in the network view.
2. Use a drag-and-drop operation to move a PROFIBUS-capable communication processor
from the hardware catalog to the WinCC Runtime.
3. Click the PROFIBUS interface of the communication processor and change the interface
to "MPI".
4. Click the "Connections" button and select "HMI connection" for the connection type.
The devices available for connection are highlighted in color.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2017
5. Click the MPI interface of the PLC and use a drag-and-drop operation to draw a connection
to the MPI interface of the communication processor.
6. Click the connecting line.
7. Click "Highlight HMI connection" and select the HMI connection.
The connection is displayed graphically in the Inspector window.
8. Click the communication partners in the "Network view" and change the MPI parameters
in the Inspector window according to the requirements of your project.
See the chapter "MPI parameters (Page 2018)" for additional details.
Note
The created HMI connection is also shown in the tabular area of the editor on the
"Connections" tab. You check the connection parameters in the table.
You can change the local name for the connection only in the table.
Result
You have created an HMI connection between an HMI device and a SIMATIC S7 300/400 via
MPI.
MPI parameters
MPI parameters for the HMI connection
MPI parameters for the HMI connection
An overview of the configured HMI connection parameters can be found in the properties for
the HMI connection.
Only limited changes are possible in this Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2018 System Manual, 08/2011,
Displaying and changing the HMI connection parameters
1. Click the HMI connection in the "Devices & Networks" editor.
2. Change the parameters of the HMI connection in the Inspector window under "Properties
> General > General".
"Connection"
Displays whether the devices are networked together.
- displayed if the devices are networked together.
- displayed if the devices are not networked together.
"Connection path"
The communication partners of the selected HMI connection and the associated MPI
parameters are displayed in the "Connection path" area. Some of the areas displayed cannot
be edited in this dialog.
"End point"
Displays the name of the device. This area is not editable.
"Interface"
Displays the selected interface of the device. You can choose between several interfaces,
depending on the device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2019
"Interface type"
Displays the selected interface type. This area is not editable.
"Subnet"
Displays the selected subnet. This area is not editable.
"Address"
Displays the MPI address of the device. This area is not editable.
"Find connection path" button
Enables the subsequent specification of connections.
MPI parameters for the HMI device
MPI parameters for the HMI device
An overview of the configured HMI device parameters can be found in the properties for the
HMI device.
Displaying and changing MPI parameters of the HMI device
1. Click the HMI device in the "Devices & Networks" editor.
2. Change the parameters of the HMI device in the Inspector window under "Properties >
General > General".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2020 System Manual, 08/2011,
"Interface networked with"
In the "Interface networked with" area, select the subnet of the HMI connection via which the
HMI device is connected to the network. You use the "Add new subnet" button to create a new
subnet.
"Parameters"
"Interface type"
You assign the interface type in the "Interface type" area. Depending on the HMI device
type, you have various interfaces to choose from.
"Address"
You assign the MPI address of the HMI device in the "Address" area. The MPI address
must be unique throughout the MPI network.
"Highest address"
The "Highest address" area displays the highest address of the MPI network.
"Transmission speed"
The "Transmission speed" is determined by the slowest device connected to the network.
The setting is identical throughout the network.
MPI parameters for the PLC
MPI parameters for the PLC
An overview of the configured parameters can be found in the properties for the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2021
Displaying and changing PROFIBUS parameters of the PLC
1. Click the PLC in the "Devices & Networks" editor.
2. Change the parameters of the PLC in the Inspector window under "Properties > General >
General".
"Interface networked with"
In the "Subnet" area, select the subnet of the HMI connection via which the HMI device is
connected to the network. You use the "Add new subnet" button to create a new subnet.
"Parameters"
"Interface type"
Depending on the HMI device type, you have various interfaces to choose from.
"Address"
You assign the MPI address of the HMI device in the "Address" area. The MPI address
must be unique throughout the MPI network.
"Highest address"
The "Highest address" area displays the highest address of the MPI network.
"Transmission speed"
The "Transmission speed" is determined by the slowest device connected to the network.
The setting is identical throughout the network.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2022 System Manual, 08/2011,
Addressing of the PLC via MPI
Introduction
Each communication partner must be assigned an MPI network address.
Each S7 module which supports communication functions and is operated the SIMATIC
S7-300/400 PLC is assigned a unique MPI address. Only one CPU may be used per rack.
Note
HMI devices cannot be operated with incorrect addressing
Always avoid redundant addressing on the MPI bus.
MPI address of the communication partner of a SIMATIC S7-300
When assigning addresses, you have to distinguish between communication partners with and
without separate MPI address.
If the communications partner has its own MPI address, you only need to define the MPI
address.
If the communication partners do not have a separate MPI address, specify the MPI address
of the communications partner used for the connection. In addition, define the slot and rack
of a communication partner without its own MPI address.
MPI address of the communication partner of a SIMATIC S7-400
Only S7 modules with an MPI connector are assigned an MPI address. Modules without an
MPI connector are addressed indirectly:
MPI address of the module to which the HMI is connected.
The slot and the rack of the module with which the HMI device communicates.
9.11.6.5 Data exchange
Data exchange using area pointers
General information on area pointers
Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC
and the HMI device alternately access these data areas for read and write operations.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2023
The PLC and the HMI device trigger defined interactions based on the evaluation of stored
data.
Configuration of area pointers
Before you use an area pointer, you enable it under "Connections > Area pointer". You then
assign the area pointer parameters.
You can find more detailed information on configuring area pointers in:
Configuring area pointers (Page 1885)
"Screen number" area pointer
Function
The HMI device saves information about the screen called on the HMI device to the "Screen
number" area pointer.
This allows the transfer of the current screen contents from the HMI device to the PLC. The
PLC can trigger specific reactions such as the call of a different screen.
Use
Configure and enable the area pointer in "Communication > Connections" before you put it
into use. You can create only one instance of the "Screen number" area pointer and only on
one PLC.
The screen number is always transferred to the PLC when a new screen is activated or when
the focus within a screen changes from one screen object to another.
Structure
The area pointer is a data area in the memory of the PLC with a fixed length of 5 words.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1st word Current screen type
2nd word Current screen number
3rd word Reserved
4th word Current field number
5th word Reserved
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2024 System Manual, 08/2011,
Current screen type
"1" for root screen or
"4" for permanent window
Current screen number
1 to 32767
Current field number
1 to 32767
"Date/time" area pointer
Function
This area pointer is used to transfer the date and time from the HMI device to the PLC.
The PLC writes control job "41" or "40" to the job mailbox.
When it evaluates the control job, the HMI device writes its current date and the time in the
data area configured in the "Date/time" area pointer. All definitions are coded in BCD format.
The "Date/Time" area pointer when used in a project which contains multiple connections must
be enabled for each configured connection.
The date/time data area has the following structure:
Data word Most significant byte Least significant byte
7 0 7 0
n+0 Reserved Hour (0 to 23)
Time
n+1 Minute (0 to 59) Second (0 to 59)
n+2 Reserved Reserved
n+3 Reserved Weekday (1 to 7, 1=Sunday)
Date
n+4 Day (1 to 31) Month (1 to 12)
n+5 Year (80 to 99/0 to 29) Reserved
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29result in the years 2000 through 2029.
"Date/time PLC" area pointer
Function
This area pointer is used to transfer the date and time from the PLC to the HMI device. Use
this area pointer if the PLC is the time master.
The PLC loads the data area of the area pointer. All definitions are coded in BCD format.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2025
The HMI device reads the data cyclically within the configured acquisition cycle and
synchronizes itself.
Note
Set an acquisition cycle of sufficient length for the date/time area pointer in order to avoid
any negative impact on HMI device performance.
Recommended: Acquisition cycle of 1 minute, if the process allows this.
The date/time data area has the following structure:
DATE_AND_TIME format (in BCD code)
Data word Most significant byte Least significant byte
7 . . . . . . 0 7 . . . . . . 0
n+0 Year (80 to 99/0 to 29) Month (1 to 12)
n+1 Day (1 to 31) Hour (0-23)
n+2 Minute (0-59) Second (0 to 59)
n+3 Reserved Reserved Weekday
(1 to 7,
1=Sunday)
n+4
1)
Reserved Reserved
n+5
1)
Reserved Reserved
1) The two data words must exist in the data area to ensure that the data format
corresponds to WinCC flexible and to avoid false information being read.
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29 result in the years 2000 through 2029.
"Coordination" area pointer
Function
The "Coordination" area pointer is used to implement the following functions:
Detecting the startup of the HMI device in the control program
Detecting the current operating mode of the HMI device in the control program
Detecting whether the HMI device is ready to communicate in the control program
The "Coordination" area pointer has a length of two words.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2026 System Manual, 08/2011,
Use
Note
The HMI device always writes the entire coordination area when updating the area pointer.
The control program can for this reason not make changes to the coordination area.
Assignment of bits in the "Coordination" area pointer
0 1 2 7 8 15
X X X
high-order byte
1st word
= reserved
x = assigned
2st word not assigned
low-order byte
Startup bit
Operation mode
Life bit
Startup bit
The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently
to "1" when startup is completed.
Operating mode
The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The
status of the operating mode bit is "0" during normal operation of the HMI device. You can
determine the current operating mode of the HMI device by reading this bit in the control
program.
Life bit
The HMI device inverts the life bit at intervals of approximately one second. You can check
whether or not there is still a connection to the HMI device by querying this bit in the control
program.
"Project ID" area pointer
Function
When Runtime starts it can check to see if the HMI device is connected to the correct PLC.
This check is important when operating with several HMI devices.
The HMI device compares a value stored on the PLC with the value specified in the
configuration data. This ensures the compatibility of the configuration data and the PLC
program. If there is no concordance, a system alarm is given on the HMI device and Runtime
is stopped.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2027
Use
To use this area pointer, set up the following during the configuration:
Define the version of configuration. Possible values between 1 and 255.
You enter the version in the editor "Runtime settings > General" in the "Identification" area.
Data address of the value for the version that is stored in the PLC:
Enter the data address in the "Communication > Connections" editor in "Address".
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in
all the other connections in the project being switched to "offline".
This behavior has the following prerequisites:
You have configured several connections in a project.
You are using the "project ID" area pointer in at least one connection.
The following causes which may set connections to "offline":
The PLC is not available.
The connection has been switched offline in the engineering system.
"Job mailbox" area pointer
Function
The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding
actions on the HMI device. These functions include:
Display screen
Set date and time
Data structure
The first word of the job mailbox contains the job number. Depending on the job mailbox, up
to three parameters can be transferred.
Word Most significant byte Least significant byte
n+0 0 Job number
n+1 Parameter 1
n+2 Parameter 2
n+3 Parameter 3
The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This
means that the parameters must be entered in the job mailbox first, followed by the job number.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2028 System Manual, 08/2011,
Once the HMI device has accepted the job mailbox, the first word is set to 0 again. The
execution of the job mailbox is generally not completed at this point in time.
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job
number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI
device is online.
No
.
Function
14 Setting the time (BCD coded)
Parameter 1 Left byte: -
Right byte: hours (0-23)
Parameter 2 Left byte: minutes (0-59)
Right byte: seconds (0-59)
Parameter 3 -
15 Setting the date (BCD code)
3) 4)
Parameter 1 Left byte: -
Right byte: weekday
(1-7: Sunday-Saturday)
Parameter 2 Left byte: day (1-31)
Right byte: month (1-12)
Parameter 3 Left byte: year
23 User logon
Logs the user on with the name "PLC user" at the HMI device with the group number transferred
in parameter 1.
The logon is possible only when the transferred group number exists in the project.
Parameter 1 Group number 1 to 255
Parameter 2, 3 -
24 User logoff
Logs off the current user.
(The function corresponds to the "logoff" system function)
Parameter 1, 2, 3 -
40 Transfer date/time to PLC
(in the S7 format DATE_AND_TIME)
An interval of at least 5 seconds must be maintained between two successive jobs in order to
prevent overload of the HMI device.
Parameter 1, 2, 3 -
41 Transfer date/time to PLC
(In OP/MP format)
An interval of at least 5 seconds must be maintained between two successive jobs in order to
prevent overload of the HMI device.
Parameter 1, 2, 3 -
46 Update tags
Causes the HMI device to read the current value of the tagsfrom the PLC whose update ID
matches the value transferred in parameter 1.
(Function corresponds to the "UpdateTag" system function.)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2029
No
.
Function
14 Setting the time (BCD coded)
Parameter 1 1 - 100
49 Delete alarm buffer
Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer.
Parameter 1, 2, 3 -
50 Delete alarm buffer
Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer.
Parameter 1, 2, 3 -
51 Screen selection
2)
Parameter 1 Screen number
Parameter 2 -
Parameter 3 Field number
69 Reading data record from PLC
1)
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Parameter 3 0: Do not overwrite existing data record
1: Overwrite existing data record
70 Writing data record from PLC
1)
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Parameter 3 -
1)
Only for devices supporting recipes.
2)
OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if
the on-screen keyboard is active.
3)
The weekday is ignored on HMI device KTP 600 BASIC PN.
4)
The weekday is ignored when you configure the "Date/Time PLC" area pointer.
"Data record" area pointer
"Data record" area pointer
Function
When data records are transferred between the HMI device and PLC, both partners access
common communications areas on the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2030 System Manual, 08/2011,
Data transfer types
There are two ways of transferring data records between the HMI device and PLC:
Transfer without synchronization
Transfer with synchronization via the data mailbox
Data records are always transferred directly, which means that the tag values are read straight
from an address or written straight to an address configured for this tag without being redirected
via an interim memory.
Initiating the transfer of data records
There are three ways of triggering the transfer:
Operator input in the recipe view
Job mailboxes
The transfer of data records can also be triggered by the PLC.
Triggering by configured functions
If the transfer of data records is triggered by a configured function or by a job mailbox, the
recipe view on the HMI device remains operable. The data records are transferred in the
background.
Simultaneous processing of several transfer requests is, however, not possible. In this case,
the HMI device rejects the other transfer requests with a system alarm.
Transfer without synchronization
If you select asynchronous transfer of data records between the HMI device and PLC, there
is no coordination over the common data areas. It is therefore unnecessary to set up a data
area during configuration.
Asynchronous data record transfer can be a useful alternative, for example when:
The system is capable of excluding the risk of uncontrolled overwriting of data by the
communication peer.
The PLC does not require information about the recipe number and data record number.
The transfer of data records is triggered by the operator of the HMI device.
Reading values
When a read job is triggered, the values are read from the PLC addresses and transferred to
the HMI device.
Triggering by the operator in the recipe view:
The values are downloaded to the HMI device. You can then, for example, process, edit,
or save these values in the HMI device.
Triggering by a function or job mailbox:
The values are saved immediately to the data volume.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2031
Writing values
When a write job is triggered, the values are written to the PLC addresses.
Triggering by the operator in the recipe view:
The current values are written to the PLC.
Triggering by a function or job mailbox:
The current values are written to the PLC from the data medium.
Transfer with synchronization
If you select synchronous transfer, both communication partners set status bits in the common
data area. You can use this mechanism to prevent uncontrolled overwriting of data in either
direction in your control program.
Application
Synchronous data record transfer can be a useful solution, for example, when:
The PLC is the "active partner" in the transfer of data records.
The PLC evaluates the information about the recipe number and data record number.
The transfer of data records is triggered by means of a Job mailbox.
Requirements
In order to synchronize transfer of data records between the HMI device and the PLC, the
following requirements must be met during configuration:
An area pointer has been set up: "Communication > Connections" editor in "Area pointer".
The PLC with which the HMI device synchronizes transfer of data records is specified in
the recipe:
"Recipes" editor in the inspector window the option "Coordinated transfer of data records"
under "General > Synchronization > Settings"
Structure of the data area
The data area has a fixed length of 5 words. Structure of the data area:
15 0
1. Word Current recipe number (1 - 999)
2. Word Current data record number (0 - 65535)
3. Word Reserved
4. Word Status (0, 2, 4, 12)
5. Word Reserved
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2032 System Manual, 08/2011,
Status
The status word (word 4) can adopt the following values:
Value Meaning
Decimal Binary
0 0000 0000 Transfer permitted, data mailbox free
2 0000 0010 Transferring
4 0000 0100 Transfer completed without error
12 0000 1100 Transfer completed with error
Sequence of a transfer started by the operator in the recipe view
Reading from the PLC started by the operator in the recipe view
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe number to be read and the status
"Transferring" in the data record and sets the data record number to
0.
Abort with system
event.
3 The HMI device reads the values from the PLC and displays them in
the recipe view.
If the recipes have synchronized tags, the values from the PLC are
also written to the tags.
4 The HMI device sets the status "Transfer completed."
5 The control program must reset the status word to zero in order to
enable further transfers.
Writing to the PLC started by the operator in the recipe view
Step Action
Check: Status word = 0?
1 Yes No
The HMI device enters the recipe and data record number to be
written and the status "Transferring" in the data record.
Abort with system
event.
2 The HMI device writes the current values to the PLC.
If the recipes have synchronized tags, the changed values are
synchronized between the recipe view and tags and then written to
the PLC.
3 The HMI device sets the status "Transfer completed."
4 If required, the control program can now evaluate the transferred
data.
5 The control program must reset the status word to zero in order to
enable further transfers.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2033
Note
The status word may only be set by the HMI device. The PLC may only reset the status word
to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency is
detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Sequence of the transfer triggered by a job mailbox
The transfer of data records between the HMI device and the PLC can be initiated by either
one of these stations.
The two job mailboxs No. 69 and No. 70 are available for this type of transfer.
No. 69: Read data record from PLC ("PLC DAT")
Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is
structured as follows:
Left byte (LB) Right byte (RB)
Word 1 0 69
Word 2 Recipe number (1-999)
Word 3 Data record number (1 to 65535)
Word 4 Do not overwrite existing data record: 0
Overwrite existing data record: 1
No. 70: Write data record to PLC ("DAT PLC")
Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox
is structured as follows:
Left byte (LB) Right byte (RB)
Word 1 0 70
Word 2 Recipe number (1-999)
Word 3 Data record number (1-65,535)
Word 4
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2034 System Manual, 08/2011,
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified in
the job and the status "Transferring" in the data record.
Abort without
return message.
3 The HMI device reads the values from the PLC and saves these to the
data record defined in the job mailbox.
4 If "Overwrite" was selected in the job, an existing data record is
overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "Do not overwrite" was selected in the job, and the data record
already exists, the HMI device aborts the job and enters 0000 1100
in the status word of the data mailbox.
5 The control program must reset the status word to zero in order to enable
further transfers.
Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified in
the job and the status "Transferring" in the data mailbox.
Abort without
return message.
3 The HMI device fetches the values of the data record specified in the
function from the data medium and writes the values to the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order to enable
further transfers.
Sequence of the transfer when triggered by a configured function
Reading from the PLC using a configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
mailbox.
Abort with system
event.
3 The HMI device reads the values from the PLC and stores them
in the data record specified in the function.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2035
Step Action
4 If "Yes" was selected for the "Overwrite" function, an existing
data record is overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "No" was selected for the "Overwrite" function and the data
record already exists, the HMI device aborts the job and
enters 0000 1100 in the status word of the data mailbox.
5 The control program must reset the status word to zero in order
to enable further transfers.
Writing to the PLC by means of configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
mailbox.
Abort with system
event.
3 The HMI device fetches the values of the data record specified
in the function from the data medium and transfers the values to
the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order
to enable further transfers.
Possible causes of error when transferring data records
Possible causes of error
The section below shows possible error causes which lead to the cancellation of data record
transfer:
Tag address not set up on the PLC
Overwriting data records not possible
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2036 System Manual, 08/2011,
Recipe number does not exist
Data record number does not exist
Note
The status word may only be set by the HMI device. The PLC may only reset the status
word to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency
is detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Reaction to an aborted transfer due to errors
If the transfer of data records is aborted due to errors, the HMI device reacts as follows:
Triggering by the operator in the recipe view
Information in the status bar of the recipe view and output of system alarms
Triggered by function
Output of system alarms
Triggering by job mailbox
No return message on the HMI device
You can nonetheless evaluate the status of the transfer by querying the status word in the data
record.
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
For additional information see:
Displaying tags with Runtime Advanced and Panels (Page 940)
Note
The value is read out time-triggered for Basic Panels.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2037
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
The following picture shows the structure of a trend transfer area.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2038 System Manual, 08/2011,
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Permitted data types for trends
For SIMATIC S7
You assign one bit to each trend during configuration. Tags and array tags of the "Word" or
"Int" data type are permitted.
Alarms
Configuring alarms
Configure alarms
Several steps are needed to configure alarms, such as operational messages, error alarms,
and acknowledgement.
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2039
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Data types
For connections with a SIMATIC communication driver, the following data types are supported:
PLC Permitted data types
Discrete alarms Analog alarms
SIMATIC S7
300/400
WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT, REAL,
COUNTER, TIME
How the bit positions are counted
For connections with a SIMATIC communication driver, the following counting method applies:
How the bit positions are
counted
Byte 0 Byte 1
Most significant byte Least significant byte
In SIMATIC S7
PLCs
7 0 7 0
In WinCC you configure: 15 8 7 0
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2040 System Manual, 08/2011,
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2041
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2042 System Manual, 08/2011,
9.11.6.6 Performance features of communication
Permitted data types for SIMATIC S7 300/400
Permitted data types for connections with SIMATIC S7 300/400
The table lists the data types that can be used when configuring tags and area pointers.
Data type Length
BOOL 1-bit
BYTE 1 byte
WORD 2 bytes
DWORD 4 bytes
CHAR 1 byte
INT 2 byte
DINT 4 bytes
REAL 4 bytes
TIME 4 bytes
DATE 2 bytes
TIME_OF_DAY, TOD 4 bytes
S5TIME 2 bytes
COUNTER 2 bytes
TIMER 2 bytes
DATE_AND_TIME 8 bytes
STRING (2+n) bytes, n = 0 to 254
9.11.6.7 Creating connections in the "Connections" editor
Creating a PROFINET connection
Requirements
A project is open.
An HMI device with a PROFINET interface has been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2043
Procedure
1. Open the "Connections" editor of the HMI device.
2. Double-click "<Add>".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2044 System Manual, 08/2011,
3. Select the driver in the "Communication driver" column.
4. Click the name of the connection.
5. Select a PROFINET interface of the HMI device in the Inspector window under "Parameters
> Interface".
6. Set the IP addresses of the communication partners in the Inspector window:
HMI device: "Parameters > HMI device > Address"
PLC: "Parameters > PLC > Address"
Creating a PROFIBUS connection
Requirements
A project is open.
An HMI device with a PROFIBUS interface has been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2045
Procedure
1. Open the "Connections" editor of the HMI device.
2. Double-click "<Add>".
3. Select the driver in the "Communication driver" column.
4. Click the name of the connection.
5. Select the "MPI/DP" interface in the Inspector window under "Parameters > Interface".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2046 System Manual, 08/2011,
6. Select the "DP" profile in the Inspector window under "Parameters > Network".
7. Set the addresses of the communication partners in the inspector window:
HMI device: "Parameters > HMI device > Address"
PLC: "Parameters > PLC > Address"
Creating an MPI connection
Requirements
A project is open.
An HMI device with an MPI interface has been created.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2047
Procedure
1. Open the "Connections" editor of the HMI device.
2. Double-click "<Add>".
3. Select the driver in the "Communication driver" column.
4. Click the name of the connection.
5. Select the "MPI/DP" interface in the Inspector window under "Parameters > Interface".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2048 System Manual, 08/2011,
6. Select the "MPI" profile in the Inspector window under "Parameters > Network".
7. Set the addresses of the communication partners in the inspector window:
HMI device: "Parameters > HMI device > Address"
PLC: "Parameters > PLC > Address"
Parameters for the connection
Parameters for the connection (SIMATIC S7 300/400)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning
parameters according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2049
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2050 System Manual, 08/2011,
Ethernet parameters
Parameters for the HMI device
You set the parameters for the HMI device in the network under "HMI device".. The changes
are not transferred automatically to the HMI device. You must change the settings in the Control
Panel of the HMI device.
"Interface"
If you are directly connected to the HMI device during configuration, you can set up the IP
address of the HMI device in WinCC.
Note
The IP address in the Control Panel will be overwritten upon subsequent loading if you
have already set up the IP address in the HMI device control panel.
The IP address already set up in the Control Panel will be retained upon subsequent
loading if you activate "Set IP address using a different method".
The IP address is transferred to the HMI device during project transfer.
To set up the IP address of the HMI device:
Click the HMI device.
Open the "Device configuration" editor.
Click the Ethernet interface.
Assign the IP address in the inspector window under:
"General > PROFINET interface > Ethernet addresses"
"Address"
You assign the IP address of the HMI device in the "Address" area.
When you transfer the WinCC project to the HMI device, this IP address is set up directly
in the HMI device.
"Access point"
The access point defines a logical device name through which the communication partner
can be reached.
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
Under "Address", set the IP address of the S7 module to which the HMI device is connected.
"Expansion slot"
Defines the number of the expansion slot of the CPU to be addressed.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2051
"Rack"
Defines the rack number of the CPU to be addressed.
"Cyclic mode"
Note
The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC.
When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This increases system performance.
Disable cyclic mode if you are operating several HMI devices in parallel.
PROFIBUS parameters
Parameters for the HMI device
You assign the parameters for the HMI device in the network once under "HMI device". The
change applies to each communication partner.
"Type"
Specifies the physical connection used.
"Interface"
For "Interface", you select the HMI device interface via which the HMI device is connected
to the PROFIBUS network.
"Baud rate"
For "Baud rate", you set the transmission speed of the data in the network. The baud rate
is determined by the slowest HMI device connected to the network. The setting must be
identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must
be less than or equal to 63.
"Address"
You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS
address must be unique in the PROFIBUS network.
"Sole master on bus"
Disables an additional safety feature against bus faults when the HMI device is connected
to the network. A passive station (slave) can only send data if it is requested to do so by
an active station (master).
In S7 200, you must set an HMI device as the master.
"Access point"
The access point defines a logical device name through which the communication partner
can be reached.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2052 System Manual, 08/2011,
Parameters for the network
Under "Network", you set the parameters for the PROFIBUS network to which the HMI device
is linked.
"Profile"
For "Profile", you select the network profile that is used in the network. In "Profile", set "DP",
"Universal", or "Standard". The setting must be identical throughout the network.
"Highest address"
For "Highest station address", set the highest station address. The highest station address
must be greater than or equal to the highest actual PROFIBUS address. The setting must
be identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address
must be less than or equal 63.
"Number of masters"
For "Number of masters", set the number of masters in the PROFIBUS network. This
information is necessary to correctly calculate the bus parameters.
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which
the HMI device is connected.
"Cyclic operation"
Note
The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC.
When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This increases system performance. Disable cyclic mode if you are
operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200
PLCs.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2053
MPI parameters
Parameters for the HMI device
You assign the parameters for the HMI device in the network once under "HMI device". The
change applies to each communication partner.
"Type"
Specifies the physical connection used.
"Interface"
For "Interface", you select the HMI device interface via which the HMI device is connected
to the MPI network.
"Baud rate"
For "Baud rate", you set the transmission speed of the data in the network. The baud rate
is determined by the slowest HMI device connected to the network. The setting must be
identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must
be less than or equal to 63.
"Address"
For "Address", you set the MPI address of the HMI device. The MPI address must be unique
throughout the MPI network.
"Sole master on bus"
Disables an additional safety feature against bus faults when the HMI device is connected
to the network. A passive station (slave) can only send data if it is requested to do so by
an active station (master). If you have connected only slaves to the HMI device, you must
therefore disable the "Sole master on bus" safety feature.
In S7 200, you must set an HMI device as the master.
Parameters for the network
Under "Network", you set the parameters for the MPI network to which the HMI device is linked.
"Profile"
For "Profile", you select the network profile that is used in the network. In "Profile", set "MPI".
The setting must be identical throughout the network.
"Highest address"
For "Highest station address", set the highest station address. The highest station address
must be greater than or equal to the highest actual MPI address. The setting must be
identical throughout the network.
"Number of masters"
This setting is not required for MPI.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2054 System Manual, 08/2011,
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
For "Address", set the MPI address of the S7 module (CPU, FM, or CP) to which the HMI
device is connected.
"Cyclic mode"
When cyclic mode is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This improves system performance. Disable cyclic mode if you are
operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200.
Cyclic operation
Handling the "Cyclic operation" selection
If "Cyclic operation" is enabled, the HMI device sends a message frame to the CPU at the
beginning of communication indicating that certain tags are required on a recurring basis.
The CPU then always transmits the data at the same cyclic interval. This saves the HMI device
from having to output new requests for the data.
If cyclic operation is disabled, the HMI device sends a request whenever information is required.
Additional properties:
Cyclic operation reduces data transmission load at the HMI device. The PLC resources are
used to relieve load on the HMI device.
The PLC only supports a certain number of cyclic services. The HMI device handles the
operation if the PLC cannot provide any further resources for cyclic services.
The HMI device generates the cycle if the PLC does not support the cyclic mode.
Screen tags are not integrated in cyclic operation.
Cyclic mode is only set up at the restart of Runtime.
The HMI device transfers several jobs to the PLC if cyclic mode is enabled, depending on
the PLC.
The HMI device only transfers one job to the PLC if cyclic mode is disabled.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2055
9.11.7 Communicating with SIMATIC S7 200
9.11.7.1 Communication with SIMATIC S7 200
Introduction
This section describes the communication between an HMI device and the SIMATIC S7 200
PLC.
You can configure the following communication channels for the SIMATIC S7 200 PLC:
PROFINET and Ethernet
PROFIBUS
MPI
PPI
HMI connection for communication
You configure connections between the HMI device and a SIMATIC S7 200 in the
"Connections" editor of the HMI device.
9.11.7.2 Creating a connection to SIMATIC S7 200
Introduction
You configure a connection to the SIMATIC S7 200 PLC in the "Connections" editor of the HMI
device. The interfaces are named differently depending on the HMI device.
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2056 System Manual, 08/2011,
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2057
4. In the "Communication drivers" column, select the "SIMATIC S7 200" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
See the chapter "Parameters for the connection (Page 2058)" for additional details.
9.11.7.3 Parameters for the connection
Parameters for the connection (SIMATIC S7 200)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device" and "PLC" areas are available for assigning parameters
according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2058 System Manual, 08/2011,
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2059
Ethernet parameters
Parameters for the HMI device
You set the parameters for the HMI device in the network under "HMI device".. The changes
are not transferred automatically to the HMI device. You must change the settings in the Control
Panel of the HMI device.
"Interface"
If you are directly connected to the HMI device during configuration, you can set up the IP
address of the HMI device in WinCC.
Note
The IP address in the Control Panel will be overwritten upon subsequent loading if you
have already set up the IP address in the HMI device control panel.
The IP address already set up in the Control Panel will be retained upon subsequent
loading if you activate "Set IP address using a different method".
The IP address is transferred to the HMI device during project transfer.
To set up the IP address of the HMI device:
Click the HMI device.
Open the "Device configuration" editor.
Click the Ethernet interface.
Assign the IP address in the inspector window under:
"General > PROFINET interface > Ethernet addresses"
"Address"
You assign the IP address of the HMI device in the "Address" area.
When you transfer the WinCC project to the HMI device, this IP address is set up directly
in the HMI device.
"Access point"
The access point defines a logical device name through which the communication partner
can be reached.
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
Under "Address", set the IP address of the S7 module to which the HMI device is connected.
"Expansion slot"
Defines the number of the expansion slot of the CPU to be addressed.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2060 System Manual, 08/2011,
"Rack"
Defines the rack number of the CPU to be addressed.
"Cyclic mode"
Note
The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC.
When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This increases system performance.
Disable cyclic mode if you are operating several HMI devices in parallel.
PROFIBUS parameters
Parameters for the HMI device
You assign the parameters for the HMI device in the network once under "HMI device". The
change applies to each communication partner.
"Type"
Specifies the physical connection used.
"Interface"
For "Interface", you select the HMI device interface via which the HMI device is connected
to the PROFIBUS network.
"Baud rate"
For "Baud rate", you set the transmission speed of the data in the network. The baud rate
is determined by the slowest HMI device connected to the network. The setting must be
identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must
be less than or equal to 63.
"Address"
You set the PROFIBUS address of the HMI device under "Address". The PROFIBUS
address must be unique in the PROFIBUS network.
"Sole master on bus"
Disables an additional safety feature against bus faults when the HMI device is connected
to the network. A passive station (slave) can only send data if it is requested to do so by
an active station (master).
In S7 200, you must set an HMI device as the master.
"Access point"
The access point defines a logical device name through which the communication partner
can be reached.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2061
Parameters for the network
Under "Network", you set the parameters for the PROFIBUS network to which the HMI device
is linked.
"Profile"
For "Profile", you select the network profile that is used in the network. In "Profile", set "DP",
"Universal", or "Standard". The setting must be identical throughout the network.
"Highest address"
For "Highest station address", set the highest station address. The highest station address
must be greater than or equal to the highest actual PROFIBUS address. The setting must
be identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud in the OP 73 or the OP 77A, the highest station address
must be less than or equal 63.
"Number of masters"
For "Number of masters", set the number of masters in the PROFIBUS network. This
information is necessary to correctly calculate the bus parameters.
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
For "Address", set the PROFIBUS address of the S7 module (CPU, FM, or CP) to which
the HMI device is connected.
"Cyclic operation"
Note
The setting "Cyclic operation" cannot be configured for the SIMATIC S7 1200 PLC.
When cyclic operation is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This increases system performance. Disable cyclic mode if you are
operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200
PLCs.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2062 System Manual, 08/2011,
MPI parameters
Parameters for the HMI device
You assign the parameters for the HMI device in the network once under "HMI device". The
change applies to each communication partner.
"Type"
Specifies the physical connection used.
"Interface"
For "Interface", you select the HMI device interface via which the HMI device is connected
to the MPI network.
"Baud rate"
For "Baud rate", you set the transmission speed of the data in the network. The baud rate
is determined by the slowest HMI device connected to the network. The setting must be
identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must
be less than or equal to 63.
"Address"
For "Address", you set the MPI address of the HMI device. The MPI address must be unique
throughout the MPI network.
"Sole master on bus"
Disables an additional safety feature against bus faults when the HMI device is connected
to the network. A passive station (slave) can only send data if it is requested to do so by
an active station (master). If you have connected only slaves to the HMI device, you must
therefore disable the "Sole master on bus" safety feature.
In S7 200, you must set an HMI device as the master.
Parameters for the network
Under "Network", you set the parameters for the MPI network to which the HMI device is linked.
"Profile"
For "Profile", you select the network profile that is used in the network. In "Profile", set "MPI".
The setting must be identical throughout the network.
"Highest address"
For "Highest station address", set the highest station address. The highest station address
must be greater than or equal to the highest actual MPI address. The setting must be
identical throughout the network.
"Number of masters"
This setting is not required for MPI.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2063
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
For "Address", set the MPI address of the S7 module (CPU, FM, or CP) to which the HMI
device is connected.
"Cyclic mode"
When cyclic mode is enabled, the PLC optimizes the data exchange between the HMI
device and the PLC. This improves system performance. Disable cyclic mode if you are
operating several HMI devices in parallel. This setting is not required for SIMATIC S7-200.
PPI parameters
Parameters for the HMI device
You assign the parameters for the HMI device in the network once under "HMI device". The
change applies to each communication partner.
"Type"
Specifies the physical connection used.
"Interface"
For "Interface", you select the HMI device interface via which the HMI device is connected
to the PP network.
"Baud rate"
For "Baud rate", you set the transmission speed of the data in the network. The baud rate
is determined by the slowest HMI device connected to the network. The setting must be
identical throughout the network.
Note
If you set a baud rate of 1.5 Mbaud for OP 73 or OP 77A, the highest station address must
be less than or equal to 63.
"Address"
For "Address", you set the PPI address of the HMI device. The PPI address must be unique
throughout the PPI network.
"Access point"
For "Access point", you set the access point via which the communication partner is
reached.
"Sole master on bus"
Disables an additional safety feature against bus faults when the HMI device is connected
to the network. A passive station (slave) can only send data if it is requested to do so by
an active station (master). If you have connected only slaves to the HMI device, you must
therefore disable the "Sole master on bus" safety feature.
In S7 200, you must set an HMI device as the master.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2064 System Manual, 08/2011,
Parameters for the network
Under "Network", you set the parameters for the network to which the HMI device is linked.
"Profile"
For "Profile", you select the network profile that is used in the network. In "Profile", set "PPI".
The setting must be identical throughout the network.
"Highest address"
For "Highest station address", set the highest station address. The highest station address
must be greater than or equal to the highest actual MPI address. The setting must be
identical throughout the network.
"Number of masters"
Set the number of the master on the network to "1".
Parameters for the PLC
Under "PLC", you address the S7 module with which the HMI device will exchange data. Assign
a name for the connection for each communication partner.
"Address"
For "Address", set the PPI address of the S7 module to which the HMI device is connected.
"Cyclic operation"
This parameter is not required for communication via PPI.
Cyclic operation
Handling the "Cyclic operation" selection
If "Cyclic operation" is enabled, the HMI device sends a message frame to the CPU at the
beginning of communication indicating that certain tags are required on a recurring basis.
The CPU then always transmits the data at the same cyclic interval. This saves the HMI device
from having to output new requests for the data.
If cyclic operation is disabled, the HMI device sends a request whenever information is required.
Additional properties:
Cyclic operation reduces data transmission load at the HMI device. The PLC resources are
used to relieve load on the HMI device.
The PLC only supports a certain number of cyclic services. The HMI device handles the
operation if the PLC cannot provide any further resources for cyclic services.
The HMI device generates the cycle if the PLC does not support the cyclic mode.
Screen tags are not integrated in cyclic operation.
Cyclic mode is only set up at the restart of Runtime.
The HMI device transfers several jobs to the PLC if cyclic mode is enabled, depending on
the PLC.
The HMI device only transfers one job to the PLC if cyclic mode is disabled.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2065
9.11.7.4 Data exchange
Data exchange using area pointers
General information on area pointers
Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC
and the HMI device alternately access these data areas for read and write operations.
The PLC and the HMI device trigger defined interactions based on the evaluation of stored
data.
Configuration of area pointers
Before you use an area pointer, you enable it under "Connections > Area pointer". You then
assign the area pointer parameters.
You can find more detailed information on configuring area pointers in:
Configuring area pointers (Page 1885)
See also
Data exchange using area pointers (Page 1882)
"Screen number" area pointer
Function
The HMI device saves information about the screen called on the HMI device to the "Screen
number" area pointer.
This allows the transfer of the current screen contents from the HMI device to the PLC. The
PLC can trigger specific reactions such as the call of a different screen.
Application
Configure and enable the area pointer in "Communication > Connections" before you put it
into use. You can create only one instance of the "Screen number" area pointer and only on
one PLC.
The screen number is always transferred to the PLC when a new screen is activated or when
the focus within a screen changes from one screen object to another.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2066 System Manual, 08/2011,
Structure
The area pointer is a data area in the memory of the PLC with a fixed length of 5 words.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1st word Current screen type
2nd word Current screen number
3rd word Reserved
4th word Current field number
5th word Reserved
Current screen type
"1" for root screen or
"4" for permanent window
Current screen number
1 to 32767
Current field number
1 to 32767
"Date/time" area pointer
Function
This area pointer is used to transfer the date and time from the HMI device to the PLC.
The PLC writes control job "41" to the job mailbox.
When it evaluates the control job, the HMI device writes its current date and the time in the
data area configured in the "Date/time" area pointer. All definitions are coded in BCD format.
The "Date/Time" area pointer when used in a project which contains multiple connections must
be enabled for each configured connection.
The date/time data area has the following structure:
Data word Most significant byte Least significant byte
7 0 7 0
n+0 Reserved Hour (0 to 23)
Time
n+1 Minute (0 to 59) Second (0 to 59)
n+2 Reserved Reserved
n+3 Reserved Weekday (1 to 7, 1=Sunday)
Date
n+4 Day (1 to 31) Month (1 to 12)
n+5 Year (80 to 99/0 to 29) Reserved
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2067
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29result in the years 2000 through 2029.
"Date/time PLC" area pointer
Function
This area pointer is used to transfer the date and time from the PLC to the HMI device. Use
this area pointer if the PLC is the time master.
The PLC loads the data area of the area pointer. All definitions are coded in BCD format.
The HMI device reads the data cyclically within the configured acquisition cycle and
synchronizes itself.
Note
Set an acquisition cycle of sufficient length for the date/time area pointer in order to avoid
any negative impact on HMI device performance.
Recommended: Acquisition cycle of 1 minute, if the process allows this.
The date/time data area has the following structure:
DATE_AND_TIME format (in BCD code)
Data word Most significant byte Least significant byte
7 . . . . . . 0 7 . . . . . . 0
n+0 Year (80 to 99/0 to 29) Month (1 to 12)
n+1 Day (1 to 31) Hour (0 to 23)
n+2 Minute (0 to 59) Second (0 to 59)
n+3 Reserved Reserved Weekday
(1 to 7,
1=Sunday)
n+4
1)
Reserved Reserved
n+5
1)
Reserved Reserved
1) The two data words must exist in the data area to ensure that the data format matches
WinCC flexible and to avoid reading false information.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2068 System Manual, 08/2011,
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29 result in the years 2000 through 2029.
"Coordination" area pointer
Function
The "Coordination" area pointer is used to implement the following functions:
Detecting the startup of the HMI device in the control program
Detecting the current operating mode of the HMI device in the control program
Detecting whether the HMI device is ready to communicate in the control program
The "Coordination" area pointer has a length of two words.
Use
Note
Each time the area pointer is updated by the HMI device, the entire coordination area is
always written.
For this reason, the PLC program must not make any changes in the coordination area.
Assignment of the bits in the "Coordination" area pointer
0 1 2 7 8 15
X X X
high-order byte
1st word
= reserved
x = assigned
2st word not assigned
low-order byte
Startup bit
Operation mode
Life bit
Startup bit
The startup bit is set briefly to "0" by the HMI device during startup. After startup, the bit is set
permanently to "1".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2069
Operating mode
As soon as the HMI device is switched offline by the user, the operating mode bit is set to 1.
In normal operation of the HMI device, the state of the operating mode bit is "0". You can find
out the current operating mode of the HMI device by querying this bit.
Life bit
The life bit is inverted by the HMI device at intervals of approximately one second. By querying
this bit in the PLC program, you can check whether or not the connection to the HMI device
still exists.
"Project ID" area pointer
Function
When Runtime starts it can check to see if the HMI device is connected to the correct PLC.
This check is important when operating with several HMI devices.
For this, the HMI device compares a value stored on the PLC with the value specified in
configuration. This ensures compatibility of the configuration data with the PLC program. If
there is no concordance, a system event is given on the HMI device and Runtime is stopped.
Use
To use this area pointer, set up the following during the configuration:
Define the version of configuration. Possible value between 1 and 255.
You enter the version in the editor "Runtime settings > General" in the "Identification" area.
Data address of the value for the version that is stored in the PLC:
You enter the data address in the editor "Communication > Connections" under "Address".
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in
all the other connections in the project being switched to "offline".
This behavior has the following requirements:
You have configured several connections in a project.
You are using the "project ID" area pointer in at least one connection.
Causes which may set connections "offline":
The PLC is not available.
The connection has been switched offline in the engineering system.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2070 System Manual, 08/2011,
"Job mailbox" area pointer
Function
The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding
actions on the HMI device. These functions include, for example:
Display screen
Set date and time
Data structure
The first word of the job mailbox contains the job number. Depending on the job mailbox, up
to three parameters can be transferred.
Word Most significant byte Least significant byte
n+0 0 Job number
n+1 Parameter 1
n+2 Parameter 2
n+3 Parameter 3
The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This
means that the parameters must be entered in the job mailbox first, followed by the job number.
When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution
of the job mailbox is generally not completed at this point in time.
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job
number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI
device is online.
Note
Please note that not all HMI devices support job mailboxes. TP 170A and Micro Panel do not
support job mailboxes, for example.
No
.
Function
14 Setting the time (BCD coded)
Parameter 1 Left byte: -
Right byte: hours (0-23)
Parameter 2 Left byte: minutes (0-59)
Right byte: seconds (0-59)
Parameter 3 -
15 Set date (BCD code)
3)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2071
No
.
Function
14 Setting the time (BCD coded)
Parameter 1 Left byte: -
Right byte: weekday
(1-7: Sunday-Saturday)
Parameter 2 Left byte: day (1-31)
Right byte: month (1-12)
Parameter 3 Left byte: year
23 User logon
Logs the user on with the name "PLC user" at the HMI device with the group number transferred
in parameter 1.
The logon is possible only when the transferred group number exists in the project.
Parameter 1 Group number 1 to 255
Parameter 2, 3 -
24 User logoff
Logs off the current user.
(The function corresponds to the "logoff" system function)
Parameter 1, 2, 3 -
40 Transfer date/time to PLC
(in the S7 format DATE_AND_TIME)
An interval of at least 5 seconds must be maintained between two successive jobs to prevent
overload of the HMI device.
Parameter 1, 2, 3 -
41 Transfer date/time to PLC
(In OP/MP format)
An interval of at least 5 seconds must be maintained between successive jobs in order to prevent
overload of the HMI device.
Parameter 1, 2, 3 -
46 Update tags
Causes the HMI device to read the current value of the tagsfrom the PLC whose update ID
matches the value transferred in parameter 1.
(Function corresponds to the "UpdateTag" system function.)
Parameter 1 1 - 100
49 Delete alarm buffer
Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer.
Parameter 1, 2, 3 -
50 Delete alarm buffer
Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer.
Parameter 1, 2, 3 -
51 Screen selection
2)
Parameter 1 Screen number
Parameter 2 -
Parameter 3 Field number
69 Reading data record from PLC
1)
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2072 System Manual, 08/2011,
No
.
Function
14 Setting the time (BCD coded)
Parameter 3 0: Do not overwrite existing data record
1: Overwrite existing data record
70 Writing data record from PLC
1)
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Parameter 3 -
1)
Only devices supporting recipes
2)
OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if
the on-screen keyboard is active.
3)
The weekday is ignored on HMI device KTP 600 BASIC PN.
"Data record" area pointer
"Data record" area pointer
Function
When data records are transferred between the HMI device and PLC, both partners access
common communications areas on the PLC.
Data transfer types
There are two ways of transferring data records between the HMI device and PLC:
Transfer without synchronization
Transfer with synchronization over the data record
Data records are always transferred directly. That is, the tag values are read from an address
or written to an address configured for this tag directly, without redirecting the values by means
of interim memory.
Initiating the transfer of data records
There are three ways of triggering the transfer:
Operator input in the recipe view
Job mailboxes
The transfer of data records can also be triggered by the PLC.
Triggering by configured functions
If the transfer of data records is triggered by a configured function or by a job mailbox, the
recipe view on the HMI device remains operable. The data records are transferred in the
background.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2073
Simultaneous processing of several transfer requests is, however, not possible. In this case,
the HMI device rejects the other transfer requests with a system event.
Sequence of a transfer started by the operator in the recipe view
Reading from the PLC started by the operator in the recipe view
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe number to be read and the status
"Transferring" in the data record and sets the data record number to
0.
Abort with system
event.
3 The HMI device reads the values from the PLC and displays them in
the recipe view.
If the recipes have synchronized tags, the values from the PLC are
also written to the tags.
4 The HMI device sets the status "Transfer completed."
5 The control program must reset the status word to zero in order to
enable further transfers.
Writing to the PLC started by the operator in the recipe view
Step Action
Check: Status word = 0?
1 Yes No
The HMI device enters the recipe and data record number to be
written and the status "Transferring" in the data mailbox.
Abort with system
event.
2 The HMI device writes the current values to the PLC.
If the recipes have synchronized tags, the changed values are
synchronized in the recipe view and tags and then written to the PLC.
3 The HMI device sets the status "Transfer completed."
4 If required, the control program can now evaluate the transferred
data.
5 The control program must reset the status word to zero in order to
enable further transfers.
Note
The status word may only be set by the HMI device. The PLC may only reset the status word
to zero.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2074 System Manual, 08/2011,
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency is
detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Sequence of the transfer triggered by a job mailbox
The transfer of data records between the HMI device and the PLC can be initiated by the HMI
device or by the PLC.
The two job mailboxes No. 69 and No. 70 are available for this type of transfer.
No. 69: Read data record from PLC ("PLC DAT")
Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is
structured as follows:
Left byte (LB) Right byte (RB)
Word 1 0 69
Word 2 Recipe number (1-999)
Word 3 Data record number (1-65,535)
Word 4 Do not overwrite existing data record: 0
Overwrite existing data record: 1
No. 70: Write data record to PLC ("DAT PLC")
Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox
is structured as follows:
Left byte (LB) Right byte (RB)
Word 1 0 70
Word 2 Recipe number (1-999)
Word 3 Data record number (1-65,535)
Word 4
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified in
the job and the status "Transferring" in the data mailbox.
Abort without
return message.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2075
Step Action
3 The HMI device reads the values from the PLC and saves these to the
data record defined in the job mailbox.
4 If "Overwrite" was selected in the job, an existing data record is
overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "Do not overwrite" was selected in the job, and the data record
already exists, the HMI device aborts the job and enters 0000 1100
in the status word of the data mailbox.
5 The control program must reset the status word to zero in order to enable
further transfers.
Sequence of writing to the PLC using job mailbox "DAT PLC" (no. 70)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified in
the job and the status "Transferring" in the data mailbox.
Abort without
return message.
3 The HMI device fetches the values of the data record specified in the
job from the data medium and writes the values to the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order to enable
further transfers.
Sequence of the transfer when triggered by a configured function
Reading from the PLC using a configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
mailbox.
Abort with system
event.
3 The HMI device reads the values from the PLC and stores them
in the data record specified in the function.
4 If "Yes" was selected for the "Overwrite" function, an existing
data record is overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "No" was selected for the "Overwrite" function and the data
record already exists, the HMI device aborts the job and
enters 0000 1100 in the status word of the data mailbox.
5 The control program must reset the status word to zero in order
to enable further transfers.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2076 System Manual, 08/2011,
Writing to the PLC by means of configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
mailbox.
Abort with system
event.
3 The HMI device fetches the values of the data record specified
in the function from the data medium and transfers the values to
the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order
to enable further transfers.
Possible causes of error when transferring data records
Possible causes of faults
The section below shows possible causes of errors which lead to a data record transfer being
terminated with errors:
Tag address not set up on the PLC
Overwriting data records not possible
Recipe number does not exist
Data record number does not exist
Note
The status word may only be set by the HMI device. The PLC may only reset the status
word to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency
is detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2077
Reaction to an aborted transfer due to errors
If the transfer of data records is aborted due to errors, the HMI device reacts as follows:
Triggering by the operator in the recipe view
Information in the status bar of the recipe view and output of system events
Triggered by function
Output of system events
Triggering by job mailbox
No return message on the HMI device
You can nonetheless evaluate the status of the transfer by querying the status word in the data
mailbox.
Transfer without synchronization
If you select asynchronous transfer of data records between the HMI device and PLC, there
is no coordination over the common data areas. It is therefore unnecessary to set up a data
area during configuration.
Asynchronous data record transfer can be a useful alternative, for example, when:
The system is capable of excluding the risk of uncontrolled overwriting of data by the
communication peer.
The PLC does not require information about the recipe number and data record number.
The transfer of data records is triggered by the operator of the HMI device.
Reading values
When a read job is triggered, the values are read from the PLC addresses and transferred to
the HMI device.
Triggering by the operator in the recipe view:
The values are downloaded to the HMI device. You can then process, edit, or save these
values, for example.
Triggering by a function or job mailbox:
The values are saved immediately to the data volume.
Writing values
When a write job is triggered, the values are written to the PLC addresses.
Triggering by the operator in the recipe view:
The current values are written to the PLC.
Triggering by a function or job mailbox:
The current values are written to the PLC from the data medium.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2078 System Manual, 08/2011,
Transfer with synchronization
If you select synchronous transfer, both communication partners set status bits in the common
data area. You can use this mechanism to prevent uncontrolled overwriting of data in either
direction in your control program.
Application
Synchronous data record transfer can be a useful solution, for example, when:
The PLC is the "active partner" in the transfer of data records.
The PLC evaluates the information about the recipe number and data record number.
The transfer of data records is triggered by means of a Job mailbox.
Requirements
In order to synchronize transfer of data records between the HMI device and the PLC, the
following requirements must be met during configuration:
An area pointer has been set up: "Communication > Connections" editor in "Area pointer".
The PLC with which the HMI device synchronizes transfer of data records is specified in
the recipe:
"Recipes" editor in the Inspector window the "Coordinated transfer of data records" option
under "General > Synchronization > Settings".
Structure of the data area
The data area has a fixed length of 5 words. Structure of the data area:
15 0
1. Word Current recipe number (1 - 999)
2. Word Current data record number (0 - 65535)
3. Word Reserved
4. Word Status (0, 2, 4, 12)
5. Word Reserved
Status
The status word (word 4) can adopt the following values:
Value Meaning
Decimal Binary
0 0000 0000 Transfer permitted, data record free
2 0000 0010 Transferring
4 0000 0100 Transfer completed without error
12 0000 1100 Transfer completed with error
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2079
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
For additional information see:
Displaying tags with Runtime Advanced and Panels (Page 940)
Note
The value is read out time-triggered for Basic Panels.
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2080 System Manual, 08/2011,
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
The following picture shows the structure of a trend transfer area.
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Permitted data types for trends
For SIMATIC S7
You assign one bit to each trend during configuration. Tags and array tags of the "Word" or
"Int" data type are permitted.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2081
Alarms
Configuring alarms
Configure alarms
Several steps are needed to configure alarms, such as operational messages, error alarms,
and acknowledgement.
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Data types
For connections with a SIMATIC communication driver, the following data types are supported:
PLC Permitted data types
Discrete alarms Analog alarms
SIMATIC S7 PLCs WORD, INT BYTE, CHAR, WORD, INT, DWORD, DINT,
REAL, TIMER
How the bit positions are counted
For connections with a SIMATIC communication driver, the following counting method applies:
How the bit positions are
counted
Byte 0 Byte 1
Most significant byte Least significant byte
In SIMATIC S7
PLCs
7 0 7 0
In WinCC you configure: 15 8 7 0
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2082 System Manual, 08/2011,
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2083
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2084 System Manual, 08/2011,
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
9.11.7.5 Performance features of communication
Permitted data types for SIMATIC S7 200
Permitted data types for connections with SIMATIC S7 200
The table lists the data types that can be used when configuring tags and area pointers.
Data type Length
Bool 1 bit
Byte 1 byte
Char 1 byte
Word 2 bytes
Int 2 bytes
DWord 4 bytes
DInt 4 bytes
Real 4 bytes
StringChar --
Timer 2 bytes
Array --
Note
Disconnection with a PPI network
If you are using arrays in the configuration, an array size of approximately 1000 bytes may
cause an interruption of the connection.
Use smaller arrays in your configuration.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2085
9.11.8 Configuring direct keys
9.11.8.1 Direct keys
Introduction
In addition to their standard use, the F, K and S keys of an HMI device with key operation can
be used as direct keys.
With HMI devices with touch operation, you configure the system function "Direct key" to a
button
You can configure the following direct keys:
PROFINET connection: PROFINET IO direct keys
PROFIBUS connection: PROFIBUS DP direct keys
Operating mode of HMI devices with direct keys
Before accessing the PLC from the HMI device using the direct keys you have to change the
operating mode of the HMI device.
9.11.8.2 Changing the operating mode of the HMI device
Changing the operating mode for a PROFINET connection
Requirements
The HMI device is networked with a PLC via PROFINET.
Procedure
1. Click the PROFINET interface of the HMI device in the "Devices & Networks" editor.
2. Click "Operating mode" under "Properties > General" in the Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2086 System Manual, 08/2011,
3. Select the function "IO device" in the "Operating mode" area.
4. Select the PLC which is networked with the HMI device under "Assigned IO controller".
Changing the operating mode for a PROFIBUS connection
Requirements
The HMI device is networked with a PLC via PROFIBUS.
Procedure
1. Click the PROFIBUS interface of the HMI device in the "Devices & Networks" editor.
2. Click "Operating mode" under "Properties > General" in the Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2087
3. Select the function "DP slave" in the "Operating mode" area.
4. Select the PLC which is networked with the HMI device under "Assigned DP master".
9.11.8.3 Configuring direct keys
Configuring direct keys for an HMI device with key operation
Requirements
You have created an HMI device with key operation.
You have created an LED tag.
Procedure
1. Create a new screen.
2. Click an F-key of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2088 System Manual, 08/2011,
3. In the Inspector window, click "Properties > Properties > General".
4. Select a tag under "LED tag" in the "General > Settings" area.
5. Under "Bit" enter the correct bit number.
The correct bit number depends on the HMI device and the input and output assignments
on the HMI device.
Assignment of inputs and outputs
The exact assignment of inputs and outputs can be found under:
PROFINET IO direct keys: Assignment of inputs and outputs (Page 2095)
PROFIBUS DP direct keys: Assignment of inputs and outputs (Page 2110)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2089
Configuring direct keys for an HMI device with touch operation
Requirements
An HMI device with key operation has been created.
You have created an LED tag.
Procedure
1. Create a new screen.
2. Drag-and-drop a button from the "Tools" task card into the screen.
3. Click the button.
4. In the Inspector window, click "Properties > Events > Press".
5. Click "<Add function>".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2090 System Manual, 08/2011,
6. Select the "Direct key" system function.
7. Under "Bit" enter the correct bit number.
The correct bit number depends on the HMI device and the input and output assignments
on the HMI device.
Assignment of inputs and outputs
The exact assignment of inputs and outputs can be found under:
PROFINET IO direct keys: Assignment of inputs and outputs (Page 2095)
PROFIBUS DP direct keys: Assignment of inputs and outputs (Page 2110)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2091
9.11.8.4 PROFINET IO direct keys
PROFINET IO direct keys
PROFINET IO direct keys
You configure the HMI device created in WinCC as an active communication partner in the
automation network.
For the PROFINET IO direct keys, the HMI device can also be configured as a slave in the
PROFINET IO network.
The following figure shows the basic configuration based on an automation network with an
HMI device and a PLC.
HMl device
Active device
PROFlNET lO
direct keys
General
communication
PLC
PROFlNET lO
PROFlBUS DP Slave
Mode of operation of the PROFINET IO direct keys
The cycle time of the Ethernet bus can be set between 8 ms and 512 ms.
Thus, the reaction time of the PROFINET IO direct keys can also be determined. For a typical
configuration with a cycle time of 64 ms, the response time of the PROFINET IO direct keys
is < 100 ms.
A response time of < 100 ms to the CPU is usually ensured when using the PROFINET IO
direct keys. This time can be exceeded significantly in the following cases:
Complex functions run in the background, e.g. transmitting recipes, printing reports.
At the same time, multiple connections can be maintained to the CPU.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2092 System Manual, 08/2011,
HMI devices for the configuration of PROFINET IO direct keys
HMI devices
You can configure PROFINET IO direct keys with the following HMI devices:
HMI device class HMI device
Panel OP 177B PN/DP
OP 277 6"
TP 177B 4" PN/DP
TP 177B 6" PN/DP
TP 277 6"
Mobile Panel Mobile Panel 177 PN
Mobile Panel 277 8"
Mobile Panel 277 10"
Mobile Panel 277 IWLAN V2
Mobile Panel 277(F) IWLAN V2
Mobile Panel 277(F) IWLAN V2 (RFID tags)
Multi Panel Multi Panel 177 6" Touch
Multi Panel 277 Key
Multi Panel 277 Touch
Multi Panel 377 Key
Multi Panel 377 Touch
Comfort Panel KTP400 Comfort
KP400 Comfort
KP700 Comfort
TP700 Comfort
KP900 Comfort
TP900 Comfort
KP1200 Comfort
TP1200 Comfort
Restrictions for PROFINET IO direct keys
NOTICE
Direct keys are still active when the HMI device is in "offline" mode.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2093
NOTICE
If an external application such as Pocket Internet Explorer or Control Panel is started, it will
run in the foreground and Runtime is placed in the background. The bit for the function
"DirectKeyScreenNumber" is no longer set and the keys or buttons with the configured
function "DirectKey" no longer trigger the associated bit in the PLC.
Restrictions
It is not permitted to operate PROFIBUS IO direct keys and PROFINET DP direct keys
simultaneously.
Establish the following via the "PROFINET IO enabled" option in the control panel of the
HMI device:
Option disabled = PROFIBUS DP direct keys enabled
Option enabled = PROFINET IO direct keys enabled
If communication is enabled with PROFINET IO, you are not permitted to use the serial
interface.
You can operate direct keys only on local HMI devices. On the Sm@rtClient it is possible
to operate the key / button for the direct key. However, No bit is set in the I/O area of the
CPU.
Direct keys which are assigned to a button are only triggered through touch operation.
Triggering with a mouse click, for example with a connected USB mouse, is not possible.
With touch operation, direct keys are triggered independent of any configured password
protection.
The buttons used as direct keys on HMI devices with touch screen functionality may not
be modified as follows by means of scripting:
Moving
Resizing
Hiding
Disabling for operation.
The LEDs are addressed either via the PROFINET IO direct keys or the HMI Runtime
application. Avoid concurrent addressing via the PROFINET IO direct keys and the HMI
Runtime application. The LEDs "ACK", "A-Z l", "A-Z r" and "HELP" are reserved for system
functions and cannot be configured. It is not advisable to control the "ACK", "A-Z l", "A-Z r"
and "HELP" LEDs by means of PROFINET IO direct key functionality.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2094 System Manual, 08/2011,
Inputs and outputs of HMI devices
Assignment of inputs and outputs
Assigning the inputs/outputs
The keys or buttons of the device are assigning bytes in the input area. The LEDs are assigning
bytes in the output area. The number of bytes used depends on the HMI device.
The touch panels do not have any permanently assigned keys. They only have user-
configurable buttons. Via the "DirectKey system function you can assign a bit to a button in
the input area. The counting direction of the bit in the input direction is from right to left. In
contrast to the operator panels which have permanently assigned keys, the touch panel buttons
can be assigned freely.
Assigning direct keys to screen numbers (only for touch devices)
If a PROFINET IO direct key is using the same bit for different functions in different screens,
the SIMATIC PLC must differentiate between the respective functionality by means of the
screen number. You can use the "DirectKeyScreenNumber" system function to avoid the
delayed updating of the screen number following a screen change.
Using the "DirectKeyScreenNumber"system function you can set within the input area any
number of bits in order to identify the screen and simultaneously transfer the direct key bits to
the PLC. This ensures unambiguous allocation of a control bit to screen number at all times.
Panel
OP 177
OP 177B
Inputs Outputs
9 bytes 4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2095
7 6 5 4 3 2 1 0
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0
K2 K1 F14 F13 F12 F11 F10 F9
K8 K7 K6 K5 K4 K3 K10 K9
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
K8 K7 K6 K5 K4 K3 K10 K9
K2 K1
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0
K16 K15 K14 K13 K12 K11 K18 K17 K16 K15 K14 K13 K12 K11 K18 K17
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
T
o
u
c
h
b
u
t
t
o
n
s
LED
TP 177
TP 177B 4"
Inputs Outputs
5 bytes
Byte
Direct key assignment
Membrane keys
T
o
u
c
h
b
u
t
t
o
n
s
LED bits
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
F4 F3 F2 F1
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
TP 177B 6"
Inputs Outputs
4 bytes --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2096 System Manual, 08/2011,
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
OP 277
OP 277 6"
Inputs Outputs
4 bytes 4 bytes
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
7 6 5 4 3 2 1 0
CTRL SHlFT ACK ALT
K8 K7 K6 K5 K4 K3 K10 K9 K8 K7 K6 K5 K4 K3 K10 K9
K2 K1 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
K2 K1
F6 F5 F8 F7 F2 F1 F4 F3
ACK
Direct keys assignment
K
e
y
s
LED
HELP
A-Z
right
A-Z
left
Byte
TP 277
TP 277 6"
Inputs Outputs
4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2097
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel
Multi Panel 177
Multi Panel 177 6" Touch
Inputs Outputs
4 bytes -
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel 277
Multi Panel 277 8" Key
Inputs Outputs
5 bytes 5 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2098 System Manual, 08/2011,
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
7 6 5 4 3 2 1 0
CTRL SHlFT ACK ALT
K8 K7 K6 K5 K8 K7 K6 K5
K2 K1 F18 F17 K4 K3
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
K2 K1 K4 K3
F6 F5 F8 F7 F2 F1 F4 F3
F10 F9
ACK
Direct keys assignment
K
e
y
s
LED
HELP
A-Z
right
A-Z
left
Byte
Multi Panel 277 10" Key
Inputs Outputs
5 bytes 5 bytes
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
7 6 5 4 3 2 1 0
K14 K13 K16 K15 CTRL SHlFT ACK ALT K14 K13 K16 K15
K10 K9 K8 K7 K6 K5 K12 K11 K10 K9 K8 K7 K6 K5 K12 K11
K2 K1 F20 F19 F18 F17 K4 K3
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
K2 K1 K4 K3
F6 F5 F8 F7 F2 F1 F4 F3
F12 F11 F10 F9
ACK
Direct keys assignment
K
e
y
s
LED
HELP
A-Z
right
A-Z
left
Byte
Multi Panel 277 8" Touch
Inputs Outputs
5 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2099
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel 277 10" Touch
Inputs Outputs
5 bytes
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel 377
Multi Panel 377 Key
Inputs Outputs
5 bytes 5 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2100 System Manual, 08/2011,
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
7 6 5 4 3 2 1 0
F18 F17 F20 F19 CTRL SHlFT ACK ALT
F14 F13 F12 F11 F10 F9 F16 F15
F6 F5 F4 F3 F2 F1 F8 F7
S16 S15 S14 S13 S12 S11 S10 S9
S8 S7 S6 S5 S4 S3 S2 S1
F18 F17 F20 F19
F14 F13 F12 F11 F10 F9 F16 F15
F6 F5 F8 F7 F2 F1 F4 F3
S12 S11 S10 S9 S16 S15 S14 S13
S8 S7 S6 S5 S4 S3 S2 S1
ACK
Direct keys assignment
K
e
y
s
LED
lNFO
A-Z
right
A-Z
left
Byte
Multi Panel 377 Touch
Inputs Outputs
5 bytes
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Mobile Panel
Mobile Panel 177
Mobile Panel 177 PN
Inputs Outputs
9 bytes 2 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2101
T1
F8 F7 F6 F5 F4 F3 F2 F1
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
D5 D4 D3 D2 D1 D0 D7 D6
l5 l4 l3 l2 l1 l0 l7 l6
T1 S1 S0
F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
S0-S1: Key-operated switch
T1: llluminated pushbutton 1
l0-l7: Handwheel pulses (forwards)
D0-D7: Handwheel pulses (backwards)
Byte
T
o
u
c
h
b
u
t
t
o
n
s
o
p
t
i
o
n
a
l
o
p
e
r
a
t
o
r
c
o
n
t
r
o
l
s
M
e
m
b
r
a
n
e
k
e
y
s
LED-Bits Direct keys assignment
Mobile Panel 277
Mobile Panel 277 8"
HMI device Inputs Outputs
Mobile Panel 277 8" 10 bytes 4 bytes
T2 T1
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
D5 D4 D3 D2 D1 D0 D7 D6
l5 l4 l3 l2 l1 l0 l7 l6
T2 T1 S1 S0
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
n+9
S0-S1: Key-operated switch
T1: llluminated pushbutton 1
T2: llluminated pushbutton 2
l0-l7: Handwheel pulses (forwards)
D0-D7: Handwheel pulses (backwards)
Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
o
p
t
i
o
n
a
l
o
p
e
r
a
t
o
r
c
o
n
t
r
o
l
s
T
o
u
c
h
b
u
t
t
o
n
s
LED-Bits
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2102 System Manual, 08/2011,
Mobile Panel 277 10"
HMI device Inputs Outputs
Mobile Panel 277 10" 5 bytes --
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Mobile Panel 277 IWLAN V2
Mobile Panel 277 IWLAN V2
The assignment of the inputs and outputs of the PN direct keys applies to the following HMI
devices:
Mobile Panel 277 IWLAN V2
Mobile Panel 277F IWLAN V2
Mobile Panel 277 IWLAN V2 (RFID tags)
Inputs Outputs
10 bytes 4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2103
T2 T1
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
D5 D4 D3 D2 D1 D0 D7 D6
l5 l4 l3 l2 l1 l0 l7 l6
T2 T1 S1 S0
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
n+9
S0-S1: Key-operated switch
T1: llluminated pushbutton 1
T2: llluminated pushbutton 2
l0-l7: Handwheel pulses (forwards)
D0-D7: Handwheel pulses (backwards)
Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
o
p
t
i
o
n
a
l
o
p
e
r
a
t
o
r
c
o
n
t
r
o
l
s
T
o
u
c
h
b
u
t
t
o
n
s
LED-Bits
Comfort Panel
KTP400 Comfort
KTP400 Comfort
HMI device Inputs Outputs
Touch operation 4 bytes -
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
HMI device Inputs Outputs
Key operation 1 byte 1 byte
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2104 System Manual, 08/2011,
3 2 1 0
n+0
3 2 1 0
F4 F3 F2 F1 F2 F1 F4 F3
LED
Byte
Direct keys assignment:
K
e
y
s
KP400 Comfort
KP400 Comfort
Inputs Outputs
1 byte 1 byte
F8 F7 F6 F5
3 2 1 0
n+0 F4 F3 F2 F1
LED
Byte 7 6 5 4
F8 F7 F6 F5
3 2 1 0
F4 F3 F2 F1
7 6 5 4
Direct keys assignment:
K
e
y
s
KP700 Comfort
KP700 Comfort
Inputs Outputs
3 bytes 3 bytes
3 2 1 0
n+0 F8 F7 F6 F5 F4 F3 F2 F1
LED
Byte 7 6 5 4
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+1
n+2
3 2 1 0 7 6 5 4
F8 F7 F6 F5 F4 F3 F2 F1
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
Direct keys assignment:
K
e
y
s
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2105
TP700 Comfort
TP700 Comfort
Inputs Outputs
4 bytes --
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
KP900 Comfort
KP900 Comfort
Inputs Outputs
4 bytes 4 bytes
3 2 1 0
n+0 F8 F7 F6 F5 F4 F3 F2 F1
LED
Byte 7 6 5 4
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+1
n+2
3 2 1 0 7 6 5 4
F8 F7 F6 F5 F4 F3 F2 F1
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
F25 F26 n+3 F17 F18
Direct keys assignment:
K
e
y
s
TP900 Comfort
TP900 Comfort
Inputs Outputs
5 bytes --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2106 System Manual, 08/2011,
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
39 38 37 36 35 34 33 32 n+4
KP1200 Comfort
KP1200 Comfort
Inputs Outputs
5 bytes 5 bytes
3 2 1 0
n+0 F8 F7 F6 F5 F4 F3 F2 F1
LED
Byte 7 6 5 4
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+1
n+2
3 2 1 0 7 6 5 4
F8 F7 F6 F5 F4 F3 F2 F1
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+3 F25 F26 F27 F28 F29 F30 F31 F32
F33 F34
F25 F26 F27 F28 F29 F30 F31 F32
F33 F34 n+4
Direct keys assignment
K
e
y
s
TP1200 Comfort
TP700 Comfort
Inputs Outputs
5 bytes --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2107
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
39 38 37 36 35 34 33 32 n+4
9.11.8.5 PROFIBUS DP direct keys
PROFIBUS DP direct keys
PROFIBUS DP direct keys
You configure the HMI device created in WinCC as an active communication partner in the
automation network.
For the PROFIBUS DP direct keys, also configure the HMI device as a slave in the
PROFIBUS DP network.
The following figure shows the basic configuration based on an automation network with an
HMI device and a PLC.
HMl device
Active device
PROFlBUS DP
direct keys
General
communication
PLC
PROFlBUS DP
PROFlBUS DP Slave
Mode of operation of the PROFIBUS DP direct keys
With PROFIBUS DP direct keys, when the key or button is pressed, a bit is set in the I/O area
of the CPU.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2108 System Manual, 08/2011,
The cycle time of the PROFIBUS DP bus is calculated from the total of all configured inputs
and outputs.
The number of configured inputs and outputs can influence the reaction time of the
PROFIBUS DP direct key. For a typical configuration the response time of the PROFIBUS DP
direct key is < 100 ms.
HMI devices for the configuration of PROFIBUS DP direct keys
HMI devices
You can configure PROFINET IO direct keys with the following HMI devices:
HMI device class HMI device
Panel OP 77B
OP 177B
OP 277 6"
TP 177B 4"
TP 177B 6"
TP 277 6"
Mobile Panel Mobile Panel 177 DP
Mobile Panel 277 8"
Mobile Panel 277 10"
Multi Panel Multi Panel 177 6" Touch
Multi Panel 277 Key
Multi Panel 277 Touch
Multi Panel 377 Key
Multi Panel 377 Touch
Comfort Panel KTP400 Comfort
KP400 Comfort
KP700 Comfort
TP700 Comfort
KP900 Comfort
TP900 Comfort
KP1200 Comfort
TP1200 Comfort
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2109
Restrictions for PROFIBUS DP direct keys
NOTICE
If an external application such as Pocket Internet Explorer or Control Panel is started, it will
run in the foreground and Runtime is placed in the background. The bit for the function
"DirectKeyScreenNumber" is no longer set and the keys or buttons with the configured
function "DirectKey" no longer trigger the associated bit in the PLC.
Restrictions
It is not possible to operate PROFIBUS DP direct keys and PROFINET IO direct keys
simultaneously.
Establish the following via the "PROFINET IO enabled" option in the control panel of the
HMI device:
Option disabled = PROFIBUS DP direct keys enabled
Option enabled = PROFINET IO direct keys enabled
You can operate direct keys only on local HMI devices. On the Sm@rtClient it is possible
to operate the key / button for the direct key. However, No bit is set in the I/O area of the
CPU.
The buttons used as direct keys on HMI devices with touch screen functionality may not
be modified as follows by means of scripting:
Moving
Resizing
Hiding
Disabling for operation
The LEDs are addressed either via the PROFIBUS DP direct keys or the HMI Runtime
application. Avoid concurrent addressing via the PROFIBUS DP direct keys and the HMI
Runtime application. The LEDs "ACK", "A-Z l", "A-Z r" and "HELP" are reserved for system
functions and cannot be configured. We do not recommend addressing the LEDs "ACK",
"A-Z l", "A-Z r" and "HELP" with the PROFIBUS DP direct keys.
The PROFIBUS direct keys on an HMI device are triggered independent of any configured
password protection.
Inputs and outputs of HMI devices
Assignment of inputs and outputs
Assigning the inputs/outputs
The keys or buttons of the device are assigning bytes in the input area. The LEDs occupy
bytes in the DP output area. The following table shows the number of bytes used in the various
HMI devices. The precise assignment is shown in the following screens.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2110 System Manual, 08/2011,
The touch panels do not have any permanently assigned keys. They only have user-
configurable buttons. Via the direct keys function you can assign to a button a bit in the input
area. The counting direction of the bit in the input direction is from right to left. In contrast to
the operator panels which have permanently assigned keys, the touch panel buttons can be
assigned freely. For more detailed information, refer to the "WinCC flexible - Configuring
WinCC Windows-based Systems" user manual.
Assigning direct keys to screen numbers (only for touch devices)
If a PROFIBUS DP direct key is using the same bit for different functions in different screens,
the S7 must differentiate between the respective functionality by means of the screen number.
To combat the delayed updating of the screen number in the PLC after a change of screen
you use the "DirectKeyScreenNumber" screen function.
Using the "DirectKeyScreenNumber" you can set within the input area any number of bits in
order to identify the screen and simultaneously transfer the direct key bits to the PLC. This
ensures unambiguous allocation of a control bit to screen number at all times.
Panel
OP 77
OP 77B
Inputs Outputs
4 bytes 4 bytes
7 6 5 4 3 2 1 0
K4 K3 K2 K1
F4 F3 F2 F1
n+0
n+1
n+2
n+3
K4 K3 K2 K1
7 6 5 4 3 2 1 0 Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
LED
OP 177
OP 177B
Inputs Outputs
9 bytes 4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2111
7 6 5 4 3 2 1 0
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0
K2 K1 F14 F13 F12 F11 F10 F9
K8 K7 K6 K5 K4 K3 K10 K9
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
K8 K7 K6 K5 K4 K3 K10 K9
K2 K1
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0
K16 K15 K14 K13 K12 K11 K18 K17 K16 K15 K14 K13 K12 K11 K18 K17
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
T
o
u
c
h
b
u
t
t
o
n
s
LED
TP 177
TP 177B 4"
Inputs Outputs
5 bytes
Byte
Direct key assignment
Membrane keys
T
o
u
c
h
b
u
t
t
o
n
s
LED bits
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
F4 F3 F2 F1
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
TP 177B 6"
Inputs Outputs
4 bytes --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2112 System Manual, 08/2011,
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
OP 277
OP 277 6"
Inputs Outputs
4 bytes 4 bytes
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
7 6 5 4 3 2 1 0
CTRL SHlFT ACK ALT
K8 K7 K6 K5 K4 K3 K10 K9 K8 K7 K6 K5 K4 K3 K10 K9
K2 K1 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
K2 K1
F6 F5 F8 F7 F2 F1 F4 F3
ACK
Direct keys assignment
K
e
y
s
LED
HELP
A-Z
right
A-Z
left
Byte
TP 277
TP 277 6"
Inputs Outputs
4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2113
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel
Multi Panel 177
Multi Panel 177 6" Touch
Inputs Outputs
4 bytes -
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel 277
Multi Panel 277 8" Key
Inputs Outputs
5 bytes 5 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2114 System Manual, 08/2011,
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
7 6 5 4 3 2 1 0
CTRL SHlFT ACK ALT
K8 K7 K6 K5 K8 K7 K6 K5
K2 K1 F18 F17 K4 K3
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
K2 K1 K4 K3
F6 F5 F8 F7 F2 F1 F4 F3
F10 F9
ACK
Direct keys assignment
K
e
y
s
LED
HELP
A-Z
right
A-Z
left
Byte
Multi Panel 277 10" Key
Inputs Outputs
5 bytes 5 bytes
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
7 6 5 4 3 2 1 0
K14 K13 K16 K15 CTRL SHlFT ACK ALT K14 K13 K16 K15
K10 K9 K8 K7 K6 K5 K12 K11 K10 K9 K8 K7 K6 K5 K12 K11
K2 K1 F20 F19 F18 F17 K4 K3
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
K2 K1 K4 K3
F6 F5 F8 F7 F2 F1 F4 F3
F12 F11 F10 F9
ACK
Direct keys assignment
K
e
y
s
LED
HELP
A-Z
right
A-Z
left
Byte
Multi Panel 277 8" Touch
Inputs Outputs
5 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2115
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel 277 10" Touch
Inputs Outputs
5 bytes
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Multi Panel 377
Multi Panel 377 Key
Inputs Outputs
5 bytes 5 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2116 System Manual, 08/2011,
7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
7 6 5 4 3 2 1 0
F18 F17 F20 F19 CTRL SHlFT ACK ALT
F14 F13 F12 F11 F10 F9 F16 F15
F6 F5 F4 F3 F2 F1 F8 F7
S16 S15 S14 S13 S12 S11 S10 S9
S8 S7 S6 S5 S4 S3 S2 S1
F18 F17 F20 F19
F14 F13 F12 F11 F10 F9 F16 F15
F6 F5 F8 F7 F2 F1 F4 F3
S12 S11 S10 S9 S16 S15 S14 S13
S8 S7 S6 S5 S4 S3 S2 S1
ACK
Direct keys assignment
K
e
y
s
LED
lNFO
A-Z
right
A-Z
left
Byte
Multi Panel 377 Touch
Inputs Outputs
5 bytes
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Mobile Panel
Mobile Panel 177
Mobile Panel 177 DP
Inputs Outputs
9 bytes 4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2117
T1
F8 F7 F6 F5 F4 F3 F2 F1
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
D5 D4 D3 D2 D1 D0 D7 D6
l5 l4 l3 l2 l1 l0 l7 l6
T1 S1 S0
F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
S0-S1: Key-operated switch
T1: llluminated pushbutton 1
l0-l7: Handwheel pulses (forwards)
D0-D7: Handwheel pulses (backwards)
Byte
T
o
u
c
h
b
u
t
t
o
n
s
o
p
t
i
o
n
a
l
o
p
e
r
a
t
o
r
c
o
n
t
r
o
l
s
M
e
m
b
r
a
n
e
k
e
y
s
LED-Bits Direct keys assignment
Mobile Panel 277
Mobile Panel 277 8"
HMI device Inputs Outputs
Mobile Panel 277 8" 10 bytes 4 bytes
T2 T1
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
D5 D4 D3 D2 D1 D0 D7 D6
l5 l4 l3 l2 l1 l0 l7 l6
T2 T1 S1 S0
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
n+9
S0-S1: Key-operated switch
T1: llluminated pushbutton 1
T2: llluminated pushbutton 2
l0-l7: Handwheel pulses (forwards)
D0-D7: Handwheel pulses (backwards)
Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
o
p
t
i
o
n
a
l
o
p
e
r
a
t
o
r
c
o
n
t
r
o
l
s
T
o
u
c
h
b
u
t
t
o
n
s
LED-Bits
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2118 System Manual, 08/2011,
Mobile Panel 277 10"
HMI device Inputs Outputs
Mobile Panel 277 10" 5 bytes --
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
n+4
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
39 38 37 36 35 34 33 32
LED
No output area
Direct keys assignment
T
o
u
c
h
b
u
t
t
o
n
s
Byte
Mobile Panel 277 IWLAN V2
Mobile Panel 277 IWLAN V2
The assignment of the inputs and outputs of the PN direct keys applies to the following HMI
devices:
Mobile Panel 277 IWLAN V2
Mobile Panel 277F IWLAN V2
Mobile Panel 277 IWLAN V2 (RFID tags)
Inputs Outputs
10 bytes 4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2119
T2 T1
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16
15 14 13 12 11 10 9 8
7 6 5 4 3 2 1 0
D5 D4 D3 D2 D1 D0 D7 D6
l5 l4 l3 l2 l1 l0 l7 l6
T2 T1 S1 S0
F18 F17
F16 F15 F14 F13 F12 F11 F10 F9
F8 F7 F6 F5 F4 F3 F2 F1
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
n+0
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
n+9
S0-S1: Key-operated switch
T1: llluminated pushbutton 1
T2: llluminated pushbutton 2
l0-l7: Handwheel pulses (forwards)
D0-D7: Handwheel pulses (backwards)
Byte
Direct keys assignment
M
e
m
b
r
a
n
e
k
e
y
s
o
p
t
i
o
n
a
l
o
p
e
r
a
t
o
r
c
o
n
t
r
o
l
s
T
o
u
c
h
b
u
t
t
o
n
s
LED-Bits
Comfort Panel
KTP400 Comfort
KTP400 Comfort
HMI device Inputs Outputs
Touch operation 4 bytes -
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
HMI device Inputs Outputs
Key operation 1 byte 1 byte
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2120 System Manual, 08/2011,
3 2 1 0
n+0
3 2 1 0
F4 F3 F2 F1 F2 F1 F4 F3
LED
Byte
Direct keys assignment:
K
e
y
s
KP400 Comfort
KP400 Comfort
Inputs Outputs
1 byte 1 byte
F8 F7 F6 F5
3 2 1 0
n+0 F4 F3 F2 F1
LED
Byte 7 6 5 4
F8 F7 F6 F5
3 2 1 0
F4 F3 F2 F1
7 6 5 4
Direct keys assignment:
K
e
y
s
KP700 Comfort
KP700 Comfort
Inputs Outputs
3 bytes 3 bytes
3 2 1 0
n+0 F8 F7 F6 F5 F4 F3 F2 F1
LED
Byte 7 6 5 4
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+1
n+2
3 2 1 0 7 6 5 4
F8 F7 F6 F5 F4 F3 F2 F1
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
Direct keys assignment:
K
e
y
s
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2121
TP700 Comfort
TP700 Comfort
Inputs Outputs
4 bytes --
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
KP900 Comfort
KP900 Comfort
Inputs Outputs
4 bytes 4 bytes
3 2 1 0
n+0 F8 F7 F6 F5 F4 F3 F2 F1
LED
Byte 7 6 5 4
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+1
n+2
3 2 1 0 7 6 5 4
F8 F7 F6 F5 F4 F3 F2 F1
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
F25 F26 n+3 F17 F18
Direct keys assignment:
K
e
y
s
TP900 Comfort
TP900 Comfort
Inputs Outputs
5 bytes --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2122 System Manual, 08/2011,
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
39 38 37 36 35 34 33 32 n+4
KP1200 Comfort
KP1200 Comfort
Inputs Outputs
5 bytes 5 bytes
3 2 1 0
n+0 F8 F7 F6 F5 F4 F3 F2 F1
LED
Byte 7 6 5 4
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+1
n+2
3 2 1 0 7 6 5 4
F8 F7 F6 F5 F4 F3 F2 F1
F16 F15 F14 F13 F12 F11 F10 F9
F17 F18 F19 F20 F21 F22 F23 F24
n+3 F25 F26 F27 F28 F29 F30 F31 F32
F33 F34
F25 F26 F27 F28 F29 F30 F31 F32
F33 F34 n+4
Direct keys assignment
K
e
y
s
TP1200 Comfort
TP700 Comfort
Inputs Outputs
5 bytes --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2123
No output area
Direct keys assignment:
T
o
u
c
h
b
u
t
t
o
n
s
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0 n+0
n+1
n+2
n+3
15 14 13 12 11 10 9 8
23 22 21 20 19 18 17 16
31 30 29 28 27 26 25 24
LED
Byte
39 38 37 36 35 34 33 32 n+4
9.11.9 Communication via SIMATIC HMI HTTP
9.11.9.1 Basic information on SIMATIC HMI HTTP
Introduction
You use the SIMATIC HMI HTTP Protocol for data exchange between HMI devices.
The SIMATIC HMI HTTP Protocol is not suited for exchange of bulk data.
Data exchange occurs according to the Request-Response method. The HTTP client sends
its request to the HTTP server, which processes it and returns a response.
A device can be configured as an HTTP client and HTTP server simultaneously.
The client and server establish a connection via the Ethernet interface for data exchange.
HTTP server
Ethernet
PROFlBUS
HTTP client
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2124 System Manual, 08/2011,
HTTP components
The components of the SIMATIC HMI HTTP Protocol are transferred to the HMI device in
"Load to device".
HTTP components are:
HTTP server
HTTP client
If you use a Standard-PC or SIMATIC IPC, you must install WinCC RT Advanced or WinCC
RT Professional first.
SMTP protocol
The SMTP protocol is not a requirement for communication via SIMATIC HMI HTTP Protocol .
HTTP / HTTPS
TheSIMATIC HMI HTTP Protocol offers two standards:
HTTP
Is implemented in local networks for a fast, uncoded transfer of uncritical data.
HTTPS
Enables a reliable HTTP connection between devices. Initially there is an exchange of
secret keys. Then, in a further step, the respective public keys can be securely exchanged
in the form of digital certificates. The public keys are used to encode the utility data in order
to guarantee a bug-proof communication.
Note
Due to the encryption, the HTTPS protocol has a lower transmission performance than
the HTTP protocol.
CAUTION
End users are responsible for the security of their own networks.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2125
9.11.9.2 Configuring a connection via SIMATIC HMI HTTP
Configuring a connection via SIMATIC HMI HTTP
Communication between HMI devices via SIMATIC HMI HTTP protocol
Several steps are needed to configure communication between HMI devices via the SIMATIC
HMI HTTP protocol:
1. Configure HMI device as a server.
2. Configure HMI device as a client.
3. Assign tag parameters in the client.
4. Commission connection.
Access to tags via SIMATIC HMI HTTP protocol
If access to tags via the SIMATIC HMI HTTP protocol is to be enabled, these tags must be
defined for the relevant HMI devices and interconnected.
Configuring an HMI device as a server
Configuring a server
Requirements
The HTTP communication channel must be set in the Control Panel of the HMI device.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click "Runtime settings".
The "Runtime settings" editor opens.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2126 System Manual, 08/2011,
3. Click "Services".
4. Select the "HTTP channel server" option.
If you use the SMTP protocol, you assign the following values under "SMTP settings" according
to your project specifications:
Server name
Login
Password
Result
The HMI device has been configured as a server.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2127
Tags in the server
Tags used
The client can use the HTTP protocol for read and write access to tags configured on the server
in runtime. This means that it is not necessary to configure additional tags for an HTTP
communication.
However, the following aspects must be taken into account to ensure correct data exchange:
The data type of the server tags must match the data type in the client.
The tag name configured in the HTTP server must be identical to the name of the address
tag of the HTTP client.
Configuring an HMI device as a client
Configuring a client
Requirements
The HTTP communication channel must be set in the Control Panel of the HMI device.
An HMI device has been configured as a server.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
3. Double-click "<Add>" in the "Connections" editor.
4. In the "Communication drivers" column, select the "SIMATIC HMI HTTP Protocol" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
6. Set the parameters in the Property window.
See "Setting parameters for the client" for more information about the parameters.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2128 System Manual, 08/2011,
Setting parameters for the client
Requirements
Connection has been created via SIMATIC HMI HTTP protocol.
"Connections" editor is open.
Procedure
1. Select "Ethernet" in the Inspector window under "Parameters > Interface".
2. Select protocol http:// or https://.
3. Enter the name of the server or its IP address.
User name and password
If the "Authentication required" check box was selected in the server in the "Control Panel >
WinCC Internet Settings > Web Server" dialog, a user name and password must be entered
here in the client.
Timeout
Assign a time after which a connection break is recognized.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2129
HTTPS protocol
If the HTTPS protocol is selected, with the following settings you can establish how the HTTPS
client should check the properties of the server certificate and how it should react in the event
of error:
"Allow invalid computer names for certificates"
"Allow expired certificates"
"Allow certificates signed by unknown publishers"
Reading out an IP address
If the server has already been commissioned, you can read out the IP address on the server
as well:
For Panel
Click "Start > Programs > Command Prompt" on the server and enter the "ipconfig"
command using the screen keyboard. The IP address is displayed after pressing <Ret>.
For PC / Panel PC
Click "Start > Run" on the server, enter "Cmd", and press <Ret>: The command interpreter
is displayed. Enter the "ipconfig" command. The IP address is displayed after pressing
<Ret>.
Assigning tag parameters in the client
Assigning tag parameters in the client
Introduction
In order to be able to access tags on the server, they must be configured in the client as tag
addresses.
Requirements
Tags have been created in the "HMI tags" editor of the server.
Procedure
1. Double-click the client under "Devices" in the project tree.
2. Double-click "HMI tags".
3. Create a new tag.
4. Select a data type.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2130 System Manual, 08/2011,
5. Open the selection dialog in the "Addresses" column.
6. Define the parameters in the working area:
See "Parameters for the client tags" for more information about the parameters.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2131
Parameters for the tags of the client
Parameters for the tags
Data type
The client does not check the data type. Therefore, pay attention that the data type selected
here matches the data type of the tags on the server.
Array tags are not permitted.
Addressing
If the server and client are not within the same project, note the following:
Enter the exact name of the tag that is to be communicated with on the server.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2132 System Manual, 08/2011,
Commissioning a connection
Setting the server's Internet Settings
Introduction
To commission an HTTP/HTTPS connection, the WinCC Internet Settings must be set up in
the Control Panel of both the server and client, in addition to the configuration in WinCC.
The name and number of tabs contained in the "WinCC Internet Settings" dialog depend on
the software installed.
Only the required tabs with the MP 277 HMI device as an example are shown below.
WinCC Internet Settings, Proxy tab
The valid network settings are specified by the network administrator.
Make the following settings:
Internet settings for HMI devices with Windows CE
In this case, there are several options for calling the Control Panel:
In the startup phase, click on the "Control Panel" button in the Windows CE Loader
menu.
Select "Start > Settings > Control Panel" in the toolbar.
During normal operation, pressing the key combination <CTRL + ESC> opens the
toolbar. Start the Control Panel by selecting "Start > Settings > Control Panel".
Using the RT function "OpenControlPanel"
The language in the Windows CE based devices is always English.
WinCC Internet Settings, Web Server tab
Settings for using the integrated Web Server are made in this tab.
The "Web Server" tab is only available in the WinCC Internet Settings if the Web Server is
installed on the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2133
Tag authenticate
Controls authentication for tag access:
"No authentication": Authentication (user name password) is not required for access.
"Authentication required": Authentication (user name password) is required for access.
The user name and password for the client are specified during configuration.
Tag access
Controls access to tags:
"Read/write": Tags can be read and rewritten.
"Read only": Tags can only be read.
Group for defining operational performance
The following check boxes are not selected in conjunction with tag exchange via the HTTP/
HTTPS protocol:
Enable remote transfer (project)
Select this check box to enable an HTTP transfer from the configuration computer to
the HMI device.
Start automatically after booting
Specifies when the HTTP server should be started:
Enabled: The HTTP server starts immediately after the HMI device is booted,
irrespective of the runtime software
Disabled: The HTTP server starts at the same time as the runtime software.
Close with Runtime
Enabling this check box causes the HTTP server to be closed at the same time as the
runtime software.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2134 System Manual, 08/2011,
User Administration
This button opens the "UserDatabase-Edit" dialog box.
In the "User Manager" tab of this dialog box, you can select, delete, or create a new user.
The "Description" and "Authorizations" tabs always apply to the user currently selected.
(This example dialog box shows a user with the name 'Panel-1_HTTP-Server'.)
User Manager
"Administrator" is the default user name, and "100" is the default password setting. If a user
name and password have been entered for the HTTP server under "Connections" in your
WinCC project, the same user name and password must be specified on the server.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2135
Description
Enables input of a user description.
Authorizations
The newly set up user must be assigned the authorizations for "RT Communication on the
"Authorizations" tab control.
Establishing an HTTP connection
Introduction
To establish an HTTP connection, you must perform the following actions:
In the "Connections" editor of WinCC flexible ES, configure the connection as an "https://"
protocol type and define how the HTTPS client should verify the properties of the server
certificate and respond to errors.
Install a valid certificate on the HTTPS client.
Certificates are necessary for server authentication. Using certificates you can ensure that
the server with which the connection is to be developed is actually the server for which it
is outputting.
Principle of an HTTPS connection
After runtime start, the HTTPS client establishes a connection to the HTTPS server. The
HTTPS server presents its certificate, which the client verifies for authenticity. The session
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2136 System Manual, 08/2011,
code that can only be read by the HTTPS server is then transmitted. The session code is now
available on both sides and enables a symmetrical data encryption.
Note
The certificate contains the current time. The current time can lead to problems if the time
zones of the server and client are different. For example, a certificate generated on a server
with an Asian time zone only becomes valid on a client with European time zone in the future
(8 hours).
Preparation for installing a certificate on the client
With the first HTTPS client access, the HTTPS server generates the certificate itself and then
saves it in the "Cert.cer" memory. The file is stored in the following directory:
On a PC / Panel PC (with Windows XP) in the directory "..\\Siemens\Automation\WinCC
Runitme Advanced\SystemRoot\SSL"
On Windows CE-based devices in the directory "Flash\Simatic\SystemRoot\SSL"
The certificate must be stored on the HTTPS client on a storage medium from which it can
be launched with a double click.
Server Client Possible file transfer
with Windows XP
(PC, Panel PC)
with Windows XP
(PC, Panel PC)
Disk
USB stick
LAN (Ethernet)
Internet Explorer (via TCP/IP, if
Service is already running)
with Windows CE
(xP 270, xP 277, MP 370,
MP 377, xP 177B,
Mobile Panel 177 PN,
Mobile Panel 277)
with Windows XP
(PC, Panel PC)
Memory card
ActiveSync (serial)
with Windows XP
(PC, Panel PC)
with Windows CE
(xP 270, xP 277, MP 370,
MP 377, xP 177B,
Mobile Panel 177 PN,
Mobile Panel 277)
with Windows CE
(xP 270, xP 277, MP 370,
MP 377, xP 177B,
Mobile Panel 177 PN,
Mobile Panel 277)
with Windows CE
(xP 270, xP 277, MP 370,
MP 377, xP 177B,
Mobile Panel 177 PN,
Mobile Panel 277)
Memory card
Installing a certificate on a client with Windows XP
Insert the storage medium on which you have saved the "Cert.cer" file into the HTTPS client
or open the directory in which the file is located. Double click on the file and follow the
instructions in the Windows dialog.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2137
Tip: The Internet Explorer provides an easy way to install a certificate. Connect to this device
via HTTPS (e.g.: https://<my device>). The browser establishes if a certificate has not yet been
imported. In this case, the browser asks if you want to install the certificate. Any errors in the
certificate will be displayed.
Installing a certificate on a client with Windows CE
Insert the memory card on which you have saved the converted "Cert.cer" file into the HTTPS
client. WinCC flexible provides the "InstallCert.exe" tool for importing certificates using
Windows CE.
You can implement the installation as follows:
In Explorer:
Double click the "Cert.cer" file to install the certificate.
In the command prompt:
Enter "InstallCert /[command parameter] [filename]".
command parameters:
Parameter /r must be specified because the certificate used in WinCC flexible Runtime
is a root certificate.
A root certificate is the main certificate and is used to verify the authenticity of all other
certificates transferred.
filename
You must specify the certificate file with its complete path (e.g. "\Storage Card\Cert.cer")
A status alarm is output when you completed the installation. Runtime has to be restarted after
the installation of a certificate on Windows CE- HMI devices with HTTPS clients. It is necessary
to restart Runtime so that an HTTPS connection can be established.
The file "Cert.cer" cannot be opened.
The "Cert.cer" file generated at the HTTPS server cannot be opened on HMI devices based
on Windows CE 5.0 by double-clicking the client.
1. Open the Control Panel.
2. Select "Certificates > My Certificates."
3. Click the "Import" button.
A dialog box opens.
4. Select the "From a File" menu in the file browser and select the "Cert.cer" file.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2138 System Manual, 08/2011,
9.11.9.3 Performance features of communication
Permitted data types
Permitted data types
When configuring tags, the data types listed below can be used.
Data type in the
SIMATIC HMI
HTTP protocol
Length Sign Range of values
Bool 0 No true (-1) or false (0)
SInt 1 Byte Yes -128 to 127
USint 1 Byte No 0 to 255
Int 2 Byte Yes -32768 to 32767
UInt 2 Byte No 0 to 65535
DInt 4 Byte Yes -2,147,483,648 to 2,147,483,647
UDInt 4 Byte No 0 to 4,294,967,295
Real 4 Byte Yes -3.402823E38 to -1.401298E-45 for negative values and
1.401298E-45 to 3.402823E38 for positive values
LReal 8 Byte Yes -1.79769313486231E308 to
-4.94065645841247E-324 for negative values and
4.94065645841247E-324 to 1.79769313486232E308 for positive
values
String 1 to
255 byte
DateTime 8 Byte 1.1.1970 00:00:00 up to 31.12.2037 23:59:59
Note
Data types for third-party PLCs
Data types in third-party PLCs may differ from those in WinCC.
Note the the tag definition of the third-party PLC for the correct assignment.
Note
It is not possible to access array tags from an HTTP client.
Multiplex tags are not supported by the HTTP protocol. If you need a multiplex tag, you must
configure it on the HTTP client. You will have to create the tags for the multiplex list on the
server and the client and then connect them. You will then add these tags to the multiplex
list on the client.
Address multiplex tags are not supported by the HTTP protocol.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2139
9.11.10 Communication via OPC
9.11.10.1 Communication via OPC
Introduction
This section describes the communication between an HMI device and a device via OPC.
In this case, the HMI device is the OPC client and the device is the OPC server.
For more detailed information on OPC and on configuring OPC servers, refer to Section
"OPC (Page 2651)".
9.11.10.2 Configuring a connection via OPC
Introduction
You configure a connection to a device via OPC in the "Connections" editor of the HMI device.
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
3. Double-click "<Add>" in the "Connections" editor.
4. In the "Communication drivers" column, select the "OPC" driver.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2140 System Manual, 08/2011,
5. Select the "OPC" interface for the HMI device under "Parameters > Interface".
6. Select an OPC server from the tree view under "Parameters > OPC servers".
The OPC server is entered in the "Name of OPC server" field.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2141
9.11.10.3 Performance features of communication
Permitted data types for OPC DA
Permitted data types for connections with OPC DA
The table lists the user data types that can be used when configuring tags.
Data type Length
VT_BOOL 1-bit
VT_I1 1 byte
VT_UI1 1 bytes
VT_I2 2 bytes
VT_UI2 2 bytes
VT_I4 4 bytes
VT_UI4 4 bytes
VT_R4 4 bytes
VT_R8 8 bytes
VT_BSTR --
VT_DATE 8 bytes
VT_DATE|VT_ARRAY --
VT_I1|VT_ARRAY --
VT_UI1|VT_ARRAY --
VT_I2|VT_ARRAY --
VT_UI2|VT_ARRAY --
VT_I4|VT_ARRAY --
VT_UI4|VT_ARRAY --
VT_R4|VT_ARRAY --
VT_R8|VT_ARRAY --
Permitted data types for OPC XML DA
Permitted data types for connections with OPC DA XML
The table lists the user data types that can be used when configuring tags.
Data type Length
boolean 1-bit
byte 1 byte
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2142 System Manual, 08/2011,
Data type Length
unsignedByte 1 byte
short 2 bytes
unsignedShort 2 bytes
int 4 bytes
unsignedInt 4 bytes
float 4 bytes
double 8 bytes
string --
dateTime --
time --
date --
Permitted data types for OPC UA
Permitted data types for connections with OPC UA
The table lists the user data types that can be used when configuring tags.
Data type Length
Boolean 1-bit
SByte 1 byte
Byte 1 byte
Int16 2 bytes
UInt16 2 bytes
Int32 4 bytes
UInt32 4 bytes
Float 4 bytes
Double 8 bytes
String --
DateTime --
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2143
9.11.11 Communication via routing
9.11.11.1 Communication via routing
Introduction
If all stations in an automation system are not connected to the same subnet, these stations
cannot be accessed directly online.
A connection between partners in different subnets is only possible via routing.
You configure the routing settings with the properties of the interfaces.
Communication from connection partners in various different subnets can be routed via the
following links:
PROFINET
PROFIBUS
MPI
Requirements for routing
To establish a connection to these devices, a router must be interposed. In this case, a
SIMATIC station can also act as a router if it has appropriate interfaces with the different
subnets.
Modules with communication capability (CPUs or CPs) used to establish gateways between
the subnetworks must have routing capability.
A connection between partners in different subnets is only possible with IP routing. The routing
settings can be edited in the corresponding interface properties.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2144 System Manual, 08/2011,
Routing path
The routing path is determined in Runtime by the system and cannot be influenced by the user.
During configuration, it is not possible to generate information about a faulty connection.
HMI devices as routers
Only SIMATIC PCs or PC stations can be used as a router.
All other HMI devices from the "HMI" area cannot be used as a router.
9.11.11.2 Example for communication via routing
Communication via routing
Illustration of a hardware configuration with a routing connection
In the figure above, a routing connection has been established between an HMI device and
the SIMATIC S7-300 controller.
The SIMATIC S7-400 automation device serves as a router.
A routing connection can be made directly in integrated projects. The communication partners
are connected in the "Devices and Networks" editor.
You configure the parameters of the connection and interface in the Inspector window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2145
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2146 System Manual, 08/2011,
9.11.11.3 Configuring communication via routing
Introduction
The following configuration describes a network for the following communication partners:
KTP1000 Basic PN
SIMATIC S7-400 with PROFINET and PROFIBUS interface
SIMATIC S7-300 with PROFIBUS interface
Requirements
KTP1000 Basic PN is connected via PROFINET to the SIMATIC S7-400.
SIMATIC S7-400 is connected via PROFIBUS to the SIMATIC S7-300.
Procedure
1. Click on the PROFINET interface of the HMI device.
2. In the Inspector window, click "Properties > General > Ethernet addresses".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2147
3. Click "Use router" in the "IP protocol" area.
4. Enter the IP address of the router in the "Router address" field.
9.11.12 Communication with other PLCs
9.11.12.1 Communication with other PLCs
Introduction
Communication with other PLCs is communication with PLCs that are not in the SIMATIC
family.
These PLCs have proprietary protocols for data exchange. The protocols are configured as
communication drivers in WinCC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2148 System Manual, 08/2011,
Communication drivers
The following communication drivers are supported in WinCC and are already installed:
Allen-Bradley
Allen-Bradley EtherNet/IP
Allen-Bradley DF1
Mitsubishi
Mitsubishi MC TCP/IP
Mitsubishi FX
Modicon Modbus
Modicon Modbus TCP/IP
Modicon Modbus RTU
Omron
Omron Host Link
Communication drivers in WinCC RT Professional
The following communication drivers are supported for RT Professional:
Allen-Bradley
Allen-Bradley EtherNet/IP
Mitsubishi
Mitsubishi MC TCP/IP
Modicon Modbus
Modicon Modbus TCP
Connections between HMI devices and other PLCs
You configure the connections between HMI devices and other PLCs in the "Connections"
editor of the HMI device. These connections are non-integrated connections.
9.11.12.2 Distinctive features when configuring
Distinctive features for data exchange
Distinctive features apply when configuring connections to other PLCs, compared to
configuring integrated connections.
Note the following distinctive features when configuring:
Addressing of tags
Permitted data types
Distinctive features when configuring area pointers
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2149
Distinctive features when configuring alarms
Distinctive features when configuring trends
For more detailed information on distinctive features when configuring, refer to Section "Data
exchange" of the respective communication driver.
9.11.12.3 Parallel communication
Parallel communication of communication drivers
The following table shows an overview of which communication drivers you can use
simultaneously on one HMI device.
Note
Parallel communication is not approved for Basic Panels.
Parallel communication over Ethernet interfaces
The approved combinations can be operated via the same Ethernet interface. Several Ethernet
interfaces are not required.
Parallel communication only concerns the Ethernet-based communication drivers.
Allen-
Bradley
EtherNet/
IP
Mitsubishi
MC TCP/
IP
Modicon
Modbus
TCPIP
OPC (DA/
XML DA)
OPC UA
(DA)
SIMATIC
S7 300/40
0
SIMATIC
S7 1200
SIMATIC
HTTP
protocol
Sinumerik
NC
Allen-
Bradley
EtherNet/
IP
-- No No Yes Yes Yes Yes Yes Yes
Mitsubishi
MC TCP/
IP
No -- No Yes Yes No No Yes No
Modicon
Modbus
TCPIP
No No -- Yes Yes No No Yes No
OPC (DA/
XML DA)
Yes Yes Yes -- Yes Yes Yes Yes Yes
OPC UA
(DA)
Yes Yes Yes Yes -- Yes Yes Yes Yes
SIMATIC
S7 300/40
0
Yes No No Yes Yes -- Yes Yes Yes
SIMATIC
S7 1200
Yes No No Yes Yes Yes -- Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2150 System Manual, 08/2011,
SIMATIC
HTTP
protocol
Yes Yes Yes Yes Yes Yes Yes -- Yes
Sinumerik
NC
Yes No No Yes Yes Yes Yes Yes --
Parallel communication over serial interfaces
The following applies for parallel communication over serial interfaces:
One communication driver per interface.
One interface per communication driver.
9.11.12.4 Communication drivers
Allen-Bradley
Allen-Bradley communication drivers
Introduction
This section describes the communication between an HMI device and PLCs that use Allen-
Bradley communication drivers.
The following communication drivers are supported:
Allen-Bradley EtherNet/IP
Allen-Bradley DF1
Data exchange
Data is exchanged by means of tags or area pointers.
Tags
The PLC and the HMI device use process values for data exchange. You create tags in
the configuration that point to addresses in the PLC. The HMI device reads the value from
the defined address, and then displays it. The operator may also enter values on the HMI
device, which are then written to the address in the PLC.
Area pointers
Area pointers are used to exchange specific data and are only set up when these data are
used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2151
Allen-Bradley EtherNet/IP
Configuring a connection via Allen-Bradley EtherNet/IP
Introduction
You configure a connection to a PLC with an Allen-Bradley EtherNet/IP communication driver
in the "Connections" editor of the HMI device.
The Ethernet interfaces are named differently depending on the HMI device.
Example: PROFINET interface corresponds to the Ethernet interface
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2152 System Manual, 08/2011,
4. In the "Communication drivers" column, select the "Allen-Bradley EtherNet/IP" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
Parameters for the connection (Allen-Bradley EtherNet/IP)
Parameters to be set
To assign the connection parameters, such as addresses and profiles, click the connection
that you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "PLC" area is available for assigning parameters according to the interface
used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2153
Parameters for the HMI device
You can select only one interface for the HMI device in the Inspector window under
"Parameters". Depending on the HMI device, there are several interfaces available.
If you are directly connected to the HMI device during configuration, you can set up the IP
address of the HMI device in WinCC. The IP address is transferred to the HMI device upon
subsequent loading.
Note
The IP address in the control panel will be overwritten upon subsequent loading if you have
already set up the IP address in the HMI device control panel.
The IP address already set up in the control panel will be retained upon subsequent loading
if you activate "Set IP address using a different method".
To set up the IP address of the HMI device:
1. Click on the HMI device.
2. Open the "Device configuration" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2154 System Manual, 08/2011,
3. Click the Ethernet interface.
4. Assign the IP address in the inspector window under:
"General > PROFINET interface > Ethernet addresses"
Parameters for the PLC
CPU type
For "CPU type", set the CPU type of the PLC used.
IP address
Set the IP address or host name of the Ethernet/IP module of the PLC. Only the IP address
can be used on a Basic Panel.
Communication path
Set the CIP path from the Ethernet module to the PLC. This establishes a logical connection
between the Ethernet module and PLC, even if both devices are located in different CIP
networks.
For additional information see: Examples: Communication path
Connecting HMI device to PLC
Connections via Allen-Bradley EtherNet/IP
Connection
The HMI device can be connected to the Allen-Bradley PLC using the following components:
Existing Ethernet network that also contains the PLCs
Cross-over Ethernet cable connected directly to the Ethernet interface of the CPU or the
communication module
The connection of the HMI device to an Allen-Bradley PLC is limited primarily to the physical
connection of the HMI device. Special blocks for the connection are not required in the PLC.
Communication types
Approved communication types with Allen-Bradley EtherNet/IP
The following communication types are system-tested and approved:
Point-to-point connection to the approved PLCs
Multipoint connection from a HMI device (Allen-Bradley Ethernet/IP-Client) with up to 4
PLCs with the respectively approved PLCs. CPU types can be mixed.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2155
Connection
Connection with the following PLCs is approved with Allen-Bradley EtherNet/IP:
CPU type: "ControlLogix, Compact Logix"
ControlLogix
556x(1756-L6x) with Ethernet module 1756-ENBT
Guard Logix-System ControlLogix
556xS(1756-L6xS) with Ethernet module 1756-ENBT
CompactLogix
533xE(1769-L3xE) with Ethernet interface onboard
532xE(1769-L2xE) with Ethernet interface onboard
534x (1768-L4x) with Ethernet module 1768-ENBT
CPU type: "SLC, MicroLogix"
MicroLogix 1100 (with Ethernet interface onboard)
MicroLogix 1400 (with Ethernet interface onboard)
SLC 5/05 (with Ethernet interface onboard)
Performance features of communication
Permitted data types for Allen-Bradley EtherNet/IP
Permitted data types
The table lists the data types that can be used when configuring tags and area pointers.
CPU type: ControlLogix, CompactLogix
Data type Length
Bool 1 bit
DInt 4 bytes
Int 2 bytes
Real 4 bytes
SInt 1 byte
String 1 to 80 characters
UDInt 4 bytes
UInt 2 bytes
USInt 1 byte
Permitted data types arrays
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2156 System Manual, 08/2011,
Address Permitted data types
Array SInt, USInt, Int, UInt, DInt, UDInt, Real
Individual bits from the basic data types of
the PLC SInt, USInt, Int, UInt, DInt, UDInt
Bool*
* Any changed value of certain defined bits is written back to the PLC. There is no check to
determine whether any other bits have changed. The PLC (or other PLCs) may only read
access the value.
CPU type: SLC, MicroLogix
Data type Operand type Length
ASCII A 0 to 80 characters
Bool N, R, C, T, B, S, I, O 1 bit
DInt N 4 bytes
Int N, R, C, T, S 2 bytes
Real N, F 4 bytes
String ST 1 to 80 characters
UDInt N 4 bytes
UInt N, R, C, T, B, I, O 2 bytes
Note
Strings in RSLogix 5000 have a default length of 82 characters. A maximum of 80 characters
can be displayed in WinCC. Always use strings which do not exceed the maximum length of
80 characters.
Permitted data types - arrays
Address Permitted data types
Array Int, UInt, DInt, UDInt, Real
Distinctive features for connections with Allen-Bradley Ethernet/IP
With the communication driver Allen Bradley Ethernet/IP and the CPU type SLC, MicroLogix,
you can only use array tags for discrete alarms and trends.
Note
I/O modules with 8 or 16 ports occupy one data word on the PLC.
I/O modules with 24 or 32 ports occupy two data words.
The HMI device does not output an error message if using non-existent bits.
You should always make sure that I/O modules with 8 or 24 ports only occupy the bits that
are actually assigned to a port.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2157
Supported CPU types for Allen-Bradley EtherNet/IP
CPU types
The following CPU types are supported for configuring the Allen-Bradley EtherNet/IP
communication driver.
CompactLogix
1769-L2xE with Ethernet interface onboard
1769-L3xE with Ethernet interface onboard
1768-L4x with Ethernet module 1768-ENBT
ControlLogix
1756-L6x with Ethernet module 1756-ENBT
GuardLogix
1756-L61S with Ethernet module 1756-ENBT
1756-L62S with Ethernet module 1756-ENBT
1756-L63S with Ethernet module 1756-ENBT
MicroLogix
MicroLogix 1100 / 1400
SLC50x
SLC5/05
Addressing in the C.Logix CPU type
Addressing
Addressing
A tag is uniquely referenced in WinCC by means of an address in the PLC. The address must
correspond with the tag name in the PLC. The tag address is defined by a string with a length
of up to 128 characters.
Using characters for addressing
Valid characters for tag addressing:
Letters (a to z, A to Z)
Numbers (0 to 9)
Underscore ( _ )
The tag address consists of tag name and other character strings used to specify the tag in
the PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2158 System Manual, 08/2011,
Tag name properties:
The tag name may begin but not end with an underscore character.
Strings with successive underscore and space characters are invalid.
The address may not exceed a length of 128 characters.
Note
The characters reserved for tag addressing may not be used in program/tag names or at
any other address instance.
The reserved characters are listed below:
Reserved character Function
. Element delimiter
: Definition of a program tag
, Delimiter for addressing multi-dimensional arrays
/ Reserved for bit addressing.
[ ] Addressing of array elements or arrays
PLC and program tags
The Allen-Bradley EtherNet/IP communication driver supports addressing of PLC tags (global
project tags) and/or program tags (global program tags).
A program tag is declared based on the program name in the PLC and actual tag name which
are delimited by colon. PLC tags are simply addressed by their name.
NOTICE
Addressing errors
Addressing errors occur when the tag name and data type are inconsistent.
Note that the tag name defined in the address field in WinCC must match the tag name in
the PLC. Make sure that the data types of tags in WinCC match the data types in the PLC.
Note
Module-specific tags, e.g. for data on input and output modules, cannot be addressed directly.
Instead, use an alias tag in the PLC.
Example: Local:3:O. Data cannot be addressed in WinCC flexible.
If the alias "MyOut" is defined for Local:3:O in the PLC, you can address with WinCC via
MyOut.Data.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2159
Addressing syntax
Notation of addresses
The tables below define the notation for the individual addressing options for Allen-Bradley
EtherNet/IP.
Table 9-24 Access to arrays, basic data types and structure elements
Data types Type Address
Basic data types PLC tag Tag name
Program tag Programname:tagname
Arrays PLC tag Array tag
Program tag Program name: array tag
Bits PLC tag Tagname/bitnumber
Program tag Programname:tagname/bitnumber
Structure elements PLC tag Structure tag. Structure element
Program tag Program name: structure tag. structure element
Note
Bit addressing with the data types Bool, Real and String is not permitted and will cause an
addressing fault.
Description of the syntax
Syntax description:
(Programname:)tagname([x(,y)(,z)]){.tagname([x(,y)(,z)])}(/
bitnumber)
The "( )" defines an optional, single instance of an expression.
The "{ }" defines an optional expression with multiple single instances.
The address string length may not exceed 128 characters.
Addressing types
Arrays
An array is a data structure that includes a number of data of the same type. WinCC only
supports one-dimensional arrays.
In the address column of the tag editor, enter the array name possibly by specifying a start
element. The length is defined in the Array Elements input box of the tag editor. If array limits
in the PLC are exceeded (due to faulty indexing), addressing errors result.
These arrays must be declared in the PLC as controller or program tags.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2160 System Manual, 08/2011,
Two- or three-dimensional arrays in the PLC can only be addressed in WinCC if these can be
mapped area-wise onto one-dimensional arrays .
Note
During all read accesses and all write accesses, all array elements of a tag are always read
or written, respectively. The contents of an array tag which is interconnected with a PLC are
always transferred whenever there is a change. The HMI device and the PLC cannot
concurrently write data to the same array tag for this reason. Instead of writing data only to
a single element, the program writes the entire array to the PLC.
Array elements
Elements of one-dimensional, two-dimensional and three-dimensional arrays in the PLC are
indexed by setting an index and the corresponding notation in the tag editor. Array addressing
starts at element "0", with arrays of all basic types being valid for element addressing. Read/
write operations are only carried out at the addressed element, and not for the entire array.
Bits and bit tags
Bit access is allowed to all basic data types with the exception of Bool, Real and String. Bit
addressing is also allowed at array/structure elements. The Bool data type is set in WinCC
when bits and bit tags in the basic data types are addressed.
Single-digit bit numbers are addressed with "/x" or "/0x" (x = bit number). Bit numbers are
defined by up to two digits.
Note
With the "Bool" data type in the data types SInt, Int and DInt, after changing the specified bit
the complete tag is then written in the PLC again. In the meantime, no check is made as to
whether other bits in the tag have since changed. Therefore, the PLC may have only read
access to the specified tag.
Structures
User-defined data types are created by means of structures. These structures group tags of
different data types. Structures may consist of basic types, arrays and of other structures. In
WinCC, only structure elements are addressed and not entire structures.
Structure elements
Structure elements are addressed by means of the name of the structure and of the required
structure element. This addressing is separated by point. In addition to basic data types, the
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2161
structure elements may represent arrays or other structures. Only one-dimensional arrays may
be used as a structure element.
Note
The nesting depth of structures is only limited by the maximum length of 128 characters for
the address.
Address multiplexing
Address multiplexing
Address multiplexing is possible with the CompactLogix, ControlLogix CPU type.
Address multiplexing requires two tags:
"Tag_1" of data type "String"; contains a logical address such as "HMI:Robot5.Block5" as
value.
The value may change to a second valid address, for example, "HMI:Robot4.Block3".
"Tag_2" is a tag in which the "Allen-Bradley EtherNet/IP" communication driver is set up as
a connection.
Enter a valid name of an HMI_tag in square brackets as the address.
e.g.: "[Tag_1]"
The tag must be of the String data type.
The square brackets indicate address multiplexing.
The address is derived from the actual value in "Tag_1".
Note
You can only multiplex entire Allen-Bradley EtherNet/IP addresses. Multiplexing of
address elements is not possible. "HMI:Robot[Tag_1].Block5" is an invalid address.
You can optionally click the arrow right icon in the "Address" column. Replace the
"Constant" with the "Multiplex" entry by clicking the arrow on the left edge of the next
address dialog box. Now the tag selection list only returns tags of data type "String".
You can also configure a function triggered by a "change of value" event for multiplexed
tags.
Examples for addressing
Example of a table for addressing
The table below defines the basic variants for addressing PLC tags. Other addressing variants
are possible by means of combination.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2162 System Manual, 08/2011,
Type Type Address
General PLC tag Tag name
Program tag Program:tagname
Array Access to an element of a 2-
dimensional array
Arraytag[Dim1,Dim2]
Element of structure array (1-
dimensional)
Arraytag[Dim1].structureelement
Bit in element basic type
array (2-dimensional)
Arraytag[Dim1,Dim2]/Bit
Structure Array in structure Structuretag.arraytag
Bit in the element of an array
in the substructure
Structuretag.structure2.arraytag [element]/
bit
Note
Program tags are addressed by leading the address with the program name derived from the
PLC with colon delimiter.
Example: Programname:arraytag[Dim1,Dim2]
Access to array elements
Type Address
PLC tag Arraytag[Dim1]
Arraytag[Dim1,Dim2]
Arraytag[Dim1,Dim2,Dim3]
Program tag Programname:arraytag[Dim1]
Programname:arraytag[Dim1,Dim2]
Programname:arraytag[Dim1,Dim2,Dim3]
Examples: Communication path
Example 1:
Connection with a PLC in the same Allen-Bradley rack.
1,0
Number Meaning
1 Stands for a backplane connection.
0 Stands for a CPU slot number.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2163
Example 2:
Connection with a PLC in remote Allen-Bradley racks. Two Allen-Bradley racks are networked
on Ethernet.
1,2,2,190.130.3.101,1,5
Number Meaning
1 Backplane connection
2 Stands for the CPU slot number of the second Ethernet module.
2 Stands for an Ethernet connection.
190.130.3.101 IP address of a remote AB rack on the network in particular the third Ethernet
module
1 Backplane connection
5 Slot number of the CPU
Addressing in the SLC, MicroLogix CPU type
Addressing
Addressing
The addressing in the SLC, MicroLogix CPU type is entered in the following order:
Operand type
File number
Element number
Child element
Bit number
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2164 System Manual, 08/2011,
The address then appears in the following format without spaces:
File type file number : Element number . Child element
e.g. T8:2.ACC
Operand type
You have the following options under operand type:
I
O
S
B
C
T
R
F
N
ST
A
File number
Select the number between two limits under file number:
Low limit
High limit
The limit values depend on the selected operand type.
Child element
You can select a child element when you have selected one of the following operand types:
R
C
T
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2165
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2166 System Manual, 08/2011,
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Allen-Bradley DF1
Configuring a connection via Allen-Bradley DF1
Introduction
You configure a connection to a PLC with an Allen-Bradley DF1 communication driver in the
"Connections" editor of the HMI device.
The interfaces are named differently depending on the HMI device.
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2167
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2168 System Manual, 08/2011,
4. In the "Communication drivers" column, select the "Allen-Bradley DF1" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
Parameters for the connection (Allen-Bradley DF1)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning
parameters according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2169
Parameters for the HMI device
Interface
Under "Interface", you select the interface of the HMI device to which the PLC is connected.
For additional information, refer to the device manual for the HMI device.
Type
Specifies the physical connection used.
Note
If you are using the IF1B interface, you must also reconnect the RS-485 receive data and
the RTS signal to the rear of the HMI devices via 4 DIP switches.
Baud rate
For "Baud rate", select the transmission speed between the HMI device and PLC.
Data bits
For "Data bits", you can choose between "7 bits" and "8 bits".
Parity
For "Parity", you can choose from "None", "Even", and "Odd".
Stop bits
For "Stop bits", you can choose between 1 and 2 bits.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2170 System Manual, 08/2011,
Parameters for the network
Checksum
For "Checksum", choose the method for determining the error code: "BCC" or "CRC".
Parameters for the PLC
Destination address
For "Destination address", choose the PLC address. If there is a point-to-point DF1
connection, you set the address "0".
CPU type
For "CPU type", set the CPU type of the PLC used.
Note
Assign the DF1 FULL-DUPLEX driver in the CPU as follows: "NO HANDSHAKING" for
"Control Line" and "AUTO-DETECT" for "Embedded Responses".
Connecting HMI device to PLC
Connections via Allen-Bradley DF1
Connection
The connection is established when you have matched the parameters of the PLC and the
HMI device. Special blocks for the connection are not required in the PLC.
Note
Rockwell offers a variety of communication adapters for integrating "DF1 devices" for the
DH485, DH, and DH+ networks. Of these connections, the direct connection and the
connection via KF2 and KF3 module are approved. None of the other connections have been
system-tested by SIEMENS AG and are therefore not approved.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2171
Communication partners for Allen-Bradley DF1
Connectable PLCs
The communication drivers listed below support Allen-Bradley PLCs: :
PLC
DF1
(point-to-point)
RS-232
DF1
(point-to-point)
RS-422
DF1
(multipoint)
over KF2 module
to DH+ LAN
RS-232/RS-422
DF1
(multipoint)
over KF3 module
to DH485 LAN
RS-232
SLC500 X
SLC501 X
SLC502 X
SLC503 X X
SLC504 X X X
SLC505 X X
MicroLogix X X
PLC-5
1)
X X X
1)
Processors released for PLC-5: PLC-5/11, PLC-5/20, PLC-5/30, PLC-5/40, PLC-5/60, and
PLC-5/80.
Communication types
PLCs with Allen-Bradley DF1 communication driver
The communication between the HMI device and the following Allen Bradley PLCs is described
in this section:
SLC500
SLC501
SLC502
SLC503
SLC504
SLC505
PLC5
MicroLogix
In these PLCs the connection is made by the PLC-internal protocols Allen Bradley DF1, Allen
Bradley DH485 and Allen Bradley DH+.
The Allen-Bradley DF1 communication driver is used here, the protocol of which is converted
into one of the other two PLC-internal protocols in multipoint communication with the
communication modules KF2 (Allen Bradley DH+) and KF3(Allen Bradley DH485).
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2172 System Manual, 08/2011,
Enabled types of communication with Allen-Bradley DF1
The following communication types are system-tested and enabled:
HMI (Allen Bradley DF1)
Point-to-point connection
HMI (Allen Bradley DF1)
Via KF2 module to Allen Bradley DH+ (communication with up to 4 PLCs)
HMI (Allen Bradley DF1)
Via KF3 module to Allen Bradley DH485 (communication with up to 4 PLCs)
Connectable PLCs
The Allen Bradley DF1 communication driver is available for the following Allen-Bradley PLCs:
PLC
DF1
(point-to-point)
RS 232
DF1
(point-to-point)
RS 422
DF1
(multipoint)
via KF2 module
to DH+ LAN
RS 232/RS 422
DF1
(multipoint)
via KF3 module
to DH485 LAN
RS 232
2)
SLC500 X
SLC501 X
SLC502 X
SLC503 X
2)
X
SLC504 X
2)
X X
SLC505 X
2)
X
MicroLogix X
2)
X
PLC-5
1)
X X X
1)
Only the following processors are approved for PLC-5: PLC-5/11, PLC-5/20,
PLC-5/30, PLC-5/40, PLC-5/60 und PLC-5/80.
2)
For HMI devices which only have an RS 422/485 interface and the communication
partner is an RS 232 interface, the RS 422/232 converter is tested and approved.
Order number: 6AV6 671-8XE00-0AX0
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2173
DF1 protocol with multi-point connection
Point-to-point connection with DF1 protocol
Only point-to-point connections can be established with the DF1 protocol.
DF1 DF1 DF1
PLC5x SLC5/03, SLC5/04,
SLC5/05
Micro Logix
Channel 0
8-Pin Mini-DlN
Channel 0
9-Pin Sub D
Channel 0
25-Pin Sub D
RS 232
9-Pin Sub D
RS 232
9-Pin Sub D
RS 232 / RS 422
9-Pin Sub D
HMl HMl
PLC PLC PLC
HMl
1) Only RS 232 is possible for Panel PC and PC.
2) A point-to-point connection to the SLC500, SLC501, and SLC502 PLCs via DF1 is not possible.
3) For MicroLogix ML1500 LRP, Channel 1 (9-pin Sub D) is also possible.
Connecting cable
HMI panel interface used For connection to PLC5x For connection to
SLC5/03, SLC5/04,
SLC5/05
For connection to
MicroLogix
RS 232 9-pin Allen-Bradley cable
1784-CP10
Allen-Bradley cable
1747-CP3
Allen-Bradley cable
1761-CBL-PM02
RS 422 9-pin Connecting cable 9-pin
Sub D RS 422
Refer to the relevant device manual to determine which HMI device interface is to be used.
The cable pin assignments can be found in Section "Connecting cables for Allen-Bradley".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2174 System Manual, 08/2011,
DF1 protocol with multi-point connection via KF2 module
DF1 protocol with multi-point connection via KF2 module to DH+ LAN
The use of a KF2 protocol interface module enables a connection to be made to PLCs in the
DH+ LAN (Data Highway Plus Local Area Network).
HMl
PLC
KF2
PLC5x
DH+ (Data Highway Plus)
DF1
(RS232)
SLC5/04
PLC PLC
RS232 / RS422
15-/9-Pin Sub D
25-Pin Sub D
Channel 1A
3-Pin Phoenix
Channel 1B
8-Pin Mini-Din
PLC5x
(except PLC5/11)
Channel 1
8-Pin Mini-Din
or
3-Pin Phoenix
Connecting cable
HMI panel interface used For connection to
KF2 interface module
RS 232 9-pin Allen-Bradley cable
1784-CP10 and 25-pin socket/socket adapter
RS 422 9-pin 9-pin Sub D RS 422 connecting cable and 25-pin female/female adapter
Refer to the Allen-Bradley documentation for the cable connection from the PLCs to the DH+
data bus.
Refer to the relevant device manual to determine which HMI device interface is to be used.
The cable pin assignments can be found in Section "Connecting cables for Allen-Bradley".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2175
DF1 protocol with multi-point connection via KF3 module
DF1 protocol with multi-point connection via KF3 module to DH485 LAN
DH485 (RS 485)
KF3 AlC AlC+ AlC+
DH485
(RS 232)
DH485
(RS 232)
DF1
(RS 232)
DH485
(RS 232)
Micro Logix
SLC5/03, SLC5/04,
SLC5/05
SLC500, SLC5/01,
SLC5/02, SLC5/03
9-Pin Sub D 9-Pin Sub D 8-Pin AMP SDL 25-Pin Sub D
Channel 0
8-Pin Mini-DlN
Channel 0
9-Pin Sub D
Channel 1
8-Pin RJ45
RS 232
15-/9-Pin Sub D
PLC PLC PLC
HMl
1) For MicroLogix ML1500 LRP, Channel 1 (9-pin Sub D) is also possible.
Connecting cable
HMI panel interface used For connection to
KF3 interface module
RS 232 9-pin Allen-Bradley cable
1784-CP10 and 25-pin socket/socket adapter
Refer to the relevant device manual to determine which HMI device interface is to be used.
The cable pin assignments can be found in Section "Connecting cables for Allen-Bradley".
Connecting cables for Allen-Bradley DF1
Connecting cable 9-pin Sub D RS 422 for Allen-Bradley
Connecting cable 9-pin Sub D RS 422
For interconnecting the HMI device (RS 422, 9-pin sub D) - PLC5x, KF2, KF3
You require an additional 25-pin, female / female adapter (gender changer) for
interconnections with KF2 and KF3.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2176 System Manual, 08/2011,
GND
TxD-
TxD+
RxD-
RxD+
7
2
14
3
16
5
9
4
8
3
GND
RxD-
RxD+
TxD-
TxD+
+
-
+
-
+
-
+
-
enclosure
connector 2
25-pin D-Sub connector
screw-locking
cable outlet to the rear
Allen-Bradley
connector 1
9-pin D-Sub connector
screw-locking
cable outlet to the rear
HMl device
Shield with large-area contact to housing at both ends, interconnected shield contacts
Cable: 3 x 2 x 0.14 mm
2
, shielded,
max. length 60 m
Connecting cable 1784-CP10, RS 232, for Allen-Bradley
Allen-Bradley cable 1784-CP10
For interconnecting the HMI device (RS 232, 9-pin sub D) - PLC5x, KF2, KF3
You require an additional 25-pin, female / female adapter (gender changer) for
interconnections with KF2 and KF3.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2177
CTS
RTS
GND
RxD
TxD
DTR
DSR
DCD
5
4
7
3
2
20
6
8
7
8
5
3
2
6
4
RTS
CTS
GND
TxD
RxD
DSR
DTR
enclosure
connector 2
25-pin D-Sub connector
screw-locking
cable outlet to the rear
Allen-Bradley
connector 1
9-pin D-Sub female connector
screw-locking
cable outlet to the rear
HMl device
Screen connected with housing over large area on both sides
max. length 15 m
Connecting cable 1747-CP3, RS-232, for Allen-Bradley
Allen-Bradley cable 1747-CP3
For interconnecting the HMI device (RS 232, 9-pin sub D) - SLC503, SLC504, SLC505
(Channel 0), AIC+
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2178 System Manual, 08/2011,
CTS
RTS
GND
RxD
TxD
DTR
DSR
DCD
8
7
5
2
3
4
6
1
7
8
5
3
2
1
6
4
RTS
CTS
GND
TxD
RxD
DCD
DSR
DTR
enclosure
connector 2
9-pin D-Sub female connector
screw-locking
cable outlet to the rear
Allen-Bradley
connector 1
9-pin D-Sub female connector
screw-locking
cable outlet to the rear
HMl device
Screen connected with housing over large area on both sides
max. length 3 m
Connecting cable 1761-CBL-PM02, RS-232, for Allen-Bradley
Allen-Bradley cable 1761-CBL-PM02
For interconnecting the HMI device (RS 232, 9-pin sub D) - Micro Logix, AIC+
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2179
CTS
RTS
GND
RxD
TxD
DCD
6
3
2
4
7
5
7
8
5
3
2
1
RTS
CTS
GND
TxD
RxD
DCD
enclosure
HMl device
connector 1
9-pin D-Sub female connector
screw-locking
cable outlet to the rear
Allen-Bradley
connector 2
8-pin mini DlN connector
cable outlet to the rear
Screen connected with housing over large area on both sides
max. length 15 m
Performance features of communication
Permitted data types for Allen-Bradley DF1
Permitted data types for Allen-Bradley DF1
The table lists the user data types that can be used when configuring tags and area pointers.
Data type Operand type Length
ASCII A
1)
1 to 80 characters
Bool N, R, C, T, B, S, I, O 1 bit
Int N, R, C, T, S 2 bytes
DInt N, D
2)
4 bytes
UInt N, R, C, T, B, I, O, D
2)
2 bytes
UDInt N, D
2)
4 bytes
Real N, F
1)
4 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2180 System Manual, 08/2011,
1)
Selectable depending on the selected CPU type.
2)
Only for PLC5 CPU type
Abbreviations
In WinCC, formats of the data types are abbreviated as follows:
UNSIGNED INT = UInt
UNSIGNED LONG = UDInt
SIGNED INT = Int
SIGNED LONG = DInt
Distinctive features for connections with Allen-Bradley DF1
With Allen Bradley DF1, array tags may only be used for discrete alarms and trends.
Note
I/O modules with 8 or 16 ports occupy one data word on the PLC.
I/O modules with 24 or 32 ports occupy two data words.
The HMI device does not output an error message if using non-existent bits.
You should always make sure that I/O modules with 8 or 24 ports only occupy the bits that
are actually assigned to a port.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2181
Supported CPU types for Allen-Bradley DF1
CPU types
The following CPU types are supported for configuring the Allen-Bradley DF1 communication
driver.
SLC
SLC500
SLC501
SLC502
SLC503
SLC504
SLC505
MicroLogix
MicroLogix 1x00
MicroLogix 1100 / 1400
PLC 5
PLC-5/11
PLC-5/20
PLC-5/40
PLC-5/60
PLC-5/80
Addressing
Addressing
The addressing is entered in the following order in the Allen-Bradley DF1 communication driver:
Operand type
File number
Element number
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2182 System Manual, 08/2011,
Child element
Bit number
The address then appears in the following format without spaces:
File type file number : Element number . Child element
e.g. T8:2.ACC
Operand type
You have the following options under operand type:
I
O
S
B
T
C
R
N
A
D only for PLC5 CPU type
File number
Select the number between two limits under file number:
Low limit
High limit
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2183
The limit values depend on the selected file type.
Child element
You can select a child element when you have selected one of the following data types:
R
C
T
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2184 System Manual, 08/2011,
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Data exchange
Area pointers for Allen-Bradley
Area pointers for connections using an Allen-Bradley communication driver
You use an area pointer to access a data area in the PLC.
For more detailed information on area pointers and their configuration, refer to Section "Data
exchange using area pointers".
Distinctive features for connections via Allen-Bradley EtherNet/IP
You can configure the following area pointers
Area pointer Allen-Bradley EtherNet/IP Allen-Bradley DF1
Screen number Yes Yes
Date/time Yes Yes
Date/time PLC Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2185
Area pointer Allen-Bradley EtherNet/IP Allen-Bradley DF1
Coordination Yes Yes
Project ID Yes Yes
Job mailbox Yes Yes
Data record Yes Yes
Restrictions Allen-Bradley Ethernet/IP
The following restrictions apply for configuring area pointers.
CPU type Data types File types
ControlLogix,CompactLogix Int, UInt --
SLC, MicroLogix Int, UInt N, B
Restrictions Allen-Bradley DF1
The following restrictions apply for configuring area pointers.
CPU type Data types File types
MicroLogix -- N, O, I, B
SLC50x -- N, O, I, B
PLC5 -- N, O, I, B
See also
Data exchange using area pointers (Page 2267)
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
For additional information see:
Displaying tags with Runtime Advanced and Panels (Page 940)
Note
The value is read out time-triggered for Basic Panels.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2186 System Manual, 08/2011,
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
The following picture shows the structure of a trend transfer area.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2187
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Restrictions to the trend control
For Allen-Bradley DF1 communication drivers
Tags of the following operand types are permitted:
"N"
"O"
"I"
"S"
"B"
Permitted data types:
"UInt"
"Int"
Array tag of "UInt"
Array tag of "Int"
You assign a bit to a trend during configuration. This sets a defined bit assignment for all trend
areas.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2188 System Manual, 08/2011,
For Allen-Bradley EtherNet/IP communication drivers
Tags of data type "Int" or an array tag of data type "Int" are permitted. You assign a bit to a
trend during configuration. This sets a defined bit assignment for all trend areas.
ControlLogix and CompactLogix
The following data types are possible for tags for the ControlLogix and CompactLogix CPU
types:
"UInt"
"Int"
Array tag of "UInt"
Array tag of "Int"
SLC and MicroLogix
The following operand types are permitted for tags of the SLC and MicroLogix CPU types:
"N"
"O"
"I"
"S"
"B"
Permitted data types:
"UInt"
"Int"
Array tag of "UInt"
Array tag of "Int"
Alarms
Configuring alarms
Configuring alarms for non-integrated connections
Several steps are necessary to configure alarms such as warnings, error messages and
acknowledgement.
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2189
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Restrictions
Only tags whose "File type" is "N", "O", "I", "S" and "B" are allowed for use as a "trigger tag"
for discrete alarms. These tags are only valid for the data types "Int" and "UInt".
Data types
For connections with an Allen-Bradley communication driver, the following data types are
supported:
Communication drivers PLC Permitted data types
Discrete alarms Analog alarms
Allen-Bradley DF1 SLC500, SLC501,
SLC502, SLC503,
SLC504, SLC505,
PLC5, MicroLogix
Int, UInt Int, UInt, Long,
ULong, Real
Allen-Bradley EtherNet/IP ControlLogix,
CompactLogix, SLC,
Micrologix
Int, UInt SInt, USInt, Int, UInt,
DInt, UDInt, Real
How the bit positions are counted
For connections with an Allen-Bradley communication driver, the following counting method
applies:
How the bit positions are counted Left byte Right byte
In Allen-Bradley PLCs 15 8 7 0
In WinCC you configure: 15 8 7 0
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2190 System Manual, 08/2011,
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2191
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2192 System Manual, 08/2011,
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
Mitsubishi
Mitsubishi communication drivers
Introduction
This section describes the communication between an HMI device and PLCs that use
Mitsubishi communication drivers.
The following communication drivers are supported:
Mitsubishi MC TCP/IP
Mitsubishi FX
Data exchange
Data is exchanged by means of tags or area pointers.
Tags
The PLC and the HMI device use process values for data exchange. You create tags in
the configuration that point to addresses in the PLC. The HMI device reads the value from
the defined address, and then displays it. The operator may also enter values on the HMI
device, which are then written to the address in the PLC.
Area pointers
Area pointers are used to exchange specific data and are only set up when these data are
used.
Mitsubishi MC TCP/IP
Configuring a connection via Mitsubishi MC TCP/IP
Introduction
You configure a connection to a PLC with a Mitsubishi MC TCPI/IP communication driver in
the "Connections" editor of the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2193
The Ethernet interfaces are named differently depending on the HMI device.
Example: PROFINET interface corresponds to the Ethernet interface
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2194 System Manual, 08/2011,
4. In the "Communication drivers" column, select the "Mitsubishi MC TCPI/IP" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
Parameters for the connection (Mitsubishi MC TCP/IP)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device" and "PLC" areas are available for assigning parameters
according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2195
Parameters for the HMI device
You can select only one interface for the HMI device in the Inspector window under
"Parameters". Depending on the HMI device, there are several interfaces available.
If you are directly connected to the HMI device during configuration, you can set up the IP
address of the HMI device in WinCC. The IP address is transferred to the HMI device during
project transfer.
Note
The IP address in the control panel will be overwritten upon subsequent loading if you have
already set up the IP address in the HMI device control panel.
The IP address already set up in the control panel will be retained upon subsequent loading
if you activate "Set IP address using a different method".
To set up the IP address of the HMI device:
1. Click on the HMI device.
2. Open the "Device configuration" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2196 System Manual, 08/2011,
3. Click the Ethernet interface.
4. Assign the IP address in the inspector window under:
"General > PROFINET interface > Ethernet addresses"
Parameters for the PLC
CPU type
For "CPU type", you set the type of PLC to which the HMI device is connected.
The following settings are possible:
FX3
Q
If you select the FX3 CPU type, the Mitsubishi MC protocol "1E" is used and "3E" for the
"Q" CPU type.
The "Binary code" protocol variant is always used.
NOTICE
If the CPU type is changed for a configured connection, tags with the following properties
must be revised:
Operands that do not exist for the new CPU type, such as "W", "B", "F".
Inputs and outputs with different addressing (hexadecimal/octal)
Addresses greater than the valid address area of the new CPU type
IP address
Set the IP address or host name of the Ethernet/IP module of the PLC. Only the IP address
can be used on a Basic Panel.
Port
Set the port number of the module of the PLC.
Connecting HMI device to PLC
Connections via Mitsubishi MC TCP/IP
Connection
The HMI device can be connected to the Mitsubishi PLC using the following components:
Existing Ethernet network that also contains the PLCs
Cross-over Ethernet cable connected directly to the Ethernet interface of the CPU or the
communication module
The connection of the HMI device to a Mitsubishi PLC is limited primarily to the physical
connection of the HMI device. Special blocks for the connection are not required in the PLC.
Connect the HMI device to one or several Q-series and/or FX3 PLCs. Connect the HMI device
via the following interfaces:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2197
Communication interface OnBoard
Approved communication module suitable for the PLC
Note
Timeout response with TCP/IP (Ethernet)
Due to the use of the TCP/IP protocol, the breakdown of a connection is detected at the
earliest after approximately one minute. Communication failure cannot be reliably
detected if no tags are requested, for example, no output tags in the current screen.
Configure area pointer coordination for each PLC. This setting ensures that a
communication failure is recognized after approximately two minutes, even in the
aforementioned scenario.
Communication types
Approved communication types
Only applies for Mitsubishi FX(PG protocol):
The point-to-point connection from a HMI device to an approved Mitsubishi FXCPU via
Mitsubishi FX is system-tested and approved by Siemens AG.
Only applies for Mitsubishi MC TCP/IP:
The following communication types are system-tested and approved:
Point-to-point connection to the approved PLCs
Multipoint connection from a HMI device with up to 4 PLCs with the respectively
approved PLCs. CPU types (FX3 and Q) can be mixed.
Note
The HMI device is a client and the PLC must operate as a server.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2198 System Manual, 08/2011,
Connectable PLCs
Connections can be implemented for the following Mitsubishi PLCs:
PLC
Mitsubishi FX
(PG protocol)
Mitsubishi MC TCP/IP
MELSEC FX1n, FX2n Yes No
MELSEC FX3U, FX3UC, FX3G with
communication module FX3U-ENET
No Yes
MELSEC System Q
Q-series with the communication
module QJ71E71-100
QnUDEH CPU with Ethernet interface
onboard
No Yes
Parameterization of the communications modules
FX3 PLCs
Procedure
1. Start the FX-Configurator.
2. Select the module.
3. Assign the following settings in the "Operational settings" dialog.
Communication data code:
Binary code
Initial timing:
Always wait for OPEN
IP address:
IP address
Send frame setting:
Ethernet(V2.0)
TCP Existence confirmation setting:
Use the Ping
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2199
4. Assign the following settings in the "Open Settings" dialog:
Protocol:
TCP
Open system:
Unpassive
Fixed buffer:
Receive
Fixed buffer communication procedure:
Procedure exist(MC)
Pairing open
Disable
Existence confirmation
No confirm
Host station Port No. (DEC)
Port number
Note
The port number chosen in the communication module must match the port number
in WinCC. A connection with a port number must be assigned for each connected HMI
device.
5. Confirm the default settings of the other dialog boxes.
The network no. and station no. parameters are not relevant for the connection and can be
chosen as required.
Q PLCs
Procedure
1. Click "Edit network parameters".
2. Select the network type:
Ethernet
The network number and the group / station number are not evaluated and can be freely
assigned
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2200 System Manual, 08/2011,
3. Assign the following settings in the "Operational settings" dialog.
Communication data code:
Binary code
Initial timing:
Always wait for OPEN
IP address:
IP address
Send frame setting:
Ethernet(V2.0)
Enable write operations during RUN
4. Assign the following settings in the "Open settings" dialog.
Protocol:
TCP
Open system:
Unpassive
Pairing open
Disable
Existence confirmation
No confirm
Host station Port No. (HEX)
Port-Nummer
Note
The port number chosen in the communication module must match the port number
in WinCC. A connection with a port number must be assigned for each connected HMI
device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2201
Internal Ethernet port of the Q0xUDEH CPU
Procedure
1. Assign the following settings in the "Internal Ethernet Port" dialog.
IP address:
IP address
Communication data code:
Binary code
Enable online changes
2. Assign the following settings in the "Open settings" dialog.
Protocol:
TCP
Open system:
MC-Protocol
Host station Port No. (HEX)
Port number
Note
The port number chosen in the communication module must match the port number
in WinCC. A connection with a port number must be assigned for each connected HMI
device.
Performance features of communication
Permitted data types for Mitsubishi MC TCPI/IP
Permitted data types
The table lists the data types that can be used when configuring tags and area pointers.
Data type Operand type Length
4-bit block M, X, Y, B, F 1 byte
8-bit block M, X, Y B, F 1 byte
12-bit block M, X, Y B, F 2 bytes
16-bit block M, X, Y B, F 2 bytes
20-bit block M, X, Y B, F 4 bytes
24-bit block M, X, Y B, F 4 bytes
28-bit block M, X, Y B, F 4 bytes
32-bit block M, X, Y B, F 4 bytes
Bool M, D, X, Y B, F 1-bit
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2202 System Manual, 08/2011,
Data type Operand type Length
DInt D, W 4 bytes
DWord D, C, W 4 bytes
Int D, W 2 bytes
Real 1) D, W 4 bytes
String 1) D, W 1 to 80 characters
Word D, T, C, W 2 bytes
1) The "String" and "Real" data types are not available for all CPUs.
2) Operand types B, F and W are only available for CPU type "Q".
Note
Note the following for write accesses:
Tags can only be written if "Enable online changes" or "Enable write operations during RUN"
was selected when parameterizing the Mitsubishi communication modules.
For data type "Bool" in operand type "D", the entire word is written back to the PLC following
a change to the specified bit. There is no check to determine whether any other bits in the
word have changed. As a result, the PLC only has read access to the specified word.
Note
Array elements in I/O fields cannot be used in communication with a Mitsubishi PLC.
Supported CPU types for Mitsubishi MC TCP/IP
CPU types
The following CPU types are supported for configuring the Mitsubishi MC TCP/IP
communication driver.
FX3 series
FX 3G / FX 3G with communication modul FX3U-ENET
FX 3U / FX 3U with communication modul FX3U-ENET
FX 3UC / FX 3UC with communication modul FX3U-ENET
Q series
Q-Series with QJ71E71-100 communication module
iQ series / QnUD
QnUDEHCPU with built in ethernet module
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2203
Addresses for Mitsubishi MC TCP/IP
Address areas for connections via Mitsubishi MC TCP/IP
The address area boundaries differ for the different series; refer to the Mitsubishi Computerlink
manuals for this information.
Examples of address area boundaries dependent on the CPU and communication format:
Name Operand type Max. address
FX3
Max. address
Q-Series
Output/Input Y/X Octal X/Y 0 - 267 HEX X/Y 0 - 7FF
Bit memory M M0 - M3071 and
M8000 - M8255
M/L/S 0 - 8191
Data register D D0 - 7999
D8000 - D8255
D0 - 8191
D9000 - D9255 becomes SD1000 -
SD1255
Counter C C0 - 255 C0 - 1023
Timer T T0 - 255 T0 - 2047
Link register W -- Hex: W0 - FFF
Link flag B -- Hex: B0 - FFF
Error flag F -- F0 - 2047
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2204 System Manual, 08/2011,
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2205
Mitsubishi FX
Configuring a connection via Mitsubishi FX
Introduction
You configure a connection to a PLC with a Mitsubishi FX communication driver in the
"Connections" editor of the HMI device.
The Mitsubishi FX protocol is also referred to as the Mitsubishi PG protocol.
The interfaces are named differently depending on the HMI device.
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2206 System Manual, 08/2011,
4. In the "Communication drivers" column, select the "Mitsubishi FX" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
Parameters for the connection (Mitsubishi FX)
Parameters to be set
To assign the connection parameters, such as addresses and profiles, click the connection
that you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device", "Network", and "PLC" areas are available for assigning
parameters according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2207
Parameters for the HMI device
You can select an interface for the HMI device in the Inspector window under "Parameters".
Depending on the HMI device, there are several interfaces available.
"Type"
Specifies the physical connection used.
Note
If you use the IF1B interface, you must switch over the RS422 receive data and the RTS
signal additionally by 4 DIL-switches on the back of the HMI device.
Parameters for the PLC
Baud rate
For "Baud rate", select the transmission speed between the HMI device and PLC.
Select the baud rate "9600".
Data bits
For "Data bits", you can choose between "7 bits" and "8 bits".
Select "7 bits".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2208 System Manual, 08/2011,
Parity
For "Parity", you can choose from "None", "Even", and "Odd".
Select "Even".
Stop bits
For "Stop bits", you can choose between 1 and 2 bits.
Select "1 bit".
Connecting HMI device to PLC
Connections via Mitsubishi FX
Connection
Connect the HMI device to the programming interface of the CPU (RS 422) (see documentation
of the PLC).
The connection between the HMI device and the Mitsubishi PLC is basically restricted to setting
the interface parameters. Special blocks for the connection are not required in the PLC.
Connecting cable
The following connecting cables are available to connect the HMI device to the PLC.
Interface to
HMI device or adapter
Mitsubishi Electric PLC via FX protocol
FX1n, Fx2n, Mini DIN, 8pin
RS 232, 9-pin Mitsubishi SC-09
1)
RS 422, 9-pin Connecting cable RS422-2P
1)
Since the Mitsubishi PLCs communicate via RS 422 as a standard, the Mitsubishi programming
cable SC09 with integrated RS 422/RS 232 adaptor is necessary for connecting a HMI device via RS
232.
Note
Applies only to RS 232:
Cable length is restricted to 0.32 m.
Refer to the relevant device manual to determine which HMI device interface is to be used.
The cable pin assignments can be found in Section "Connecting cables for Mitsubishi FX".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2209
Communication types
Approved communication types
Only applies for Mitsubishi FX(PG protocol):
The point-to-point connection from a HMI device to an approved Mitsubishi FXCPU via
Mitsubishi FX (PG protocol := protocol for access to the program and memory elements of
the FX series PC CPU version V1.21 and after) is system-tested and approved by Siemens
AG.
Only applies for Mitsubishi MC TCP/IP:
The following communication types are system-tested and approved:
Point-to-point connection to the approved PLCs
Multipoint connection from a HMI device with up to 4 PLCs with the respectively
approved PLCs. CPU types (FX3 and Q) can be mixed.
Note
The HMI device is a client and the PLC must operate as a server.
Connectable PLCs
Connections can be implemented for the following Mitsubishi PLCs:
PLC
Mitsubishi FX
(PG protocol)
Mitsubishi MC TCP/IP
MELSEC FX1n, FX2n Yes No
MELSEC FX3U, FX3UC, FX3G with
communication module FX3U-ENET
No Yes
MELSEC System Q
Q-series with the communication
module QJ71E71-100
QnUDEH CPU with Ethernet interface
onboard
No Yes
Connecting cables for Mitsubishi FX
Connecting cable RS 422 2P, for Mitsubishi
Connecting cable RS422-2P
TxD-
TxD+
GND
RxD-
RxD+
4
7
3
1
2
9
4
5
8
3
RxD-
RxD+
GND
TxD-
TxD+
+
-
+
-
+
-
+
-
enclosure
HMl device
connector 1
9-pin D-Sub connector
screw-locking
cable outlet to the rear
Mitsubishi
connector 2
8-pin mini DlN connector
screw-locking
cable outlet to the rear
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2210 System Manual, 08/2011,
Shield with large-area contact to housing at both ends
Cable: 3 x 2 x 0.14 mm
2
, shielded,
max. length 500 m
Performance features of communication
Permitted data types for Mitsubishi FX
Permitted data types
The table lists the data types that can be used when configuring tags and area pointers.
Data type Operand type Length
4-bit block M, X, Y 1 byte
8-bit block M, X, Y 1 byte
12-bit block M, X, Y 2 bytes
16-bit block M, X, Y 2 bytes
20-bit block M, X, Y 4 bytes
24-bit block M, X, Y 4 bytes
28-bit block M, X, Y 4 bytes
32-bit block M, X, Y 4 bytes
Bool D, M, X, Y 1-bit
DWord D, C-32 bit 4 bytes
Real D 4 bytes
String D 1 to 50 characters
Word D, T, C-16 bit 2 bytes
Note
Note the following for write accesses:
For data type "Bool" in operand type "D", the entire word is written back to the PLC following
a change to the specified bit. There is no check to determine whether any other bits in the
word have changed. As a result, the PLC only has read access to the specified word.
Note
Array elements in I/O fields cannot be used in communication with a Mitsubishi PLC.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2211
Supported CPU types for Mitsubishi FX
CPU types
The following CPU types are supported for configuring the Mitsubishi FX communication
driver.
FX1 series
FX1n
FX2 series
FX2n
Configurable address areas for Mitsubishi FX
Permitted address areas
The following address areas can be configured for the "Mitsubishi FX" communication driver
X Input Octal 0- 377
Y Output Octal 0- 377
M Bit memory 0...9999
D Data register 0...999
C Counter 0...199
T Timer 0...25
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2212 System Manual, 08/2011,
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2213
Data exchange
Area pointers for Mitsubishi
Area pointers for connections via Mitsubishi communication drivers
You use an area pointer to access a data area in the PLC.
For more detailed information on area pointers and their configuration, refer to Section "Data
exchange using area pointers".
Special considerations for connections via Mitsubishi communication drivers
You can configure the following area pointers
Area pointer Mitsubishi MC TCP/IP Mitsubishi FX
Screen number Yes Yes
Date/time Yes Yes
Date/time PLC Yes Yes
Coordination Yes Yes
Project ID Yes Yes
Job mailbox Yes Yes
Data record Yes Yes
Restrictions Mitsubishi MC TCP/IP
The following restrictions apply for configuring area pointers.
CPU type Data types Operand type
FX3 Int, Word D
Q Int, Word D
Mitsubishi FX restrictions
You cannot use the D operand type for configuring area pointers.
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2214 System Manual, 08/2011,
For additional information see:
Auto-Hotspot
Note
The value is read out time-triggered for Basic Panels.
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
See also
Displaying tags with Runtime Advanced and Panels (Page 940)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2215
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
The following picture shows the structure of a trend transfer area.
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Restrictions to the trend control
Data types for Mitsubishi MC TCPI/IP
For trend control you can create tags and array tags of the operand type "D" with the data type
"Word" or "Int".
Data types for Mitsubishi FX
For trend control you can create tags and array tags of the operand type "D" with the data type
"Word".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2216 System Manual, 08/2011,
Alarms
Configuring alarms
Configuring alarms for non-integrated connections
Several steps are necessary to configure alarms such as warnings, error messages and
acknowledgement.
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Data types
For connections with a Mitsubishi communication driver, the following data types are
supported:
PLC Permitted data types
Discrete alarms Analog alarms
FX1n, FX2n, FX3 series, Q-
Series, iQ-Series
Word,
Int
1)
4 bit-block, 8 bit-block,
12 bit-block, 16 bit-block,
20 bit-block, 24 bit-block,
28 bit-block, 32 bit-block,
Word, DWord, Int
1)
, DInt
1)
, Real,
1)
Not for Mitsubishi FX communication driver
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2217
How the bit positions are counted
For connections with a Mitsubishi communication driver, the following counting method applies:
How the bit positions are
counted Left byte Right byte
In Mitsubishi
PLCs
15 8 7 0
In WinCC you configure: 15 8 7 0
Restrictions on alarms
Mitsubishi MC TCP/IP
Only tags of operand type "D" and data types "Word" and "Int" are permitted as trigger tags
for discrete alarms. You can use array tags (operand type: "D"; data types: "ARRAY [x..y]
of Word" or "ARRAY [x..y] of Int") for discrete alarms.
Mitsubishi FX
Only tags of operand type "D" and data type "Word" are permitted as trigger tags for discrete
alarms. You can use array tags (operand type "D"; data type "ARRAY [x..y] of Word") for
discrete alarms."
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2218 System Manual, 08/2011,
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2219
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
Modicon Modbus
Modicon Modbus communication drivers
Introduction
This section describes the communication between an HMI device and PLCs that use Modicon
Modbus communication drivers.
The following communication drivers are supported:
Modicon Modbus TCP/IP
Modicon Modbus RTU
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2220 System Manual, 08/2011,
Data exchange
Data is exchanged by means of tags or area pointers.
Tags
The PLC and the HMI device use process values for data exchange. You create tags in
the configuration that point to addresses in the PLC. The HMI device reads the value from
the defined address, and then displays it. The operator may also enter values on the HMI
device, which are then written to the address in the PLC.
Area pointers
Area pointers are used to exchange specific data and are only set up when these data are
used.
Modicon Modbus TCP/IP
Configuring a connection via Modicon Modbus TCP/IP
Introduction
You configure a connection to one of the PLCs with Modicon Modbus TCP/IP communication
driver in the "Connections" editor of the HMI device.
The Ethernet interfaces are named differently depending on the HMI device.
Example: PROFINET interface corresponds to the Ethernet interface
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2221
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2222 System Manual, 08/2011,
4. Select the "Modicon Modbus TCP" driver in the "Communication driver" column.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
Parameters for the connection (Modicon Modbus TCP/IP)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device" and "PLC" areas are available for assigning parameters
according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2223
Parameters for the HMI device
You can select only one interface for the HMI device in the Inspector window under
"Parameters". Depending on the HMI device, there are several interfaces available.
If you are directly connected to the HMI device during configuration, you can set up the IP
address of the HMI device in WinCC. The IP address is transferred to the HMI device during
project transfer.
Note
The IP address in the control panel will be overwritten upon subsequent loading if you have
already set up the IP address in the HMI device control panel.
The IP address already set up in the control panel will be retained upon subsequent loading
if you activate "Set IP address using a different method".
To set up the IP address of the HMI device:
1. Click the HMI device.
2. Open the "Device configuration" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2224 System Manual, 08/2011,
3. Click the Ethernet interface.
4. Assign the IP address in the inspector window under:
"General > PROFINET interface > Ethernet addresses"
Parameters for the PLC
"CPU type"
For "CPU type", you set the Modicon PLC to which the HMI device is connected.
"Port"
For "Port", you set the port that is used for the TCP/IP connection. The port used by the
Modicon PLCs is 502.
"Server"
You set the IP address or host name of the PLC under "Server". Only the IP address can
be used on a Basic Panel.
"Remote Slave address"
Under "Remote Slave address" you only set which slave address the remote PLC has when
using a bridge.
If no bridge is used, the default value 255 (or 0) must be retained.
"Change word order"
The "Change word order " parameter only affects the word order of the 32-bit values display.
The setting pertains to the data types Double, Double+/-, and Float. The byte order cannot
be changed.
"Change word order" not activated
The most significant byte is sent first.
For double words, the least significant word is sent before the most significant word.
This setting has been system-tested for all approved PLCs.
"Change word order" activated
The most significant byte is sent first.
For double words, the most significant word is sent before the least significant word.
Note
This setting must be used for the SIEMENS SENTRON PAC3200 and PAC4200 multi-
function meters and can be used for PLCs of other manufacturers.
"Use single write"
If you deselect this function, only function codes 15H and 16H are used for writing into the
PLC.
If this function remains selected, the function codes 05H, 06H 16H and 16H are used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2225
Connecting HMI device to PLC
Connections via Modicon Modbus TCP/IP
Connection
The HMI device can be connected to the Modicon Modbus PLC using the following
components:
Existing Ethernet network that also contains the PLCs
Cross-over Ethernet cable connected directly to the Ethernet interface of the CPU or the
communication module
The connection of the HMI device to a Modicon Modbus PLC is limited primarily to the physical
connection of the HMI device. Special blocks for the connection are not required in the PLC.
Note
Timeout response with TCP/IP (Ethernet)
Due to the use of the TCP/IP protocol, the breakdown of a connection is detected at the
earliest after approximately one minute. Communication failure cannot be reliably detected
if no tags are requested, for example, no output tags in the current screen.
Configure area pointer coordination for each PLC. This setting ensures that a communication
failure is recognized after approximately two minutes, even in the aforementioned scenario.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2226 System Manual, 08/2011,
Communication types
Enabled types of communication
The following communication types are system-tested and enabled:
Point-to-point coupling:
Multiple point coupling of a HMI device (Modbus TCP/IP Client) with up to 4 PLCs, each
with different couplings. It is possible to mix the types of CPU.
The following couplings are possible:
Coupling the Ethernet CPU interface of the TSX Unity Quantum.
Coupling via the communication modules for Ethernet 140 NOE 771 01 for the TSX
Quantum and TSX Unity Quantum series
Coupling via the Ethernet interface of the 171 CCC 980 30 CPU adapter of the
Momentum series
Coupling the Ethernet CPU interface of the TSX Unity Premium.
Coupling via the Ethernet TCP/IP connect module TSX ETY 110 for the TSX Premium
and TSX Unity Premium series
Coupling via the Ethernet TCP/IP connect module TSX ETY 410 for the Micro series
Coupling via the Ethernet TCP/IP Modbus Plus Bridge 174 CEV 200 40 to the Modbus
Plus interface of the Compact, the TSX Quantum and the TSX Unity Quantum series
Via the TCP/IP Modbus Plus Bridge, 174 CEV 200 40, the PLCs can be accessed at their
Remote Slave Address via the Ethernet interface of this bridge.
Note
Integration of the HMI device in a Modbus network via a bridge is not possible. The HMI
device is the Modbus master.
Restrictions
The coupling of the HMI device to PLCs of other manufacturers who offer a Modbus TCP/IP
interface is not system-tested and thus, not enabled.
However, if another PLC is to be used, observe the following instructions:
Use the following CPU types, because these operate without address offset and in the
usual bit count manner.
Unity, PL7: Premium, Micro, Quantum, M340
The following function codes are used for the respective data areas:
Reading function codes Address range
01 ReadCoilStatus 0x / %M DIGITAL_OUT
02 ReadInputStatus 1x / %I DIGITAL_IN
03 ReadHoldingRegisters 4x / %MW USERDATA
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2227
Reading function codes Address range
04 ReadInputRegisters 3x / %IW ANALOG_IN
20 (14Hex) ReadGeneralReference 6x / EXTENDEDMEMORY
(not for all CPUs)
Writing function codes Address range
06
1)
PresetSingleRegister 4x / %MW USERDATA Single
16 (10Hex) PresetMultipleRegisters 4x / %MW USERDATA Multiple
05
1)
ForceSingleCoil 0x / %M DIGITAL_OUT with BIT
15 (0FHex) ForceMultipleCoils 0x / %M DIGITAL_OUT with 16 BIT GROUP
21 (15Hex) WriteGeneralReference 6x / EXTENDEDMEMORY
(not for all CPUs)
1)
Select use with "Use single write".
Connectable PLCs
Connections can be implemented for the following Modicon Modbus PLCs:
Modicon Modbus PLC Supported protocol
Modicon Modbus RTU
2)
Modicon Modbus TCP/IP
TSX Compact x x
1)
TSX Quantum x x
Momentum x x
Premium - x
Micro - x
M340 20X0 (without 2010) - x
1)
Only via Ethernet TCP/IP Modbus Plus Bridge
2)
Communication via RS 232 is tested and enabled for the PLC. In the HMIs that only have
a RS 422/485 interface, the RS 422/232 converter with the order number 6AV6
671-8XE00-0AX0 was tested and enabled.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2228 System Manual, 08/2011,
Performance features of communication
Permissible data types for Modicon Modbus TCP/IP
Permitted data types
The table lists the data types that can be used when configuring tags and area pointers.
Note
If you change the Modicon Modbus RTU communication driver to Modicon Modbus TCP/IP,
the string in the "String" data type may be different.
Permitted data types for CPU type "Unity, PLC: Premium, Micro, Quantum M340"
Data type Operand type Length
+/- Double %MW 4 bytes
+/- Int %MW, %IW 2 bytes
16-bit group %MW, %I 2 bytes
ASCII %MW 0 to 80 characters
Bit %MW, %IW,
%M, %I
1-bit
Double %MW 4 bytes
Float %MW 4 bytes
Int %MW, %IW 2 bytes
Note
The ranges "%I" and "%IW" are not supported for the following CPU types:
Premium
Micro
M340
Permitted data types for CPU type "Concept, ProWORX: Compact, Quantum, Momentum"
Data type Operand type Length
+/- Double 4x, 6x 4 bytes
+/- Int 3x, 4x, 6x 2 bytes
16-bit group 0x, 1x 2 bytes
ASCII 4x, 6x 0 to 80 characters
Bit 0x, 1x, 3x, 4x,
6x
1-bit
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2229
Data type Operand type Length
Double 4x, 6x 4 bytes
Float 4x, 6x 4 bytes
Int 3x, 4x, 6x 2 bytes
Bit counting method
The usual bit counting method "16 LSB - 1 MSB" in the following CPU types is only used in
the "HMI tags" editor with the selected "Bit" data type:
Concept, ProWORX: Compact, Quantum, Momentum
The following bit location assignment applies:
Left byte Right byte
Counting with tags 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Format for "Signed"
The placeholder "+/-" stands for the data types "Signed Int" and "Signed Double".
Supported CPU types for Modicon Modbus TCP/IP
CPU types
The following CPU types are supported for configuring the Modicon Modbus TCP/IP
communication driver.
Compact
Momentum
Quantum
Concept Quantum
Unity Quantum
Micro
Premium
Modicon M340
20x0 (except 2010)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2230 System Manual, 08/2011,
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2231
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Modicon Modbus RTU
Configuring a connection via Modicon Modbus RTU
Introduction
You configure a connection to a PLC with a Modicon Modbus RTU communication driver in
the "Connections" editor of the HMI device.
The interfaces are named differently depending on the HMI device.
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2232 System Manual, 08/2011,
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2233
4. In the "Communication drivers" column, select the "Modicon Modbus RTU" driver.
5. Select all necessary connection parameters for the interface in the Inspector window under
"Parameters".
Parameters for the connection (Modicon Modbus RTU)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device" and "PLC" areas are available for assigning parameters
according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2234 System Manual, 08/2011,
Parameters for the HMI device
You can select an interface for the HMI device in the Inspector window under "Parameters".
Depending on the HMI device, there are several interfaces available.
Type
Only RS 232 is system-tested.
No warranty is given for RS 485.
Note
RS 422 is only approved in combination with the RS 422-RS 232 converter.
Order number: 6AV6 671-8XE00-0AX0
Note
If you use the IF1B interface, you must switch over the RS422 receive data additionally
by 4 DIL-switches on the back of the HMI device.
Baud rate
For "Baud rate", select the transmission speed between the HMI device and Modicon PLC.
A baud rate of 19200 or 9600 can be selected for the communication.
A baud rate of 4800 can be selected for certain HMI devices.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2235
Data bits
For "Data bits", only the value "8" can be selected.
Parity
For "Parity", you can choose from "None", "Even", and "Odd".
Stop bits
For "Stop bits", you can choose between 1 and 2 bits.
Parameters for the PLC
CPU type
For "CPU type", you set the Modicon PLC to which the HMI device is connected.
You can select the following CPUs:
Concept, ProWORX: Compact, Quantum
Slave address
Under "Slave address" you set which slave address the CPU has.
Connecting HMI device to PLC
Connections via Modicon Modbus RTU
Connection
Connect the HMI device to the Modicon Modbus RTU interface of the Modicon Modbus RTU
slave.
The connection of the HMI device to Modicon is limited primarily to the physical connection of
the HMI device. Special blocks for the connection are not required in the PLC.
Connection cable
The following connecting cables are available to connect the HMI device to Modicon
Modbus.
Interface to the
HMI device
Modicon PLC
directly via Modbus
interface (RS232) 9-pin
Sub D male connector
Via MB Bridge
(RS 232)
directly via Modbus interface
(RS232) 8-pin RJ45
connector
RS 232, 9-pin PP1 PP1 PP2
The cable pin assignments can be found in Section "Connecting cables for Modicon Modbus
RTU".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2236 System Manual, 08/2011,
Communication types
Enabled types of communication
The following communication types are system-tested and enabled:
Ppoint-to-point connection only via the RS-232 interface.
Multipoint connection from a HMI device (Modbus-Master) with up to 4 PLCs: The HMI
device must be connected with a Modbus Plus Bridge or a Compact, Momentum CPU or
TSX Quantum CPU which is configured as a Modbus Plus Bridge.
You connect the other PLCs via the Modbus Plus connection on the first PLC. The PLCs
can be reached under their address via the bridge functionality of the first PLC.
Note
It is not possible to integrate the HMI device into a Modbus network because the HMI
device is Modbus-Master.
Integration of the HMI device into a Modbus Plus network via the "bridge mode" of the
Compact, Momentum or Quantum (logical point-to-point communication of the HMI device
with a Compact, Momentum or Quantum).
Restrictions
The connection of the HMI device to PLCs of other manufacturers which offer a Modicon
Modbus interface is not system-tested and therefore not approved.
If you use another PLC nevertheless, observe the following information:
These drivers only work for tags with the bit counting method typical for Modicon PLCs from
left (bit1 = most significant bit) to right (bit16 = least significant bit in data type INT).
The address offset displayed in the configuring is subtracted at protocol level in the
message frame. E.g. in Holding Register 4x the offset "40001". The configured address
"40006" therefore becomes address "5" in the message frame. The address (e.g. "5")
transferred in the message frame is transformed to the PLC-specific address range in the
different Non-Modicon PLCs.
A reply message frame without "ExceptionCode" is expected within 500 ms.
The following function codes are used for the respective data areas:
Reading function codes Address range
01 ReadCoilStatus 0x DIGITAL_OUT
02 ReadInputStatus 1x DIGITAL_IN
03 ReadHoldingRegisters 4x USERDATA
04 ReadInputRegisters 3x ANALOG_IN
20 (14Hex) ReadGeneralReference 6x EXTENDEDMEMORY
(not for all CPUs)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2237
Writing function codes Address range
06 PresetSingleRegister 4x USERDATA Single
16 (10Hex) PresetMultipleRegisters 4x USERDATA Multiple
05 ForceSingleCoil 0x DIGITAL_OUT with data type Bit
15 (0FHex) ForceMultipleCoils 0x DIGITAL_OUT with data type 16 bit
group
21 (15Hex) WriteGeneralReference 6x EXTENDEDMEMORY
(not for all CPUs)
Connectable PLCs
Connections can be implemented for the following Modicon Modbus PLCs:
Modicon Modbus PLC Supported protocol
Modicon Modbus RTU
2)
Modicon Modbus TCP/IP
TSX Compact x x
1)
TSX Quantum x x
Momentum x x
Premium - x
Micro - x
M340 20x0 (without 2010) - x
1)
Only via Ethernet TCP/IP-Modbus Plus Bridge
2)
Communication via RS 232 is tested and enabled for the PLC. In the HMI devices which
only have an RS 422/485 interface, the RS 422/232 converter with the order number 6AV6
671-8XE00-0AX0 was tested and approved.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2238 System Manual, 08/2011,
Connecting cables for Modicon Modbus RTU
Connecting cable PP1, RS-232, for Modicon
Point-to-point cable 1: PLC > PC ...
CTS
RTS
DSR
DTR
RxD
TxD
GND
8
7
6
4
2
3
5
1
3
2
5
TxD
RxD
GND
shield
enclosure
Modicon-Modbus
connector 2
9-pin D-Sub connector 9-pin D-Sub female connector
HMl device
connector 1
Cables: 3 x 0.14 mm
2
, shielded,
max. length 15 m
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2239
Connecting cable PP2, RS-232, for Modicon
Point-to-point cable 2: PLC (TSX Compact) > PC...
CTS
RTS
RxD
TxD
GND
7
6
2
3
5
8
3
2
5
TxD
RxD
GND
enclosure
Modicon-Modbus
connector 2
8-pin RJ45 connector 9-pin D-Sub female connector
HMl device
connector 1
shield
Pin 1 is at the top when looking at the controller
Cables: 3 x 0.14 mm
2
, shielded,
max. length 15 m
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2240 System Manual, 08/2011,
Performance features of communication
Permitted data types for Modicon Modbus RTU
Permitted data types
The table lists the data types that can be used when configuring tags and area pointers.
Data type Operand type Length
+/- Double 4x, 6x 4 bytes
+/- Int 3x, 4x, 6x 2 bytes
16-bit group 0x, 1x 2 bytes
ASCII 4x, 6x 0 to 80 characters
Bit
1)
0x, 1x, 3x, 4x, 6x 1-bit
Double 4x, 6x 4 bytes
Float 4x, 6x 4 bytes
Int 3x, 4x, 6x 2 bytes
1)
Note the following for write accesses:
For data type "Bit" with the operand types "4x" and "6x", the entire word is written back
to the PLC following a change to the specified bit. There is no check to determine
whether any other bits in the word have changed. As a result, the PLC only has read
access to the specified word.
The usual bit counting method (16 LSB - 1 MSB) in the following CPU types is only used in
the "HMI tags" editor with the selected "Bit" data type:
Concept ProWORX: Compact, Quantum
The following bit location assignment applies:
Left byte Right byte
Counting with tags 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Format for "Signed"
The placeholder "+/-" stands for the data types "Signed Int" and "Signed Double".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2241
Supported CPU types for Modicon Modbus RTU
CPU types
The following CPU types are supported in the configuration of the Modicon Modbus RTU
communication driver.
Compact
Momentum
Quantum
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2242 System Manual, 08/2011,
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Data exchange
Area pointers for Modicon Modbus
Area pointers for connections via Modicon Modbus communication drivers
You use an area pointer to access a data area in the PLC.
For more detailed information on area pointers and their configuration, refer to Section "Data
exchange using area pointers".
Special considerations for connections via Modicon communication drivers
You can configure the following area pointers
Area pointer Modicon Modbus TCP/IP Modicon Modbus RTU
Screen number Yes Yes
Date/time Yes Yes
Date/time PLC Yes Yes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2243
Area pointer Modicon Modbus TCP/IP Modicon Modbus RTU
Coordination Yes Yes
Project ID Yes Yes
Job mailbox Yes Yes
Data record Yes Yes
Restrictions Modicon Modbus TCP/IP
The following restrictions apply for configuring area pointers.
CPU type Data types File types
Concept, ProWORX: Compact,
Quantum, Momentum
+/- Int, Int 4x, 6x
Unity, PL7: Premium, Micro,
Quantum, M340
+/- Int, Int %MW
Modicon Modbus RTU restrictions
The following restrictions apply for configuring area pointers.
CPU type Data types File types
Concept, ProWORX: Compact,
Quantum, Momentum
+/- Int, Int 4x, 6x
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
For additional information see:
Displaying tags with Runtime Advanced and Panels (Page 940)
Note
The value is read out time-triggered for Basic Panels.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2244 System Manual, 08/2011,
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
The following picture shows the structure of a trend transfer area.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2245
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Permitted data types for trend control
Modicon Modbus TCP/IP
Tags of the following operand types are permitted for CPU type "Concept, ProWORX:
Compact, Quantum, Momentum".
"4x"
"6x"
Tags of the following operand types are permitted for CPU type "Unity, PL7: Premium, Micro,
Quantum, M340".
"%MW"
The tags for trend control must have data type "Int" or "+/- Int" or be an array tag with data
type "Int" or "+/-Int".
You assign a bit to a trend during configuration. This sets a defined bit assignment for all areas.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2246 System Manual, 08/2011,
Modicon Modbus RTU
Tags of the following operand types are permitted for CPU type "Concept, ProWORX:
Compact, Quantum".
"4x"
"6x"
The tags for trend control must have data type "Int" or "+/- Int" or be an array tag with data
type "Int" or "+/-Int".
You assign a bit to a trend during configuration. This sets a defined bit assignment for all areas.
Alarms
Configuring alarms
Configuring alarms for non-integrated connections
Several steps are necessary to configure alarms such as warnings, error messages and
acknowledgement.
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Data types
For connections with a Modicon Modbus communication driver, the following data types are
supported:
PLC Permitted data types
Discrete alarms Analog alarms
All Modicon series Int, +/-Int 16 Bit Group, Int, +/-Int,
Double, +/-Double, Float
Arrays and array tags cannot be used for discrete alarms.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2247
How the bit positions are counted
For connections with a Modicon Modbus communication driver, the following counting method
applies:
How the bit positions are counted Left byte Right byte
In WinCC you configure: 15 1
4
1
3
1
2
1
1
1
0
9 8 7 6 5 4 3 2 1 0
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2248 System Manual, 08/2011,
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2249
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
Omron
Omron communication drivers
Introduction
This section describes the communication between an HMI device and PLCs that use Omron
communication drivers.
The following communication drivers are supported:
Omron Host Link
Data exchange
Data is exchanged by means of tags or area pointers.
Tags
The PLC and the HMI device use process values for data exchange. You create tags in
the configuration that point to addresses in the PLC. The HMI device reads the value from
the defined address, and then displays it. The operator may also enter values on the HMI
device, which are then written to the address in the PLC.
Area pointers
Area pointers are used to exchange specific data and are only set up when these data are
used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2250 System Manual, 08/2011,
Omron Host Link
Configuring a connection via Omron Host Link
Introduction
You configure a connection to a PLC with an Omron Host Link communication driver in the
"Connections" editor of the HMI device.
Note
Connection with Omron Host Link
A connection will not automatically be established when runtime is started if you have
configured a connection via Omron.
A tag which is in the valid PLC memory area must be configured in the runtime start screen.
The connection will otherwise only be established once a corresponding screen has been
selected.
This tag will be accessed when runtime is started and a connection will then be established.
The interfaces are named differently depending on the HMI device.
Requirements
A project is open.
An HMI device has been created.
Procedure
1. Double-click the HMI device under "Devices" in the project tree.
2. Double-click the "Connections" item.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2251
3. Double-click "<Add>" in the "Connections" editor.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2252 System Manual, 08/2011,
4. Select the "Omron Host Link" driver in the "Communication driver" column.
5. Select all necessary connection parameters for the interface in the inspector window under
"Parameters".
Parameters for the connection (Omron Hostlink)
Parameters to be set
To set the connection parameters, such as addresses and profiles, click the connection that
you have created in the "Connections" editor.
The communication partners are displayed schematically in the Inspector window under
"Parameters". The "HMI device" and "PLC" areas are available for assigning parameters
according to the interface used.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2253
Parameters for the HMI device
You can select an interface for the HMI device in the Inspector window under "Parameters".
Depending on the HMI device, there are several interfaces available.
Type
Specifies the physical connection used.
Baud rate
For "Baud rate", you set the transmission speed of the HMI device to OMRON. A baud rate
of 19200 or 9600 can be selected for the communication.
Data bits
For "Data bits", you can choose between "7 bits" and "8 bits".
Parity
For "Parity", you can choose from "None", "Even", and "Odd".
Stop bits
For "Stop bits", you can choose between 1 and 2 bits.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2254 System Manual, 08/2011,
Parameters for the PLC
Station address
For "Station address", set the station number of the connected PLC.
Connecting HMI device to PLC
Connections via Omron Host Link
Connection
The connection of the HMI device to an OMRON PLC is limited primarily to the physical
connection of the HMI device. Special blocks for the connection are not required in the
PLC.
Connection cable
The following connecting cables are available to connect the HMI device to an Omron
PLC.
Interface to the HMI
device
Omron PLC
RS232, 9-pin RS232 I/O port RS422, 9-pin RS422, terminals/
pins
RS232, 9-pin PP1 Programming
cable (standard
cable of Omron)
RS232 via converter Multi-point cable 1
RS422, 9-pin PP2 Multi-point cable 2
Refer to the relevant device manual to determine which HMI device interface is to be used.
Communication types
Approved communication types
The connection from a HMI device to an OMRON-CPU with the Omron Host Link protocol via
RS232 and via RS 422 is system-tested and approved by Siemens AG.
This concerns the following CPU types:
CP1x (CP1L, CP1H, CP1E)
CJ1x(CJ1M, CJ1H, CJ1G)
CJ2H
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2255
CS1x(CS1G, CS1H, CS1D)
CPM2C
Note
Only the following CPU types have been tested and released for Basic Panels, TP 177A
and OP 77A:
CP1x (CP1L, CP1H, CP1E)
CJ1x (CJ1M, CJ1H, CJ1G)
Multipoint connection
A multipoint connection to the up to 4 approved OMRON PLCs in a RS422-four-wire connection
can be implemented with communication modules on the PLCs and is system-tested and
approved by Siemens AG.
Note
The HMI device can only be operated as a master. Exactly one master is possible in the
RS422-four-wire-Multidrop connection.
Connecting cables for Omron Host Link
Connecting cable MP1, RS-232, over converter, for Omron
Multipoint cable 1: MP/TP/PC > PLC
RDA
RDB
TDA
TDB
+5V
SG
TxD
RxD
TDA
TDB
RDA
RDB
TDA
TDB
RDA
RDB
TDA
TDB
RDA
RDB
TDA
TDB
RDA
RDB
ClF-11
1
2
6
8
1
2
6
8
1
2
6
8
GND
RxD
TxD
5
2
3
6
9
2
3
DC 5V, 200mA
(lnrush current max. 0.8 A)
R = On
R = Off
R = Off
R = Off
R = On
HMl device Omron
9-pin D-Sub female
connector
9-pin D-Sub connector
or
6-pin screw terminal
converter
NT-AL001
RS 232 / RS 422
9-pin D-Sub
connector
1)
Inrush current max. 0.8 A
shielded, max. length 500 m
Connecting cable MP2, RS-422, for Omron
Multipoint cable 2: RS422, MP/TP/PC > SPS_
-RxD
+RxD
-TxD
+TxD
9
4
8
3
TDA
TDB
RDA
RDB
TDA
TDB
RDA
RDB
TDA
TDB
RDA
RDB
TDA
TDB
RDA
RDB
ClF-11
1
2
6
8
1
2
6
8
1
2
6
8
Omron
9-pin D-Sub connector
or
6-pin screw terminal
HMl device
9-pin D-Sub connector
R = On
R = Off
R = Off
R = On
shielded, max. length 500 m
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2256 System Manual, 08/2011,
Connecting cable PP1, RS-232, for Omron
Point-to-point cable PP1, PC/TP/OP - PLC
SG
DR
CS
RS
RD
SD
9
7
5
4
3
2
5
8
7
6
4
3
2
GND
CTS
RTS
DSR
DTR
TxD
RxD
enclosure
connector 2
9-pin D-Sub connector
connector 1
9-pin D-Sub female connector
Omron HMl device
shielded, max. length 15 m
Connecting cable PP2, RS-422, for Omron
Point-to-point cable PP2, RS-422
+TxD
-TxD
+RxD
-RxD
1
2
6
8
9
4
8
3
-RxD
+RxD
-TxD
+TxD
R
lnsert resistor 220 ohms / > 150 mW
(e.g. design 0207)
enclosure
connector 2
9-pin D-Sub connector
screw-locking
cable outlet to the rear
connector 1
9-pin D-Sub connector
screw-locking
cable outlet to the rear
Omron HMl device
shielded, max. length 500 m
Performance features of communication
Permissible data types for Omron Host Link
Permitted data types
The table lists the data types that can be used when configuring tags and area pointers.
Data type Operand type Length
Bool I/O, HR, AR, LR, DM, T/
C bit, CPU status
1-bit
Byte CPU type 1 byte
DInt HR, AR, LR, DM 4 bytes
Int I/O, HR, AR, LR, DM, T/
C Val
2 bytes
Real HR, DM 4 bytes
String HR, AR, LR, DM 0 to 80 characters
UDInt HR, AR, LR, DM 4 bytes
UInt I/O, HR, AR, LR, DM, T/
C Val
2 bytes
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2257
Note
Read and write operations of all data areas in the OMRON PLC can only be reliably carried
out in "STOP" or "MONITOR" mode.
"I/O" refers either to the IR/SR area or the CIO area depending on the PLC series. The
operand types "LR", "HR" and "AR" are not available in all PLC series.
Note
Note the following for write accesses:
For the "Bool" data type with the operand types "I/O", "HR", "AR", "LR" and "DM", the entire
word is written back into the PLC when the specified bit is changed. There is no check to
determine whether any other bits in the word have changed. As a result, the PLC only has
read access to the specified word.
Operand type old PLC Operand type CS and CJ PLC
CPU Status CPU Status
I/O CIO
HR H
Range 0-511
AR A
LR n/a 1)
DM D
T/C T/C
CPU type CPU type
1) You do not get an error message when you read or write the LR area in the
following PLCs
CS
CJ
CP
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2258 System Manual, 08/2011,
Supported CPU types for Omron Host Link
CPU types
The following CPU types are supported in the configuration of the Omron Host Link
communication driver.
CP1
CP1L
CP1H
CP1E
CJ1
CJ1M
CJ1H
CJ1G
CJ2
CJ2H
CS1
CS1G
CS1H
CS1D
CPM
CPM2C
Addressing in Omron Host Link
Addressing of PLCs in Omron Host Link
In PLCs of the series CS, CP and CJ, the timers 0-4095 are addressed with T/C 0-2047.
The counters 0-4095 must be addressed with an offset of 2048 (T/C 2048-4095 correspond
to the counters 0-2047). Counters and timers with addresses > 2047 cannot be addressed via
Host Link.
Counters and timers with addresses > 2047 cannot be addressed via Host Link.
Example:
If you want to address counter C20, you must address T/C 20+2048 = T/C 2068.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2259
Commissioning components
Transferring a project to the HMI device
1. Switch the HMI device to "transfer mode".
2. Set all necessary transfer parameters.
Interface
Transfer parameters
Target storage location
3. Start the project transfer.
The project is compiled automatically.
All compilation and transfer steps are logged to a message window.
Interconnecting the PLC with the HMI device
1. Interconnect the PLC with the HMI device using a suitable cable.
2. The message "Connection to PLC .... is established" is output to the HMI device.
Optimizing the configuration
Acquisition cycle and update time
The acquisition cycles for the "Area pointers" and of the tags defined in the configuration
software are decisive in terms of the update times which can actually be achieved.
The update time is equivalent to the acquisition cycle + transmission time + processing time.
Items to observe when optimizing the update times in configuration data:
Optimize the maximum and minimum size of the data areas.
Acquisition cycles which are too short lead to unnecessary load on overall performance.
Set the acquisition cycle according to the rate of change of the process values. The rate of
temperature changes at a furnace, for example, is significantly slower compared to the
speed rate of an electrical drive. A time of approx. 1 second is a benchmark for the
acquisition cycle.
Avoid any gaps when entering the alarm or screen tags in a data area.
Changes in the PLC can only be detected reliably if these are available at least within the
actual acquisition cycle.
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized.
Only configure short acquisition cycles for objects which actually require shorter refresh cycles.
This procedure reduces update times.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2260 System Manual, 08/2011,
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend
transfer area". It resets the bits in the next cycle.
The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication
between the HMI device and the PLC.
The HMI device confirms acceptance of the job mailbox by entering the value zero in the first
data word of the job mailbox. The HMI device now processes the job for which it requires a
certain time slice. It may take the HMI device some time to process a new job mailbox which
is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted
if sufficient computing resources are available.
Data exchange
Area pointers for Omron
Area pointers in connections via Omron communication drivers
You use an area pointer to access a data area in the PLC.
For more detailed information on area pointers and their configuration, refer to Section:
"Data exchange using area pointers".
Special features of connections via Omron Host Link
Area pointers can only be created in the following "File types": "DM", "I/O", "HR", "AR", and
"LR".
Trends
General information on trends
Trends
A trend is the graphical representation of one or more values from the PLC. The value is read
out either time- or bit-triggered, depending on the configuration.
For additional information see:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2261
Displaying tags with Runtime Advanced and Panels (Page 940)
Note
The value is read out time-triggered for Basic Panels.
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
Time-triggered trends are suitable for continuous curves, such as the operating temperature
of a motor.
Bit-triggered trends
Through a trigger bit set in the trend request tag, the HMI device either reads in a trend value
or an entire trend buffer. This setting is defined in the configuration. Bit-triggered trends are
normally used to represent fast changing values. One example might be the injection pressure
in the production of plastic parts.
To trigger bit-triggered trends, appropriate external tags must be created in the "HMI tags"
editor and connected to trend areas during configuration. The HMI device and PLC then
communicate with each other via these trend areas.
The following areas are available for trends:
Trend request area
Trend transfer area 1
Trend transfer area 2 (required only with switch buffers)
Trend request and trend transfer
Trend request area
The HMI device sets corresponding bits in the trend request area when you open a screen
which contains one or more trends on the HMI device. After closing the screen, the HMI device
resets the relevant bits in the trend request area.
The trend request area can be used for evaluation purposes in the PLC to determine which
trend is currently being displayed on the HMI device. Trends can also be triggered without
evaluation of the trend request area.
Trend transfer area 1
This area is used to trigger trends. You must set the bit assigned to the trend in the trend
transfer area and set the trend group bit in your control program. The trend group bit is the last
bit in the trend transfer area.
The HMI device detects the trigger. The HMI device reads either a value or the entire buffer
from the PLC. It then resets the trend bit and the trend group bit.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2262 System Manual, 08/2011,
The following picture shows the structure of a trend transfer area.
15 8 7 0
high-order byte
1st word
nth word
low-order byte
Trend group bit
Bit number
The trend transfer area must not be modified by the PLC program until the trend group bit has
been reset.
Trend transfer area 2
Trend transfer area 2 is required for trends configured with a switch buffer. The trend transfer
areas 1 and 2 have a similar structure.
Switch buffer
The switch buffer is a second buffer for the same trend that can be set up during configuration.
The PLC writes to Buffer 2 while the HMI device reads values from Buffer 1, and writes to
Buffer 1 when the HMI device is reading Buffer 2. This prevents the PLC from overwriting trend
values while the trend is being read by the HMI device.
Restrictions to the trend control
For Omron Host Link communication drivers
Tags of "Operand type" "DM", "I/O", "HR", "AR" or "LR" are permitted.
They must be data type "UInt", "Int" or an array tag of data type "UInt", "Int". You assign a bit
to a trend during configuration. This sets a defined bit assignment for all areas.
Alarms
Configuring alarms
Configuring alarms for non-integrated connections
Several steps are necessary to configure alarms such as warnings, error messages and
acknowledgement.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2263
Step 1: Create tags
Step 2: Configure alarms
Step 3: Configure acknowledgment
You can find additional information in the section:
Working with Alarms (Page 963)
Distinctive features when configuring alarms
If you are configuring connections of HMI devices to PLCs of other manufacturers, note the
following distinctive features when configuring:
Data types of the tags
Addressing of tags
How the bit positions are counted
Data types
For connections with an Omron communication driver, the following data types are supported:
PLC Permitted data types
Discrete alarms Analog alarms
CP1, CJ1, CJ2, CS1, CPM Uint, int UInt, Int,
UDInt, DInt
How the bit positions are counted
For connections with an Omron communication driver, the following counting method applies:
How the bit positions are
counted Left byte Right byte
In Omron
PLCs
15 8 7 0
In WinCC you configure: 15 8 7 0
Only tags for the "DM", "I/O", "HR", "AR", and "LR" file types are allowed for use as a trigger
tag for discrete alarms.
Configuring discrete alarms
Use arrays for discrete alarms and append each individual alarm to one bit of the array tags
themselves and not to the individual subelements.
Only tags for the "DM", "I/O", "HR", "AR", LR" areas and the "Int" and "UInt" file types are
permitted for discrete alarms and arrays.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2264 System Manual, 08/2011,
Acknowledgment of alarms
Procedure
Create suitable tags on the PLC to acknowledge an error alarm. You assign these tags to an
alarm in the "Bit messages" editor. You make the assignment in "Properties >
Acknowledgment".
Distinction in terms of acknowledgment:
Acknowledgment by the PLC
Acknowledgment on the HMI device
Acknowledgment by the PLC
In "Write acknowledgment tag", you configure the tag or the array tag and the bit number based
on which the HMI device can recognize an acknowledgment by the PLC.
A bit set in the tag triggers acknowledgment of the assigned error alarm bit at the HMI device.
This tag bit returns a function similar to acknowledgment on the HMI device which is triggered
by pressing the "ACK" button, for example.
The acknowledgment bit must be located in the same tag as the bit for the error alarm.
Reset the acknowledgment bit before setting the bit in the alarm area again. The figure below
shows the pulse diagram.
New
error alarm
Reset of
acknowledgm. bit
Acknowledgm.
via PLC .
Arrival of the
error alarm
Acknowledgment
PLC HMl device
Error alarm
Acknowledgment on the HMI device
In "Read acknowledgment tag", you configure the tag or the array tag and the bit number that
is written to the PLC after acknowledgment from the HMI device. Make sure when you use an
array tag that it is not longer than 6 words.
To always create a signal change when setting an assigned acknowledgment bit of a discrete
alarm that must be acknowledged, the HMI device will reset the acknowledgment bit assigned
to the alarm as soon as it detects an alarm subject to acknowledgment and write the
acknowledgment tag in the PLC. There will be a certain delay between detecting the message
and writing the acknowledgment tag in the PLC because the HMI device has to process the
operations.
If a discrete alarm subject to acknowledgment is acknowledged by the HMI device, then the
corresponding bit in the assigned acknowledgment tag will be set. The entire acknowledgment
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2265
tag is then written to the PLC by the HMI device. This allows the PLC to recognize that a certain
alarm message has been acknowledged at the HMI device.
Note
All alarm bits acknowledged since the last Runtime start will remain in the acknowledgment
tag until a new incoming of the respective discrete alarms is detected.
This area should only be read by the PLC because the entire section of the HMI device will
be overwritten once the next acknowledgment tag is written.
The figure below shows the pulse diagram.
New
error alarm
Acknowledgm.
via HMl device
Reset of
acknowledgm. bit
Arrival of the
error alarm
Acknowledgment
HMl device PLC
Error alarm
LED mapping
Function
Keyboard devices have LEDs in the function keys. These LEDs can be activated from the PLC.
Thus, it is possible, for example, to signal to the user which key he should press in a given
situation by lighting up an LED.
Note
The LED function cannot be configured for Basic Panels.
Requirements
In order to activate an LED, an LED tag or an array tag must be set up in the PLC and specified
as an LED tag during configuration.
LED assignment
The assignment of the individual LEDs to the bits in the LED tags is specified when the function
keys are configured. In this process, the "LED tag" and the assigned "Bit" are specified for
each function key in the "General" group of the properties window.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2266 System Manual, 08/2011,
The "Bit" bit number designates the first of two consecutive bits that control the following LED
statuses.
Bit n+ 1 Bit n
LED function
All Mobile Panels, all Operator Panels,
all Multi Panels Panel PCs:
0 0 Off Off
0 1 Rapid flashing Flashing
1 0 Slow flashing Flashing
1 1 On permanently On permanently
9.11.12.5 Data exchange using area pointers
General information on area pointers
Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC
and the HMI device alternately access these data areas for read and write operations.
The PLC and the HMI device trigger defined interactions based on the evaluation of stored
data.
Configuration of area pointers
Before you use the area pointer, you enable it in "Connections Area pointers". You then
assign the area pointer parameters.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2267
Active
Enables the area pointer.
Pointer name
Name of the area pointer specified by WinCC.
PLC tag
Here you select the PLC tag or the tag array that you have configured as the data area for
the area pointer.
Address
No address is entered into this field because of the symbolic access.
Length
WinCC specifies the length of the area pointer.
Acquisition cycle
You specify the acquisition cycle in this field for area pointers that are read by the HMI
device. Note that a very short acquisition time may have a negative impact on HMI device
performance.
Comment
Enter a comment, for example, to describe the purpose of the area pointer.
Accessing data areas
Accessing data areas
The following table shows how HMI devices and PLCs access individual data areas for read
(R) or write (W) operations.
Data area Required for HMI device PLC
Screen number Evaluation by the PLC in order to determine the active screen. W R
Data record Transfer of data records with synchronization R/W R/W
Date/time Transfer of the date and time from the HMI device to the PLC W R
Date/time PLC Transfer of the date and time from the PLC to the HMI device R W
Coordination Requesting the HMI device status in the PLC program W R
Project ID Runtime checks for consistency between the WinCC project
ID and the project in the PLC
R W
Job mailbox Triggering of HMI device functions by the PLC program R/W R/W
"Screen number" area pointer
Function
The HMI device saves information about the screen called on the HMI device to the "Screen
number" area pointer.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2268 System Manual, 08/2011,
This allows the transfer of the current screen contents from the HMI device to the PLC. The
PLC can trigger specific reactions such as the call of a different screen.
Use
Configure and enable the area pointer in "Communication > Connections" before you put it
into use. You can create only one instance of the "Screen number" area pointer and only on
one PLC.
The screen number is always transferred to the PLC when a new screen is activated or when
the focus within a screen changes from one screen object to another.
Structure
The area pointer is a data area in the memory of the PLC with a fixed length of 5 words.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1. word Current screen type
2. word Current screen number
3. word Reserved
4th word Current field number
5. word Reserved
Current screen type
"1" for root screen or
"4" for permanent window
Current screen number
1 to 32767
Current field number
1 to 32767
"Date/time" area pointer
Function
This area pointer is used to transfer the date and time from the HMI device to the PLC.
The PLC writes control job "41" to the job mailbox.
When it evaluates the control job, the HMI device writes its current date and the time in the
data area configured in the "Date/time" area pointer. All definitions are coded in BCD format.
The "Date/Time" area pointer when used in a project which contains multiple connections must
be enabled for each configured connection.
The date/time data area has the following structure:
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2269
Data word Left byte Right byte
15 8 7 0
n+0 Reserved Hour (0 to 23)
Time
n+1 Minute (0 to 59) Second (0 to 59)
n+2 Reserved Reserved
n+3 Reserved Weekday (1 to 7, 1=Sunday)
Date
n+4 Day (1 to 31) Month (1 to 12)
n+5 Year (80 to 99/0 to 29) Reserved
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29result in the years 2000 through 2029.
"Date/time PLC" area pointer
Function
This area pointer is used to transfer the date and time from the PLC to the HMI device. Use
this area pointer if the PLC is the time master.
The PLC loads the data area of the area pointer. All definitions are coded in BCD format.
The HMI device reads the data cyclically within the configured acquisition cycle and
synchronizes itself.
Note
Set an acquisition cycle of sufficient length for the date/time area pointer in order to avoid
any negative impact on HMI device performance.
Recommended: Acquisition cycle of 1 minute if your process can handle it.
The "Date/time PLC" data area has the following structure:
Data word Left byte Right byte
15 . . . . . . 8 7 . . . . . . 0
n+0 Year (80 to 99/0 to 29) Month (1 to 12)
n+1 Day (1 to 31) Hour (0 to 23)
n+2 Minute (0 to 59) Second (0 to 59)
n+3 Reserved Reserved Weekday
(1 to 7,
1=Sunday)
n+4
1)
Reserved Reserved
n+5
1)
Reserved Reserved
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2270 System Manual, 08/2011,
1) The two data words must exist in the data area to ensure that the data format matches
WinCC and to avoid reading false information.
Note
Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and
the values 0 to 29result in the years 2000 through 2029.
"Coordination" area pointer
Function
The "Coordination" area pointer is used to implement the following functionality:
Detecting the startup of the HMI device in the control program
detection in the control program of the current HMI device operating mode
detection in the control program of the HMI devices ready to communicate state
The "Coordination" area pointer has a length of one word.
Use
Note
The HMI device always writes the entire coordination area when updating the area pointer.
The control program may not make changes to the coordination area for this reason.
Assignment of bits in the "Coordination" area pointer
0 1 2 7 8 15
X X X
high-order byte
1st word
= reserved
x = assigned
2st word not assigned
low-order byte
Startup bit
Operation mode
Life bit
Startup bit
The startup bit is set briefly to "0" by the HMI device during startup. It sets the bit permanently
to "1" when startup is completed.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2271
Operating mode
The operating mode bit is set to 1 as soon as the user switches the HMI device offline. The
state of the operating mode bit is "0" during normal operation of the HMI device. You can
determine the current operating mode of the HMI device by reading this bit.
Life bit
The HMI device inverts the life bit at intervals of approximately one second. You can check
whether or not the connection to the HMI device is still up by querying this bit in the control
program.
"Project ID" area pointer
Function
You can check whether the HMI device is connected to the correct PLC at the start of runtime.
This check is important when operating with several HMI devices.
The HMI device compares a value stored on the PLC with the value specified in configuration.
This ensures compatibility of configuration data with the control program. If discrepancy is
detected, a system event is displayed on the HMI device and runtime is stopped.
Use
To use this area pointer, set up the following during the configuration:
Define the version of configuration. Possible values between 1 and 255.
You enter the version in the editor "Runtime settings > General" in the "Identification" area.
Data address of the value for the version that is stored in the PLC:
You enter the data address in the editor "Communication > Connections".
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in
all the other connections in the project being switched to "offline".
This behavior has the following prerequisites:
You have configured several connections in a project.
You are using the "project ID" area pointer in at least one connection.
Causes which may set connections "offline":
The PLC is not available.
The connection has been switched offline in the engineering system.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2272 System Manual, 08/2011,
"PLC job" area pointer
Function
The PLC can use the job mailbox to transfer jobs to the HMI device to trigger corresponding
actions on the HMI device. These functions include, for example:
Display screen
Set date and time
Data structure
The first word of the job mailbox contains the job number. Depending on the job mailbox, up
to three parameters can be transferred.
Word Left byte Right byte
n+0 0 Job number
n+1 Parameter 1
n+2 Parameter 2
n+3 Parameter 3
The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This
means that the parameters must be entered in the job mailbox first, followed by the job number.
When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution
of the job mailbox is generally not completed at this point in time.
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job
number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI
device is online.
Note
Please note that not all HMI devices support job mailboxes.
No
.
Function
14 Setting the time (BCD coded)
Parameter 1 Left byte: -
Right byte: hours (0-23)
Parameter 2 Left byte: minutes (0-59)
Right byte: seconds (0-59)
Parameter 3 -
15 Setting the date (BCD coded)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2273
No
.
Function
14 Setting the time (BCD coded)
Parameter 1 Left byte: -
Right byte: weekday
(1-7: Sunday-Saturday)
Parameter 2 Left byte: day (1-31)
Right byte: month (1-12)
Parameter 3 Left byte: year
23 User logon
Logs the user on with the name "PLC user" at the HMI device with the group number transferred
in Parameter 1.
The logon is possible only when the transferred group number exists in the project.
Parameter 1 Group number 1 to 255
Parameter 2, 3 -
24 User logoff
Logs off the current user.
(The function corresponds to the "logoff" system function)
Parameter 1, 2, 3 -
40 Transfer date/time to PLC
(in the S7 format DATE_AND_TIME)
An interval of at least 5 seconds must be maintained between two successive jobs to prevent
overload of the HMI device.
Parameter 1, 2, 3 -
41 Transfer date/time to PLC
(In OP/MP format)
An interval of at least 5 seconds must be maintained between successive jobs in order to prevent
overload of the HMI device.
Parameter 1, 2, 3 -
46 Update tags
Causes the HMI device to read the current value of the tagsfrom the PLC whose update ID
matches the value transferred in parameter 1.
(Function corresponds to the "UpdateTag" system function.)
Parameter 1 1 - 100
49 Delete alarm buffer
Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer.
Parameter 1, 2, 3 -
50 Delete alarm buffer
Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer.
Parameter 1, 2, 3 -
51 Screen selection
1)
Parameter 1 Screen number
Parameter 2 -
Parameter 3 Field number
69 Read data record from PLC
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2274 System Manual, 08/2011,
No
.
Function
14 Setting the time (BCD coded)
Parameter 3 0: Do not overwrite existing data record
1: Overwrite existing data record
70 Write data record to PLC
Parameter 1 Recipe number (1-999)
Parameter 2 Data record number (1-65535)
Parameter 3 -
1)
OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job
mailbox if the on-screen keyboard is active.
"Data record" area pointer
"Data mailbox" area pointer
Function
When data records are transferred between the HMI device and PLC, both partners access
common communications areas on the PLC.
Data transfer types
There are two ways of transferring data records between the HMI device and PLC:
Transfer without synchronization
Transfer with synchronization over the data record
Data records are always transferred directly. That is, the tag values are read from an address
or written to an address configured for this tag directly, without redirecting the values by means
of interim memory.
Initiating the transfer of data records
There are three ways of triggering the transfer:
Operator input in the recipe view
Job mailboxes
The transfer of data records can also be triggered by the PLC.
Triggering by configured functions
If the transfer of data records is triggered by a configured function or by a job mailbox, the
recipe view on the HMI device remains operable. The data records are transferred in the
background.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2275
Simultaneous processing of several transfer requests is, however, not possible. In this case,
the HMI device rejects the other transfer requests with a system event.
Transfer without synchronization
If you select asynchronous transfer of data records between the HMI device and PLC, there
is no coordination over the common data areas. It is therefore unnecessary to set up a data
area during configuration.
Asynchronous data record transfer can be a useful alternative, for example, when:
The system is capable of excluding the risk of uncontrolled overwriting of data by the
communication peer.
The PLC does not require information about the recipe number and data record number.
The transfer of data records is triggered by the operator of the HMI device.
Reading values
When a read job is triggered, the values are read from the PLC addresses and transferred to
the HMI device.
Triggering by the operator in the recipe view:
The values are downloaded to the HMI device. You can then process, edit, or save these
values, for example.
Triggering by a function or job mailbox:
The values are saved immediately to the data volume.
Writing values
When a write job is triggered, the values are written to the PLC addresses.
Triggering by the operator in the recipe view:
The current values are written to the PLC.
Triggering by a function or job mailbox:
The current values are written to the PLC from the data medium.
Transfer with synchronization
If you select synchronous transfer, both communication partners set status bits in the common
data area. You can use this mechanism to prevent uncontrolled overwriting of data in either
direction in your control program.
Application
Synchronous data record transfer can be a useful solution, for example, when:
The PLC is the "active partner" in the transfer of data records.
The PLC evaluates the information about the recipe number and data record number.
The transfer of data records is triggered by means of a Job mailbox.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2276 System Manual, 08/2011,
Requirements
In order to synchronize transfer of data records between the HMI device and the PLC, the
following requirements must be met during configuration:
An area pointer has been set up: "Communication > Connections" editor in "Area pointer".
The PLC with which the HMI device synchronizes transfer of data records is specified in
the recipe:
"Recipes" editor in the inspector window the option "Coordinated transfer of data records"
under "General > Synchronization > Settings"
Structure of the data area
The data area has a fixed length of 5 words. Structure of the data area:
15 0
1. Word Current recipe number (1 - 999)
2. Word Current data record number (0 - 65535)
3. Word Reserved
4. Word Status (0, 2, 4, 12)
5. Word Reserved
Status
The status word (word 4) can adopt the following values:
Value Meaning
Decimal Binary
0 0000 0000 Transfer permitted, data record free
2 0000 0010 Transferring.
4 0000 0100 Transfer completed without error
12 0000 1100 Transfer completed with error
Sequence of a transfer started by the operator in the recipe display
Reading from the PLC started by the operator in the recipe view
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe number to be read and the status
"Transferring" in the data record and sets the data record number to
0.
Abort with system
event.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2277
Step Action
3 The HMI device reads the values from the PLC and displays them in
the recipe view.
If the recipes have synchronized tags, the values from the PLC are
also written to the tags.
4 The HMI device sets the status "Transfer completed."
5 The control program must reset the status word to zero in order to
enable further transfers.
Writing to the PLC started by the operator in the recipe view
Step Action
Check: Status word = 0?
1 Yes No
The HMI device enters the recipe and data record number to be
written and the status "Transferring" in the data record.
Abort with system
event.
2 The HMI device writes the current values to the PLC.
If the recipes have synchronized tags, the changed values are
synchronized between the recipe view and tags and then written to
the PLC.
3 The HMI device sets the status "Transfer completed."
4 If required, the control program can now evaluate the transferred
data.
5 The control program must reset the status word to zero in order to
enable further transfers.
Note
The status word may only be set by the HMI device. The PLC may only reset the status word
to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency is
detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Sequence of the transfer triggered by a PLC job
The transfer of data records between the HMI device and the PLC can be initiated by either
one of these stations.
The two job mailboxes No. 69 and No. 70 are available for this type of transfer.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2278 System Manual, 08/2011,
No. 69: Read data record from PLC ("PLC DAT")
Job mailbox no. 69 transfers data records from the PLC to the HMI device. The job mailbox is
structured as follows:
Left byte (LB) Right byte (RB)
Word 1 0 69
Word 2 Recipe number (1-999)
Word 3 Data record number (1 to 65535)
Word 4 Do not overwrite existing data record: 0
Overwrite existing data record: 1
No. 70: Write data record to PLC ("DAT PLC")
Job mailbox No. 70 transfers data records from the HMI device to the PLC. The job mailbox
is structured as follows:
Left byte (LB) Right byte (RB)
Word 1 0 70
Word 2 Recipe number (1-999)
Word 3 Data record number (1 to 65535)
Word 4
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified in
the job and the status "Transferring" in the data record.
Abort without
return message.
3 The HMI device reads the values from the PLC and saves these to the
data record defined in the job mailbox.
4 If "Overwrite" was selected in the job, an existing data record is
overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "Do not overwrite" was selected in the job, and the data record
already exists, the HMI device aborts the job and enters 0000 1100
in the status word of the data record.
5 The control program must reset the status word to zero in order to enable
further transfers.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2279
Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70)
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number specified in
the job and the status "Transferring" in the data record.
Abort without
return message.
3 The HMI device fetches the values of the data record specified in the
function from the data medium and writes the values to the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order to enable
further transfers.
Sequence of the transfer when triggered by a configured function
Reading from the PLC using a configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
record.
Abort with system
event.
3 The HMI device reads the values from the PLC and stores them
in the data record specified in the function.
4 If "Yes" was selected for the "Overwrite" function, an existing
data record is overwritten without any prompt for confirmation.
The HMI device sets the status "Transfer completed."
If "No" was selected for the "Overwrite" function and the data
record already exists, the HMI device aborts the job and
enters 0000 1100 in the status word of the data record.
5 The control program must reset the status word to zero in order
to enable further transfers.
Writing to the PLC by means of configured function
Step Action
1 Check: Status word = 0?
Yes No
2 The HMI device enters the recipe and data record number
specified in the function and the status "Transferring" in the data
record.
Abort with system
event.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2280 System Manual, 08/2011,
Step Action
3 The HMI device fetches the values of the data record specified
in the function from the data medium and transfers the values to
the PLC.
4 The HMI device sets the status "Transfer completed."
5 The control program can now evaluate the transferred data.
The control program must reset the status word to zero in order
to enable further transfers.
Possible causes of error when transferring data records
Possible causes of error
The section below shows possible error causes which lead to the cancellation of data record
transfer:
Tag address not set up on the PLC
Overwriting data records not possible
Recipe number does not exist
Data record number does not exist
Note
The status word may only be set by the HMI device. The PLC may only reset the status
word to zero.
Note
The PLC may only evaluate the recipe and data record numbers when data inconsistency
is detected if one of the conditions outlined below has been met:
The data mailbox status is set to "Transfer completed".
The data mailbox status is set to "Transfer completed with error".
Reaction to an aborted transfer due to errors
If the transfer of data records is aborted due to errors, the HMI device reacts as follows:
Triggering by the operator in the recipe view
Information in the status bar of the recipe view and output of system alarms
Triggered by function
Output of system alarms
Triggering by job mailbox
No return message on the HMI device
You can nonetheless evaluate the status of the transfer by querying the status word in the data
record.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2281
9.11.13 Special features of WinAC MP
9.11.13.1 WinAC MP basics
WinAC MP basics
WinAC MP is a software package for HMI devices. WinAC MP integrates a software PLC
compatible with SIMATIC S7 in WinCC Runtime.
Using WinAC MP you can execute STEP 7 programs on the HMI device.
The common use of WinAC MP and WinCC provides process control and visualization on one
HMI device.
The communications driver for WinAC MP supports the following protocols for controlling the
process components:
Industrial Ethernet
PROFIBUS DP
The following screen shows the principal connection of the process components on the
PROFIBUS DP example.
HMl device
MP 277
Configuration PC
PG/PC
ET 200pro
lndustrial Ethernet
PROFlBUS DP
ET 200 S
S7-300
S7-400
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2282 System Manual, 08/2011,
If you wish to control your process using an HMI device and WinAC MP, then you must install
WinAC MP on your configuration PC. Then transfer WinAC MP and the project to your HMI
device.
Note
Notes about instructions
The following describes how to install WinAC MP and transfer WinAC MP to an HMI device.
To transfer a STEP 7 project with a WinAC MP controller to an HMI device, you require
experience with STEP 7.
9.11.13.2 Communication options with WinAC MP
Definition of "routing"
If there are stations in an automation system that are not connected to the same bus, these
stations cannot be accessed directly online. To establish a connection to these devices, a
router must be included between them.
An MP x77 HMI device with WinAC MP can function as the router. As a router, it connects the
Ethernet and PROFIBUS networks.
You can use routing, for example, to do the following:
Download STEP 7 user programs
Download a hardware configuration
Execute testing and diagnostics functions
Definition of "Softbus"
Virtual bus that allows data exchange between WinCC Runtime and WinAC MP. This bus is
also installed when you install WinCC . After installing WinAC MP, S7 connections from WinCC
Runtime to external stations on PROFIBUS or Ethernet are routed over Softbus.
Prior to installation of WinAC MP (without Softbus)
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2283
HMl - RT
PROFlBUS PROFlNET
Operating system
After installation of WinAC MP (with Softbus)
HMl - RT WinAC MP
PROFlBUS PROFlNET
Softbus
Operating system
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2284 System Manual, 08/2011,
Routing from Ethernet to PROFIBUS DP with WinAC MP
With STEP 7 on Industrial Ethernet, you can access all nodes on PROFIBUS DP from the HMI
device. With WinCC, you can access the HMI device but not the nodes connected over
PROFIBUS DP.
If the configuration PC is not connected directly to PROFIBUS DP, the nodes on PROFIBUS
can nevertheless be reached because the MP x77 HMI device serves as a router.
l-slave
WinCC
WinAC MP
lndustrial Ethernet
ET 200
PROFlBUS DP
STEP 7
WinCC RT
S7-CPU
Figure 9-2 Routing from Ethernet to PROFIBUS DP with WinAC MP
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2285
Routing from PROFIBUS DP to Ethernet with WinAC MP
With STEP 7 on PROFIBUS DP, you can access all nodes on Industrial Ethernet from the HMI
device. With WinCC on PROFIBUS DP, you have access to the HMI device and to OPs
connected over PROFIBUS DP.
l-slave
Drive
OP
WinCC WinAC MP
lndustrial Ethernet
ET 200
PROFlBUS DP
STEP 7 WinCC RT
S7-CPU
Figure 9-3 Routing with WinAC MP over PROFIBUS
Visualization over WinAC MP
Visualization over the HMI device between Industrial Ethernet and PROFIBUS DP is possible
with WinCC.
It is not necessary to program the communication links. A PC serves as the visualization
platform.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2286 System Manual, 08/2011,
l-slave
Drive
OP
PROFlBUS DP
WinAC MP
WinAC MP
lndustrial Ethernet
ET 200
WinCC RT
S7-CPU
WinCC RT
S7-CPU
Figure 9-4 Visualization over WinAC MP
CPU-CPU communication over WinAC MP
CPU-CPU communication is possible with the HMI device.
l-slave
Drive
OP
WinAC MP
PUT/GET
BSEND/BRCV
S7-CPU
lndustrial Ethernet
ET 200
PROFlBUS DP
WinCC RT
S7-CPU
Figure 9-5 CPU-CPU communication over WinAC MP
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2287
9.11.13.3 Standard procedure for communication with WinAC MP
Overview
The section below shows how to configure WinAC MP in a SIMATIC HMI station using a
configuration PC on which STEP 7 and WinCC are installed.
The configuration PC and WinAC MP in a SIMATIC HMI station are interconnected via
PROFIBUS DP. Configuration via Ethernet is also possible. A description of the procedure can
be found in the "WinAC MP" manual.
You can integrate DP slaves for WinAC MP in the STEP 7 project.
WinCC
WinAC MP
ET 200
PROFlBUS DP
WinCC RT
OP
STEP 7
l-slave
Drive
Configuration PC HMl device
Procedure
The basic steps are as follows:
1. Configure WinAC MP in STEP 7.
2. Create a connection between WinAC MP and WinCC Runtime.
3. In STEP 7, download the configuration to WinAC MP.
4. Configure (visualization) HMI objects with WinCC .
5. Download the (visualization) configuration (for example, visualization with histogram) from
WinCC to the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2288 System Manual, 08/2011,
9.11.13.4 Configuring the WinAC MP communications driver
Requirements for the use of WinAC MP
Requirements
In order to use WinAC MP in the process control, you must perform the installation and
development steps on your configuration PC. Transfer the necessary components to the HMI
device.
Basic procedure
The following steps are described in more detail in the following:
1. Check that your system meets the system requirements:
STEP 7 and the authorization are installed on the configuration PC.
WinCC and the authorization are installed on the configuration PC.
WinCC Runtime and ProSave were installed along with WinCC.
2. When WinCC is installed, the WinAC MP option is also automatically installed. Authorization
of the WinAC MP is carried out via separate licenses.
The following components are installed alongside WinAC MP:
WinAC MP Runtime files
WinAC MP system library
3. Develop a STEP 7 project for controlling your process with WinAC MP on the HMI device.
4. Develop a WinCC project for operating and visualizing your controller.
5. Connect the process components via the PROFIBUS network and configure the hardware.
6. Transfer the WinAC MP Runtime files from the configuration PC to the HMI device.
Use ProSave for this.
7. Transfer the WinAC MP authorization from its storage location to the HMI device.
Use the Automation License Manager for this.
8. Transfer the STEP 7 project to the HMI device.
9. Transfer WinCC Runtime and the WinCC project to the HMI device.
To do this, use the "Transfer" function.
Changing the device type
Introduction
There are different ways to create a SIMATIC HMIstation with an HMI device and a configured
WinAC MP controller.
Procedure 1
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2289
Create an HMI device in a SIMATIC HMIstation in the device and network view. Then add the
corresponding variant of WinAC MP.
The advantage of this procedure is that you can choose the device type (MP 177, MP 277 or
MP 377) and the design of the device type (monitor size and touch or key) directly on selection
in the hardware catalog.
Procedure 2
Insert the desired variant of WinAC MP directly in the device and network view.
This procedure creates, by default, the largest touch design of the selected HMI device in the
device and network view.
Changing the device type
Select a device. You can change the device type using the shortcut menu command "Change
device". When the device type MP277 is changed to MP377 and MP 177 or vice versa with a
configured WinAC MP controller in a SIMATIC HMI station, the WinAC MP controller is
automatically moved to the storage location of the non slotted modules. It can therefore not
be used in the new HMI device. If the the device type is changed, the WinAC MPconfiguration
must be created again.
Connecting the configuration PC and HMI device
Procedure for creating a connection via Ethernet or PROFIBUS DP
Basic procedure
WinAC MP supports the communication between the configuration PC and the HMI device via
the following connections:
Industrial Ethernet
PROFIBUS DP
USB
To achieve successful communication, follow these steps:
1. Connect the configuration PC to the HMI device.
2. Make the parameter settings for data transfer on the control panel.
3. Make the parameter settings for data transfer on the configuration PC.
4. Set the communications parameters in ProSave.
With ProSave you can load the WinAC MP Runtime files in the HMI device. Therefore, you
must set the communication parameters both in ProSave as well as on the HMI device.
5. Set the communications parameters in WinCC flexible.
Use WinCC flexible to load your project in the HMI device using the "Transfer" function.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2290 System Manual, 08/2011,
Establishing a connection over Ethernet
Connect the configuration PC to the HMI device (Ethernet)
In order to communicate via an Ethernet network you can either use a direct connection or a
networked connection.
To connect a configuration PC to an HMI device via Ethernet, follow these steps:
1. Connect the interfaces of the configuration PC and the HMI device with an Ethernet cable.
Note
Use a crossover cable to create a direct connection between the configuration PC and
the HMI device.
To connect the configuration PC and the HMI device to an Ethernet (LAN) use a 1 to 1
cable with RJ45 connector.
The interface to be used on the HMI device can be established from the operating
instructions of your HMI device.
Configuring the transmission settings in the Control Panel (Ethernet)
Requirements
The configuration PC and HMI device are connected to each other over an Ethernet cable.
Setting up an IP address on the control panel
The set up the IP address on the control panel, follow these steps:
1. Switch on the HMI device.
Before the HMI device opens an existing project, the "Loader" selection field appears.
2. Select "Control Panel".
3. Double click on the "Network and Dial-up Connection" symbol.
4. Double-click on the LAN connection.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2291
5. Select the "IP Adress" tab.
6. Select "Specify an IP address".
7. Enter the IP address and the subnet mask that you were given by your network
administrator.
8. Confirm your entries with "OK".
Entering transfer settings
To make the data transfer settings, follow these steps:
1. In the control panel, double click on the "Transfer" symbol.
2. Select the "Channel" tab.
3. Select the "Ethernet" option in the "Channel 2" area.
4. Enable "Enable Channel" and confirm your entries.
5. Click "OK" and end the dialog "Transfer Settings".
The transmission settings are configured on the configuration PC
Requirement
The configuration PC and HMI device are connected to each other over an Ethernet cable
The data transfer settings have been made on the control panel
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2292 System Manual, 08/2011,
Procedure
To make the data transfer settings on the configuration PC, follow these steps:
1. Open the network settings of your PC.
2. Select the "Internet Protocol (TCP/IP)".
3. Enable the "General" tab.
4. Select the "Use the following IP address" check box in the protocol properties.
5. Enter an "IP address".
6. Enter a "subnetwork mask".
7. Confirm your entries.
Note
The IP addresses of the configuration PC and the HMI device must not be the same.
The subnet mask must be the same for the configuration PC and the HMI device.
Set the communication parameters (Ethernet)
Requirement
The configuration PC and HMI device are connected to each other over an Ethernet cable
The data transfer settings have been made on the control panel
The data transfer settings have been made on the configuration PC
Procedure
To make the communications parameter settings in ProSave, follow these steps:
1. Make the transfer settings first.
2. To do this, select the desired component in the project tree.
3. Select the "Download to device > Software" command in the shortcut menu.
If you have not already established an online connection, the "Extended download to
device" dialog will automatically open. In this case, set all the necessary parameters for
the connection and click "Load".
If you have already defined an online connection, the project data will be compiled
immediately and the "Load preview" dialog will open. This dialog displays messages
and proposes actions necessary for uploading.
4. Select the "Options" command from the "Online > HMI device maintenance" menu to start
ProSave .
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2293
5. Select an element under "Available options".
6. Click ">>".
Setting the communication parameters in WinCC (Ethernet)
Requirement
The configuration PC and HMI device are connected to each other over an Ethernet cable.
The data transfer settings have been made on the control panel.
The data transfer settings have been made on the configuration PC.
Procedure
To make the connection settings in WinCC, follow these steps:
1. Open the transfer settings.
2. Select the desired HMI device in the project tree.
3. Select the "Download to device > Software" command in the shortcut menu.
If you have not already established an online connection, the "Extended download to
device" dialog will automatically open. In this case, set all the necessary parameters for
the connection and click "Load".
If you have already defined an online connection, the project data will be compiled
immediately and the "Load preview" dialog will open. This dialog displays messages
and proposes actions necessary for uploading.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2294 System Manual, 08/2011,
4. Select the "Ethernet" mode.
5. Specify the IP address or the computer name of the HMI device.
6. Switch the HMI device to "transfer" mode.
7. Transfer the WinCC project to the HMI device.
WARNING
Death, serious bodily harm and / or damage to property from unexpected process or
machine behavior.
If you use DHCP it is not guaranteed that every time the same IP address will be issued
if a node is switched on.
Nodes could lose the connection in the Industrial Ethernet or be connected with incorrect
nodes. Always enter a static IP address for the HMI device. Contact your network
administrator for address allocations.
Establishing a connection via PROFIBUS DP
Connect the configuration PC to the HMI device (PROFIBUS DP)
1. Connect the interfaces from the configuration PC and the HMI device with an
PROFIBUS DP cable.
Note
To communicate via an PROFIBUS DP network you must create a direct connection.
Check if your configuration PC has a suitable interface for connection to the PROFIBUS
DP.
If this interface is missing, you must perform the following steps:
Build a card into the configuration PC, e.g. CP 5611 for desktop PCs.
Install the respective drivers.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2295
Configuring the transmission settings in the Control Panel (PROFIBUS DP)
Requirement
The configuration PC and HMI device are linked with each other via a PROFIBUS DP cable.
Procedure
Perform the following steps on the HMI device:
1. Switch on the HMI device.
Before the HMI device opens an existing project, the "Loader" selection field appears.
2. Select "Control Panel".
3. Double click on "Transfer".
4. Select the "MPI/PROFIBUS" option from the "Channel 2" selection list under the "Channel"
tab.
5. Select "Enable Channel".
6. Confirm with "OK".
7. "Transfer Settings" End the dialog.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2296 System Manual, 08/2011,
Setting the communication parameters in ProSave (PROFIBUS DP)
Requirement
The configuration PC and HMI device are linked with each other via a PROFIBUS DP cable.
The data transfer settings have been made on the control panel.
Procedure
To make the communications parameter settings in ProSave, follow these steps:
1. Make the transfer settings first.
2. To do this, select the desired component in the project tree.
3. Select the "Download to device > Software" command in the shortcut menu.
If you have not already established an online connection, the "Extended download to
device" dialog will automatically open. In this case, set all the necessary parameters for
the connection and click "Load".
If you have already defined an online connection, the project data will be compiled
immediately and the "Load preview" dialog will open. This dialog displays messages
and proposes actions necessary for uploading.
4. Select the "Options" command from the "Online > HMI device maintenance" menu to start
ProSave .
5. Select an element under "Available options".
6. Click ">>".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2297
Set the communication parameters in WinCC (PROFIBUS DP)
Requirement
The configuration PC and HMI device are linked with each other via a PROFIBUS DP cable.
The data transfer settings have been made on the control panel.
Procedure
To make the connection settings in WinCC, follow these steps:
1. Open the transfer settings.
2. Select the desired HMI device in the project tree.
3. Select the "Download to device > Software" command in the shortcut menu.
If you have not already established an online connection, the "Extended download to
device" dialog will automatically open. In this case, set all the necessary parameters for
the connection and click "Load".
If you have already defined an online connection, the project data will be compiled
immediately and the "Load preview" dialog will open. This dialog displays messages
and proposes actions necessary for uploading.
4. Select the "MPI / PROFIBUS DP" mode.
5. Specify the PROFIBUS address that is assigned to the HMI device.
The PROFIBUS address is the station address and corresponds to the address configured
for the WinAC MP controller.
6. Switch the HMI device to "transfer" mode.
7. Transfer the WinCC project to the HMI device.
NOTICE
For PROFIBUS DP transmission the WinAC MP control must be started on the HMI device.
9.11.13.5 Transferring WinAC MP to the HMI device
Procedure for transferring WinAC MP
Introduction
If you want to execute WinAC MP on the HMI device you must transfer the WinAC MP Runtime
files from the configuration PC to the HMI device. For the transfer there must be a data
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2298 System Manual, 08/2011,
connection between the configuration PC and the HMI device. The following screen shows the
arrangement using example Industrial Ethernet.
WinAC MP authorization
WinAC MP Runtime files
Configuration PC
Automation License
Manager
HMl device
lndustrial Ethernet
S7-300
S7-400
ProSave
Basic procedure
To transfer WinAC MP Runtime files to an HMI device, follow these steps:
1. Setting up the HMI device.
2. Configure the ProSave on the configuration PC.
3. Start transfer.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2299
Switch the HMI device to transfer mode
Procedure
For the transfer of data you must switch the HMI device to "Transfer":
1. Switch on the HMI device.
Before the HMI device opens an existing project, the "Loader" selection field appears.
2. Click on the "Transfer" button.
The dialog window displays the message "Connecting to host ...".
Configuring ProSave on the configuration PC
Requirement
The HMI device was switched to transfer mode.
Procedure
To set up a configuration PC to transfer WinAC MP, proceed as follows:
1. Start ProSave.
2. Select the "General" tab.
3. Select the device type of your HMI device.
4. Select the "Ethernet" connection type.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2300 System Manual, 08/2011,
5. Specify the IP address or the computer name of the HMI device.
6. Start the transfer of WinAC MP.
Start transfer
Requirement
The HMI device was switched to transfer mode.
ProSave is set up on the configuration PC.
Procedure
To start the transfer of WinAC MP files, follow these steps:
1. Open the "Options" tab in transfer mode and click the "Device status" button. If no error
message is shown then the communication connection is valid.
Note
If there is a communication error, then you must check the following circumstances:
The HMI device must be in Transfer mode.
Check the cable connections for a correct and firm connection.
The settings in ProSave and on the HMI device must be correctly defined for the
connection.
2. In the "Options" tab, select "WinAC MP" below "Available options".
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2301
3. To transfer WinAC MP to the HMI device, click the button.
ProSave then starts to load the software of the WinAC MP control to the HMI device. While
the files are being transferred the configuration PC shows the progress of the transfer.
The following messages are displayed on the HMI device in the "Transfer" dialog box:
Progress of the file receipt on the HMI device.
Unzip data in the Flash file system.
Save data in the Flash file system.
At the end of the transfer, a message confirms a successful transfer.
4. When transfer is complete, you will be asked to restart the device. Restart the device.
Result
The WinAC MP control is now installed on the HMI device. Now, transfer the authorization for
WinAC MP to the HMI device.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2302 System Manual, 08/2011,
9.11.13.6 Transferring authorization to the HMI device
Introduction
You need a license key to operate WinAC MP. The license key is transferred with the
Automation License Manager to the HMI device.
lndustrial Ethernet
WinAC MP authorization
WinAC MP Runtime files
Configuration PC HMl device
S7-300
S7-400
ProSave
Automation License
Manager
Requirements
The storage location of the license key can be called from the configuration PC.
Procedure
To transfer the WinAC MP authorization to an HMI device, follow these steps:
1. Select the "Authorize/License" command from the "Online > Device maintenance" menu
to start WinAC MP authorization.
Automation License Manager is launched.
2. Select the "Connect HMI device" menu command.
3. Select the device type of the HMI device.
4. Select the type of connection and set the parameters for the connection.
The connection to the HMI device is established. The connected HMI device is displayed.
5. Select the source drive.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2303
6. Drag one or more license keys to the HMI device.
The license keys are then transferred to the HMI device.
7. Close the Automation License Manager after a successful transfer.
9.11.13.7 WinAC MP system library
Screens from the system library
The screens from the system library are optimized for a 6' display with a resolution of 320 x
240. If you use a display of a different size, you can adapt the screens for your display in WinCC.
Standard screens and tags
The WinAC MPsystem library offers you the standard screens "WinAC_MP_Home" and
"WinAC_MP_Tuning" and the tags "WinAC_MP_Tags". To use the standard screens, move
them to the "Screens" folder in the project tree.
In addition to the standard screens, the tags must be copied separately. To do this, drag
"WinAC_MP_Tags" from the WinAC MPsystem library to the "HMI_Tags" folder in the project
tree.
Visualizing processes (Advanced)
9.11 Communicating with PLCs
WinCC Advanced V11.0 SP1
2304 System Manual, 08/2011,
9.12 Using global functions
9.12.1 HMI device wizard basics
Introduction
The HMI device wizard will automatically start when you create a new HMI device in your
project.
HMI device wizard
The HMI device wizard will guide you through each dialog step by step and help you set up a
device. You use the HMI device wizard to specify the basic settings for your HMI device, such
as screen layout and the connection to your PLC.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2305
See also
HMI device wizard basics (Page 2306)
9.12.2 HMI device wizard basics
Introduction
The HMI device wizard will guide you through each dialog step by step and help you set up a
device. You use the HMI device wizard to specify the basic settings for your HMI device, such
as screen layout and the connection to your PLC.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2306 System Manual, 08/2011,
Opening the HMI device wizard
1. Add a new device to your project, for example, RT Advanced.
2. Click on the device in the project tree.
3. Select "Start the HMI device wizard" in the shortcut menu. The "HMI device wizard" opens.
Note
If you make changes after adding the device, such as adding a new screen, the HMI device
wizard will not open again.
See also
HMI device wizard basics (Page 2305)
9.12.3 Importing and exporting project data
9.12.3.1 Importing and exporting project data
Introduction
WinCC enables you to export data from a project and import it into another project.
You export or import the following project data:
Recipe data records
Alarms
Tags
Text lists
Project texts
Exporting and importing reduces the workload. Instead of creating new data records, you use
data already created in previous projects.
Editing the export file
The following file formats are available for export and import depending on the editor:
*.xlsx for alarms, tags, project texts and text lists
*.csv for recipe data records
You can edit the import file in Excel, for example.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2307
XLSX file format
XLSX format is a file format for Excel tables based on the Open XML format. XLSX files are
optimized for Microsoft Excel 2007.
You can sort the columns as required in the XLSX file.
CSV file format
CSV stands for Comma Separated Value. In this format, the columns of the table that contain
the names and the value of the entry are separated by semicolons. Each table row terminates
with a line break. You can also open the CSV file for editing in Excel.
Importing project data
When project data is imported, the objects in the project are created.
The syntax of the import file is checked during import. The accuracy of the values imported
and dependencies between the imported values are not checked.
Any errors found in the imported data are reported when the project is compiled.
9.12.3.2 Importing and exporting recipes
Exporting recipes
Introduction
WinCC features an export function for exporting data records from recipes.
Requirements
The WinCC project for the export is open.
Recipes have been created in a project.
The "Recipes" editor is open.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2308 System Manual, 08/2011,
Exporting recipes
1. In the "Recipes" editor, select the recipe with the data records you want to export.
2. Click .
The "Export" dialog box opens.
The selected recipe is shown under "Recipe selection".
3. Under "Content selection", specify if all or only selected data records are to be exported.
4. Under "File selection", specify the file in which the recipe data is to be stored.
5. Specify the list separator and decimal separator under "Data separation".
6. Click "Export."
The export will start.
Result
The exported data has been written to a CSV file. The CSV file will be stored in the specified
directory.
See also
Exporting alarms (Page 2312)
Exporting text lists (Page 2324)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2309
Importing recipes
Introduction
Recipes are identified by their name. The recipe name must therefore be unique. Open the
import file in a simple text editor to check that it has the correct data structure.
Specify whether or not existing data records should be overwritten by records with the same
name during the import.
Requirements
A CSV file containing at least one recipe has been created.
The WinCC project for the import is open.
The "Recipes" editor is open with at least one recipe.
Importing a recipe
1. In the "Recipes" editor, select the recipe with the data records you want to import.
2. Click .
The "Import" dialog box opens.
The selected recipe is shown under "Recipe selection".
3. Select the file you want to import under "File selection".
4. Under "Strategy", specify if existing data records should be overwritten by records of the
same name.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2310 System Manual, 08/2011,
5. Under "Data separation", select the list separator and the decimal separator to use in the
CSV file.
6. Click "Import".
The import will start.
Result
The data records are created in the selected recipe. Depending on the setting for "Strategy",
existing data records are overwritten by records with the same name from the CSV file.
Existing data records with the same name will also be imported from the CSV file if you
deactivate the "Overwrite existing data records" option.
Format of recipe data
Introduction
This section describes the required format of the file for the import of recipes. The file containing
the data of the recipes must be available in "*.csv" format. :
Structure of recipe data
The structure of the import file is fixed. The following example shows the structure of a recipe
containing two recipe elements, each with two data records:
List separator=<List separator>Decimal symbol=<Decimal
separator><List separator><Line break>
<Name of the recipe><List separator><List separator><Line break>
LANGID_<ID of the language><List separator>
<Display name, recipe element 1><List separator>
<Display name, recipe element 2><Line break>
<Number recipe><List separator>
<Recipe data record number 1><List separator>
<Recipe data record number 2><Line break>
<Tag recipe element 1><List separator>
<Recipe data record 1 value 1><List separator>
<Recipe data record 2 value 1><Line break>
<Tag recipe element 2><List separator>
<Recipe data record 1 value 2><List separator>
<Recipe data record 2 value 2><Line break>
ID of the language
Use the "Windows language ID" in decimal notation, e.g. "1033" for English. Additional
information is available in the documentation for the Windows operating system.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2311
9.12.3.3 Importing and exporting alarms
Exporting alarms
Introduction
WinCC has an export function for alarms.
Requirements
The WinCC project for the export is open.
Alarms have been created in the project.
The "HMI alarms" editor is open.
Exporting alarms
1. Click the button in "Discrete alarms" or "Analog alarms".
The "Export" dialog box opens.
2. Click the "..." button and specify in which file the data are saved.
3. Specify whether you want to export "Disrete alarms" or "Analog alarms".
4. Click "Export". The export will start.
Result
The exported data has been written to an xlsx file. The xlsx file will be stored in the specified
folder.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2312 System Manual, 08/2011,
See also
Importing alarms (Page 2313)
Format of the analog alarm data (Page 2314)
Format of the discrete alarm data (Page 2317)
Exporting recipes (Page 2308)
Exporting text lists (Page 2324)
Exporting tags (Page 2319)
Importing alarms
Introduction
Alarms are identified by their alarm number. The alarm numbers must be unique in the analog
and discrete alarm types. Alarms with redundant alarm numbers will be overwritten. An alarm
without an existing alarm number is created.
Any empty list entries for existing alarms contained in an xlsx file will be ignored for the
purposes of the import. The entries of the existing alarms remain active and will not be replaced
by empty ones.
Requirements
An xlsx file with alarms has been created.
The structure of the xlsx file meets the requirements.
The WinCC project for the import is open.
The "HMI alarms" editor is open.
Importing alarms
1. Click the button in "Discrete alarms" or "Analog alarms". The "Import" dialog box opens.
2. Click the "..." button and select the file that you want to import.
3. Click on the "Import" button. The import will start. A progress bar indicates the progress of
the import operation.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2313
Result
The corresponding alarms including alarm texts are created in WinCC on the basis of the import
data. Alarms relating to the import operation are displayed in the output window. A log file is
saved in the source directory of the import files. The log file has the same name as the
respective import file but with the "*.xml" extension.
Check when importing the data whether there are any links to objects, for example, dynamic
parameters such as tags.
If an object with the same name already exists, the existing object is used.
If no object of the same name yet exists, create an object with the relevant name or create
a new link.
Note
The syntax of the import file is checked during xlsx file import. The meaning of the properties
or dependencies between the properties is not checked. It is possible to assign a trigger tag
of an incorrect type, such as string, to an alarm. An error will be reported during compilation.
See also
Exporting alarms (Page 2312)
Format of the discrete alarm data (Page 2317)
Format of the analog alarm data
Introduction
This chapter describes the required format of the file for the import of analog alarms. The file
containing the analog alarm data must be in "*.xlsx" format.
Structure of the alarm data
The import file in Microsoft Excel consists of a number of worksheets:
Analog alarms(Analog alarms)
Limits (Limits)
Each alarm is assigned a separate row in the import file. The import file with the analog alarms
must be formatted as follows:
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2314 System Manual, 08/2011,
Example of the worksheet "Analog alarms"
Table 9-25 Meaning of the entries
List entry Meaning
ID The alarm number is used to reference an alarm. The alarm number is unique.
Alarms with identical alarm numbers are overwritten during import. An alarm
without an existing alarm number is created.
Name Name of the analog alarm
Event text [de-DE], Alarm text Displays the alarm text. The field designation contains a language ID. Alarm texts
must be assigned a language ID for import.
An expression with a reference ID will be added to the alarm text if the text has a
dynamic parameter. Example: text <field ref="0" />. Use the ID to assign dynamic
parameters to alarm texts.
FeldInfo Specifies whether the alarm text contains dynamic parameters. The settings are
separated by a semicolon ";".
Example of dynamic parameters:
Tag: <ref id = 0; type = AlarmTag; Tag = Tag1; DisplayType = Decimal; Length =
5;>
Text list: <ref id = 1; type = CommonTextList; TextList = Textlist1; Tag = tag 2;
Length = 5;>
Class The class of an alarm determines whether or not the alarm must be acknowledged.
It can also be used to determine how the alarm appears when it is displayed on
the HMI device. The alarm class also determines whether and where the
corresponding alarm will be logged.
Group Indicates the allocation to an alarm group. If an alarm belongs to a group with
other alarms, it can be acknowledged together with these alarms of the same
group in a single operation.
Trigger tag Specifies the tag monitored for limit value violation.
Delay time value Specifies the delay time. The alarm is not triggered until the duration of the limit
value violation equals the specified delay time.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2315
List entry Meaning
Delay time unit Specifies the time unit for the delay.
Report Enables reporting of the specific alarm on a printer.
True or "1" = Reporting enabled.
False or "0" = Reporting disabled.
Reporting must also be globally enabled in the project.
Info text [de-DE], Info text The tooltip is an optional property of an alarm. Tooltips can contain additional
information about the alarm. A tooltip will be displayed in a separate window on
the HMI device when the operator presses the <HELP> key.
The field designation contains a language ID.
Example of the worksheet "Limits"
Table 9-26 Meaning of the entries
List entry Meaning
Alarm ID Alarm number
The alarm number is used to reference an alarm. The alarm
number is unique. Alarms with identical alarm numbers are
overwritten during import. An alarm without an existing alarm
number is created.
Limit mode Trigger mode
Indicates the method used for monitoring the limit value.
Limit type Specifies the limit that will be monitored. Both a tag and a
constant can be used as limit value.
Limit value Limit value
Indicates the tag or constant monitored for limit violation.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2316 System Manual, 08/2011,
List entry Meaning
Deadband mode Hysteresis mode
Specifies whether and in which cases hysteresis will be used.
For "Outgoing"
For "Incoming"
For "Incoming" and "Outgoing"
Deadband in percent 0 = The value specified for "Hysteresis" is considered to be
absolute.
1 = The value specified for "Hysteresis" is referred to as a
percentage of the limit value.
Deadband mode Hysteresis
Specifies a constant as a value of the hysteresis.
Note
"No value" in the table
Entries in the table which have the value "No value" delete the corresponding values in an
existing alarm of the same name.
See also
Exporting alarms (Page 2312)
Format of the discrete alarm data (Page 2317)
Format of the discrete alarm data
Introduction
This chapter describes the required format of the file for the import of discrete alarms. The file
containing the discrete alarm data must be in "*.xlsx" format.
Structure of the alarm data
The import file in Microsoft Excel consists of the worksheets "Discrete alarms" (discrete
alarms). Each alarm is assigned a separate row in the import file. Structure of the import file
containing the discrete alarms:
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2317
Example of the worksheet "Discrete alarms"
Table 9-27 Meaning of the entries
List entry Meaning
ID The alarm number is used to reference an alarm. The alarm number is unique.
Alarms with identical alarm numbers are overwritten during import. An alarm
without an existing alarm number is created.
Name Name of the analog alarm
Event text [de-DE], Alarm text Displays the alarm text. The field designation contains a language ID. For import,
a language ID must be assigned to alarm text.
An expression with a reference ID will be added to the alarm text if the text has a
dynamic parameter. Example: text <field ref="0" />. Use the ID to assign dynamic
parameters to alarm texts.
FeldInfo Specifies whether the alarm text contains dynamic parameters. The settings are
separated by a semicolon ";".
Example of dynamic parameters:
Tag: <ref id = 0; type = AlarmTag; Tag = Tag1; DisplayType = Decimal; Length =
5;>
Text list: <ref id = 1; type = CommonTextList; TextList = Textlist1; Tag = tag 2;
Length = 5;>
Class The class of an alarm determines whether or not the alarm must be acknowledged.
It can also be used to determine how the alarm appears when it is displayed on
the HMI device. The alarm class also determines whether and where the
corresponding alarm will be logged.
Group Indicates the allocation to an alarm group. If an alarm belongs to a group with
other alarms, it can be acknowledged together with these alarms of the same
group in a single operation.
Trigger tag Specifies the tag containing the bit that triggers the alarm.
Trigger bit Specifies the number of the bit that triggers the alarm.
Acknowledge tag Specifies the tag containing the bit that is set by the operator upon
acknowledgment. Only available if the selected alarm class requires alarm
acknowledgment.
Acknowledgment bit Specifies the number of the bit that is set when the operator acknowledges the
alarm.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2318 System Manual, 08/2011,
List entry Meaning
PLC acknowledgement tag Specifies the tag containing the bit that acknowledges the alarm of the control
program. Only available if the selected alarm class requires alarm
acknowledgment.
PLC acknowledgment bit Specifies the number of the bit that acknowledges the alarm of the control program.
Delay time value
Specifies the delay time. The alarm is not triggered until the duration of the limit
value violation equals the specified delay time.
Delay time unit Specifies the time unit for the delay.
Report Enables reporting of the specific alarm on a printer.
True or "1" = Reporting enabled.
False or "0" = Reporting disabled.
Reporting must also be globally enabled in the project.
Info text [de-DE], Info text The tooltip is an optional property of an alarm. Tooltips can contain additional
information about the alarm. A tooltip will be displayed in a separate window on
the HMI device when the operator presses the <HELP> key.
The field designation contains a language ID.
Note
"No value" in the table
Entries in the table which have the value "No value" delete the corresponding values in an
existing alarm of the same name.
See also
Exporting alarms (Page 2312)
Format of the analog alarm data (Page 2314)
Importing alarms (Page 2313)
9.12.3.4 Importing and exporting tags
Exporting tags
Introduction
WinCC has an export function for tags.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2319
Requirements
The WinCC project for the export is open.
Tags have been created in the project.
The "HMI tags" editor is open.
Exporting tags
1. Click on the button in the "HMI Tags" tab.
The "Export" dialog box opens.
2. Click the "..." button and specify in which file the data are saved.
3. Click "Export". The export will start.
Result
The exported data has been written to an xlsx file. The xlsx file will be stored in the specified
folder.
See also
Importing tags (Page 2320)
Format of the tag data (Page 2322)
Exporting text lists (Page 2324)
Exporting alarms (Page 2312)
Importing tags
Introduction
Tags are identified by the tag name. An existing tag will be overwritten with the data from the
xlsx file if the tag name already exists in the project. A new tag is created if the tag does not
yet exist.
Requirements
An xlsx file with tags has been created.
The structure of the xlsx file meets the requirements.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2320 System Manual, 08/2011,
The WinCC project for the import is open.
The "HMI tags" editor is open.
Importing tags
1. Click on the button. The "Import" dialog box opens.
2. Click the "..." button and select the file that you want to import.
3. Click on the "Import" button. The import will start.
Result
The relevant tags have been created in WinCC. Alarms relating to the import operation are
displayed in the output window. A log file is saved in the source directory of the import files.
The log file has the same name as the respective import file but with the "*.xml" extension.
Check when importing the data whether there are any links to objects, for example, dynamic
parameters such as tags.
If an object with the same name already exists, the existing object is used.
If no object of the same name yet exists, create an object with the relevant name or create
a new link.
Note
The syntax of the import file is checked during xlsx file import. The meaning of the properties
or dependencies between the properties is not checked. It is possible to assign a tag a trigger
tag of the wrong type, for example, string. An error will be reported during compilation.
See also
Exporting tags (Page 2319)
Format of the tag data (Page 2322)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2321
Format of the tag data
Introduction
This section describes the format required for the file with tag data used for imports. The tag
data file must be in "*.xlsx" format.
Tag data structure
The import file in Microsoft Excel consists of a number of worksheets:
HMI Tags (HMI tags)
Multiplexing (multiplex tags)
Each tag is on a separate line in the import file. The import file with the tag data must have the
following format:
Example of the worksheet "HMI Tags"
Table 9-28 Meaning of the entries
List entry Meaning
Name Indicates the configured name of an HMI tag.
Path Specifies which folders in the project tree contain the tag. The folder structure is
represented by "\" : "FolderName1\FolderName2\TagName".
PLC Tag Indicates whether the tag is linked to a PLC tag.
Connection Indicates the name of the connection to the PLC.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2322 System Manual, 08/2011,
List entry Meaning
Data type Specifies the data type of a tag. The data types allowed depend on the
communication driver being used. See the "Communication" section of the
documentation for additional information on the data types permitted for the
various communication drivers.
Length Specifies the length of the tag. This entry is only useful for data types with a
dynamic length such as strings; it is left empty for all other data types.
Address Specifies the tag address in the PLC. The tag address must exactly match the one
used in WinCC, for example, "%DB1.DBW0". The tag address is empty for internal
tags.
Multiplexing Specifies whether multiplexing is used.
Index tag Shows the name of the index tag for multiplexing.
In Runtime, the system first reads the value of the index tag. It then accesses the
tag in the corresponding place in the tag list.
StartValue Specifies the start value of a tag.
ID tag The update ID updates the value of a tag with the aid of a function or a PLC job.
The update ID must be unique within an HMI device.
Coding Shows the coding method.
DiplayName [de_DE]
Shows the display name of an HMI tag. The field designation contains a language
ID. The field designation contains a language ID. Display names must be assigned
a language ID for import. Texts are imported to the corresponding project
language.
Acquisition mode Specifies the tag acquisition mode.
Acquisition cycle Specifies the tag acquisition cycle. The acquisition cycle must correspond exactly
to the one used in WinCC. The value is not language-dependent and should
therefore be the same in every language. The default value is "1 s". The acquisition
cycle is undefined if the tag acquisition mode is "on demand".
User-defined acquisition cycles must be created beforehand as the file will
otherwise not be imported.
High High Limit type Indicates whether the limit value "High high" is monitored by a constant, a tag or
not at all.
High High Limit Displays the limit value "High High".
High Limit type Indicates whether the limit value "High" is monitored by a constant, a tag or not at
all.
High Limit Displays the limit value "High".
Low Limit type Indicates whether the limit value "Low" is monitored by a constant, a tag or not at
all.
Low Limit Displays the limit value "Low".
Low Low Limit type Indicates whether the limit value "Low Low" is monitored by a constant, a tag or
not at all.
Low Low Limit Displays the limit value "Low Low".
Linear scaling Indicates whether linear scaling is enabled. This entry can only be used for external
tags.
End value PLC Specifies the end value of the PLC tag.
Start value PLC Specifies the start value of the PLC tag.
End value HMI Specifies the end value of the HMI tag.
Start value HMI Specifies the start value of the HMI tag.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2323
Example of the worksheet "Multiplexing"
Table 9-29 Meaning of the entries
List entry Meaning
Name Indicates the configured name of an HMI tag which uses indirect addressing. The
HMI tag must be available in the "HMI Tags" worksheet.
Index Shows the value which governs which tag is selected.
Multiplex Tag Displays the tag from the tag list corresponding to the index value.
Note
"No value" in the table
Entries in the table which have the value "No value" delete the corresponding values in an
existing tag of the same name.
See also
Exporting tags (Page 2319)
Importing tags (Page 2320)
9.12.3.5 Importing and exporting text lists
Exporting text lists
Introduction
WinCC has an export function for text lists.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2324 System Manual, 08/2011,
Requirements
The WinCC project for the export is open.
Text lists have been created in the project.
The "Text & graphics lists" editor is open.
Exporting text lists
1. Click on the button in the "TextLists" tab.
The "Export" dialog box opens.
2. Click the "..." button and specify in which file the data are saved.
3. Click "Export". The export will start.
Result
The exported data has been written to an xlsx file. The xlsx file will be stored in the specified
folder.
See also
Exporting alarms (Page 2312)
Exporting recipes (Page 2308)
Exporting tags (Page 2319)
Importing text lists
Introduction
You then import text lists from an xlsx file to WinCC.
Requirements
An xlsx file with text lists has been created.
The structure of the xlsx file meets the requirements.
The WinCC project for the import is open.
The "Text & graphics lists" editor is open.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2325
Importing text lists
1. Click on the button in the "Text lists" tab.
The "Import" dialog box opens.
2. Select the file you want to import under "File selection".
3. Click on the "Import" button. The import will start.
Result
You have now imported the text lists. The relevant text lists have been created in WinCC.
Alarms relating to the import operation are displayed in the output window. A log file is saved
in the source directory of the import files. The log file has the same name as the respective
import file but with the "*.xml" extension.
Check when importing the data whether there are any links to objects, for example, dynamic
parameters such as tags.
If an object with the same name already exists, the existing object is used.
If no object of the same name yet exists, create an object with the relevant name or create
a new link.
Format of text list data
Introduction
This section describes the format required for the file with the text lists used for imports. The
text list data file must be in "*.xlsx" format.
Tag data structure
The import file in Microsoft Excel consists of two worksheets:
TextList (Text lists)
TextListEntry (Text list entry)
Each text list is assigned a separate line in the import file. The import file containing the data
must be structured as follows:
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2326 System Manual, 08/2011,
Example of the worksheet "TextList"
Table 9-30 Meaning of the entries
List entry Meaning
Name Shows the name of the text list.
ListRange Shows the text list range:
Number = Bit number (0-31)
Range = value/range (...-...)
Bit = Bit (0;1)
Comment Any comments on the text list. You can use up to 500 characters
Example of the worksheet "TextListEntry"
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2327
Table 9-31 Meaning of the entries
List entry Meaning
Name Shows the name of the text list entry.
Parent Specifies the name of the corresponding text list.
DefaultEntry Indicates whether the text list entry is a default entry. The default entry is always
displayed when the tag has an undefined value.
Value Specifies the tag integer values or value ranges which are assigned to the text
entries in the text list.
Text Shows the text list entry. The field designation contains a language ID. Text list
entries must be assigned a language ID for import.
An expression with a reference ID will be added to the text if the text list entry has
a dynamic parameter. Example: text <field ref="0" />. Use the ID to assign the
dynamic parameter to a text list entry.
FeldInfo Specifies whether the text list contains dynamic parameters. The settings are
separated by a semicolon ";".
Example of dynamic parameters:
Tag: <ref id = 0; type = CommonTagDisplayFormat; Tag = tag 1; DisplayType =
Decimal; DisplayFormat = 9;>
Text list: <ref id = 1; type = CommonTextList; TextList = Textliste_1; Tag = tag 2;
Length = 5;>
PLC tag: <ref id = 0; type = CommonControlTagDisplayFormat; DisplayType =
Decimal; DisplayFormat = 9;>
9.12.4 Using cross-references
9.12.4.1 General information about cross references
Introduction
The cross-reference list provides an overview of the use of objects within the project.
Uses of cross-references
The cross-reference list offers you the following advantages:
When creating and changing a program, you retain an overview of the objects, tags, and
alarms etc. you have used.
From the cross-references, you can jump directly to the object location of use.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2328 System Manual, 08/2011,
You can learn the following when debugging:
The objects used in a specific screen.
The alarms and recipes shown in a specific display.
The tags used in a specific alarm or object.
As part of the project documentation, the cross-references provide a comprehensive
overview of all object, alarms, recipes, tags and screens.
9.12.4.2 Displaying the cross-reference list
Introduction
Details on the use of objects can be found in the cross-reference list. You can show cross-
references for HMI devices, folders and all editors in the project tree. The detail view also lets
you select individual objects of the editors.
Requirement
You have created a project.
Several objects have been created.
Procedure
1. Select the required entry in the project tree or detail view.
2. Select "Cross-references" in the shortcut menu. The cross-reference list is opened in the
work area.
3. Open the "Used by" tab to display where the objects shown in the cross-reference list are
used.
4. Open the "Used" tab to view the users of the objects displayed in the cross-reference list.
5. You can sort the entries in the "Object" column in ascending or descending order by clicking
on the corresponding column header.
6. To go to the location of use for a specific object, click on the displayed link.
Result
The cross-reference list for the selected object is displayed in the work area.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2329
9.12.4.3 Structure of the cross-reference list
Views of the cross-reference list
There are two views of the cross-reference list. The difference between the two views is in the
objects displayed in the first column:
Used by:
Display of the referenced objects. Here, you can see where the object is used.
Used:
Display of the referencing objects. The users of the object are shown here.
The assigned tool tips provide additional information about each object.
Structure of the cross-reference list
Column Content/meaning
Object Name of the object that uses the lower-level objects or that is being
used by the lower-level objects.
Numbers Number of uses
Location of use Each location of use, for example, an object or event
Property Function of the referenced objects, for example, tag for data record or
process value
Connected to PLC tag with which the object is connected.
Type Type of object
Path Path of object
Depending on the installed products, additional columns or different columns are displayed for
the cross-references.
Settings in the cross-reference list
You can make the following settings using the icons in the toolbar for the cross-reference list:
Update cross-reference list
Updates the current cross-reference list.
Making settings for the cross-reference list
Here, you specify whether all used, all unused, all defined or all undefined objects will be
displayed. If the "Undefined objects" option is enabled, references to previously deleted
objects are also displayed.
Collapse entries
Reduces the entries in the current cross-reference list by closing the lower-level objects.
Expand entries
Expands the entries in the current cross-reference list by opening the low-level objects.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2330 System Manual, 08/2011,
Sorting in the cross-reference list
You can sort the entries in the "Object" column in ascending or descending order. Click on the
column header to do this.
9.12.4.4 Displaying cross-references in the Inspector window
Introduction
The Inspector window displays cross-reference information about a selected object in the "Info
> Cross-references" tab. The Inspector window displays the cross-reference information in
tabular format.
Requirement
You have created a project.
Several objects have been created.
Procedure
1. Select an object in a screen or a tabular editor.
2. Select "Cross-reference information" in the shortcut menu. The cross-references are
opened in the Inspector window.
Result
The instances where and the other objects by which the selected object is being used are
displayed.
The table below shows the additional information listed in the "About > Cross-reference" tab:
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2331
Column Meaning
Object Name of the object that uses the lower-level
objects or that is being used by the lower-level
objects.
Numbers Number of uses
Location of use Each location of use, for example an object or
event
Property Function of the referenced objects, for example
tag for data record or process value
Connected to PLC tag with which the object is connected.
Type Type of object
Path Path of object
Depending on the installed products, additional columns or different columns are displayed for
the cross-references.
9.12.5 Managing languages
9.12.5.1 Languages in WinCC
User interface language and project languages
A distinction is drawn between two different language levels in WinCC:
User interface language
During configuration, the text in the WinCC menus and dialogs is displayed in the user
interface language. The user interface language also affects the labeling of operating
elements, the parameters of the system functions, the online help, etc.
Project languages
Project languages are all languages in which a project will later be used. Project languages
are used to create a project in multiple languages.
The two language levels are completely independent of one another. For example, you can
create English projects at any time using a German user interface and vice versa.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2332 System Manual, 08/2011,
Project languages
The following languages are differentiated within the project languages:
Reference language
The reference language is the language that you use to configure the project initially.
During configuration, you select one of the project languages as the reference language.
You use the reference language as a template for translations. All of the texts for the project
are first created in the reference language and then translated. While you are translating
the texts, you can have them displayed simultaneously in the reference language.
Editing language
You produce translations of the texts in the editing language.
Once you have created your project in the reference language, you can translate the texts
into the remaining project languages. Select a project language respectively as an edit
language and edit the texts for the appropriate language variant. You can change the editing
language at any time.
Note
When switching the project languages, the assignment to the keys on the keyboard also
changes. For some languages (for example, Spanish), the operating system does not
allow you to switch to the corresponding keyboard assignment. In this case, the keyboard
assignment is switched to English.
Runtime languages
Runtime languages are those project languages that are transferred to the HMI device. You
decide which project languages to transfer to the HMI device depending on your project
requirements.
You must provide appropriate controls so that the operator can switch between languages
in runtime.
See also
Language settings in the operating system (Page 2334)
Operating system settings for Asian languages (Page 2334)
Selecting the user interface language (Page 2335)
"Graphics" editor (Page 2346)
Languages in Runtime (Page 2350)
Example: Configuring a button for language switching (Page 2357)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2333
9.12.5.2 Language settings in the operating system
Introduction
The configuration PC operating system settings influence WinCC language management in
the following areas:
Selection of project languages
Regional format of dates, times, currency, and numbers
Displaying ASCII characters
Project language selection
A language is not available as a project language unless it is installed in the operating system.
Regional format of dates, times, currency, and numbers
WinCC specifies a fixed date and time format in the Date - Time field for the selected project
language and runtime language.
In order for dates, times, and numbers to be presented correctly in the selected editing
language, this language must be set in the Regional Options in the Control Panel.
Displaying ASCII characters
With text output fields, the display of ASCII characters as of 128 depends on the set language
and the operating system being used.
If the same special characters are to be displayed on different PCs, the PCs must use the
same operating system and regional settings.
See also
Languages in WinCC (Page 2332)
Operating system settings for Asian languages (Page 2334)
9.12.5.3 Operating system settings for Asian languages
Settings on Western operating systems
If you want to enter Asian characters, you must activate the support for this language in the
operating system.
The Input Method Editor (IME) is available in Windows for configuring Asian texts. Without this
editor, you can display Asian text but not edit it. For more information on the Input Method
Editor, refer to the documentation for Windows. To enter Asian characters when configuring,
switch to the Asian entry method in the "Input Method Editor".
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2334 System Manual, 08/2011,
Switch the operating system to the appropriate language to have language-specific project
texts, such as alarm texts, displayed in the simulator in Asian characters.
Settings on Asian operating systems
If you are configuring on an Asian operating system, you must switch to the English default
input language to enter ASCII characters, for example, for object names. As the English default
input language is included in the basic installation of the operating system, you do not need
to install an additional input locale.
Enable language support
1. Open the system controller.
2. Select "Regional and Language Options".
3. On the "Languages" tab, activate the check box "Install files for East Asian languages".
4. Then click on "Details" under "Text Services and Input Languages". The dialog "Text
Services and Input Languages" is opened.
5. On the "Settings" tab add the required default input language under the "Installed Services".
6. Select the language of the operating system in the "Language for non-Unicode programs"
area in the "Advanced" tab.
See also
Languages in WinCC (Page 2332)
Language settings in the operating system (Page 2334)
9.12.5.4 Setting project languages
Selecting the user interface language
Introduction
The user interface language is used for displaying menu entries, title bars, infotexts, dialog
texts and other designations in the WinCC user interface.
You can switch between the installed user interface languages during configuration. The
labeling of the operating elements remains in the language you set when you added the object
even if you change the user interface language.
Procedure
1. Select "Options > Settings" in the menu.
The "Settings" dialog box is opened.
2. Select the desired user interface language under "General > General settings".
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2335
Result
WinCC will use the selected language as user interface language.
See also
Enable project languages (Page 2336)
Selecting the reference language and editing language (Page 2337)
Languages in WinCC (Page 2332)
Enable project languages
Introduction
The project languages are set in the "Project languages" editor. You define which project
language is to be the reference language and which the editing language.
Enable project languages
1. Click on the arrow to the left of "Languages & resources" in the project tree.
The lower-level elements will be displayed.
2. Double-click on "Project languages".
The possible project languages will be displayed in the working area.
3. Enable the relevant project languages.
Note
Copying multilingual objects
The copies of multilingual objects to a different project only include text objects in the
project languages which are activated in the target project. Activate all project languages
in the target project to include the corresponding text objects when transferring the copy.
Disabling project languages
1. Disable the languages which are not relevant for the project.
CAUTION
If you disable a project language, all text and graphic objects you have already created
in this language will be deleted from the current project.
See also
Selecting the user interface language (Page 2335)
Selecting the reference language and editing language (Page 2337)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2336 System Manual, 08/2011,
Selecting the reference language and editing language
Introduction
The project languages are set in the "Project languages" editor. You define which project
language is to be the reference language and which the editing language. You can change
the editing language at any time.
Requirements
The "Project languages" editor is open.
Several project languages have been activated.
Selecting the reference language and editing language
1. Click the arrow in the drop-down list in the "General > Editing language" section.
2. Click on the required language in the drop-down list, for example, German.
3. Click on the arrow in the drop-down list in the "General > Reference language" section.
4. Click on the required language in the drop-down list, for example, English.
The language selection is displayed in the list box.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2337
Result
You have now selected the editing and reference languages.
If you change the editing language, all future text input will be stored in the new editing
language.
See also
Selecting the user interface language (Page 2335)
Enable project languages (Page 2336)
9.12.5.5 Creating one project in multiple languages
Working with multiple languages
Multilingual configuration in WinCC
You can configure your projects in multiple languages using WinCC. There are various grounds
for creating a project in multiple languages:
You would like to use a project in more than one country.
You create the project in multiple languages but when the HMI device is commissioned,
only the language spoken by the operators at the respective site will be transferred to the
HMI device.
The operators of a system speak a range of different languages.
Example: An HMI device is used in China, but the service personnel understand only
English.
Translating project texts
With WinCC, you can enter project texts directly in several languages in various different
editors, for example, in the "Project texts" editor. WinCC also allows you to export and import
your configuration for translation purposes. This is particularly advantageous if you configure
projects containing a large amount of text and want to have it translated.
Language management and translation in WinCC
The following editors are used to manage languages and translate texts in WinCC:
Editor Short description
Project languages Selection of project languages, editing language and reference
language.
Languages and fonts Management of runtime languages and fonts used on the HMI device.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2338 System Manual, 08/2011,
Editor Short description
Project texts Central management of configured texts in all project languages.
Graphics Graphic library for managing graphics and their language-specific
versions.
See also
Project text basics (Page 2339)
Translating texts directly (Page 2340)
Translating texts using reference texts (Page 2342)
Exporting project texts (Page 2343)
Importing project texts (Page 2345)
Project text basics
Texts in different languages in the project
Texts that are output on display devices during processing are typically entered in the language
in which the automation solution is programmed. Comments and the names of objects are also
entered in this language.
If operators do not understand this language, they require a translation of all operator-relevant
texts into a language they understand. You can therefore translate all the texts into any
language. In this way, you can ensure that anyone who is subsequently confronted with the
texts in the project sees the texts in his/her language of choice.
User texts and system texts
In the interests of clarity, a distinction is drawn between user texts and system texts:
User texts are texts created by the user.
System texts are texts created automatically and which are a product of configuration in
the project.
The project texts are managed in the project text editor. This can be found in the project tree
under "Languages & Resources > Project texts".
Examples of multilingual project texts
You can, for example, manage the following types of text in more than one language:
Display texts
Alarm texts
Comments in tables
Labels of screen objects
Text lists
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2339
Translating texts
There are two ways of translating texts.
Translating texts directly
You can enter the translations for the individual project languages directly in the "Project
texts" editor.
Translating texts using reference texts
You can change the editing language for shorter texts. You can enter the new texts in the
editing language while the texts of the reference language are displayed.
See also
Working with multiple languages (Page 2338)
Translating texts directly (Page 2340)
Translating texts using reference texts (Page 2342)
Exporting project texts (Page 2343)
Importing project texts (Page 2345)
Translating texts directly
Translating texts
If you use several languages in your project, you can translate individual texts directly. As soon
as you change the language of the software user interface, the translated texts are available
in the selected language.
Requirements
You are in the project view.
A project is open.
You have selected at least two further project languages.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2340 System Manual, 08/2011,
Procedure
Proceed as follows to translate individual texts:
1. Click on the arrow to the left of "Languages & resources" in the project tree.
The elements below this are displayed.
2. Double-click on "Project texts".
A list with the texts in the project is displayed in the work area. There is a separate column
for each project language.
3. To group identical texts and translate them simultaneously, click on the " " button in the
toolbar.
4. To hide texts that do not have a translation, click on the button in the toolbar.
5. Click on an empty column and enter the translation.
Result
You have translated individual texts in the "Project texts" editor. The texts will then be displayed
in the runtime language.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2341
See also
Working with multiple languages (Page 2338)
Exporting project texts (Page 2343)
Project text basics (Page 2339)
Importing project texts (Page 2345)
Translating texts using reference texts
Introduction
After changing the editing language, all texts are shown in input boxes in the new editing
language. If there is not yet a translation available for this language, the input boxes are empty
or filled with default values.
If you enter text again in an input field, this is saved in the current editing language. Following
this, the texts exist in two project languages for this input field, in the previous editing language
and in the current editing language. This makes it possible to create texts in several project
languages.
You can display existing translations for an input box in other project languages. These serve
as a comparison for text input in the current editing language and they are known as the
reference language.
Requirement
There is at least one translation into a different project language for an input field.
Procedure
To display the translation of an input cell in a reference language, follow these steps:
1. Select "Tasks > Languages & resources" in the task card.
2. Select a reference language from the "Reference language" drop-down list.
Result
The reference language is preset. If you click in a text block, translations that already exist in
other project languages are shown in the "Tasks > Reference text" task card.
See also
Working with multiple languages (Page 2338)
Exporting project texts (Page 2343)
Project text basics (Page 2339)
Importing project texts (Page 2345)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2342 System Manual, 08/2011,
Exporting project texts
Project texts are exported for translation. Texts are exported to Office Open XML files ending
in ".xlsx". These files can be edited in Microsoft Excel, for example.
You can exchange the file with the translators and import it back to the project as soon as it
has been translated.
Requirements
At least two languages have been enabled in the "Project languages" editor, for example,
Italian and French.
Exporting project texts
To export individual project texts, proceed as follows:
1. Click on the arrow to the left of "Languages & resources" in the project tree.
The child elements are displayed.
2. Double-click on "Project texts". The "Project texts" editor will open.
3. Select the texts you want to export.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2343
4. Click on the button. The "Export" dialog opens.
5. From the "Source language" drop-down list, select the language from which you wish to
translate, for example Italian.
6. From the "Target language" drop-down list, select the language into which the texts are to
be translated, for example, French.
7. Enter a file path and a file name for the export file in the "Export file" input field.
8. Click "Export".
Result
The texts selected in the "Project texts" editor are written to an xlsx file. The xlsx file will be
stored in the specified folder.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2344 System Manual, 08/2011,
You can alternatively select and export all project texts from categories. Select "User texts" or
"System texts" in the "Export" dialog in line with the type of texts you wish to export. In this
case, export can additionally be limited by categories.
Note
Project texts in library objects cannot be exported.
See also
Working with multiple languages (Page 2338)
Translating texts using reference texts (Page 2342)
Translating texts directly (Page 2340)
Project text basics (Page 2339)
Importing project texts (Page 2345)
Importing project texts
Edit the xlsx file or send it to a translator. Import the texts once they have been translated. The
foreign languages will be imported to the relevant object in the project.
Requirements
At least two languages have been enabled in the "Project languages" editor, for example,
Italian and French.
Importing project texts
To import a project text file, proceed as follows:
1. Click on the arrow to the left of "Languages & resources" in the project tree.
The lower-level elements will be displayed.
2. Double-click on "Project texts". The "Project texts" editor will open.
3. Click on the button. The "Import" dialog opens.
4. Select the path and file name of the import file from the "Import file" field.
5. Activate the "Import source language" check box if you have made changes to the source
language in the export file and would like to overwrite the entries in the project with the
changes.
6. Click on "Import".
Result
You have imported the project texts.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2345
See also
Exporting project texts (Page 2343)
Working with multiple languages (Page 2338)
Project text basics (Page 2339)
Translating texts directly (Page 2340)
Translating texts using reference texts (Page 2342)
9.12.5.6 Using language-specific graphics
"Graphics" editor
Introduction
You use the "Graphics" editor to manage the configured graphic objects in different language
versions. Multilingual projects sometimes also require language-specific versions of the
graphics, for example, if
the graphics contain text;
cultural aspects play a role in the graphics.
Opening the "Graphics" editor
Double-click on "Languages and resources" in the project tree.
Work area
The work area displays all configured graphic objects in a table. There is a separate column
in the table for each project language. Each column in the table contains the versions of the
graphics for one particular language.
In addition, you can specify a default graphic for each graphic to be displayed whenever a
language-specific graphic for a project language does not exist.
Preview
The preview shows you how the graphics will look on various devices.
See also
Storing external graphics in the graphics library (Basic, Advanced, Professional) (Page 2348)
Storing graphics in the graphics library (Basic, Advanced, Professional) (Page 2347)
Languages in WinCC (Page 2332)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2346 System Manual, 08/2011,
Storing graphics in the graphics library (Basic, Advanced, Professional)
Introduction
You use the "Graphics" editor to import graphics you want to use in screens in the "Screens"
editor. It also allows you to manage language-specific versions of graphics. A preview shows
the graphic displays on various HMI devices.
Requirement
The language-dependent versions of a graphic are available.
Multiple languages have been enabled in the "Project languages" editor.
The "Graphics" editor is open.
Inserting graphics
1. Click "Add" in the "Graphics library" table. A dialog box opens.
2. Select the required graphic file.
3. Click "Open" in the dialog box.
The graphic will be imported to the project and displayed in all cells in this row in the
"Graphics" editor.
4. Click in the corresponding cell of a language for which a language-dependent version of
this graphic exists.
5. Select "Add graphic" from the shortcut menu. A dialog box opens.
6. Select the desired graphic file and click "Open."
The language-dependent version is inserted in the table in place of the reference language
graphic.
7. Then, in the "Default graphic" column, import a graphic to be displayed in runtime for those
languages for which there is no language-specific graphic.
You can also drag&drop a graphic from Windows Explorer to the relevant position in the
"Graphics library" table.
Displaying graphics in the HMI device preview
1. Click on a graphic in the table.
2. Select the required HMI device under "Properties > Graphics settings > Device preview" in
the Inspector window.
The graphic will then be displayed as it will appear in runtime on the selected HMI device.
Result
The graphics added are available in the "Graphics" editor. The graphic assigned to the
respective editing language will be displayed during editing. The default screen will be
displayed in all editing languages for which no screen has been imported.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2347
The screens assigned to the respective runtime language are displayed during runtime. The
default screen is displayed in all runtime languages for which a screen has not been imported.
Note
If you disable a project language, all of the graphic objects you have already created in this
language will be deleted from the current project.
See also
"Graphics" editor (Page 2346)
Storing external graphics in the graphics library (Basic, Advanced, Professional)
Introduction
To display graphics that have been created in an external graphics program in your screens,
you will first have to store these graphics in the graphics browser of the WinCC project.
Requirement
Multiple languages have been enabled in the "Project languages" editor.
The "Graphics" editor is open.
There is a graphic in the "Graphics" editor.
Creating and adding a new graphic as an OLE object
1. Click "Add" in the "Graphics library" table. A dialog box opens.
2. Navigate to the folder in which the graphic is stored.
3. Click "Open" in the dialog box.
The graphic will be imported to the project and displayed in all cells in this row in the
"Graphics" editor.
4. Click in the corresponding cell of a language for which a language-dependent version of
this graphic exists.
5. Select "Insert object" from the shortcut menu. The "Insert object" dialog box opens.
Note
In addition, the dialog "External application running..." will open. The dialog will not close
until you exit the external application.
6. Select "Insert object > Create new" and an object type in the dialog.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2348 System Manual, 08/2011,
7. Click "OK." The associated graphic program is opened.
8. Close the graphics program once you have created the graphic.
The graphic will be stored in the graphic programming software standard format and added
to the graphic browser.
Inserting created graphics in WinCC
1. Click in the corresponding cell of a language for which a language-dependent version of
this graphic exists.
2. Select "Insert object" from the shortcut menu. The "Insert object" dialog box opens.
Note
In addition, the dialog "External application running..." will open. The dialog will not close
until you exit the external application.
3. From the "Insert object" dialog box, select "Create from file."
4. Click the "Browse" button.
5. Navigate to the created graphic and select it.
Note
To import graphics files, note the following size restrictions:
*.bmp, *.tif, *.emf, *.wmf 4 MB
*.jpg, *.jpeg, *.ico, *.gif "*1 MB
Result
The OLE objects added are available in the "Graphics" editor.
Versions of the graphics for the current editing language are displayed in the "Screens" editor.
The default graphic is displayed in all editing languages for which no screen has been imported.
The graphic is displayed in runtime in the set runtime language. The default graphic is displayed
in all runtime languages for which no graphic has been imported.
You can double-click OLE objects in your library to open them for editing in the corresponding
graphic editor.
See also
"Graphics" editor (Page 2346)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2349
9.12.5.7 Languages in runtime
Languages in Runtime
Using multiple runtime languages
You can decide which project languages are to be used in runtime on a particular HMI device.
The number of runtime languages that can be available at one time on the HMI device depends
on the device. To enable the operator to switch between languages during runtime, you must
configure a corresponding operator control.
When runtime starts, the project is displayed according to the most recent language setting.
When runtime starts the first time, the language with the lowest number in the "Order for
language setting" is displayed.
Setting runtime languages during configuration
In the "Languages and Fonts" editor you can specifiy:
The project languages to be available as runtime languages for the respective HMI device.
The order in which the languages are to be switched.
See also
Methods for language switching (Page 2350)
Enabling the runtime language (Page 2351)
Setting the runtime language order for language switching (Page 2353)
Setting the default font for a runtime language (Page 2355)
Selecting the log language (Page 2356)
Languages in WinCC (Page 2332)
Methods for language switching
Introduction
You need to configure language switching if you want to have multiple runtime languages
available on the HMI device. This is necessary to enable the operator to switch between the
various Runtime languages.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2350 System Manual, 08/2011,
Methods for language switching
You can configure the following methods for language switching:
Direct language selection
Each language is set by means of a separate button. In this case, you create a button for
each Runtime language.
Language switching
The operator switches the languages using a button.
Regardless of the method used, the button names must be translated into each of the
languages used. You can also configure an output field that displays the current language
setting.
See also
Languages in Runtime (Page 2350)
Selecting the log language (Page 2356)
Enabling the runtime language (Page 2351)
Setting the runtime language order for language switching (Page 2353)
Setting the default font for a runtime language (Page 2355)
Enabling the runtime language
Introduction
The "Language & Font" editor shows all project languages available in the project. Here you
select which project languages are to be available as runtime languages on the HMI device.
Requirements
Multiple languages have been enabled in the "Project languages" editor.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2351
Procedure
1. Double-click on "Runtime settings" in the project tree.
2. Click on "Language & Font".
3. Select the following languages:
German
Chinese
French
Result
You have now set three runtime languages. A number is automatically assigned to each
language in the "Order" column. The enabled runtime languages are transferred with the
compiled project to the HMI device.
If the number of languages selected exceeds the number that can be transferred to the HMI
device, the table background changes color.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2352 System Manual, 08/2011,
See also
Languages in Runtime (Page 2350)
Selecting the log language (Page 2356)
Setting the runtime language order for language switching (Page 2353)
Methods for language switching (Page 2350)
Setting the runtime language order for language switching
Introduction
You specify the language order for runtime language switching. The first time runtime starts,
the project is displayed in the language with the lowest number in the "Order" column.
Requirements
Multiple languages have been enabled in the "Project languages" editor.
"Language & Font" is open in the editor and three runtime languages have been set in the
following order:
1. German
2. Chinese
3. French
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2353
Procedure
1. Select the runtime language "German".
2. Click the button. The runtime language "German" will move down a place. The number
will automatically be changed to "2" in the "Order" column.
Result
You have changed the order of runtime languages. The first time runtime starts, the project
will be displayed in the language with the smallest number, in other words Chinese. If the
language is switched, this will happen in numerical order.
See also
Languages in Runtime (Page 2350)
Selecting the log language (Page 2356)
Enabling the runtime language (Page 2351)
Setting the default font for a runtime language (Page 2355)
Methods for language switching (Page 2350)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2354 System Manual, 08/2011,
Setting the default font for a runtime language
Introduction
You can specify the font used to display the texts for each runtime language on the HMI device
in the "Language & Font" editor. The default font is used in all texts, such as dialog texts, for
which you cannot define a specific font.
WinCC offers only fonts supported by the HMI device.
Requirements
Multiple languages have been enabled in the "Project languages" editor.
Three runtime languages have been enabled in the "Language & Font" editor.
1. Chinese
2. German
3. French
Procedure
1. Double-click on "Runtime settings" in the project tree.
2. Click on "Language & Font". The table shows the runtime languages and fonts set.
3. Click in the "French" row in the "Default font" column.
4. Select the font to be used by default if a font cannot be selected for a given text.
Result
The project texts for the runtime language "French" are displayed on the HMI device in the
selected font.
These fonts are transferred to the HMI device during a transfer operation.
The default font is also used for the representation of dialogs in the operating system of the
HMI device. Select a smaller font as default if the full length of the dialog texts or headers is
not displayed.
See also
Languages in Runtime (Page 2350)
Selecting the log language (Page 2356)
Setting the runtime language order for language switching (Page 2353)
Methods for language switching (Page 2350)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2355
Selecting the log language
Introduction
In the "Runtime settings > General" editor, select the language to be used for writing to logs
in runtime.
Requirements
The languages used in your project are activated in the "Project languages" editor, for
example "German" and "English" .
Procedure
1. Double-click on "Runtime settings" in the project tree.
2. Click on "Language & Font".
3. Activate the runtime languages, for example, "German" and "English".
4. Specify the "order":
1 German
2 English
5. Click on "Runtime settings > General".
6. Select "German" for "Logs > Log language".
Result
After loading, the project will start in the runtime language "German". The logs are now written
in German. During runtime, the operator switches the runtime language to English. The logs
will still to be written in German.
See also
Languages in Runtime (Page 2350)
Setting the default font for a runtime language (Page 2355)
Setting the runtime language order for language switching (Page 2353)
Methods for language switching (Page 2350)
Enabling the runtime language (Page 2351)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2356 System Manual, 08/2011,
9.12.5.8 Example of multilingual configuration
Example: Configuring a button for language switching
Introduction
In this example, you configure a button that can be used to toggle between multiple runtime
languages during runtime.
Requirements
You have completed the "Configuring a button in multiple languages" example.
The "Screen_1" screen is open.
The button on the screen has been selected.
Procedure
1. In the Inspector window, select "Properties > Events > Press".
2. Click on "Add function" in the table.
3. Select the "SetLanguage" system function.
Result
You have assigned the button the function "SetLanguage". Pressing the button during runtime
will switch the runtime language. The runtime languages are switched in the order specified
by the number sequence in the "Languages and fonts" editor.
See also
Example: Configuring a button in multiple languages (Page 2357)
Example: Configuring a button for language switching for each runtime language
(Page 2358)
Languages in WinCC (Page 2332)
Example: Configuring a button in multiple languages
Introduction
In this example, you configure a "Sprache umschalten" button in German and "Switch
language" button in English.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2357
Requirements
The languages "German" and "English" have been enabled in the "Project languages"
editor.
German has been set as editing and reference language.
You have created and opened the "Screen_1" screen.
The Inspector window is open.
Procedure
1. Drag-and-drop a button from the "Tools" task card into the screen.
The button will be added to the screen.
2. In the Inspector window, open "Properties > Properties > General".
3. Enter the text ""Sprache umschalten" under "Text > off".
4. Press <Enter> to confirm. The button is named.
5. Open the "Tasks" task card.
6. Select "English" under "Languages & Resources > Editing language".
7. Enter the label "Switch Language" under "Properties > Properties > General > Text > Off"
in the Inspector window.
Result
The button name is configured in German and English language. The button name
corresponding with the current Runtime language is shown in Runtime.
See also
Example: Configuring a button for language switching (Page 2357)
Example: Configuring a button for language switching for each runtime language
(Page 2358)
Example: Configuring a button for language switching for each runtime language
Introduction
In this example, you configure a "Sprache umschalten" button in German and "Switch
language" button in English.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2358 System Manual, 08/2011,
Requirements
The following languages have been enabled in the "Project languages" editor
German
English
Italian
All languages have been set as runtime languages in the "Runtime settings > Language &
Font" editor.
You have created and opened the "Screen_1" screen.
Three buttons have been created on the screen:
Button_1 labelled "Deutsch"
Button_2 labelled "English"
Button_3 labelled "Italiano"
The Inspector window is open.
Procedure
1. Select "Button_1".
2. In the Inspector window, select "Properties > Events > Press".
3. Click on <Add function> in the table.
4. Select the "SetLanguage" system function.
5. Click on the "Switch" field.
6. Click on the button.
7. Select "Runtime language". The field will be highlighted in red.
8. Select "German" from the drop-down list.
9. Repeat steps 1 - 8 for the other two buttons and select the corresponding runtime language.
Result
You have configured three buttons for switching language in runtime. Each button will switch
to a different runtime language. For example, clicking on the "English" button during runtime
will switch the runtime language to English.
See also
Example: Configuring a button for language switching (Page 2357)
Example: Configuring a button in multiple languages (Page 2357)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2359
9.12.6 Replacing devices
9.12.6.1 Basics
Introduction
You can use existing configurations for new devices and optimize these configurations with
little manual effort.
All data configured by you is retained in the configuration data. This means you do not need
to copy individual objects of one device and paste them to another.
Principle
The following applies when you replace devices:
Only functions supported by the new device are available. Only configuration data
supported by the new device are displayed.
This affects
recipes,
objects available on the screens,
available system functions,
available communication logs, etc.
The number of supported objects, such as screens or tags, may be limited on the new
device. If the existing objects exceed the limitations on the new device, the objects are
displayed in full. The objects are, however, highlighted in color in the individual editors. An
error is generated when the project data is compiled.
Manual post processing is required when switching to a device with fewer features.
Example: Limited number of connections
All connections will be highlighted in color as invalid if fewer connections are supported on
the new device than have been configured. Delete any excess connections.
Note
If you replace a Panel and select a PC Station as your new device, for example, WinCC
Runtime Advanced will automatically be moved below the PC Station in the project tree.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2360 System Manual, 08/2011,
See also
Example: Replacing devices (Page 2371)
Screen adjustment options (Page 2366)
Key assignment when replacing devices (Page 2362)
Device-specific functions (Page 2361)
Engineering system (Page 2512)
Basic Panel (Page 2514)
Panel (Page 2517)
Mobile Panel (Page 2521)
Multi Panel (Page 2525)
Comfort Panel (Page 2529)
WinCC Runtime Advanced (Page 2532)
9.12.6.2 Device-specific functions
Device-specific functions
Functions dependent on the device
Functions dependent on the device are implemented as follows:
Colors
The color is changed automatically when you switch from a device with full color display to
one with a smaller color range.
If you change the color manually and then change back again to a device with a larger
range of colors, the reduced range of colors will be retained.
Fonts
Any configured font not available on a device will be replaced by a similar one or by the
configured default font. The default font depends on the device selected.
Character sets with different font sizes
Avoid using too many different font sizes when configuring the following devices:
OP 73
OP 77A
TP 177A
A character set is downloaded to the device for each font size. Check the Inspector window
during compilation to see how much of the device memory is being used by the character
sets.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2361
Font size
Use small Windows fonts to display the text on devices. If you use large Windows fonts,
then, depending on the size of the display, the text will not be displayed in full.
Using font sizes of 28 pixels or more for the OP 77A and TP 177A devices will affect device
performance.
The character scope is much greater for Asian languages. The use of different font sizes
therefore has serious implications on the memory requirements of all devices.
Use the same font type for all large characters throughout the project to ensure effective
and efficient configuration.
Screens and screen objects
If the new device supports a different resolution than the previous device when you replace
a device, there are several ways to adjust the screens.
Adjust the size of the screens to the new device in the menu under "Options > Settings >
Visualization > Fit to size screen".
See also
Example: Replacing devices (Page 2371)
Basics (Page 2360)
Key assignment when replacing devices
Introduction
The devices available each have different function keys. The functions configured for these
keys will be mapped to the available function keys of the new device if the device is replaced.
Function key mapping
The function keys to the left and right of the display are mapped from top to bottom to the new
device. If the new device has fewer keys, the keys it does not have are not mapped. The
function keys below the display are mapped from left to right to the new device. If the new
device has fewer keys, the keys it does not have are not mapped.
Example: Exchange MP 377 with KP700 Comfort
You have configured a function on key S3 on the MP 377. This function is triggered by F5 if
the panel is replaced with an KP700 Comfort.
If you use the S8 key on an MP 377, this function is no longer available when the panel is
replaced with a KP700 Comfort.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2362 System Manual, 08/2011,
Mapping K-keys
K-keys are only mapped to the same K-keys in the new device, e.g. K5 to K5.
If the new device has no K keys, configurations for the K keys are lost.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2363
If you replace a KP700 with an OP 277,for example, the F1 - F14 keys are retained. The
configuration of the K keys is lost, because the KP700 has no K keys.
Mapping of control keys and cursor keys
The following keys are mapped only to the same keys of the new device:
HELP
ESC
ACK
ENTER
PAGE UP
PAGE DOWN
CURSOR UP
CURSOR DOWN
Exception
"HELP" is triggered by "SHIFT+ ESC" on OP 73.
See also
Key assignment when replacing devices (Page 2364)
Basics (Page 2360)
Screen adjustment options (Page 2366)
Key assignment when replacing devices
Introduction
The devices available each have different function keys. The functions configured for these
keys will be mapped to the available function keys of the new device if the device is replaced.
Function key mapping
The function keys below the display are mapped from left to right to the new device. If the new
device has fewer keys, the keys it does not have are not mapped.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2364 System Manual, 08/2011,
Example: Replacing a KTP1000 Basic with a KTP600 Basic
You have configured a function for F2 in KTP1000 Basic. This function is triggered by F2
following replacement with a KTP600 Basic.
If you have used F7 in a KTP1000 Basic, this function will no longer be available if the panel
is replaced with a KTP600 Basic.
Mapping of control keys and cursor keys
The following keys are mapped only to the same keys of the new device:
HELP
ESC
ACK
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2365
ENTER
PAGE UP
PAGE DOWN
CURSOR UP
CURSOR DOWN
See also
Key assignment when replacing devices (Page 2362)
9.12.6.3 Adjust screens to the new device
Screen adjustment options
Introduction
Select fit to size for screens before you replace a device. Fit to size is particularly important
when switching devices with different display resolutions.
Screen adjustment when replacing devices
Adjust the size of the screens to the new device in the menu under "Options > Settings >
Visualization > Fit to size screen".
Select one of the following settings.
None
The screens are not scaled. The objects in the screen retain their position and size.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2366 System Manual, 08/2011,
This option may result in objects being outside the configurable area if the display of the new
device is smaller than the old one.
Adjusting the width and height to the new device
The position and object size are adjusted to the new display size. Adjustment takes place along
the x-axis and the y-axis. Graphics and font size are adjusted accordingly.
Object adjustment to content can be prevented for objects such as graphic views or text fields.
Note
The objects are distorted if you replace a device with a landscape format display with a device
with a portrait format display. The difference in display format can, for example, result in object
labels being cut off and content not being fitted to the object. You must therefore adjust the
screens to the new device once you have replaced devices.
Fit screen to window height
The aspect ratio is maintained and the screens are adjusted to the height of the new device.
Use this option when you are replacing a device with display format 4:3, for example, with a
device with widescreen.
Fit screen to window width
The aspect ratio is maintained and the screens are adjusted to the width of the new device.
Use this option when you are replacing a device with widescreen, for example, with a device
with display format 4:3.
Free scale factor
You select a free scale factor for screen adjustment. You can specify a factor for the x-axis
and the y-axis.
Using a free scale factor of < 1 may distort the objects. Object labels may, for example, be cut
off and the content may not be fitted to the object.
You must therefore adjust the screens to the new device once you have replaced devices.
Note
The aspect ratio is not adjusted for objects with a fixed aspect ratio, for example, gauge,
circle. The objects are displayed on the new device with the same aspect ratio as prior to the
replacement of the device.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2367
See also
Example: Adjusting screens (Page 2370)
Specifying the position of screen objects (Page 2369)
Fit objects to contents (Page 2368)
Basics (Page 2360)
Key assignment when replacing devices (Page 2362)
Fit objects to contents
Introduction
For some objects, you can specify fit to respective content in the Inspector window, for example:
Text field: fit to text content
I/O field: fit to text content
Symbolic I/O field: fit to text content or to text list
Graphic view: fit to included graphic
Fit to size for text and graphic objects
Disable automatic fit to size of the individual objects in the menu under "Options > Settings >
Visualization > Resize screen and screen objects > Fit to content". This results in scaling of
the objects as specified under "Options > Settings > Visualization > Resize screen and screen
objects".
Select the objects which are not automatically fitted to size.
If "Disable 'fit to size' for text objects" is activated, automatic fit to size is ignored in the text
object properties.
If you have activated "Fit screen to window height", the text field along with the other objects
is scaled in accordance with the height of the new device.
If "Disable 'fit to size' for graphic objects" is activated, automatic fit to size is ignored in the
graphic object properties.
If you have activated "Fit screen to window width", the graphics view along with the other
objects is scaled in accordance with the width of the new device.
Note
The settings have no effect on screen objects whose size cannot be changed, such as alarm
indicators or screen objects with a fixed aspect ratio.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2368 System Manual, 08/2011,
"Disable 'fit to size' for text objects" and "Disable 'fit to size' for graphic objects" have no effect
if:
- You have activated "Resize screen and screen objects > None".
- You have activated "Fit screen to window width and height" and the new device has the same
resolution as the current device.
- You have activated "Fit screen to window height" and the new device has the same resolution
as the current device.
- You have activated "Fit screen to window width" and the new device has the same resolution
as the current device.
See also
Specifying the position of screen objects (Page 2369)
Screen adjustment options (Page 2366)
Example: Adjusting screens (Page 2370)
Specifying the position of screen objects
Introduction
There are various ways to adjust the position of screen objects to the new device.
Select position
Adjust the position of the screen objects to the new device in the menu under "Options >
Settings > Visualization > Fit to size screen > Select position".
Example
The following option aligns the objects with the top left edge.
The following object centers the objects in the middle of the screen.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2369
See also
Screen adjustment options (Page 2366)
Fit objects to contents (Page 2368)
Example: Adjusting screens (Page 2370)
9.12.6.4 Example: Replacing devices
Example: Procedures overview
Introduction
In the following example you replace a TP177 B 6'' PN/DP with a TP700 Comfort.
Procedures overview
The procedure when replacing a device is as follows:
1. Adjust screens to the new device
2. Replacing devices
See also
Example: Adjusting screens (Page 2370)
Example: Replacing devices (Page 2371)
Example: Adjusting screens
Introduction
Adapt the screen before you replace a device. Screen adaptation is required as the display
formats are different.
The TP 177B format is 320 x 240 pixels while the format of the TP700 Comfort is 800 x 480
pixels.
Requirements
A project is open.
The TP 177B 6'' PN/DP device is used in the project.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2370 System Manual, 08/2011,
Adjusting screens
1. Open the "Options > Settings" menu.
2. Click on "Visualization > Fit screen to size".
3. Select "Fit screen to window height".
4. Select "Disable fit to size for text objects".
5. Select "Disable fit to size for graphical objects".
Result
You have carried out screen adjustment in preparation for replacing devices.
See also
Example: Replacing devices (Page 2371)
Screen adjustment options (Page 2366)
Specifying the position of screen objects (Page 2369)
Fit objects to contents (Page 2368)
Example: Procedures overview (Page 2370)
Example: Replacing devices
Introduction
The following example shows you how to replace a device.
Requirements
A project has been created and opened.
The TP 177B 6'' PN/DP device is used in the project.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2371
Procedure
1. Double-click on "Devices & Networks" in the project tree. The editor will open.
2. Click on the "TP 177B" device.
3. Select "Replace device" in the device shortcut menu. A dialog box opens.
4. Select the TP700 Comfort device.
Details of hardware differences can be found in the "Compatibility information".
5. Click on the "OK" button. Device replacement is started.
Result
You have replaced the TP 177B device used in the project. You now use the TP700 Comfort
device.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2372 System Manual, 08/2011,
See also
Example: Adjusting screens (Page 2370)
Device-specific functions (Page 2361)
Basics (Page 2360)
Example: Procedures overview (Page 2370)
9.12.7 Copying between devices and editors
9.12.7.1 Basics
Basics
Copying and pasting within an HMI device
You can copy and paste objects, such as display objects, within an HMI device. If the object
is already created in the editor, when the object name is inserted a number is automatically
attached, in accordance with the following principle:
"<Object_name>_1" is renamed to "<Object_name>_2".
"<Object_name>_2" is renamed to "<Object_name>_3".
Copying and pasting between HMI devices
You can also copy and paste between HMI devices. If an object with the same name already
exists, you have the following options:
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2373
Note
Exception to this basic rule
Copying and pasting of an alarm class that has been generated from project-wide alarm class
is handled differently than with this basic rule. When the copied alarm class already exists in
the target HMI device within the same project, the "Paste" command is not performed.
Copying user-defined folders
You can create user-defined folders for editors, for example, for HMI tags, screens, etc.
You can copy user-defined folders and paste them into another HMI device. The objects
contained in a user-defined folder may exceed the limitations applying to the other HMI device,
such as the number of supported screens. After they have been pasted, all the objects are
displayed. An error is displayed when the project data is compiled.
System folders cannot be copied.
See also
Unsupported objects and functionalities (Page 2375)
Copy and paste options (Page 2374)
Copy and paste options
Copy and paste options
Copy and pasting individual objects simplifies configuration.
WinCC offers a number of options for copying and pasting objects.
Shortcut menu
To copy and paste objects using the shortcut menu, proceed as follows:
1. Select an object, for example a button.
2. Select "Copy" in the shortcut menu.
3. Move the mouse cursor to the place on the screen where you want to paste the button.
4. Select "Paste" in the shortcut menu.
The button will be pasted together with all properties already defined.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2374 System Manual, 08/2011,
Drag&drop
To drag-and-drop objects, proceed as follows:
1. Click on "Screens > Start" in the project tree of a device.
2. Drag-and-drop the "Start" screen into the "Screens" folder of another device.
3. A dialog will appear if the second device already contains a screen with the same name.
4. Choose whether to replace or rename the existing screen.
See also
Basics (Page 2373)
Unsupported objects and functionalities
Introduction
When an object is copied, all its properties and settings are transferred to the target HMI device.
Unsupported objects
Objects that are not supported in the target HMI device cannot be pasted.
Note
When you copy a screen containing objects which are not supported by the destination HMI
device, the objects remain in the background. When you copy the screen again and the new
device supports the objects, they are displayed again.
Invalid objects
The following objects become invalid once they have been pasted into the target HMI device:
Referenced objects that do not exist in the target HMI device.
Objects with settings that are not supported in the target HMI device.
System functions that were configured for objects and that are not supported in the target
HMI device.
Invalid objects are highlighted by a color coding. Select a supported object or create a new
one. If you retain an invalid object, an error will be displayed when the project data is compiled.
Colors and fonts
Colors and fonts are supported to varying degrees by HMI devices. When unsupported colors
and fonts are pasted, they are replaced by supported colors and fonts. When you paste the
same object back into the source HMI device, the original settings become active again.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2375
See also
Basics (Page 2373)
9.12.7.2 Copy and paste
Copying screens
Introduction
You copy one or more screens from the "Screens" folder and paste them into the "Screens"
folder of another device.
Type and size of the displays
In the case of HMI devices with keys, the available keys are displayed automatically in the
screen. When a screen is copied between HMI devices, the keys are either displayed or hidden;
functions configured for function keys are not transferred.
If there is less space for the screen in the target HMI device than in the source HMI device,
you can adjust the size of and the spacing between existing objects.
Automatic fit to size for objects
1. Select "Options > Settings > Visualization > Resize screen and screen objects" in the menu.
2. Activate, for example, "Fit screen to window width and height".
See also
Screen adjustment options (Page 2366)
Fit objects to contents (Page 2368)
Specifying the position of screen objects (Page 2369)
Copying recipes within an HMI device (Page 2376)
Copying objects with linked objects (Page 2377)
Linked objects copied automatically (Page 2378)
Linked objects copied automatically (Page 2378)
Drag & drop from the details view (Page 2379)
Copying recipes within an HMI device
"Recipes" Editor
You can copy recipes, recipe elements and recipe data records within each table. You copy
a recipe element to another recipe.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2376 System Manual, 08/2011,
Only WinCC Runtime Professional: You can copy a recipe view element to another recipe
view. If a recipe view element of the same name already exists, a conflict dialog is displayed.
You can select whether to replace or rename the recipe element. You can copy recipe elements
to the first empty row of the "Recipe views" editor, "Elements" tab.
You can copy a recipe data record to another recipe, if the other recipe contains the same
number of recipe elements. If the data types differ, the value will be copied to the target data
record but it is assigned an error flag.
"Tags" editor
You can drag-and-drop a tag to a recipe element in the "Tag" column. The tag is linked to the
recipe element. If a tag is already linked, an error message will be generated.
"Screens" editor
If you drag-and-drop a recipe to a screen, a new recipe display will be created and linked to
the recipe.
See also
Copying screens (Page 2376)
Copying objects with linked objects
Introduction
An object is linked to another object in the following situations, for example:
You specify a tag for an alarm as a trigger tag.
The alarm is the object. The tag is the linked object.
You specify a connection for an external tag.
The tag is the object. The connection is the linked object.
The object is always fully inserted during copying and pasting. Whether or not the linked object
is pasted depends on the command used to insert it.
Simple pasting
The linked object is not copied. The linked object is transferred and handled as follows in the
target HMI device:
If an object with the same name exists, the existing object with its settings is used.
If no object with the same name exists, the name of the object will be displayed. The object
becomes invalid.
For some objects, linked objects are pasted automatically during simple pasting.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2377
Extended pasting
Select the "Extended paste" command in the shortcut menu to paste the linked objects as well.
If objects of the same name exist in the target HMI device, you need to decide whether or not
to overwrite each of these objects.
See also
Copying screens (Page 2376)
Linked objects copied automatically
Copying linked objects
The following table shows the objects for which linked objects are pasted automatically in
simple pasting.
Object Linked object
Screen Template
Symbolic I/O field Text list
Graphic I/O field Graphics list
Graphic view Graphic
Tag Alarm
Cycle
Recipe element Text list
Scheduler Triggers
See also
Copying screens (Page 2376)
Linked objects copied automatically
Copying linked objects
The following table shows the objects for which linked objects are pasted automatically in
simple pasting.
Object Linked object
Screen Cycle
Template
Symbolic I/O field Text list
Graphic I/O field Graphics list
Graphic view Graphic
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2378 System Manual, 08/2011,
Object Linked object
Tag Alarm
Logging tag
Cycle
Log Logging tag
Logging tag Log type
Recipe element Text list
Scheduler Triggers
See also
Copying screens (Page 2376)
Drag & drop from the details view
Introduction
You can improve configuration efficiency with just a few simple measures. Below are a few
examples of efficient configuration.
Pasting objects to a screen from the details view
You can drag objects in the details view from various different editors to other editors.
Pasting a symbolic I/O field
1. Open a screen.
2. Click on the "Text and graphics lists" editor in the project tree. All existing text and graphics
lists will be shown in the details view.
3. Click on a text list, for example, "Textlist1" in the Details view.
4. Drag-and-drop a text list from the Details view to a screen. A symbolic I/O field has been
created and connected to the text list "Textlist1".
Pasting a graphic I/O field
1. Open a screen.
2. Click on the "Text and graphics lists" editor in the project tree. All existing text and graphics
lists will be shown in the details view.
3. Click on a graphics list in the Details view, for example "Graficlist1".
4. Drag-and-drop a graphics list from the Details view to a screen. A graphic I/O field has been
created and connected to the graphics list "Graficlist1".
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2379
Pasting an I/O field
1. Open a screen.
2. Click on the "HMI tags" editor in the project tree. All existing HMI tags will be shown in the
Details view.
3. Click on an HMI tag in the Details view, for example "Tag1".
4. Drag-and-drop the HMI tag from the Details view to a screen. An I/O field has been created
and connected to the HMI tag "Tag1".
See also
Copying screens (Page 2376)
9.12.8 Configuring system diagnostics
9.12.8.1 System diagnostics basics
Introduction
You use system diagnostics to detect problems and errors in any part of your plant. WinCC
has two display and operating elements for quick error localization.
The objects for system diagnostics are only available with Comfort Panels.
System diagnostics view
The alarm view shows the status of a PLC while the system diagnostics view gives you an
overview of all devices available in your plant: You navigate directly to the cause of the error
and to the relevant device. You have access to all devices supporting diagnostics you have
configured in the "Devices & networks" editor.
System diagnostics window
The system diagnostics window is an operating and display element that you can only use in
the global screen.
The functions of the system diagnostics window are no different than those of the system
diagnostics view. Because the system diagnostics window is configured in the global screen,
you can, for example, also specify if the object is closable in Runtime.
See also
System diagnostics views (Page 2381)
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2380 System Manual, 08/2011,
9.12.8.2 System diagnostics views
Introduction
There are three different views available in the system diagnostics view and the system
diagnostics window.
Device view
Details view
Matrix view (for master systems, PROFIBUS, PROFINET only)
Device view
The device view shows all the available devices of a layer in a table. Double-clicking on a
device opens either the child devices or the detail view. Symbols in the first column provide
information about the current status of the device.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2381
Details view
The detail view gives detailed information about the selected device and any pending errors.
Check whether the data is correct in the detail view. You can cannot sort error texts in the
detail view.
Matrix view
The matrix view is only available for master systems. The matrix view shows the status of the
subdevices of the master system.
In PROFIBUS, the numbers assigned by Profibus are used as identification (DP station
number).
The IO devices are numbered consecutively from 1 in PROFINET.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2382 System Manual, 08/2011,
Navigation buttons
Button Function
Opens the child devices or the detail view if there are no child devices.
Opens the parent device or the device view if there is no parent device.
Opens the device view.
See also
System diagnostics basics (Page 2380)
9.12.8.3 Configuring system diagnostics objects
Enabling system diagnostics in the PLC
Introduction
Settings must be made in the PLC to enable the PLC to transfer error messages to the system
diagnostics view.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2383
Requirements
A PLC has been created.
The "Devices & Networks" editor is open in the "Device view".
Procedure
1. Select the PLC in the selection list.
2. Click on the PLC and select "Properties" in the shortcut menu. The properties of the PLC
are displayed in the Inspector window.
3. Select "Properties > General > System diagnostics" in the Inspector window.
4. Enable "Activate system diagnostics for this CPU".
5. Select "Properties > General > System diagnostics > Diagnostics support" in the Inspector
window.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2384 System Manual, 08/2011,
6. Activate "Diagnostics status DB".
7. Select the PLC and then "Compile > Hardware configuration" in the shortcut menu.
Result
The settings will be effective following compilation. The PLC can now transfer error messages
to the system diagnostics display.
Adding a system diagnostics indicator
Introduction
The system diagnostics indicator is a predefined graphic symbol of the library which alerts you
to errors in your system.
The library object shows two different statuses:
- No error
- Error
Requirement
A Comfort Panel has been set up in the project.
The "Libraries" task card is opened.
The global library "Buttons and Switches > DiagnosticsButtons" is open.
A screen is open.
A system diagnostics window has been created in the global screen.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2385
Procedure
1. Select the "DiagnosticsIndicator" object in the library.
2. Drag-and-drop the library object to the position in the work area where you want to insert
the object.
The library object is added.
3. Select the library object.
4. Click "Properties > Events" in the Inspector window.
The system function "ShowSystemDiagnosticsWindow" is preset for the event "Click".
Result
The status diagnostics indicator has been added to the project and connected with the system
diagnostics view.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2386 System Manual, 08/2011,
The system diagnostics indicator changes its appearance if an error message is output in
Runtime. The system diagnostics window opens when you click on the system diagnostics
indicator. The system diagnostics window shows the detail view of the affected device.
Configuring access protection for the system diagnostics view
Configure access protection for the system diagnostics indicator to prevent unauthorized
access to the system diagnostics window.
1. Select the "DiagnosticsIndicator" object in the screen.
2. Select an authorization in "Properties > Properties > Security in Runtime" in the Inspector
window.
A logon dialog opens when you click on the system diagnostics indicator in Runtime. The
system diagnostics window does not open unless you have the required authorization.
Configuring a system diagnostics window in the global screen
Introduction
The system diagnostics window gives you an overview of all devices available in your plant.
The system diagnostics window operates like the system diagnostics view, but it is only
available in the global screen.
Requirements
At least one PLC has been created.
The following options have been enabled in each PLC:
Enable system diagnostics for this CPU
Diagnostics status DB
A Comfort Panel has been set up in the project.
The global screen is open.
The Inspector window is open.
Procedure
1. Double-click the "System diagnostics window" object in the "Tools" task card. The object
is added to the global screen.
2. Select "Properties > Properties > Columns" in the Inspector window.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2387
3. Enable the columns that you require in the device view for Runtime, for example:
Status
Name
Operating mode
Slot
Address
4. Enable the properties which you require in the detail view for Runtime, for example:
Status
Name
Operating mode
Plant designation
Address
5. Enable "Column settings > Columns moveable" to move the columns in Runtime.
6. You can change the column headers under "Properties > Properties > Column headers",
if necessary.
7. Enable "Properties > Properties > Window > Closable" to allow the system diagnostics
window to be closed in Runtime.
Result
The system diagnostics window has been added to the global screen. The system diagnostics
window will respond to error messages in the plant and display the device affected.
Configure a system diagnostics indicator in a screen to open the system diagnostics window.
Configuring a graphic I/O field as a system diagnostics indicator
Introduction
Instead of using the object "DiagnosticsIndicator" from the library, you can configure a graphic
I/O field to indicate errors in your plant.
Requirements
At least one PLC has been created.
The following options have been enabled in each PLC:
Enable system diagnostics for this CPU
Diagnostics status DB
A Comfort Panel has been set up in the project.
The "Tools" task card is open.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2388 System Manual, 08/2011,
A bit graphics list has been created with two different graphics for the two statuses.
A screen is open.
You have created a system diagnostic view.
Procedure
1. Double-click on the "Graphic I/O field" object in the "Tools" task card. An I/O field is added
to the screen.
2. Select the "@DiagnosticsIndicatorTag" tag under "Properties > Properties > General > Tag
> Name" in the Inspector window.
3. Select the bit graphics list under "Contents > Graphics list".
4. In the Inspector window, select "Properties > Properties > Appearance > Scrollbars > Type
> No scrollbar".
Configuring a system function for the graphic I/O field
1. Click "Properties > Events" in the Inspector window.
2. Select the "Enable" event.
3. Click on "Add function" in the table.
4. Select the "EnableSystemDiagnosticsView" system function.
5. Select the system diagnostics view.
Result
You have now configured a graphic I/O field which will respond to error messages from the
PLC. The graphic I/O field will change when an error message is output in Runtime. The system
diagnostics window opens when you enable the graphic I/O field. The system diagnostics
window shows the detail view of the affected device.
Configuring the system diagnostic view
Introduction
You add a system diagnostics view to your project to get an overview of all devices available
in your plant.
Requirements
At least one PLC has been created.
The following options have been enabled in each PLC:
Enable system diagnostics for this CPU
Diagnostics status DB
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2389
A Comfort Panel has been set up in the project.
You have created a screen.
The Inspector window is open.
Procedure
1. Double-click the "System diagnostics view" object in the "Tools" task card. The object is
added to the screen.
2. Select "Properties > Properties > Columns" in the Inspector window.
3. Enable the columns that you require in the device view for Runtime, for example:
Status
Name
Operating mode
Slot
Address
4. Activate the columns you need in the detail view for Runtime, for example:
Status
Name
Operating mode
Plant designation
Address
5. Enable "Column settings > Columns moveable" to move the columns in Runtime.
6. You can change the column headers under "Properties > Properties > Column headers",
if necessary.
Result
The system diagnostics view has been added to the screen. Error messages for the entire
plant are now displayed in the system diagnostics view in Runtime.
Visualizing processes (Advanced)
9.12 Using global functions
WinCC Advanced V11.0 SP1
2390 System Manual, 08/2011,
9.13 Compiling and loading
9.13.1 Compiling and loading projects
9.13.1.1 Overview of compiling and loading projects
Overview
The project is compiled in the background even as you are configuring it in WinCC. This
reduces the time for final compilation. When you start compilation, you create a file that can
be run on the corresponding HMI device.
If an error occurs during compilation, WinCC provides support in locating and correcting it.
Once you have corrected any problems, you download the compiled project to the HMI devices
on which the project is to run. If the configuration PC is not connected to the HMI device, save
the compiled project on a data medium of your choice. The compiled project is then transferred
from a PC connected to the HMI device to the HMI device.
If you are using HMI tags in your project that are connected to PLC tags, you should also
compile all modified S7 blocks with the command "Compile > Software" in the shortcut menu
before you compile the HMI device.
Project
The term "project" has two different meanings in the contexts of compilation and loading.
"Project" is the WinCC project on the configuration PC. "Project" is also the Runtime project
you create by compiling the configuration data of an HMI device and download to the HMI
device.
WinCC project: contains the configuration data of one or more HMI devices
Runtime project: contains the compiled configuration data of an HMI device
The figure below illustrates the link between WinCC projects and Runtime projects using the
example of the "Compile and load" process:
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2391
File system
Configuration PC
Compile Download
HMl devices
Download
Download
File system
- Screens
- HMl tags
- ...
- Screens
- HMl tags
- ...
File system
File system
- Screens
- HMl tags
- ...
RT projects ES project "Mixing"
Runtime
Runtime
Runtime
HMl_3
HMl_3
HMl_2
RT Professional
RT Advanced
HMl_3
HMl_2
HMl_1
HMl_1 (Basic Panel)
WinCC
HMl_3 (RT Professional)
HMl_2 (RT Advanced)
HMl_1
Basic Panel
HMl_2
HMl_1
Runtime
Runtime is the software for process visualization. In Runtime, you execute the project in
process mode.
A distinction is made between two types of Runtime:
1. Runtime on a panel
Before executing a Runtime project on a panel, you have to transfer the Runtime project
to the panel before startup.
2. Runtime on a PC
You can execute the Runtime project directly on the configuration PC if Runtime has been
installed on the configuration PC.
If you want to execute the Runtime project on a different PC, you have to transfer the
Runtime project to the PC before startup.
Simulation
You test your configuration with a simulation. You can start a simulation without a link to the
active process.
In a simulation, you test configured tags or screen changes, for example. During the simulation,
the configured tags can be manipulated, activated and deactivated with the help of the tag
simulator.
There are two types of simulation:
1. Simulating a panel
If you created a panel in your project, the panel is displayed in the simulation. With the help
of this type of simulation, you can test your configuration on the HMI device without
transferring the project to the panel.
2. Simulating Runtime
Simulating Runtime allows you to test the project directly on the configuration PC.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2392 System Manual, 08/2011,
See also
Generating a "Pack&Go" file (Page 2396)
Starting Runtime Advanced and Panels (Page 2403)
9.13.1.2 Compiling a project
Introduction
The changes made to the project are compiled in the background even as you are configuring
a project in WinCC. Projects are compiled automatically when you load them. This ensures
that the latest version of the project is loaded at all times.
WinCC checks consistency of the project during compilation. The error locations in the project
are listed in the Inspector window. You can jump directly to the source of the error from the
entry in the Inspector window. Check and correct errors found.
Scope of the compilation
Configuration data is compiled in the background as soon as you start configuring an HMI
device. If you compile a project manually, only the changes in the configuration made since
the last compilation process are compiled in the background.
You can start complete project compilation manually at any time; this may, for example, be
done to test the consistency of the configured data.
Requirement
A project is open.
Procedure
Proceed as follows to compile a project:
1. If you want to compile several HMI devices at the same time, select all the relevant HMI
devices with multiple selection in the project tree.
2. Compile the project:
For delta compilation of the project, select the "Compile > Software" command from the
shortcut menu of the HMI device.
To compile all project data, select the "Compile > Software (compile all)" command from
the shortcut menu.
Result
The configuration data of all selected HMI devices is compiled. Any errors that occur during
compilation are shown in the Inspector window.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2393
9.13.1.3 Loading projects
Overview for loading of projects
Overview
Delta data of the project is automatically compiled before you download it to one or several
HMI devices. This always ensures that the latest version of the project is transferred.
Loading a project to an HMI device
The following steps are completed prior to downloading:
1. The download settings are verified. The "Extended loading" dialog box is opened
automatically during the initial download of a project to an HMI device. You use this dialog
to define the protocol and interface or destination path for the project in accordance with
the HMI device Runtime used.
If, for example, the HMI device is part of a subnetwork, you also select the subnetwork and
the 1st gateway.
You can call the "Extended loading" dialog at any time with the menu command "Online >
Advanced download to device...".
The "Load preview" dialog opens.
2. The project is compiled. Warnings and errors during compilation are displayed in the
Inspector window and in the "Load preview" dialog.
3. The "Load preview" dialog shows you the following information for each HMI device:
The individual steps for loading
Presettings that take effect at loading. You can change the default settings for this
download process, if necessary.
Warning events (optional). You can download a project while ignoring the "warnings".
The functionality may be restricted in Runtime.
Error events (optional). You cannot load the project. Eliminate the errors and then reload
the project.
WinCC will open the invalid configuration in the corresponding editor if you double-click
the error message in the Inspector window. Correct the errors and reload the project.
If you are using HMI tags in your project that are connected to PLC tags, you should also
compile all modified S7 blocks with the command "Compile > Software" in the shortcut menu
before you compile the HMI device.
Loading a project without a connected HMI device
If you cannot establish a direct connection from the configuration PC to the HMI device, save
the compiled project on a data medium of your choice. Additional steps depend on the Runtime
used:
Panel Runtime: Copy the compiled project to a PC connected to the HMI device, for
example, via a network. Download the project from this PC to the HMI device ("Pack&Go").
Runtime Advanced: Move the compiled project to the HMI device.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2394 System Manual, 08/2011,
Loading with S7 routing
Configure the S7 routing settings in the "Devices & Networks" editor in the relevant PLC. The
settings depend on the device configured.
S7 routing supports the following protocols:
MPI/PROFIBUS
Ethernet
See also
Loading a project (Page 2395)
Generating a "Pack&Go" file (Page 2396)
Loading a project
Introduction
Before a project can run on an HMI device, you must first load it to the HMI device. During
loading, you must most importantly specify whether existing data on the HMI device such as
"user administration" and "recipe data" is to be overwritten.
As a general rule, only one project can be active in Runtime on an HMI device. An HMI device
is generally configured to exit Runtime automatically when loading is started. If this is not the
case, you will have to exit Runtime manually on the HMI device.
You can alternatively enable the "Remote" option in the transfer settings in the control panel
of the HMI device. This will then allow you to load a project to the HMI device while another
project is still in Runtime.
Please refer to the documentation for the HMI device used for more detailed information on
transfer settings.
Requirement
You have created an HMI device in the project.
The HMI device is connected to the configuration PC.
Transfer mode is set in the HMI device.
Procedure
Proceed as follows to load a project:
1. To download a project simultaneously to several HMI devices, select the HMI devices by
means of multiple selection in the project navigation.
2. Select the "Download to device > Software" command from the shortcut menu of the HMI
device.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2395
3. If the "Extended loading" dialog is open, configure the "Settings for loading". Make sure
that the "Settings for loading" correspond to the "Transfer settings in the HMI device".
Select the protocol used, for example, Ethernet or HTTP.
Configure the relevant interface parameters on the configuration PC.
Make any interface-specific or protocol-specific settings required in the HMI device.
Click "Download".
You can call the "Extended loading" dialog at any time with the menu command "Online >
Advanced download to device...".
The "Load preview" dialog opens. The project is compiled at the same time. The result is
displayed in the "Load preview" dialog.
4. Check the displayed presettings and change them as necessary.
5. Click "Download".
Result
The project is loaded to all selected HMI devices. If errors or warnings occur during the
download, corresponding alarms are displayed under "Info > Load" in the Inspector window.
On completion of the successful download of the project, you can execute it on the HMI device.
See also
Error messages during the download of projects (Page 2420)
Overview for loading of projects (Page 2394)
Generating a "Pack&Go" file
Introduction
Create a "Pack&Go" file if you cannot connect the HMI device to the configuration PC. The
"Pack&Go" file is a ZIP file containing the following data:
The compiled project
A program for transferring the project to the HMI device
The operating system image for the configured HMI device
Typical example of an application: An engineering company creates a project variant for a new
HMI device. The project engineer of the engineering company does not have direct access to
the plant. The project engineer therefore e-mails the "Pack&Go" file to his local contact. The
contact unpacks the "Pack&Go" file on a PC connected to the HMI device via a network. He
then transfers the project from the PC to the HMI device.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2396 System Manual, 08/2011,
Requirement
You have created an HMI device in the project.
Procedure
To create a "Pack&Go" file, follow these steps:
1. Select the HMI device in the project navigation.
2. Select the "Pack&Go" command from the menu under "Online > HMI device maintenance".
1. The "Create Pack&Go file" opens.
2. Select a protocol as transfer mode.
3. Select the storage location under "Pack&Go file" and enter the file name.
4. If necessary, specify if the "Pack&Go" file is split into several files.
5. Click "Create".
Result
The "Pack&Go" file is created and saved to the specified folder in the file system. Now copy
the "Pack&Go" file to the PC connected to the HMI device.
See also
Downloading projects from a "Pack&Go" file to the HMI device (Page 2397)
Downloading projects from a "Pack&Go" file to the HMI device
Requirement
The "Pack&Go" file has been stored in the file system of a PC.
The PC is connected to the HMI device.
The HMI device operating system version is the same as the operating system version in
the project.
Procedure
To download the project from a "Pack&Go" file to an HMI device, follow these steps:
1. Unpack the "Pack&Go" file to a folder of your choice in the file system of the PC.
2. From the "PackNGo" subfolder of this directory, run "Siemens.Simatic.Hmi.PackNgo.exe".
The "Pack'n Go" dialog opens. The settings for loading are set by default. Exception: You
must select the target device if you are using an S7 USB connection.
3. Adjust the settings for loading appropriately if they differ from the interfaces or protocols
available on the PC.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2397
4. Specify whether or not to overwrite the user management and recipe data already stored
on the HMI device.
5. If necessary, edit the "settings for loading".
6. Click "Transfer".
Result
The connection to the HMI device is set up via the selected path. An alarm is output if you are
running different operating system in the project and on the HMI device.
If this is the case, update the operating system on the HMI device. To update the operating
system on the HMI device, you need ProSave. A prompt for operating system update will
appear automatically if ProSave has been installed and the selected connection supports the
update of the operating system.
See also
Generating a "Pack&Go" file (Page 2396)
Updating the operating system (Page 2414)
Updating the operating system on the HMI device (Page 2415)
Loading via USB interface
Introduction
When you load a project via a USB interface, connect the configuration PC and the HMI device
with a USB cable. You load projects in both directions.
Requirements for transfer via USB
The following conditions must be met to ensure successful data transfer using a USB interface:
Use a USB host-to-host cable, USB 2.0 standard.
You have installed the provided USB driver.
You can find the driver on the WinCC product DVD under "Support\DeviceDriver\USB".
The HMI device being used is based on Windows CE and has a USB interface.
You can find more information on the cables used and the manufacturers/suppliers in the
Internet at:
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2398 System Manual, 08/2011,
http://support.automation.siemens.com (http://support.automation.siemens.com/WW/
view/en/19142034)
Note
Driver installation
To avoid problems when transferring projects, only use the USB driver provided on the
WinCC product DVD.
Note
Comfort HMI devices
Use the micro USB interface to load projects via USB with Comfort HMI devices. This
driver is installed automatically.
Installing a USB driver in Windows XP
Introduction
To load a project via the USB port, install the USB drivers provided on the WinCC product
DVD.
Note
Driver installation
To avoid problems when transferring projects, only use the USB driver provided on the WinCC
product DVD.
Note
Comfort HMI devices
Use the micro USB interface to load projects via USB with Comfort HMI devices. This driver
is installed automatically.
Requirement
The WinCC product DVD is available.
You are using a USB host-to-host cable, USB 2.0 standard.
The HMI device has a USB interface.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2399
Procedure
To install the USB driver under Windows XP, follow these steps:
1. Connect the USB host-to-host cable to the USB port of the configuration PC.
The USB cable is automatically detected by the hardware detection under Windows XP.
The driver installation wizard starts automatically.
Note
Connect the HMI device only when the driver has been completely installed on the PC.
2. If you are prompted with "Can Windows connect to Windows Update to search for software",
select "No, not this time" and click "Next".
3. Select "Install software from a list or specific source" and click "Next".
4. Select "Search removable media".
5. Insert the WinCC product DVD into the DVD drive and click "Next".
The system will search the WinCC product DVD for the corresponding driver for the USB
host-to-host cable.
The drivers available on the WinCC product DVD are displayed. The wizard highlights the
appropriate driver for Windows XP.
6. Check the selection and click "Next".
Note
The "Hardware installation" dialog box indicates that the software found has not passed
Windows Logo testing. The Logo test does not have any effects on the functioning of the
USB driver. Continue with the installation.
7. Click "Hardware Installation > Continue installation".
The driver is installed.
8. Click "Finish".
The installation is complete.
Result
The driver for the USB host-to-host cable has been installed. To load the project, connect the
HMI device to the USB cable.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2400 System Manual, 08/2011,
Installing a USB driver in Windows 7
Introduction
To load a project via the USB port, install the USB drivers provided on the WinCC product
DVD.
Note
Driver installation
To avoid problems when transferring projects, only use the USB driver provided on the WinCC
product DVD.
Note
Comfort HMI devices
Use the micro USB interface to load projects via USB with Comfort HMI devices. This driver
is installed automatically.
Requirement
The WinCC product DVD is available.
You are using a USB host-to-host cable, USB 2.0 standard.
The HMI device has a USB interface.
Procedure
To install the USB driver under Windows 7, follow these steps:
1. Connect the USB host-to-host cable to the PC's USB port.
The USB cable is detected, but the wizard for the driver installation does not find the driver.
Note
Connect the HMI device only when the driver has been completely installed on the PC.
2. Open the Device Manager in the Control Panel.
3. Select "Other devices > USB host-to-host cable".
4. Select "USB host-to-host cable" and then select "Update driver software..." in the shortcut
menu.
5. When the "How do you want to search for driver software?" prompt appears, select "Search
for driver software on the computer".
6. Click "Update driver software > Browse...".
7. Insert the WinCC product DVD as the source for driver installation.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2401
8. Select "Include subfolders" and then click "Next".
The system will search the WinCC product DVD for the corresponding driver for the USB
host-to-host cable.
The drivers available on the WinCC product DVD are displayed. The wizard highlights the
appropriate driver for Windows 7.
9. Check the selection and click "Next".
10.To continue with the installation, click "Hardware Installation > Continue installation".
The driver is installed.
11.Click "Finish".
The installation is complete.
Result
The driver required for the USB host-to-host cable has been installed. To load the project, now
connect the HMI device to the USB cable.
9.13.1.4 Runtime start
Starting Runtime on the configuration PC
Introduction
You can start a project in Runtime on the configuration PC if Runtime has been installed. During
startup of the project in Runtime, the project settings made in the "Runtime settings" of the
HMI device are activated.
Note
You can only simulate HMI devices with Runtime Panels on the configuration PC. Select the
"Online > Start simulation" menu command.
Requirements
A project is open on the configuration PC.
Runtime is installed on the configuration PC.
There is no project in Runtime on the configuration PC.
Procedure
To start runtime on the configuration PC, follow these steps:
1. Select the desired HMI device in the project navigation.
2. Select the "Online > Start Runtime" menu command.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2402 System Manual, 08/2011,
Result
Runtime is started and the project is displayed on the configuration PC.
See also
Simulating a project (Page 2406)
Starting Runtime Advanced and Panels
Introduction
You can start the project in Runtime as soon as you have downloaded the project to the HMI
device. The project is generally started automatically on the HMI device.
There may be several projects in the file system of the HMI device for HMI devices with Runtime
Advanced. You can start one of these projects in Runtime.
The project settings defined in the "Runtime settings" of the HMI device are activated when
the project is started in Runtime. Make sure when defining the Runtime settings "Lock task
switching" and "Full screen" that you will be able to stop Runtime again. You can, for example,
configure a button with the system function "StopRuntime".
Requirements
WinCC Runtime Advanced or Panels is installed on the HMI device.
The project was downloaded to the HMI device
Starting Runtime on a PC
The compiled project is saved in the PC file system with the extension "*.fwc" and is freely
accessible.
1. To start the project once the HMI device has booted up, enter the automatic start of a project
file under "Settings" in the "RT Loader" ("HmiLoad.exe").
You can also create a link to the project file in the Windows Autostart directory.
Starting Runtime on a panel
The project will be stored on a panel in a folder you specify in the HMI device transfer settings.
The "RT Loader" application is started on a panel. The project loaded is started automatically
after expiration of the configured delay.
If the project does not start automatically:
1. Click on "Start" to start the loaded project.
Refer to the documentation for the HMI device for additional information on startup of projects.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2403
Result
Runtime is started on the HMI device.
See also
Starting and stopping the debugger (Page 1251)
Overview of compiling and loading projects (Page 2391)
Loading a project (Page 2395)
Downloading projects from a "Pack&Go" file to the HMI device (Page 2397)
9.13.2 Simulating projects
9.13.2.1 Simulation basics
Introduction
You can use the simulator to test the performance of your configuration on the configuration
PC. This allows you to quickly locate any logical configuration errors before productive
operation.
You can start the simulator as follows:
In the shortcut menu of the HMI device or in a screen: "Start simulation"
Menu command "Online > Simulation > [Start|With tag simulator|With script debugger]"
Under "Visualization > Simulate device" in the portal view.
Requirement
The simulation/runtime component is installed on the configuration PC.
Field of application
You can use the simulator to test the following functions of the HMI system, for example:
Checking limit levels and alarm outputs
Consistency of interrupts
Configured interrupt simulation
Configured warnings
Configured error messages
Check of status displays
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2404 System Manual, 08/2011,
See also
Simulating a screen (Page 2408)
WinCC Runtime Advanced simulation (Page 2405)
Working with the tag simulator (Page 2408)
9.13.2.2 WinCC Runtime Advanced simulation
Introduction
There are two different simulation modes for Runtime Advanced simulation:
Device simulation
Tag simulation
Both types of simulation simulate the project without a direct process link to the configuration
PC. Data such as logs or recipes generated during simulation are not deleted. This data is
saved on the configuration PC in the paths configured in the project.
Device simulation
Use device simulation to simulate operator control of the HMI device. Device simulation is, for
example, used to test screen switching.
Tag simulation
Use tag simulation to simulate the configured process tags. You can either have tag values
generated automatically by a simulation table or define tag values yourself.
See also
Simulation basics (Page 2404)
Simulating a project (Page 2406)
Start debugger (Page 2410)
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2405
9.13.2.3 Simulating a project
Introduction
You simulate your project with one of the following two methods:
Without a connected PLC
You change the value of area pointers and tags in a tag simulator that is read for the
simulation of WinCC Runtime.
With a connected PLC without a running process
You simulate your project by running it directly in Runtime. The tags and area pointers
become active. This allows you to create an authentic simulation of your configured HMI
device in Runtime.
Note
Simulation restrictions
You cannot simulate the following system functions:
CalibrateTouchScreen
You cannot simulate the Media Player. A static screen appears in the simulation window
instead of the Media Player.
File access via scripts is not possible for HMI devices with Windows CE.
Requirement
Simulation without a connected PLC: Tags have been created
Simulation with a connected PLC but no active process: A project with tags and area
pointers has been created
Procedure
To simulate a project using the tag simulator, follow these steps:
1. Open the project on the configuration PC.
2. Select the "Online > Simulation > With tag simulator" menu command.
For initial project simulation, the simulator is started with a new, empty table. The project
is opened simultaneously in Runtime.
Toggle between the tag simulator and Runtime using the <Alt +Tab> key combination.
3. To simulate a process value, select the corresponding "tag" from the tag simulator.
The table lists all configured tags. You can simulate up to 300 tags simultaneously.
4. Select the simulation mode in the "Simulation" column.
5. Change the value of tags and area pointers in the respective columns.
6. Activate the "Start" check box to start the simulation for this tag.
7. To save the simulation, select the menu command "File > Save" and enter a descriptive
name, for example, "Mixing".
The file name is assigned the extension "*.cors".
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2406 System Manual, 08/2011,
Result
The process values are simulated in Runtime. The tag values are created at random, or
incremented, depending on the simulation mode.
To specify tag values, change the simulation mode to "<Display" and enter a value at "Set
value".
The following figure shows a tag simulator with four tags whose values can be determined at
random in a range of values from 10 to 1000:
Managing simulation data
If you have saved data from a previous simulation, you can open the file at a later point in time
and simulate your project again. The tags and area pointers listed in the tag simulator must
still be available in the project.
Proceed as follows to open a simulation file:
1. Select the menu command "Online > Simulate Runtime > With tag simulator".
2. Select the menu command "File > Open" in the tag simulator.
3. Select the corresponding simulation file and click "Open".
The simulator loads the stored data.
Enabling and disabling tags
Start and stop the simulation for each tag separately in order to facilitate the transition from
offline to online engineering. Activate "Start" in the corresponding row.
If a tag is activated, the simulation values are calculated and transferred to the WinCC
simulator.
Deleting a tag
To delete a tag from the tag simulator, follow these steps:
1. Select the cell that contains the tag name.
2. Select the "Edit > Cut" menu command.
The tag is removed from the table.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2407
9.13.2.4 Simulating a screen
Introduction
If you have only made changes to one screen, you can temporarily specify this screen as the
start screen for simulation. In this way, you can debug changes without having to modify the
start screen, or opening the screen on the HMI device.
Requirements
You created a project that contains at least one screen.
Procedure
To define a screen as temporary start screen for simulation, follow these steps:
1. In the project navigation, select the image to display as the start screen in the simulation.
2. Select the "Start simulation" command from the shortcut menu of the screen.
Result
Project simulation is started. Instead of the configured start screen, the simulation window the
screen you selected in the project navigation.
See also
Simulation basics (Page 2404)
9.13.2.5 Working with the tag simulator
About the tag simulator
The tag simulator has the following columns:
Column Description
Tag Specifies the tags for the simulation.
Data type Shows the data type of the selected tag.
Current value Shows the simulated value of the defined tags.
Format Specifies the selected format in which the tag values are simulated:
Decimal (1, 2, 3, 4, ...)
Hexadecimal (03CE, 01F3, ...)
Binary (0 and 1)
Write cycle Specifies the selected time interval at which the current tag values are simulated. If
you enter "2", for example, the current value of the tag will be shown every 2 seconds.
Simulation Shows the method by which the tag values are processed during simulation.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2408 System Manual, 08/2011,
Column Description
Set value Sets the selected value for the respective tag. The simulation start with the specified
value.
minValue
maxValue
Specifies the value range of the tag. You set a minimum and maximum value for this
range. The default values are -32768 for the minimum and 32767 for the maximum.
Period Contains the period during which the value of the tag is repeated for the "Increment"
and "Decrement" simulation modes.
Start Starts simulation of the tag based on the previously entered information.
Simulation modes
The simulator has six different simulation modes. The configured tags are supplied with nearly
realistic values during the simulation.
Simulation mode Description
Sinusoidal Changes the tag value to form a sinusoidal curve. The value is visualized as a
periodic, non-linear function.
Random Provides randomly generated values. The tag value is changed by means of a
random function.
Increment Increases the value of the tag continuously up to a specified maximum value.
Begins again at the minimum after the maximum has been reached. The value
trend corresponds to a positive saw-tooth curve.
Decrement Reduces the value of the tag continuously down to a specified minimum value.
Begins again at the maximum after the minimum has been reached. The value
curve corresponds to a negative saw-tooth curve.
Shift bit Shifts a set bit continuously by one position. The previous position is always reset.
This lets you test the alarms of an HMI device, for example.
<Display> The current tag value is displayed statically.
Example: Simulate tags with the "Shift bit" simulation mode
Proceed as follows to simulate tags with the "Shift bit" simulation mode:
1. Open the project you want to simulate.
2. Select the menu command "Online > Simulate Runtime > With tag simulator".
The tag simulator opens.
3. In the "Tag" column, select a tag from your project.
4. Select "Bin" in the "Format" column.
5. Enter the value "1" in the "Write cycle" column.
6. Select the "Shift bit" simulation mode in the "Simulation" column.
7. Enter the value "1" in the "Set value" column.
8. Enable the tag with the "Start" check box.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2409
Result
The simulator tests the selected tag bit-by-bit as follows:
Simulation values Byte for alarms
Set start value 00000001
1. Simulation value 00000010
2. Simulation value 00000100
3. Simulation value 00001000
.... ...
In Runtime you see if the desired alarm is output at a given value.
9.13.2.6 Start debugger
Introduction
Select the "With script debugger" script mode to test scripts. The debugger allows you to set
breakpoints in the code, for example, or implement a script step by step.
Requirements
A debugger that supports VBS is installed on the Engineering Station, e.g. "MS Script
Debugger".
WinCC Runtime is installed on the Engineering Station.
A project is open.
Procedure
1. Select the "Online > Simulation > With script debugger" menu command.
The Runtime software searches for debuggers installed on the Engineering Station.
2. If several debuggers are found, click on a selected.
Result
The debugger is connected automatically with the runtime software.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2410 System Manual, 08/2011,
9.13.3 Servicing the HMI device
9.13.3.1 ProSave
Introduction
The "ProSave" service tool is installed by default when WinCC is installed. The ProSave
functions are called in WinCC with the menu "Online > HMI device maintenance".
Functional scope
ProSave provides all of the functions you need to manage data on the HMI device:
Data backup and restoration of backed-up data
Operating system update for HMI devices with Windows CE or below
Transferring License Keys
Installing and uninstalling drivers and options as well as information on installed options
and options that can be installed on an HMI device
Communication settings (transferred from WinCC)
See also
Backup of HMI data (Page 2411)
Updating the operating system (Page 2414)
Transferring license keys (Page 2417)
Installing and uninstalling an option (Page 2419)
9.13.3.2 Backup of HMI data
Introduction
Regular backups of HMI device data keep downtimes to a minimum, for example, when you
replace a device. You simply transfer the backup data to the HMI device, restoring the original
status.
Data backup with WinCC
If an HMI device is connected to the configuration PC, you can back up and restore HMI device
data from the configuration PC using WinCC.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2411
Scope of data backup
Which data is backed up and restored depends on the type of HMI device:
Complete backup
Depending on the HMI device: Runtime, firmware, operating system image, configuration,
recipes, user administration, settings
Note
License Keys are only saved for 177, 277 and 377 series HMI devices.
The License Keys are not saved for the following HMI devices:
all other Windows CE HMI devices
TP 177A and OP 77A
Recipes only
User administration only
A backup file with the extension *.psb is generated when you backup the data of an HMI device.
As a general rule, you can backup the data to any storage medium. If the HMI device is
networked, you can also backup the data to a server.
Note
Scope of data backup for Windows CE HMI devices
Data backup secures the contents of the flash memory. Alarm logs and process value logs
are generally saved on the external storage medium. Alarm logs and process value logs are
not backed up. If necessary, back up the contents of the memory card separately.
Please note the following when performing a complete data file backup and restore operation
for Windows CE devices:
A full backup includes all options installed. As a rule, the backup includes all options data
that is still available after "POWER OFF".
All data previously stored on the device, including License Keys and the operating system,
are permanently deleted when complete data restoration is carried out.
If the data restoration was interrupted, execute the command "Reset to factory settings".
Restart data restoration.
Note
Use interfaces with high bandwidths, e.g. USB or Ethernet to backup and restore data.
Note
For Windows CE devices, you can also backup the data directly to a CF or PC card,
independent of ProSave and WinCC. For additional information, refer to the relevant
operating instructions.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2412 System Manual, 08/2011,
See also
Backing up and restoring data of the HMI device (Page 2413)
9.13.3.3 Backing up and restoring data of the HMI device
Note
Use the restore function for project data only on operating devices which were configured
using the same configuration software.
Requirements
The HMI device is connected to the configuration PC
The HMI device is selected in the project navigation.
If a server is used for data backup: The configuration PC has access to the server
Backup of the data of the HMI device
Proceed as follows to backup the data of the HMI device:
1. Select the "Backup" command from the "Online > HMI device maintenance" menu.
The "SIMATIC ProSave" dialog box opens.
2. Select the data to backup for the HMI device under "Data type".
3. Enter the name of the backup file under "Save as".
4. Click "Start Backup".
This starts the data backup. The backup operation takes some time, depending on the
connection selected.
Restoring the data of the HMI device
Proceed as follows to restore the data of the HMI device:
1. Select the "Restore" command from the "Online > HMI device maintenance" menu.
2. Enter the name of the backup file under "Save as".
Information about the selected backup file is displayed under "Content".
3. Click "Start Restore".
This starts the restoration. This operation takes some time, depending on the connection
selected.
Backup/Restore from the "Backup/Restore" dialog in the control panel of the HMI device
The "Backup/Restore" function is enabled for MMC, SD memory cards and USB mass storage
devices.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2413
See also
Backup of HMI data (Page 2411)
9.13.3.4 Updating the operating system
Introduction
You must update the operating system of the HMI device if its version is not compatible with
the configuration. The operating system may (following a prompt) be updated automatically
when the project is loaded, depending on the protocol used. Loading will then continue.
Loading will otherwise be aborted. In this case, start the operating system update manually.
Note
The operating system can only be updated on Windows non-PC-based HMI devices.
Updating the operating system
Connect the HMI device to the configuration PC to update the operating system of an HMI
device. If possible, you should use the interface with the highest bandwidth for this connection,
such as Ethernet. Updating the operating system via a serial connection can take up to an
hour.
Note
Transfer of operating systems for MP 377 via PROFIBUS
The size of the image and the baud rates available with PROFIBUS mean image transfer
with an MP 377 via PROFIBUS can take up to an hour.
Updating the operating system via USB or Ethernet.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2414 System Manual, 08/2011,
"Reset to factory settings"
If the operating system on the HMI device is no longer operational, update the operating system
and reset the HMI device to the factory settings.
Note
Resetting to factory settings via Ethernet for Basic Panels
You will require the following to reset the factory settings via Ethernet:
the MAC address of the HMI device
the available IP address
the programming device/PC interface of the configuration PC set to Ethernet TCP/IP
The programming device/PC interface is configured using the control panel of the
configuration PC. Select" "S7ONLINE (STEP7) -> TCP/IP" in the "Access point of the
application" field.
See also
Updating the operating system on the HMI device (Page 2415)
9.13.3.5 Updating the operating system on the HMI device
If possible, you should use the interface with the highest bandwidth for this connection, such
as Ethernet. Updating the operating system via a serial connection can take up to an hour.
CAUTION
Updating the operating system deletes all data on the HMI device
When you update the operating system you delete data on the target system. For this reason,
it is advisable to backup the following data:
User administration
Recipes
Resetting to factory settings also deletes the License Keys. You should also back up the
License Keys before resetting to factory settings.
Requirement
The HMI device is connected to the configuration PC
The HMI device is selected in the project navigation.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2415
Updating the operating system
Proceed as follows to update the operating system:
1. Select the "Update operating system" command from the "Online > HMI device
maintenance" menu.
The "SIMATIC ProSave [OS-Update]" dialog opens. The path to the image of the operating
system has been preset.
1. If necessary, select another path to the operating system image you want to transfer to the
HMI device.
1. Click "Update OS".
This starts the update. The update operation can take time, depending on the connection
selected.
Resetting the HMI device to factory settings
To reset the HMI device to factory settings, proceed as follows:
1. Switch off power to the HMI device.
2. Connect the HMI device to the Engineering Station.
3. Select the "Update operating system" command from the menu under "Online > HMI device
maintenance" on the configuration PC in WinCC.
The "SIMATIC ProSave [OS-Update]" dialog opens. The path to the image of the operating
system has been preset.
4. If necessary, select another path to the operating system image you want to transfer to the
HMI device.
5. Activate "Reset to factory settings".
6. Click "Update OS".
7. To "Reset to factory settings", switch on power to the HMI device again.
This operation can take time.
Result
The operating system of the HMI device is operational and up-to-date.
See also
Managing licenses (Page 2417)
Backing up and restoring data of the HMI device (Page 2413)
Updating the operating system (Page 2414)
Overview for loading of projects (Page 2394)
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2416 System Manual, 08/2011,
9.13.3.6 Transferring license keys
Introduction
You need a license for certain WinCC Runtime options you may want to install on an HMI
device. Usually, the necessary licenses supplied as "License Keys" on a data medium, e.g.
USB stick. The "License Keys" can also be made available on a license server.
Use "Automation License Manager" to transfer the "License Keys" to or from an HMI device.
The "Automation License Manager" is included automatically when you install WinCC.
CAUTION
Backing up License Keys
In the following cases you have to backup the "License Keys" in order to prevent deletion of
the "License Keys":
Prior to the update of the operating system of a Windows CE HMI device
Prior to restoring the data from a full backup
"License Keys" on an HMI device are backed up depending on the HMI device
configuration. For more information, refer to the operating instructions of the
corresponding HMI device.
See also
Managing licenses (Page 2417)
9.13.3.7 Managing licenses
Requirement
The HMI device is connected to the configuration PC or the PC running the "Automation
License Manager".
If you are using the configuration PC: The HMI device is selected in the project navigation.
Procedure
To transfer license key, proceed as follows:
1. Open the "Automation License Manager". Go to the Windows Start menu and start
"Automation License Manager" on a PC on which WinCC is not installed.
The "Automation License Manager" starts.
2. Select the "Connect HMI device" command from the "Edit > Connect target system" menu.
The "Connect target system" dialog opens.
3. Select the HMI device type in the "Device type" area.
4. Select the "Connection".
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2417
5. Configure the "connection parameters" associated with the selected connection.
6. Click "OK."
The connection to the HMI device is now set up. The connected HMI device is displayed
in the left pane of "Automation License Manager".
7. Transfer the "License Keys" to the HMI device:
In the left pane, select the drive on which the "License Keys" are located.
The "License Keys" are displayed on the right pane.
Select the "License Keys"
Drag-and-drop the "License Keys" to the HMI device.
You can also remove License Keys from the HMI device using drag-and-drop.
Alternative procedure
You can also start the "Automation License Manager" from WinCC on a PC with a WinCC
installation: Select the "Authorize/License" command in the "Online > HMI device
maintenance" menu.
Result
The "License Keys" are transferred to the HMI device.
To backup the "License Keys" from the HMI device, drag-and-drop the "License Keys" from
the HMI device to an available drive.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2418 System Manual, 08/2011,
See also
Transferring license keys (Page 2417)
Installing and uninstalling an option (Page 2419)
9.13.3.8 Installing and uninstalling an option
Introduction
You can install the following options on an HMI device:
Additional options supplied with WinCC
Options purchased in addition to WinCC
Which options you can install depends on the HMI device type.
Requirements
The HMI device is connected to the Engineering Station, or to the PC with ProSave.
The HMI device is selected in the project navigation.
Procedure
To install an option on the HMI device, proceed as follows:
1. Select the "Options" command from the "Online > HMI device maintenance" menu.
All available options and the previously installed options are displayed.
2. To display the installed options on the HMI device, click "Device status".
3. Select the option to install on the HMI device and transfer it to the list of installed options
with ">>".
4. Click "<<" to uninstall an option from an HMI device.
5. To start installation or deinstallation, click on "OK".
Result
The selected options were installed on the HMI device, or removed.
See also
Managing licenses (Page 2417)
ProSave (Page 2411)
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2419
9.13.4 Reference
9.13.4.1 Error messages during the download of projects
Possible problems during the download
When a project is being downloaded to the HMI device, status messages regarding the
download progress are displayed in the output window.
Usually, problems arising during the download of the project to the HMI device are caused by
one of the following errors:
Wrong operating system version on the HMI device
Incorrect download settings on the HMI device
Incorrect HMI device type in the project
The HMI device is not connected to the configuration PC.
The most common download failures and possible causes and remedies are listed below.
The serial download is cancelled
Possible remedy: Select a lower baud rate.
The download is cancelled due to a compatibility conflict
Possible cause Remedy
Conflict between versions of the configuration
software and the operating system of the HMI
device
Synchronize the operating system of the HMI
device with the version of the configuration
software.
To update the operating system on the HMI
device, select the "Update operating system"
command from the "Online > HMI device
maintenance" menu in WinCC. You can also use
ProSave.
For additional information, refer to the operating
instructions for the HMI device.
The configuration PC is connected to the wrong
device, e.g. a controller.
Check the cabling.
Correct the communication parameters.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2420 System Manual, 08/2011,
Project download fails
Possible cause Remedy
Connection to the HMI device cannot be
established (alarm in the output window)
Check the physical connection between the
configuration PC and the HMI device.
Check whether the HMI device is in transfer mode.
Exception: Remote control
The default communication driver is not listed in
the Windows Device Manager.
Check the device status of the COM connection in
the properties window of the Device Manager.
Download over MPI/DP interface fails
Possible cause Remedy
"Configured mode" is set on the CP, for example,
if you are using the SIMATIC NET CD.
Set the CP to "PG mode" using the "Set PC
station" application.
Check the "baud rate" and "MPI address" network
parameters.
Download the project from WinCC to the CP.
Set the CP back to "configured mode".
On the programming device/PC panel, the
"S7ONLINE" access point is not set to a hardware
device such as CP5611 (MPI). This may be due
to the installation of "SIMATIC NET CD".
Set the access point "S7ONLINE" on the selected
device using the "PG/PC Panel" or "Set PC
station" application.
Check the "baud rate" and "MPI address" network
parameters.
Download the project from WinCC to the HMI
device.
Restore the "S7ONLINE" access point to the
original device.
The configuration is too complex
Possible cause Remedy
The configuration contains too many different
objects or options for the HMI device selected.
Remove all objects of a specific type, for example
all HTML browsers.
Alternatively, remove options such as
Sm@rtServer or OPC server.
9.13.4.2 Adapting the project for another HMI device
Introduction
When you download a WinCC project to an HMI device, WinCC checks whether this is
compatible with the HMI device type used in the project. If the types of HMI device do not
match, you will see a message before the download starts.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2421
The download is aborted.
Adapting the project for the HMI device
You need to adapt the project accordingly to be able to download the project to the connected
HMI device.
Add a new HMI device in the project tree. Select the correct type of HMI device from the
HMI device selection.
Copy the configured components from the previous to the new HMI device.
Copy large amounts of components directly in the project navigation and details view.
For example, copy the "Screens" folder to the screens folder of the new HMI device with
the help of the shortcut menu.
Use the detail view to copy entries in the project tree for which the "Copy" command is not
available in the shortcut menu.
Select the "Recipes" entry in the project tree, for example. The recipes are displayed in the
detail view.
Select the recipes in the detail view and drag them to the "Recipes" entry of the new HMI
device. The recipes are copied. You can also select multiple objects in the detail view.
Configure the components that cannot be copied, e.g. connections, area pointers, and
alarms.
Save the project at various points in time.
Compile the full project.
When the compilation is successfully completed, download the project to the HMI device.
Linking references
References to linked objects are included in the copying. The references are linked again once
the linked objects are copied.
Example:
You copy a screen in which objects are linked to tags. The tag names are entered at the
individual objects after the screen is added to the new HMI device. The tag names are marked
in red because the references are open. When you then copy the tags and insert them into
the new HMI device, the open references are closed. The red marking for the tag names
disappears.
For complete references to connected objects in the PLC, you first need to configure a
connection to the PLC.
Using the information area
When you compile the project for the HMI device, errors and warnings are displayed in the
"Info" tab of the Inspector window. You can use the shortcut menu command "Go to" to go
directly to the location where the error or warning can be corrected.
Work through the list of errors and warnings from top to bottom.
When the compilation is successfully completed, download the project to the HMI device.
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
2422 System Manual, 08/2011,
See also
Loading a project (Page 2395)
9.13.4.3 Establishing a connection to the HMI device
Introduction
To download a WinCC project to an HMI device, a properly configured connection must be set
up between the configuration PC and HMI device. The connection cannot be set up, the
download is cancelled.
Setting up a connection between the configuration PC and HMI device
1. Check the cable connection between the HMI device and configuration PC.
2. Open the "Devices & Networks" editor in WinCC and start the network view.
3. Select the subnet in the network view and check the settings for the subnet.
4. Select the interface of the HMI device in the network view or device view and check the
connection parameters in the Inspector window.
5. Switch on the HMI device and press the "Control Panel" button in the loader.
The Control Panel opens.
6. Press "Transfer" twice in the Control Panel.
The "Transfer Settings" dialog box opens.
7. Check the settings and then press "Advanced".
The [Protocol*] Settings" dialog opens.
*: The title of the dialog depends on the protocol used, for example, "PROFIBUS Settings".
8. Check the advanced settings and close the dialog with "OK".
Important settings
Check the connection settings and in particular the following parameters:
Network and station addresses
Selected transmission rate
Master on the bus; as a general rule, only one master is permitted.
If using a configurable adapter for the connection, check the adapter settings, for example,
transmission rate, master on the bus.
See also
Loading a project (Page 2395)
Visualizing processes (Advanced)
9.13 Compiling and loading
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2423
9.14 Operating in Runtime
9.14.1 Basics
9.14.1.1 Overview
Configuration and process control phases
HMI devices are used to operate and monitor tasks in process and production automation.
The plant screens on the HMI devices provide a clear overview of active processes. The HMI
device project, which includes the plant screens, is created during the configuration phase.
Transfer the project to the HMI device for the process control phase. Another requirement for
the process control phase is that the HMI device must be connected online to a PLC. The
process control phase, operator control, and monitoring can then be carried out during an
ongoing work process.
Connection to the PLC
Transfer the project
PLC
Test the project
Simulate the project
Save the project
(HMl-device dependent)
HMl device Operate the project
Configuration phase
Process control phase
Create project
Configuration PC
Figure 9-6 Configuration and process control phases
Downloading the project to the HMI device
The following procedures are available to download a project to an HMI device:
Downloading from the configuration PC
Restore the project from a PC using ProSave
In this case, an archived project is downloaded from a PC to the HMI device. The
configuration software need not be installed on this PC.
These procedures are available for commissioning and recommissioning a project.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2424 System Manual, 08/2011,
Commissioning and Recommissioning
When the HMI device is commissioned there is no project at first.
The HMI device is also in this state after the operating system has been updated.
When recommissioning, any project on the HMI device is replaced.
9.14.1.2 System behavior
System functions and scripts
Use
System functions and user-defined functions are used in Runtime for the following purposes:
To control the process.
To utilize the properties of the HMI device.
To configure system settings on the HMI device in online mode.
Each system function and user-defined function within WinCC is linked to an object and an
event. As soon as the event occurs, the system function is triggered.
System functions
These default system functions are used to implement many tasks in Runtime, such as:
Calculations, e.g. increasing a tag value by a specific or variable amount.
Logging functions, e.g. starting a process value log.
Settings, e.g. PLC changes or setting a bit in the PLC.
Alarms, e.g after a different user logs on.
User-defined functions
User-defined functions may also be included in the project for specific applications which may
require additional functions. WinCC provides an interface to Microsoft Visual Basic Script
(VBScript or VBS for short) for creating user-defined functions.
Examples:
Conversion of values, e.g. between different physical units (temperatures).
Automation of production sequences
The user-defined function controls a production sequence by transferring values to a PLC.
The status is checked based on return values and corresponding measures are initiated.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2425
Events
The object and the selected function determine which events can be defined as triggers for
executing a system function.
For example, the "Value change", "On exceeding" and "On falling below" events are associated
with the "Tag" object. The "Loaded" and "Cleared" events are associated with the "Screen"
object.
Reports
Overview
Logs are used to document process data and completed production cycles. The report content
and layout are specified in the project, as is the event triggering the printout of the report.
For example, a report can be configured for output at the end of a shift to record downtimes.
A log can also be configured for the purpose of the documentation of product testing or quality
inspections (ISO 9000).
Output
Reports are printed in Runtime either automatically, e.g. by means of a scheduler, or manually
by means of a softkey.
Printing reports
Reports are output to the printer in graphic mode. The use of a serial printer is not
recommended because of the accumulated data volume.
For proper output, the printer must support the paper format and page layout of the report.
Note
The value of a tag in the report is read and output at the moment of printing. A substantial
time may elapse between printing out the first and the last page of a report consisting of
several pages. This may lead to the same tag on the last page being output with a different
value from that on the first page.
Logs
Overview
Alarm events and process values can be saved to log files. Alarm events are, for example, the
"Incoming", "Acknowledge" and "Outgoing" events contained in an alarm message.
Data logging can be used for the following purposes:
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2426 System Manual, 08/2011,
Early detection of danger / fault states
Increase of productivity
Enhancement of product quality
Optimization of maintenance cycles
Documentation of processes
Quality assurance
Memory options
Depending on the configuration, the logs are written to a file or stored in a database set up for
this purpose.
Data logging to File CSV(ASCII)
In CSV format, table columns are separated by separators and the table rows are
terminated by a line break. This allows you to evaluate or edit your log data, for example,
using an external text editor or a spreadsheet program.
Note
Double quotation marks or multiple characters cannot be used as list separators for the
storage location "File - CSV (ASCII)". The setting for list separators can be found under
"Start > Settings > Control Panel > Regional and Language Options".
Data logging to File TXT (Unicode)
The data is saved in the Unicode format. This file format supports all characters than can
be used in WinCC Runtime. For processing, you require a software that can save Unicode,
such as Notepad.
Note
To save Asian languages, use the storage location "File - TXT (Unicode)".
Data logging to a File - RDB
Log files in this format can only be read or represented with WinCC flexible Runtime.
If you want to evaluate the logged data in a different manner, convert the data to the CSV
format using the "CopyLog" system function.
Data logging to a database
Data is saved in a database for which ODBC access was set up by the PC administrator.
Logging methods
Logging methods used in WinCC:
Circular log
Segmented circular log
Log with level-dependent system alarms
Log with level-dependent triggering of an event
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2427
Alarm logs
Alarms in the project indicate fault states and operating states of a process. They are generally
triggered by the controller. Alarms are output on the HMI device in form of screen objects. All
the data associated with an alarm and configuration data are saved in an alarm log, for
example, alarm class, time stamp and alarm text. All alarm classes can be logged separately.
Alarms can be logged either automatically or by operator intervention. For additional
information, refer to "Logging alarms".
Data logs
In Runtime, the process values are logged, processed and, depending on the project, written
either to files or to the log database.
Data logging is controlled by means of cyclic operations and events. Logging cycles are used
to ensure continuous acquisition and storage of the process values. Data logging can also be
triggered by events, for example, when a value has changed. For additional information, refer
to "Logging tags".
Storing logs on network drives
Close all logs with the system function "CloseAllLogs" before disconnecting the HMI device
from the network.
End Runtime if an unexpected network failure occurs. The logs will be available again after
restarting Runtime.
Storing files on a Windows 2003 server
Log files and recipes can only be stored on a Windows 2003 server with Active Directory for
the following HMI devices:
MP 277
MP 377
Mobile Panel 277
Mobile Panel 277 IWLAN
Tags
Definition
Tags correspond to defined memory areas on the HMI device, to which values are written and/
or from which values are read. This action can be initiated by the PLC, or by the operator at
the HMI device.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2428 System Manual, 08/2011,
9.14.2 Commissioning projects
9.14.2.1 Runtime Advanced and Panels
Introduction
Modern automation concepts are extremely demanding on process visualization. Process
control close to machines must in particular meet the demands for simple, high-performance
control of the processes. The objective is to present quick, clear and comprehensible
information to operators, for example, by means of a trend view. This increasingly requires
process displays that simplify understanding of the actual process. There is an increasing
demand for data logging functionality, e.g. for QC. This makes it necessary to log process data
at machine level.
Runtime Advanced and Panels is designed for visualizing and operating machines and small-
scale plants. The Runtime software has a window-based pixel-graphics user interface. Due to
its short response times, the software features secure process operation, jogging at the
machine and secure data acquisition.
Licensing
A License Key is required to install Runtime Advanced and Panels on a standard PC or on a
Panel PC. Runtime Advanced and Panels only runs in demo mode if not licensed.
PC: The license is included with your Runtime Advanced and Panels package.
Panel PCs: The "Runtime Advanced and Panels" license is shipped with the device.
WinCC components
The WinCC configuration software is used to create your project data on a PC or PG that is
operating on a Windows platform.
The Runtime software lets you visualize the process. You use Runtime to test and simulate
the compiled project file on the configuration PC.
You can order several options with enhanced functions for Runtime Advanced and Panels.
9.14.2.2 Settings for Runtime Advanced and Panels
Settings in the Runtime software
Open the WinCC configuration software and make the following settings for the Runtime
software:
Display on the PLC
In WinCC, configure the visual representation of the generated project in Runtime: Select the
full-screen or window mode for the project. The window has a smaller size than the screen. In
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2429
full-screen mode, the project is zoomed to the full screen. There will be no window and operator
control elements for this view.
Click "Screens" in the "Settings" editor to define activation of the full-screen at startup. Activate
the "Full-screen mode" check box in the "Screen" field.
You can hide the taskbar in Windows as required. Select "Start > Settings > Taskbar" and then
deactivate the "Always on Top" and "Auto hide" check boxes in the "Taskbar properties" dialog.
Note
Truncated view
If the HMI screen does not match the configured size (in pixels), the project opened in full-
screen mode only appears on a part of the screen.
Dialog fonts
The dialog text will be shown in the standard font. Define the default font by selecting
"Languages and fonts" in the "Settings" editor.
Disabling program switching
You lock program switching to prevent operators from calling other applications in Runtime.
Click "Screens" in the "Settings" editor and then activate the "Disable program switching" and
"Full-screen mode" check boxes. Also hide the Windows taskbar.
Note
Stop runtime
If you lock program switching, always configure in your project the system function
"StopRuntime" for an object, e.g. a softkey or button. Otherwise, you cannot close Runtime
or Windows.
The <CTRL+ALT+DEL> key shortcut is not available if program switching is disabled. On a
Windows 2000 operating system this effect prevents you from logging on to your device again
after the screensaver was started. Windows 2000 allows you to disable the <CTRL+ALT
+DEL> key shortcut required for logon. Open the "Control Panel > Users > Passwords >
Advanced" tab and deactivate the "Press CTRL + ALT + DEL before logon" check box.
Screen saver
A screensaver is no longer required for most modern screens and can, in fact, even cause
damage. These monitors switch to hibernate mode as soon as the video signal has not
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2430 System Manual, 08/2011,
changed for a specified time. A conventional screensaver would prevent this and thus reduce
the service life of your monitor.
Note
Approved screensavers
If you do want to use a screensaver, note that only the standard Windows screensavers are
approved for use in Runtime.
Make sure that the correct time zone is set on the PC on which the runtime software is installed.
To set the time zone in Windows, select Start > Settings > Control Panel > Date and Time.
Additional operating options
Print functions
Print functions available in online mode: :
Hardcopy
You can print the content of the currently displayed screen if you utilize the "Print screen"
system function in your configuration.
Printing alarms
Each alarm event that occurs (incoming, outgoing, acknowledgment) is also sent to a
printer.
Printing reports
LED control
The light-emitting diodes (LEDs) in the function keys of the HMI devices can be controlled from
the PLC. For example, a lit or flashing LED can signal the operator to press a specific function
key on the device.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2431
9.14.2.3 Loading a project
Overview
Various scenarios are possible for loading the project:
The Runtime software is installed on the same system as the configuration software.
The Runtime software and the configuration software are installed on different systems.
The project must be loaded from the configuration computer to the target system. The HMI
devices must be connected to the configuration PC for the transfer. Another requirement
is that the transfer mode must match on the HMI devices and in WinCC.
Note
Security prompts may appear during the loading process, depending on the configuration.
The recipe data and password list on the HMI device are overwritten following a prompt.
The configuration software and the Runtime software are installed on the same system
If the configuration software and the Runtime software are installed on the same system,
proceed as follows:
1. Create and compile your project.
2. Start Runtime directly from the active configuration software. Select the "Start Runtime"
command from the "Online" menu.
3. You may test and operate the project online with the controller if you have configured the
corresponding communication.
The configuration software and the Runtime software are installed on different systems
If the configuration software and the Runtime software are installed on different systems,
proceed as follows:
1. Create and compile your project. For additional information, refer to "Compiling a project".
2. To download the file via cable:
Connect the HMI device to the configuration computer using a standard cable to match the
desired transfer mode and then switch on the HMI device.
3. Set the HMI device to transfer mode.
To start transfer mode, press the "Transfer" button in the Loader. You can also assign the
system function "SetDeviceMode" to an operator control.
4. Load the project from the configuration computer to your target device. For further
information, refer to "Loading projects".
Note
If the HMI device is a PC, you can transfer the compiled file without using the loader, for
example, via Ethernet. Double-click the corresponding file on your PC to start Runtime.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2432 System Manual, 08/2011,
9.14.2.4 Testing a project
Introduction
You have the following options for testing a WinCC project:
Testing projects on the configuration computer.
Simulator
The Simulator is used to test WinCC projects with internal tags and process tags. For
additional information, refer to "Simulating projects".
Tests supported by the Simulator:
Offline testing of a configuration without connection to a PLC.
Online testing of a configuration with connection to a PLC and inactive process.
Implementation of a demo project.
Script debugger
The script debugger tests your scripts in Runtime to find logical programming errors. For
additional information, refer to "Working with the Debugger".
Testing projects on the HMI device
Offline testing of the project on the HMI device
Offline testing means that communication between the HMI device and the PLC is down
for the duration of the test. You can operate the HMI device, however, without being able
to exchange data with the PLC. Set the "Offline" mode on the HMI device by assigning the
system function "SetDeviceMode" to an operating element.
Online testing of the project on the HMI device
Online testing means that communication between the HMI device and the PLC is up for
the duration of the test. You can use the HMI device to control the plant as configured. Set
the "Online" mode on the HMI device by assigning the system function "SetDeviceMode"
to an operating element.
Procedure
The following steps show the basic procedures for simulating a project offline on the
configuration computer without PLC connection.
1. Start by creating a project as it is going to be run later with an interconnected PLC.
2. Save and compile the project.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2433
3. Start the Simulator directly from the active configuration software. Select "Online > Simulate
Runtime > With tag simulator".
If simulating the project for the first time, the simulator is started with a new, empty
simulation table. If you have already created a simulation table for your project, it will be
opened.
The simulation table "*.six" contains all your settings for the simulation of tags and area
pointers.
4. Make any changes to the tags and area pointers of your project in the simulation table.
Toggle between the simulation table and Runtime using the <ALT+TAB> key shortcut.
Save your simulation settings with "File > Save." Assign the file a meaningful name. The
file name is automatically assigned the extension "*.six".
9.14.2.5 Backup and restoring projects
Introduction
Backup and restore operations transfer the relevant data between flash memory on the HMI
device and a configuration computer.
Requirement
The HMI device is connected to a configuration computer.
No project is open in WinCC.
Relevant only for backup or for restore operations without reset to factory setting:
The data channel is configured on the HMI device.
Project backup
Proceed as follows to backup the project:
1. Select "Project Transfer Communication Settings" in WinCC on the configuration
computer.
The "Communication Settings" dialog opens.
2. Select the HMI device type.
3. Select the type of connection between the HMI device and the configuration computer, then
set the communication parameters.
4. Close the dialog with "OK".
5. In WinCC, select the menu command "Project Transfer Backup".
The "Backup Settings" dialog opens.
6. Select the data to be backed up.
7. Select a destination folder and a file name for the *.psb backup file.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2434 System Manual, 08/2011,
8. Set "Transfer" mode on the HMI device.
If automatic transfer mode is enabled on the HMI device, the device automatically sets
"Transfer" mode when a backup is initiated.
9. Start the backup operation in WinCC with "OK" on the configuration computer.
Follow the instructions in WinCC flexible.
A status view opens to indicate the progress of the operation.
Result
The system outputs a message when the backup is completed.
The relevant data is now backed up on the configuration computer.
Restoring projects
Proceed as follows to restore projects:
1. Select "Project Transfer Communication Settings" in WinCC on the configuration
computer.
The "Communication Settings" dialog opens.
2. Select the HMI device type.
3. Select the type of connection between the HMI device and the configuration computer, then
set the communication parameters.
4. Close the dialog with "OK".
5. In WinCC, select the menu command "Project Transfer Backup".
The "Restore Settings" dialog dialog opens.
6. Select the *.psb backup file to be restored from the "Open" dialog.
The view shows from which HMI device the backup file originates and the type of data it
contains.
7. Set "Transfer" mode on the HMI device.
If automatic transfer mode is enabled on the HMI device, the device automatically sets
"Transfer" mode when a restore operation is initiated.
8. Start the backup operation in WinCC with "OK" on the configuration computer.
Follow the instructions in WinCC.
A status view opens to indicate the progress of the operation.
Result
The transfer is completed when the backup data is restored from the configuration computer
to the HMI device.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2435
9.14.2.6 Starting the project
Project start modes
Options of starting a WinCC project on a Runtime PC:
Running it from the Explorer
You can run the project by double-clicking its file name in Windows Explorer.
Starting together with Runtime
If you enter a project file in the "HmiRT.ini" file, it will start as soon as WinCC Runtime is
started from the Windows Start menu.
Run from the command line
To run your project, type in one command either at the MS-DOS prompt, or on the "Start
> Run" command line in Windows, and then press <Enter>. Note that the following
command line may diverge from its installation path:
c:\Programs\Siemens\SIMATIC WinCC flexible\WinCC flexible 2007
Runtime\HmiRTm.exe c:\project\myproject.fwx
Autostart
If your project is linked to the Autostart directory of the Windows start menu, it will be
automatically upon system startup.
You can also make the settings for the automatic startup in the "Settings" dialog of the
WinCC Runtime Loader.
Note
Start the loader from the Windows Start menu "SIMATIC\WinCC flexible Runtime >
WinCC flexible Runtime Loader".
9.14.3 Operating projects
9.14.3.1 Setting the project language
Introduction
The HMI device supports multilingual projects. You must have configured a corresponding
operating element which lets you change the language setting on the HMI device during
runtime.
The project always starts with the language set in the previous session.
Requirement
The required language for the project must be available on the HMI device.
The language switching function must be logically linked to a configured operating element
such as a button.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2436 System Manual, 08/2011,
Selecting a language
You can change project languages at any time. Language-specific objects are immediately
output to the screen in the new language when you switch languages.
The following options are available for switching the language:
A configured operating element switches from one language to the next in a list.
A configured operating element directly sets the desired language.
9.14.3.2 Operating recipes
Structure of a recipe
Recipes
The recipe collection for the production of a product family can be compared to a file cabinet.
A recipe which is used to manufacture a product corresponds to a drawer in a file cabinet.
Example:
In a plant for producing fruit juice, recipes are required for different flavors. There is a recipe,
for example, for the flavors orange, grape, apple and cherry.
File cabinet Recipe collection Recipes for a fruit juice plant
Drawer Recipe Orange flavored drinks
Drawer Recipe Grape flavored drinks
Drawer Recipe Apple flavored drinks
Drawer Recipe Cherry flavored drinks
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2437
Recipe data records
The drawers of the file cabinet are filled with suspension folders. The suspension folders in
the drawers represent records required for manufacturing various product variants.
Example:
Product variants of the flavor apple might be a soft drink, a juice or nectar, for example.
Drawer Recipe Product variants of apple flavored drinks
Suspension
folder
Recipe data record Apple drink
Suspension
folder
Recipe data record Apple nectar
Suspension
folder
Recipe data record Apple juice
Elements
In the figure showing the file cabinet, each suspension folder contains the same number of
sheets. Each sheet in the suspension folder corresponds to an element of the recipe data
record. All the records of a recipe contain the same elements. The records differ, however, in
the value of the individual elements.
Example:
All drinks contain the same components: water, concentrate, sugar and flavoring. The records
for soft drink, fruit juice or nectar differ, however, in the quantity of sugar used in production.
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
2438 System Manual, 08/2011,
Recipes in the project
Overview
If recipes are used in a project, the following components interact:
HMI device recipe memory
Recipes are saved in the form of data records in the HMI device recipe memory.
Recipe view / recipe screen
On the HMI device, recipes are displayed and edited in the recipe view or in a recipe screen.
The recipe data records from the internal memory of the HMI device are displayed and
edited in the recipe view.
The values of the recipe tags are displayed and edited in the recipe screen.
Note
The same recipe tags can be configured in a variety of recipes. If you modify the value
of a recipe tag, the synchronization changes the value of the recipe tag in all recipes.
Recipe tags
The recipe tags contain recipe data. When you edit recipes in a recipe screen, the recipe
values are stored in recipe tags. The point at which the recipe tag values are exchanged
with the PLC depends on the configuration.
Data flow
The following figure shows the data flow in a project with recipes:
Recipe 1
Recipe 2
Recipe 3
Recipe n
Recipe memory HMl device
PLC
Recipe view
Recipe
screen
Recipe tag
Memory card
3
1
2
5
6
4
7
Visualizing processes (Advanced)
9.14 Operating in Runtime
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2439
Editing, saving or deleting a recipe data record
Display recipe data record
Synchronize or do not synchronize recipe tags
Display and edit recipe tags in the recipe screen
Write records from the recipe view to the PLC or read records from the PLC and display
them in the recipe view.
Recipe tags are to the PLC online or offline
Export or import recipe data record to memory card
Displaying a Recipe
Displaying Recipes
You can display and edit recipes on the HMI device with a recipe view or recipe screen.
Recipe view
A recipe view is a screen object used to manage recipe data records. The recipe view shows
recipe data records in tabular form.
Depending on the configuration, the recipe view is displayed as follows:
As enhanced recipe view
As simple recipe view
The configuration engineer also defines which operator controls are displayed in the recipe
view. Only the simple recipe view can be configured on the TP 177A.
Enhanced Recipe View
The figure below shows an example of the enhanced recipe view:
The title bar of the active window now has an orange background.
The title bars of inactive windows for the relevant station now have an orange line below
them.
An orange, pulsing bar appears at the right-hand edge of the status bar. If the connection
has been established but is functioning incorrectly, an icon for an interrupted connection
is displayed instead of the bar. You will find more information on the error in "Diagnostics"
in the Inspector window.
Using online and diagnostics functions
10.2 View in online mode
WinCC Advanced V11.0 SP1
System Manual, 08/2011, 2673
Operating mode symbols or diagnostics symbols for the stations connected online and
their underlying objects are shown in the project tree. A comparison of the online and
offline status is also made automatically. Differences between online and offline objects
are also displayed in the form of symbols.
The "Diagnostics > Device information" area is brought to the foreground in the Inspector
window.
Online connection abort
The online mode and its display are retained as long as at least one device is connected online.
If the online connection to one or more devices aborts, the TIA Portal remains in online mode.
The display of the TIA Portal changes to offline mode only when there is no longer an online
connection to any device.
See also
General information about online mode (Page 2671)
Basics of project data comparison (Page 209)
Using online and diagnostics functions
10.2 View in online mode
WinCC Advanced V11.0 SP1
2674 System Manual, 08/2011,
10.3 Online access
Online access of the project
In the "Online access" folder of the project tree, you will find all active interfaces of your
programming device/PC. Each interface icon provides you with information on the status of
the interface. You can also display the accessible devices and display and edit the properties
of an interface using the shortcut menu.
The following figure shows the "Online access" folder in the project tree.