Professional Documents
Culture Documents
en-US
en-US
WinCC
WinCC Professional 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
(Professional)
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....................................................................................22
1.3 Options for WinCC Engineering and Runtime systems...............................................................22
2 Readme......................................................................................................................................................25
2.1 General notes..............................................................................................................................25
2.1.1 General notes..............................................................................................................................25
2.1.2 Notes on the installation..............................................................................................................28
2.1.3 Use of communications processors.............................................................................................30
2.2 WinCC Readme...........................................................................................................................31
2.2.1 Functional Constraints.................................................................................................................31
2.2.2 Notes on use...............................................................................................................................31
2.2.3 Migration......................................................................................................................................35
2.2.4 Special considerations for Windows 7.........................................................................................36
2.2.5 Engineering System....................................................................................................................38
2.2.5.1 Screens and Screen Objects.......................................................................................................38
2.2.5.2 Tags.............................................................................................................................................40
2.2.5.3 Alarm system and alarm displays................................................................................................41
2.2.5.4 System functions and scripts.......................................................................................................41
2.2.5.5 Recipes........................................................................................................................................42
2.2.5.6 User administration......................................................................................................................42
2.2.5.7 Communication............................................................................................................................42
2.2.6 Compiling and loading.................................................................................................................46
2.2.7 Runtime.......................................................................................................................................48
2.2.7.1 Notes on operation in Runtime....................................................................................................48
2.2.7.2 Notes on operation of panels in Runtime....................................................................................49
2.2.7.3 Notes on operation of Runtime Advanced...................................................................................49
2.2.7.4 Notes on operation of Runtime Professional...............................................................................49
2.2.8 HMI devices.................................................................................................................................52
2.2.8.1 General notes..............................................................................................................................52
2.2.8.2 Printing via print server................................................................................................................53
2.2.9 Add-ons.......................................................................................................................................54
2.2.9.1 DataMonitor.................................................................................................................................54
2.2.9.2 WebNavigator..............................................................................................................................55
3 Installation..................................................................................................................................................57
3.1 System requirements for installation...........................................................................................57
3.1.1 Notes on the system requirements..............................................................................................57
3.1.2 WinCC Professional system requirements..................................................................................58
3.1.2.1 Software and hardware requirements.........................................................................................58
3.1.2.2 Add-ons.......................................................................................................................................61
3.1.2.3 Licenses and Powerpacks...........................................................................................................63
3.2 Licenses......................................................................................................................................71
WinCC Professional V11.0 SP1
System Manual, 08/2011, 3
3.3 Installation log..............................................................................................................................72
3.4 Starting installation......................................................................................................................73
3.5 Installing Support Packages........................................................................................................75
3.6 Displaying the installed software.................................................................................................76
3.7 Modifying or updating installed products.....................................................................................77
3.8 Repairing installed products........................................................................................................79
3.9 Starting to uninstall......................................................................................................................80
3.10 Installing and uninstalling the migration tool................................................................................82
3.10.1 System requirements...................................................................................................................82
3.10.2 Installing the migration tool..........................................................................................................82
3.10.3 Uninstalling the migration tool.....................................................................................................83
4 Migrating projects.......................................................................................................................................85
4.1 Migrating projects........................................................................................................................85
4.2 Preparing projects with the migration tool...................................................................................86
4.2.1 Migrating projects with the migration tool....................................................................................86
4.2.2 Calling the migration tool.............................................................................................................88
4.2.3 Creating a migration file...............................................................................................................88
4.3 Migrating projects........................................................................................................................89
4.4 Displaying the history of the migration.........................................................................................90
4.5 Displaying the log file of the migration.........................................................................................90
4.6 Migrating WinCC flexible projects (Professional)........................................................................91
4.6.1 Migrating WinCC flexible 2008 projects.......................................................................................91
4.6.1.1 Basics (WinCC flexible)...............................................................................................................91
4.6.1.2 Migrating engineering data (WinCC flexible)...............................................................................97
4.6.1.3 Migrating runtime data (WinCC flexible)....................................................................................117
4.6.1.4 Migrating integrated projects (WinCC flexible)..........................................................................120
4.6.1.5 Reference (WinCC flexible).......................................................................................................123
4.7 Post-editing integrated projects.................................................................................................138
4.7.1 Migrating an integrated project..................................................................................................138
4.7.2 Post-editing integrated projects.................................................................................................139
4.7.3 Converting unspecified CPUs into specified CPUs...................................................................141
4.7.4 Creating an integrated HMI connection.....................................................................................142
4.7.5 Re-linking HMI tags...................................................................................................................144
4.7.6 Deleting an unspecified connection...........................................................................................145
5 First steps.................................................................................................................................................147
5.1 Getting Started Documentation.................................................................................................147
6 Introduction to the TIA Portal....................................................................................................................149
6.1 User interface and operation.....................................................................................................149
6.1.1 Starting, setting and exiting the TIA Portal...............................................................................149
6.1.1.1 Starting and exiting the TIA Portal.............................................................................................149
6.1.1.2 Overview of the program settings..............................................................................................149
6.1.1.3 Overview of the script and text editor settings...........................................................................151
Table of contents
WinCC Professional V11.0 SP1
4 System Manual, 08/2011,
6.1.1.4 Overview of the print settings....................................................................................................152
6.1.1.5 Changing the settings................................................................................................................153
6.1.2 Layout of the user interface.......................................................................................................153
6.1.2.1 Views.........................................................................................................................................153
6.1.2.2 Portal view.................................................................................................................................153
6.1.2.3 Project view...............................................................................................................................155
6.1.2.4 Project navigation......................................................................................................................157
6.1.2.5 Work area..................................................................................................................................160
6.1.2.6 Inspector window.......................................................................................................................169
6.1.2.7 Task cards.................................................................................................................................171
6.1.2.8 Details view...............................................................................................................................172
6.1.2.9 Overview window.......................................................................................................................174
6.1.2.10 Resetting the user interface layout............................................................................................177
6.1.3 Keyboard shortcuts....................................................................................................................178
6.1.3.1 Keyboard shortcuts for project editing.......................................................................................178
6.1.3.2 Keyboard shortcuts for windows................................................................................................179
6.1.3.3 Keyboard shortcuts in the project tree.......................................................................................179
6.1.3.4 Keyboard shortcuts in tables.....................................................................................................179
6.1.3.5 Keyboard shortcuts for text editing............................................................................................180
6.1.3.6 Using the on-screen keyboard...................................................................................................180
6.1.4 Special features specific to the operating system.....................................................................181
6.1.4.1 Influence of user rights..............................................................................................................181
6.1.4.2 Expanding user rights................................................................................................................182
6.2 Help on the information system.................................................................................................183
6.2.1 General remarks on the information system..............................................................................183
6.2.2 Opening the Help system..........................................................................................................186
6.2.3 Searching the Help system for keywords..................................................................................186
6.2.4 Full-text searches......................................................................................................................186
6.2.5 Using favorites...........................................................................................................................187
6.2.6 Printing help topics....................................................................................................................188
6.2.7 Disabling the automatic display of tooltip cascades..................................................................188
6.2.8 Safety Guidelines......................................................................................................................189
7 Editing projects.........................................................................................................................................191
7.1 The basics of projects................................................................................................................191
7.2 Creating and managing projects................................................................................................192
7.2.1 Creating a new project...............................................................................................................192
7.2.2 Opening projects.......................................................................................................................192
7.2.3 Displaying properties of the project...........................................................................................193
7.2.4 Saving projects..........................................................................................................................194
7.2.5 Closing projects.........................................................................................................................195
7.2.6 Deleting projects........................................................................................................................195
7.2.7 Working with multi-language projects........................................................................................196
7.2.7.1 Project text basics.....................................................................................................................196
7.2.7.2 Select project languages...........................................................................................................197
7.2.7.3 Setting the editing language......................................................................................................198
7.2.7.4 Translating texts directly............................................................................................................198
7.2.7.5 Translating texts using reference texts......................................................................................199
7.2.7.6 Exporting and importing project texts........................................................................................200
7.2.7.7 Application examples for multilanguage projects......................................................................202
7.3 Editing project data....................................................................................................................203
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 5
7.3.1 Compiling and loading project data...........................................................................................203
7.3.1.1 Compiling project data...............................................................................................................203
7.3.1.2 Downloading project data..........................................................................................................205
7.3.2 Comparing project data.............................................................................................................210
7.3.2.1 Basics of project data comparison.............................................................................................210
7.3.3 Protecting project data...............................................................................................................211
7.3.3.1 Protection concept for project data............................................................................................211
7.3.3.2 Revoking access rights for devices...........................................................................................212
7.3.4 Printing project contents............................................................................................................212
7.3.4.1 Documentation settings.............................................................................................................212
7.3.4.2 Printout of project contents........................................................................................................213
7.3.4.3 Changing the print settings........................................................................................................214
7.3.4.4 Specifying the print layout.........................................................................................................215
7.3.4.5 Entering document information..................................................................................................216
7.3.4.6 Managing cover pages and frames...........................................................................................217
7.3.4.7 Designing cover pages and frames...........................................................................................220
7.3.4.8 Displaying print preview.............................................................................................................226
7.3.4.9 Printing project data...................................................................................................................229
7.4 Undoing and redoing actions.....................................................................................................231
7.4.1 Basics of undoing and redoing actions......................................................................................231
7.4.2 Undoing an action......................................................................................................................233
7.4.3 Redoing an action......................................................................................................................234
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................................................................................................................237
7.6.1 Text lists....................................................................................................................................237
7.6.2 Creating user-defined text lists..................................................................................................238
7.6.3 Editing user-defined text lists.....................................................................................................239
7.6.4 Editing system-defined text lists................................................................................................240
7.7 Using memory cards..................................................................................................................241
7.7.1 Basics about memory cards......................................................................................................241
7.7.2 Adding a user-defined card reader............................................................................................241
7.7.3 Accessing memory cards..........................................................................................................242
7.7.4 Displaying properties of memory cards.....................................................................................242
7.8 Using libraries............................................................................................................................243
7.8.1 Library basics............................................................................................................................243
7.8.2 "Libraries" task card...................................................................................................................245
7.8.3 Using the elements and parts view............................................................................................247
7.8.4 Working with the project library.................................................................................................248
7.8.4.1 Project library basics.................................................................................................................248
7.8.4.2 Creating folders in the project library.........................................................................................248
7.8.4.3 Adding elements to the project library.......................................................................................249
7.8.4.4 Using elements of the project library.........................................................................................250
7.8.4.5 Editing elements of a project library..........................................................................................253
7.8.4.6 Removing elements from the project library..............................................................................254
7.8.4.7 Filtering the view........................................................................................................................255
7.8.5 Working with global libraries......................................................................................................256
7.8.5.1 Global library basics..................................................................................................................256
7.8.5.2 Creating a new global library.....................................................................................................256
Table of contents
WinCC Professional V11.0 SP1
6 System Manual, 08/2011,
7.8.5.3 Opening a global library.............................................................................................................257
7.8.5.4 Displaying properties of global libraries.....................................................................................258
7.8.5.5 Saving a global library...............................................................................................................259
7.8.5.6 Closing a global library..............................................................................................................260
7.8.5.7 Deleting a global library.............................................................................................................261
7.8.5.8 Creating folders in the global libraries.......................................................................................262
7.8.5.9 Adding elements to a global library...........................................................................................263
7.8.5.10 Using elements of a global library.............................................................................................264
7.8.5.11 Editing elements of a global library............................................................................................267
7.8.5.12 Removing elements from a global library..................................................................................269
7.8.5.13 Using a supplied global library...................................................................................................269
7.8.5.14 Filtering the view........................................................................................................................270
7.9 Using cross-references..............................................................................................................271
7.9.1 Using cross-references..............................................................................................................271
7.10 Simulating devices.....................................................................................................................272
7.10.1 Simulation of devices.................................................................................................................272
7.10.2 Starting the simulation...............................................................................................................272
8 Editing devices and networks...................................................................................................................273
8.1 Configuring devices and networks.............................................................................................273
8.1.1 Hardware and network editor....................................................................................................273
8.1.1.1 Overview of hardware and network editor.................................................................................273
8.1.1.2 Network view.............................................................................................................................275
8.1.1.3 Device view...............................................................................................................................277
8.1.1.4 Topology view............................................................................................................................280
8.1.1.5 Printing hardware and network configurations..........................................................................281
8.1.1.6 Activating the page break preview for printout..........................................................................283
8.1.1.7 Changing the print options.........................................................................................................283
8.1.1.8 Inspector window ......................................................................................................................284
8.1.1.9 Hardware catalog .....................................................................................................................285
8.1.1.10 Information on hardware components.......................................................................................287
8.1.1.11 Enabling product support...........................................................................................................288
8.1.1.12 Keyboard action in the hardware and network editor................................................................289
8.1.2 Configuring devices...................................................................................................................290
8.1.2.1 Basics........................................................................................................................................290
8.1.2.2 Configuring individual devices...................................................................................................298
8.1.3 Configure networks....................................................................................................................312
8.1.3.1 Networking devices...................................................................................................................312
8.1.3.2 Communication via connections................................................................................................330
8.1.3.3 Displaying and configuring topology..........................................................................................373
8.1.4 Creating configurations..............................................................................................................388
8.1.4.1 Configurations for automation systems.....................................................................................388
8.1.4.2 Configurations for PROFIBUS DP.............................................................................................420
8.1.4.3 Configurations for PROFINET IO..............................................................................................442
8.1.4.4 Bus coupling with PN/PN coupler..............................................................................................470
8.1.4.5 Configurations using external tools...........................................................................................471
8.1.4.6 Loading a configuration.............................................................................................................473
8.1.5 Additional information on configurations....................................................................................475
8.1.5.1 Functional description of S7-1200 CPUs...................................................................................475
8.1.5.2 Distributed I/O............................................................................................................................534
8.1.5.3 Parameters of analog modules..................................................................................................563
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 7
8.1.6 System diagnostics with 'Report System Errors'.......................................................................564
8.1.6.1 Introduction to system diagnostics with 'Report System Errors'................................................564
8.1.6.2 Basics of system diagnostics.....................................................................................................564
8.1.6.3 Components supported.............................................................................................................565
8.1.6.4 Diagnostics blocks for reporting system errors..........................................................................565
8.1.6.5 Properties of the blocks.............................................................................................................566
8.1.6.6 Supported error OBs.................................................................................................................567
8.1.6.7 Overview of the status DBs.......................................................................................................568
8.1.6.8 Diagnostics status DB...............................................................................................................568
8.1.6.9 PROFINET IO DB......................................................................................................................572
8.1.6.10 PROFIBUS DP DB....................................................................................................................574
8.1.6.11 Displaying settings of system diagnostics.................................................................................576
8.1.6.12 Basic settings............................................................................................................................576
8.1.6.13 Advanced settings.....................................................................................................................579
8.1.7 Displaying alarms......................................................................................................................582
8.1.7.1 Overview of the alarm display...................................................................................................582
8.1.7.2 Archive view..............................................................................................................................583
8.1.7.3 Layout of the alarms in the archive view...................................................................................583
8.1.7.4 Receiving alarms.......................................................................................................................583
8.1.7.5 Export archive............................................................................................................................584
8.1.7.6 Clear archive.............................................................................................................................584
8.1.7.7 "Active alarms" view..................................................................................................................584
8.1.7.8 Layout of the alarms in the "Active alarms" view.......................................................................585
8.1.7.9 Status of the alarms...................................................................................................................585
8.1.7.10 Acknowledging alarms...............................................................................................................585
8.1.7.11 Ignoring alarms..........................................................................................................................586
8.1.7.12 Keyboard commands in the alarm display.................................................................................587
8.2 Device and network diagnostics................................................................................................587
8.2.1 Hardware diagnostics................................................................................................................587
8.2.1.1 Overview of hardware diagnostics.............................................................................................587
8.2.1.2 Showing non-editable and current values of configurable module properties...........................596
8.2.1.3 Showing the current values of dynamic modules properties.....................................................599
8.2.1.4 Checking a module for defects..................................................................................................602
8.2.1.5 Changing the properties of a module or the programming device / PC....................................608
8.2.1.6 Diagnostics in STOP mode.......................................................................................................615
8.2.1.7 Online accesses in the Online and Diagnostics view................................................................618
8.2.1.8 Checking PROFIBUS DP subnets for faults..............................................................................620
8.2.2 Connection diagnostics.............................................................................................................623
8.2.2.1 Overview of connection diagnostics..........................................................................................623
8.2.2.2 Displaying the connection status using icons............................................................................624
8.2.2.3 Detailed connection diagnostics................................................................................................625
9 Visualizing processes (Professional)........................................................................................................629
9.1 Creating screens.......................................................................................................................629
9.1.1 Principles...................................................................................................................................629
9.1.1.1 Screen basics............................................................................................................................629
9.1.1.2 Screen basics............................................................................................................................631
9.1.1.3 HMI device dependency for screens.........................................................................................632
9.1.1.4 Elements and Basic Settings.....................................................................................................634
9.1.1.5 Working with screens................................................................................................................637
9.1.1.6 Working with templates.............................................................................................................641
9.1.1.7 Working with designs.................................................................................................................648
Table of contents
WinCC Professional V11.0 SP1
8 System Manual, 08/2011,
9.1.2 Working with Objects.................................................................................................................657
9.1.2.1 Overview of objects...................................................................................................................657
9.1.2.2 Overview of objects...................................................................................................................660
9.1.2.3 Overview of objects...................................................................................................................664
9.1.2.4 Options for Editing Objects........................................................................................................666
9.1.2.5 Inserting an object.....................................................................................................................668
9.1.2.6 Deleting an Object.....................................................................................................................669
9.1.2.7 Positioning an object.................................................................................................................670
9.1.2.8 Resizing an object.....................................................................................................................671
9.1.2.9 Selecting multiple objects..........................................................................................................672
9.1.2.10 Aligning objects.........................................................................................................................674
9.1.2.11 Moving an object forward or backward......................................................................................675
9.1.2.12 Show objects outside the screen area.......................................................................................676
9.1.2.13 Rotating objects.........................................................................................................................677
9.1.2.14 Flipping objects..........................................................................................................................679
9.1.2.15 Designing an object...................................................................................................................679
9.1.2.16 Designing an object...................................................................................................................680
9.1.2.17 Rotating an object in runtime.....................................................................................................680
9.1.2.18 Flashing.....................................................................................................................................682
9.1.2.19 Flashing.....................................................................................................................................682
9.1.2.20 Inserting multiple objects of the same type (stamping tool).......................................................683
9.1.2.21 Repositioning and resizing multiple objects...............................................................................685
9.1.2.22 Hiding or showing objects..........................................................................................................685
9.1.2.23 Managing My Controls...............................................................................................................686
9.1.2.24 External graphics.......................................................................................................................688
9.1.2.25 Managing external graphics......................................................................................................689
9.1.2.26 Storing an external image in the graphics library......................................................................690
9.1.2.27 Working with object groups.......................................................................................................692
9.1.2.28 Configuring the Keyboard Access.............................................................................................699
9.1.2.29 Examples...................................................................................................................................705
9.1.3 Working with Text Lists and Graphic Lists.................................................................................708
9.1.3.1 Working with Text Lists..............................................................................................................708
9.1.3.2 Working with Graphic Lists........................................................................................................718
9.1.4 Dynamic Screen Control............................................................................................................729
9.1.4.1 Basics on dynamizing screens..................................................................................................729
9.1.4.2 Basics of dynamizing screens...................................................................................................729
9.1.4.3 Dynamization in the inspector window......................................................................................730
9.1.4.4 Dynamization in the inspector window......................................................................................732
9.1.4.5 Dynamization with animations...................................................................................................735
9.1.4.6 Dynamization in the property list...............................................................................................756
9.1.4.7 Dynamize with system functions...............................................................................................762
9.1.4.8 Show overview of the dynamizations........................................................................................764
9.1.5 Working with Layers..................................................................................................................765
9.1.5.1 Basics on working with layers....................................................................................................765
9.1.5.2 Moving objects between layers.................................................................................................766
9.1.5.3 Setting the active layer..............................................................................................................767
9.1.5.4 Show and hide layers................................................................................................................768
9.1.5.5 Show and hide layers................................................................................................................770
9.1.5.6 Hide layers and objects in Runtime...........................................................................................770
9.1.5.7 Renaming layers........................................................................................................................772
9.1.6 Working with libraries................................................................................................................773
9.1.6.1 Basics on libraries.....................................................................................................................773
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 9
9.1.6.2 Copy templates and types.........................................................................................................774
9.1.6.3 Libraries in WinCC.....................................................................................................................775
9.1.6.4 Displaying library objects...........................................................................................................777
9.1.6.5 Managing library objects............................................................................................................780
9.1.6.6 Storing an object in a library......................................................................................................781
9.1.6.7 Inserting a library object............................................................................................................782
9.1.6.8 Creating a global library.............................................................................................................783
9.1.6.9 Saving a global library...............................................................................................................783
9.1.6.10 Opening a global library.............................................................................................................784
9.1.7 Working with faceplates.............................................................................................................785
9.1.7.1 Basics on faceplates..................................................................................................................785
9.1.7.2 Faceplate editor.........................................................................................................................788
9.1.7.3 Create and manage faceplate types..........................................................................................791
9.1.7.4 Dynamizing faceplates..............................................................................................................808
9.1.7.5 Example: Creating and dynamically controlling faceplates.......................................................809
9.1.8 Display and Control Objects......................................................................................................817
9.1.8.1 Device-Specific Nature of the Objects.......................................................................................817
9.1.8.2 Objects......................................................................................................................................828
9.1.9 Configuring screen navigation...................................................................................................953
9.1.9.1 Basics on screen navigation......................................................................................................953
9.1.9.2 Basics for screen navigation......................................................................................................954
9.1.9.3 Assigning button with screen change........................................................................................954
9.1.9.4 Assigning screen change to function key..................................................................................956
9.1.9.5 Menus and toolbars for Runtime Professional...........................................................................957
9.2 Working with tags......................................................................................................................975
9.2.1 Basics........................................................................................................................................975
9.2.1.1 Basics of tags............................................................................................................................975
9.2.1.2 Overview of HMI tag tables.......................................................................................................977
9.2.1.3 External tags..............................................................................................................................978
9.2.1.4 External tags..............................................................................................................................979
9.2.1.5 Addressing external tags...........................................................................................................980
9.2.1.6 Internal Tags..............................................................................................................................982
9.2.1.7 Internal Tags..............................................................................................................................983
9.2.2 Working with Tags.....................................................................................................................984
9.2.2.1 Creating tags.............................................................................................................................984
9.2.2.2 Editing Tags...............................................................................................................................990
9.2.2.3 Configuring Tags.......................................................................................................................996
9.2.3 Working with Arrays.................................................................................................................1019
9.2.3.1 Basics on arrays......................................................................................................................1019
9.2.3.2 Creating array tags..................................................................................................................1021
9.2.3.3 Examples of arrays..................................................................................................................1022
9.2.4 Working with user data types..................................................................................................1023
9.2.4.1 Basics on user data types.......................................................................................................1023
9.2.4.2 Creating the user data type.....................................................................................................1025
9.2.4.3 Creating user data type elements............................................................................................1027
9.2.4.4 Creating tags with a user data type data type.........................................................................1030
9.2.4.5 Managing user data types.......................................................................................................1032
9.2.5 Working with cycles.................................................................................................................1034
9.2.5.1 Cycle basics............................................................................................................................1034
9.2.5.2 Defining cycles........................................................................................................................1035
9.2.6 Working with cycles.................................................................................................................1036
9.2.6.1 Cycle basics............................................................................................................................1036
Table of contents
WinCC Professional V11.0 SP1
10 System Manual, 08/2011,
9.2.6.2 Defining cycles........................................................................................................................1038
9.2.6.3 Define starting point.................................................................................................................1039
9.2.7 Reference................................................................................................................................1039
9.2.7.1 Mapping and coding of data types...........................................................................................1039
9.2.7.2 Coding and value range of data types.....................................................................................1041
9.2.7.3 Data types for SIMATIC S7 300/400.......................................................................................1048
9.2.7.4 Data types for SIMATIC S7 1200............................................................................................1058
9.2.7.5 Data types for OPC-DA...........................................................................................................1070
9.2.7.6 Data types for OPC-XML-DA...................................................................................................1076
9.2.7.7 Data types for Allen Bradley Ethernet IP.................................................................................1082
9.2.7.8 Data types for Modicon Modbus TCP/IP.................................................................................1089
9.2.7.9 Data types for Mitsubishi MC...................................................................................................1096
9.2.8 Archive tags.............................................................................................................................1107
9.2.8.1 Basic principles for data logging..............................................................................................1107
9.2.8.2 Data logging............................................................................................................................1108
9.2.8.3 Data logging............................................................................................................................1127
9.2.9 Displaying Tags.......................................................................................................................1169
9.2.9.1 Displaying tags with Basic Panels...........................................................................................1169
9.2.9.2 Displaying tags with Runtime Advanced and Panels..............................................................1171
9.2.9.3 Displaying tags with Runtime Professional..............................................................................1179
9.3 Working with alarms................................................................................................................1234
9.3.1 Principles.................................................................................................................................1234
9.3.1.1 Alarm Logging in WinCC.........................................................................................................1234
9.3.1.2 Alarm Logging in WinCC.........................................................................................................1235
9.3.1.3 Alarm Logging in WinCC ........................................................................................................1236
9.3.1.4 Alarm Procedures....................................................................................................................1238
9.3.1.5 Alarm states ............................................................................................................................1245
9.3.1.6 Alarm classes..........................................................................................................................1246
9.3.1.7 Acknowledgement...................................................................................................................1249
9.3.1.8 Alarm groups...........................................................................................................................1252
9.3.1.9 Alarm groups...........................................................................................................................1253
9.3.1.10 Alarm number .........................................................................................................................1257
9.3.1.11 Alarm number .........................................................................................................................1257
9.3.2 Working with Alarms ...............................................................................................................1258
9.3.2.1 Alarm components and properties...........................................................................................1258
9.3.2.2 Configuring Alarms..................................................................................................................1260
9.3.2.3 Configuring the Outputting of Alarms......................................................................................1306
9.3.2.4 Configuring acknowledgment..................................................................................................1343
9.3.2.5 Configuring acknowledgment..................................................................................................1346
9.3.2.6 Configuring alarm buffer overflow............................................................................................1351
9.3.3 Alarm Logging.........................................................................................................................1352
9.3.3.1 Configuring alarm logging........................................................................................................1352
9.3.3.2 Configuring alarm logging........................................................................................................1368
9.3.4 Using Alarms in Runtime.........................................................................................................1379
9.3.4.1 Alarms in Runtime...................................................................................................................1379
9.3.4.2 Alarms in Runtime...................................................................................................................1380
9.3.4.3 Using the Alarm Window or Alarm View..................................................................................1382
9.3.4.4 Using the Simple Alarm Window, Alarm View.........................................................................1385
9.3.4.5 Using the Alarm Indicator........................................................................................................1388
9.3.4.6 Acknowledging alarms.............................................................................................................1389
9.3.4.7 Filtering alarms........................................................................................................................1390
9.3.5 Using Alarms in Runtime.........................................................................................................1391
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 11
9.3.5.1 Alarms in Runtime ..................................................................................................................1391
9.3.5.2 Alarm view...............................................................................................................................1393
9.3.5.3 Alarm View Buttons.................................................................................................................1395
9.3.5.4 Filtering Alarms in Runtime.....................................................................................................1396
9.3.5.5 Sorting Alarms in Runtime.......................................................................................................1397
9.3.5.6 Toggling the Alarm View in Runtime ......................................................................................1399
9.3.5.7 Displaying logged alarms in Runtime......................................................................................1400
9.3.5.8 Printing Alarms in Runtime......................................................................................................1401
9.3.5.9 Locking Alarms in Runtime......................................................................................................1402
9.3.5.10 Acknowledgement of Alarms...................................................................................................1406
9.3.6 Reference................................................................................................................................1410
9.3.6.1 System functions for alarms....................................................................................................1410
9.3.6.2 Alarm events ...........................................................................................................................1411
9.3.6.3 Alarm events............................................................................................................................1412
9.3.6.4 System functions for logs........................................................................................................1412
9.3.6.5 Structure of *.csv files that contain alarms..............................................................................1413
9.3.6.6 Description of the System Blocks............................................................................................1414
9.3.6.7 SQL Statements for Filtering the Alarm View..........................................................................1417
9.3.6.8 System events ........................................................................................................................1418
9.3.6.9 System events for Runtime Professional.................................................................................1451
9.3.6.10 Tag Bit Assignments................................................................................................................1461
9.4 Working with logs....................................................................................................................1468
9.4.1 Working with Logs...................................................................................................................1468
9.4.1.1 Log Basics...............................................................................................................................1468
9.4.1.2 Properties of Logs...................................................................................................................1468
9.4.2 Working with Logs...................................................................................................................1470
9.4.2.1 Log basics...............................................................................................................................1470
9.4.2.2 Properties of logs ....................................................................................................................1471
9.5 Working with recipes...............................................................................................................1472
9.5.1 Working with recipes...............................................................................................................1472
9.5.1.1 Basics......................................................................................................................................1472
9.5.1.2 Displaying and Editing Recipes in Runtime.............................................................................1487
9.5.1.3 Configuring Recipes................................................................................................................1499
9.5.1.4 Using Recipes in Runtime.......................................................................................................1515
9.5.1.5 Examples.................................................................................................................................1530
9.5.2 Working with recipes...............................................................................................................1538
9.5.2.1 Principles.................................................................................................................................1538
9.5.2.2 Configuring Recipes................................................................................................................1546
9.5.2.3 Configuring the visualization of recipes ..................................................................................1558
9.5.2.4 Data transfer to the PLC..........................................................................................................1565
9.5.2.5 Operation in Runtime...............................................................................................................1579
9.5.2.6 Examples.................................................................................................................................1592
9.5.2.7 SQL language..........................................................................................................................1600
9.5.2.8 SQL keywords.........................................................................................................................1601
9.6 Working with reports................................................................................................................1602
9.6.1 Basics......................................................................................................................................1602
9.6.1.1 Reports....................................................................................................................................1602
9.6.1.2 Structure of reports..................................................................................................................1604
9.6.1.3 Structure of reports..................................................................................................................1606
9.6.2 Working with reports................................................................................................................1609
9.6.2.1 Creating reports.......................................................................................................................1609
Table of contents
WinCC Professional V11.0 SP1
12 System Manual, 08/2011,
9.6.2.2 Report output...........................................................................................................................1630
9.6.2.3 Working with objects................................................................................................................1641
9.6.2.4 Operation in Runtime...............................................................................................................1653
9.6.3 Objects in reports....................................................................................................................1655
9.6.3.1 Audit report..............................................................................................................................1655
9.6.3.2 Control Data............................................................................................................................1656
9.6.3.3 Control hard copy....................................................................................................................1657
9.6.3.4 Control Information..................................................................................................................1658
9.6.3.5 CSV provider trends................................................................................................................1659
9.6.3.6 CSV provider tables.................................................................................................................1660
9.6.3.7 Date/time field..........................................................................................................................1661
9.6.3.8 Date/time field..........................................................................................................................1662
9.6.3.9 I/O field....................................................................................................................................1663
9.6.3.10 f(t) trend view in reports...........................................................................................................1665
9.6.3.11 f(x) trend view in reports..........................................................................................................1665
9.6.3.12 Graphic view............................................................................................................................1667
9.6.3.13 Graphic I/O field.......................................................................................................................1668
9.6.3.14 Hardcopy.................................................................................................................................1668
9.6.3.15 Alarm view in reports...............................................................................................................1669
9.6.3.16 Alarm sequence report............................................................................................................1670
9.6.3.17 Alarm report.............................................................................................................................1671
9.6.3.18 ODBC database field...............................................................................................................1673
9.6.3.19 ODBC database table..............................................................................................................1674
9.6.3.20 Project name...........................................................................................................................1676
9.6.3.21 Report name............................................................................................................................1677
9.6.3.22 Recipe view in reports.............................................................................................................1678
9.6.3.23 Recipe report...........................................................................................................................1679
9.6.3.24 Page number...........................................................................................................................1680
9.6.3.25 Page number...........................................................................................................................1681
9.6.3.26 Symbolic I/O field.....................................................................................................................1682
9.6.3.27 Table view in reports...............................................................................................................1682
9.6.3.28 Text field..................................................................................................................................1683
9.7 Configuring user administration...............................................................................................1684
9.7.1 Field of application of the user administration.........................................................................1684
9.7.2 Form of the user administration...............................................................................................1685
9.7.3 Basics......................................................................................................................................1686
9.7.3.1 User.........................................................................................................................................1686
9.7.3.2 Users work area......................................................................................................................1687
9.7.3.3 User groups.............................................................................................................................1688
9.7.3.4 User groups work area............................................................................................................1688
9.7.3.5 Settings for the user administration.........................................................................................1689
9.7.3.6 Settings for the user administration.........................................................................................1691
9.7.3.7 Settings for the user administration.........................................................................................1694
9.7.4 Setting up the user administration...........................................................................................1695
9.7.4.1 Basics of user administration...................................................................................................1695
9.7.4.2 Administering users for Runtime ............................................................................................1696
9.7.4.3 Managing users on the server.................................................................................................1705
9.7.4.4 Administering users for Web Client.........................................................................................1709
9.7.4.5 Administering users in Runtime...............................................................................................1712
9.7.4.6 Configuring access protection.................................................................................................1726
9.7.5 Reference................................................................................................................................1728
9.7.5.1 Objects with access protection................................................................................................1728
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 13
9.7.5.2 Objects with access protection................................................................................................1728
9.7.5.3 Objects with access protection................................................................................................1729
9.7.5.4 Default user groups and authorizations ..................................................................................1730
9.7.5.5 Default user groups and authorizations...................................................................................1730
9.7.6 Examples.................................................................................................................................1731
9.7.6.1 Example: Configuring a button with logon dialog box.............................................................1731
9.7.6.2 Example: Logging the logon and logoff events.......................................................................1732
9.7.6.3 Example of a user administration............................................................................................1733
9.8 Working with system functions and Runtime scripting............................................................1740
9.8.1 Working with system functions and Runtime scripting............................................................1740
9.8.1.1 Principles.................................................................................................................................1740
9.8.1.2 Working with Function Lists.....................................................................................................1748
9.8.1.3 Working with customized functions.........................................................................................1753
9.8.1.4 Creating local scripts...............................................................................................................1782
9.8.1.5 Debugging...............................................................................................................................1786
9.8.1.6 Debugging...............................................................................................................................1794
9.8.1.7 Runtime behavior in Runtime..................................................................................................1807
9.8.1.8 Examples of VBS.....................................................................................................................1812
9.8.1.9 Examples of VBS.....................................................................................................................1818
9.8.1.10 Examples of C.........................................................................................................................1833
9.8.2 Reference (Panels, RT Advanced)..........................................................................................1839
9.8.2.1 Events......................................................................................................................................1839
9.8.3 Reference (RT Professional)...................................................................................................1856
9.8.3.1 C scripting................................................................................................................................1856
9.8.3.2 Events......................................................................................................................................1978
9.9 Mobile Wireless.......................................................................................................................2009
9.9.1 Field of application of the Mobile Panel Wireless....................................................................2009
9.9.2 How does the transponder system work?...............................................................................2011
9.9.3 How does the RFID system work?..........................................................................................2013
9.9.4 Basics......................................................................................................................................2015
9.9.4.1 Zones.......................................................................................................................................2015
9.9.4.2 Zones working area.................................................................................................................2016
9.9.4.3 Effective ranges.......................................................................................................................2017
9.9.4.4 Effective ranges working area.................................................................................................2018
9.9.4.5 Effective ranges (RFID)...........................................................................................................2019
9.9.4.6 Work area for effective ranges (RFID).....................................................................................2020
9.9.5 Working with zones.................................................................................................................2021
9.9.5.1 Configuring a zone..................................................................................................................2021
9.9.5.2 Displaying the screen on entering a zone...............................................................................2022
9.9.5.3 Displaying an object in relation to the zone.............................................................................2023
9.9.6 Working with effective ranges..................................................................................................2024
9.9.6.1 Overview..................................................................................................................................2024
9.9.6.2 Configure effective range........................................................................................................2025
9.9.6.3 Configuring the effective range name......................................................................................2026
9.9.6.4 Configuring additional Mobile Wireless objects.......................................................................2027
9.9.7 Working with effective ranges (RFID)......................................................................................2028
9.9.7.1 Overview..................................................................................................................................2028
9.9.7.2 Configuring effective range (RFID)..........................................................................................2029
9.9.7.3 Configuring the effective range name (RFID)..........................................................................2030
9.9.8 Reference................................................................................................................................2030
9.9.8.1 PROFIsafe address.................................................................................................................2030
Table of contents
WinCC Professional V11.0 SP1
14 System Manual, 08/2011,
9.9.8.2 Power Management................................................................................................................2031
9.9.8.3 Zone ID / connection point ID..................................................................................................2032
9.10 Planning tasks.........................................................................................................................2032
9.10.1 Field of application of the Scheduler.......................................................................................2032
9.10.2 Working with tasks and triggers...............................................................................................2033
9.10.3 Basics......................................................................................................................................2034
9.10.3.1 Work area of the "Scheduler" editor........................................................................................2034
9.10.3.2 Triggers...................................................................................................................................2035
9.10.3.3 Task type.................................................................................................................................2038
9.10.4 Planning tasks.........................................................................................................................2043
9.10.4.1 Planning tasks with acyclic triggers.........................................................................................2043
9.10.4.2 Planning tasks with cyclic triggers...........................................................................................2044
9.10.4.3 Planning tasks with event triggers...........................................................................................2046
9.10.4.4 Administer task........................................................................................................................2047
9.10.5 Examples for Runtime Professional........................................................................................2048
9.10.5.1 Example: Activate the start screen daily .................................................................................2048
9.10.5.2 Example: Printing a report once..............................................................................................2049
9.10.5.3 Example: Reading the current user name...............................................................................2051
9.10.5.4 Example: Increment a tag........................................................................................................2052
9.10.6 Examples for Runtime Advanced and Panels.........................................................................2053
9.10.6.1 Example: Update user following change of user.....................................................................2053
9.10.6.2 Example: Weekly printout of a report......................................................................................2054
9.10.6.3 Example: Changing the starting point of a task in Runtime.....................................................2056
9.11 Using global functions.............................................................................................................2060
9.11.1 HMI device wizard basics........................................................................................................2060
9.11.2 HMI device wizard basics........................................................................................................2061
9.11.3 Importing and exporting project data.......................................................................................2062
9.11.3.1 Importing and exporting project data.......................................................................................2062
9.11.3.2 Importing and exporting recipe data records...........................................................................2063
9.11.3.3 Importing and exporting alarms...............................................................................................2069
9.11.3.4 Importing and exporting tags...................................................................................................2084
9.11.3.5 Importing and exporting text lists.............................................................................................2091
9.11.3.6 Importing and exporting project texts......................................................................................2095
9.11.4 Using cross-references............................................................................................................2098
9.11.4.1 General information about cross references...........................................................................2098
9.11.4.2 Displaying the cross-reference list...........................................................................................2098
9.11.4.3 Structure of the cross-reference list.........................................................................................2099
9.11.4.4 Displaying cross-references in the Inspector window..............................................................2100
9.11.5 Managing languages...............................................................................................................2102
9.11.5.1 Languages in WinCC...............................................................................................................2102
9.11.5.2 Language settings in the operating system.............................................................................2103
9.11.5.3 Operating system settings for Asian languages......................................................................2104
9.11.5.4 Setting project languages........................................................................................................2105
9.11.5.5 Creating one project in multiple languages.............................................................................2108
9.11.5.6 Using language-specific graphics............................................................................................2116
9.11.5.7 Languages in runtime..............................................................................................................2120
9.11.5.8 Example of multilingual configuration......................................................................................2127
9.11.6 Replacing devices...................................................................................................................2130
9.11.6.1 Basics......................................................................................................................................2130
9.11.6.2 Device-specific functions.........................................................................................................2131
9.11.6.3 Adjust screens to the new device............................................................................................2136
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 15
9.11.6.4 Example: Replacing devices...................................................................................................2140
9.11.7 Copying between devices and editors.....................................................................................2144
9.11.7.1 Basics......................................................................................................................................2144
9.11.7.2 Copying and pasting................................................................................................................2146
9.11.7.3 Copying and pasting between Runtime Advanced and Panels and Runtime Professional. . . .2151
9.11.8 Configuring system diagnostics...............................................................................................2175
9.11.8.1 System diagnostics basics......................................................................................................2175
9.11.8.2 System diagnostics views........................................................................................................2176
9.11.8.3 System diagnostics..................................................................................................................2178
9.12 Compiling and loading.............................................................................................................2186
9.12.1 Compiling, downloading and simulating projects.....................................................................2186
9.12.1.1 Overview of compiling and loading projects............................................................................2186
9.12.1.2 Compiling a project..................................................................................................................2188
9.12.1.3 Loading projects......................................................................................................................2189
9.12.1.4 Starting Runtime......................................................................................................................2197
9.12.1.5 Simulating projects..................................................................................................................2198
9.12.2 Compiling, downloading and simulating projects.....................................................................2206
9.12.2.1 Overview of compiling and loading projects............................................................................2206
9.12.2.2 Compiling a project..................................................................................................................2208
9.12.2.3 Loading projects......................................................................................................................2209
9.12.2.4 Starting Runtime......................................................................................................................2220
9.12.2.5 Simulating projects..................................................................................................................2221
9.12.3 Servicing the HMI device.........................................................................................................2227
9.12.3.1 ProSave...................................................................................................................................2227
9.12.3.2 Backup of HMI data.................................................................................................................2228
9.12.3.3 Backing up and restoring data of the HMI device....................................................................2229
9.12.3.4 Updating the operating system................................................................................................2230
9.12.3.5 Updating the operating system on the HMI device..................................................................2232
9.12.3.6 Transferring license keys.........................................................................................................2233
9.12.3.7 Managing licenses...................................................................................................................2234
9.12.3.8 Installing and uninstalling an option.........................................................................................2235
9.12.4 Reference................................................................................................................................2236
9.12.4.1 Error messages during loading of projects..............................................................................2236
9.12.4.2 Adapting the project for another HMI device...........................................................................2238
9.12.4.3 Establishing a connection to the HMI device...........................................................................2239
9.13 Operating in Runtime...............................................................................................................2240
9.13.1 Basics......................................................................................................................................2240
9.13.1.1 Overview..................................................................................................................................2240
9.13.1.2 Behavior of the Runtime Advanced and Panels system..........................................................2242
9.13.1.3 System characteristics of Runtime Professional.....................................................................2245
9.13.2 Commissioning projects..........................................................................................................2247
9.13.2.1 Commissioning projects for Runtime Advanced and Panels...................................................2247
9.13.2.2 Commissioning projects for Runtime Professional..................................................................2255
9.13.3 Operating projects...................................................................................................................2277
9.13.3.1 Basics......................................................................................................................................2277
9.13.3.2 Setting the project language....................................................................................................2293
9.13.3.3 Project security .......................................................................................................................2294
9.13.3.4 Operating recipes....................................................................................................................2313
9.13.3.5 Operating alarms.....................................................................................................................2352
9.14 Performance features..............................................................................................................2380
9.14.1 Engineering system.................................................................................................................2380
Table of contents
WinCC Professional V11.0 SP1
16 System Manual, 08/2011,
9.14.2 Basic Panel..............................................................................................................................2382
9.14.3 Panel.......................................................................................................................................2385
9.14.4 Mobile Panel............................................................................................................................2389
9.14.5 Multi Panel...............................................................................................................................2393
9.14.6 Comfort Panel..........................................................................................................................2397
9.14.7 WinCC Runtime Advanced......................................................................................................2400
9.14.8 WinCC Runtime Professional..................................................................................................2404
9.14.9 Orientation help for performance in Runtime (WinCC Runtime Professional).........................2407
9.14.10 General technical specifications..............................................................................................2410
9.14.10.1 Recommended printers......................................................................................................2410
9.14.10.2 Memory requirement of recipes..........................................................................................2410
9.14.10.3 Memory requirements of recipes for Basic Panels, OP 77A, and TP 177A.......................2411
9.15 Options....................................................................................................................................2412
9.15.1 Following GMP with audit........................................................................................................2412
9.15.1.1 Basics......................................................................................................................................2412
9.15.1.2 Enabling GMP compliant configuration...................................................................................2416
9.15.1.3 Using the Audit trail.................................................................................................................2418
9.15.1.4 Configuring audit functions......................................................................................................2439
9.15.1.5 Performance features of GMP-compliant configuration...........................................................2453
9.15.2 Sm@rt Options........................................................................................................................2455
9.15.2.1 Basics......................................................................................................................................2455
9.15.2.2 Remote control via Sm@rtServer............................................................................................2484
9.15.2.3 E-mail notification from runtime...............................................................................................2495
9.15.2.4 Display integrated Service-Pages...........................................................................................2499
9.15.2.5 Access via SIMATIC HMI HTTP Protocol................................................................................2511
9.15.2.6 Connection to the Office-world................................................................................................2519
9.15.3 WinCC/Server for Runtime Professional.................................................................................2523
9.15.3.1 Guide to client server systems................................................................................................2523
9.15.3.2 Clients and servers..................................................................................................................2523
9.15.3.3 Plant configurations.................................................................................................................2524
9.15.3.4 Configuring a multiple-station system......................................................................................2527
9.15.3.5 Characteristics in runtime........................................................................................................2533
9.15.3.6 WinCCStart..............................................................................................................................2536
9.15.3.7 SIMATIC Shell.........................................................................................................................2544
9.15.4 Web Navigator.........................................................................................................................2549
9.15.4.1 The basics...............................................................................................................................2549
9.15.4.2 Installing WebNavigator...........................................................................................................2553
9.15.4.3 Configuring the Web Navigator system...................................................................................2572
9.15.4.4 Operating a WinCC project......................................................................................................2592
9.15.4.5 Setting up terminal services for Web Navigator......................................................................2601
9.15.4.6 Troubleshooting.......................................................................................................................2604
9.15.5 DataMonitor ............................................................................................................................2605
9.15.5.1 The basics...............................................................................................................................2605
9.15.5.2 Configuring the DataMonitor system.......................................................................................2611
9.15.5.3 Working with WinCCViewerRT................................................................................................2630
9.15.5.4 Working with the WebCenter...................................................................................................2633
9.15.5.5 Working with Trends and Alarms ...........................................................................................2660
9.15.5.6 Working with Excel Workbooks...............................................................................................2670
9.15.5.7 Working with reports................................................................................................................2683
9.16 Interfaces.................................................................................................................................2692
9.16.1 OPC.........................................................................................................................................2692
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 17
9.16.1.1 OPC for Runtime Advanced....................................................................................................2692
9.16.1.2 OPC for Runtime Professional................................................................................................2705
9.16.2 Customer controls...................................................................................................................2749
9.16.2.1 Overview..................................................................................................................................2749
9.16.2.2 Interfaces.................................................................................................................................2752
9.16.2.3 Demo project...........................................................................................................................2754
9.16.2.4 Creating and testing customer controls...................................................................................2754
9.16.2.5 Reference................................................................................................................................2764
9.17 Migration to WinCC V11 .........................................................................................................2772
9.17.1 Overview..................................................................................................................................2772
9.17.2 WinCC V7................................................................................................................................2773
9.17.2.1 Actions.....................................................................................................................................2773
9.17.2.2 User objects.............................................................................................................................2775
9.17.2.3 User administration..................................................................................................................2776
9.17.2.4 Direct connection.....................................................................................................................2778
9.17.2.5 Dynamic Wizard......................................................................................................................2780
9.17.2.6 Dynamics dialog......................................................................................................................2782
9.17.2.7 Working efficiently...................................................................................................................2784
9.17.2.8 Structures and structure tags..................................................................................................2785
9.17.3 WinCC flexible.........................................................................................................................2787
9.17.3.1 Libraries...................................................................................................................................2787
9.17.3.2 Screens and templates............................................................................................................2789
9.17.3.3 Scripts in faceplates................................................................................................................2791
9.17.3.4 Synchronization of recipes......................................................................................................2792
10 Using online and diagnostics functions..................................................................................................2793
10.1 General information about online mode..................................................................................2793
10.2 View in online mode................................................................................................................2795
10.3 Online access..........................................................................................................................2796
10.4 Displaying accessible devices.................................................................................................2798
10.5 Opening the properties of an interface....................................................................................2800
10.6 Establishing and canceling an online connection....................................................................2800
10.7 Connecting online with several devices...................................................................................2802
10.8 Basics of assigning parameters for the PG/PC interface........................................................2803
10.9 Adding interfaces.....................................................................................................................2803
10.10 Setting parameters for the Ethernet interface..........................................................................2804
10.10.1 Setting parameters for the Industrial Ethernet interface..........................................................2804
10.10.2 Displaying operating system parameters................................................................................2805
10.10.3 Connecting the PG/PC interface to a subnet...........................................................................2806
10.10.4 Setting parameters for the Ethernet interface..........................................................................2806
10.10.5 Assigning a temporary IP address...........................................................................................2807
10.10.6 Managing temporary IP addresses..........................................................................................2807
10.10.7 Resetting the TCP/IP configuration.........................................................................................2808
10.11 Setting parameters for the MPI and PROFIBUS interfaces.....................................................2809
10.11.1 Setting parameters for the MPI and PROFIBUS interfaces.....................................................2809
10.11.2 Setting MPI or PROFIBUS interface parameters automatically..............................................2810
10.11.3 Setting parameters for the MPI interface.................................................................................2810
Table of contents
WinCC Professional V11.0 SP1
18 System Manual, 08/2011,
10.11.4 Setting parameters for the PROFIBUS interface.....................................................................2812
10.11.5 Overview of the bus parameters for PROFIBUS.....................................................................2815
10.11.6 Resetting the MPI or PROFIBUS configuration.......................................................................2816
10.12 Establishing a remote connection with TeleService................................................................2817
10.12.1 Basics of working with TeleService.........................................................................................2817
10.12.1.1 Introduction to TeleService.................................................................................................2817
10.12.1.2 TeleService functionality....................................................................................................2818
10.12.1.3 Telephone book at TeleService..........................................................................................2818
10.12.2 Telephone networks and modems..........................................................................................2819
10.12.2.1 Supported telephone networks and modems.....................................................................2819
10.12.2.2 Installing the local modem..................................................................................................2820
10.12.2.3 Connecting and configuring the remote modem................................................................2821
10.12.2.4 Initialization string requirements.........................................................................................2822
10.12.3 Using a TS adapter to establish a remote connection.............................................................2822
10.12.3.1 Basics of using a TS adapter.............................................................................................2822
10.12.3.2 Installing TS adapter software............................................................................................2824
10.12.3.3 TS adapter MPI..................................................................................................................2824
10.12.3.4 TS adapter IE.....................................................................................................................2831
10.12.4 Access protection for TeleService and the TS Adapter...........................................................2836
10.12.4.1 Access protection information............................................................................................2836
10.12.4.2 TeleService callback options..............................................................................................2837
10.12.4.3 Levels of protection............................................................................................................2837
10.12.4.4 Setting up access protection and callback number for the TS adapter..............................2838
10.12.4.5 Complete a callback in TeleService...................................................................................2839
10.12.5 Establishing a remote connection to a remote plant................................................................2841
10.12.5.1 Establishing a remote connection......................................................................................2841
10.12.5.2 Terminating a remote connection.......................................................................................2842
10.12.5.3 Checklist for troubleshooting the modem...........................................................................2842
10.12.6 Working with the phone book..................................................................................................2843
10.12.6.1 Basics on working with the phone book.............................................................................2843
10.12.6.2 Structure of the phone book...............................................................................................2844
10.12.6.3 Symbols in the phone book................................................................................................2845
10.12.6.4 Manage phone book...........................................................................................................2845
10.12.7 CPU controlled TeleService remote connections ...................................................................2847
10.12.7.1 Overview of CPU controlled remote connections...............................................................2847
10.12.7.2 Establishing a connection from and to remote systens (PG-AS-remote coupling).............2848
10.12.7.3 Data exchange between remote systems (AS-AS-remote coupling).................................2850
10.12.7.4 Send SMS from a system...................................................................................................2852
10.12.7.5 Send an email from a system.............................................................................................2853
10.12.8 Troubleshooting.......................................................................................................................2855
10.12.8.1 General information on troubleshooting.............................................................................2855
10.12.8.2 Recording a log file for the modem....................................................................................2855
10.12.8.3 Remote connection to the TS adapter is not established...................................................2856
10.12.8.4 Remote connection from the TS adapter is not established...............................................2857
10.12.8.5 Modem connection is interrupted.......................................................................................2858
10.12.8.6 Modem alarms....................................................................................................................2859
11 Glossary.................................................................................................................................................2861
Index.......................................................................................................................................................2863
Table of contents
WinCC Professional V11.0 SP1
System Manual, 08/2011, 19
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 Professional 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.
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.
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.
System overview of STEP 7 and WinCC
1.3 Options for WinCC Engineering and Runtime systems
WinCC Professional V11.0 SP1
22 System Manual, 08/2011,
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)
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 Professional V11.0 SP1
System Manual, 08/2011, 23
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 Professional V11.0 SP1
System Manual, 08/2011, 25
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 Professional V11.0 SP1
26 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 Professional V11.0 SP1
System Manual, 08/2011, 27
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 Professional V11.0 SP1
28 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 Professional V11.0 SP1
System Manual, 08/2011, 29
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 Professional V11.0 SP1
30 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 Professional:
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 and RT Professional V11 SP1
WinCC V11 SP1 and RT Advanced V11
WinCC V11 SP1 and RT Professional V11
The Engineering System and Runtime must always be of the same version after an installation.
Parallel installation of WinCC V11 and WinCC V7
Parallel installation of WinCC V11 Professional or Runtime Professional with WinCC up to
V7.0 (including ServicePacks) is not released.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 31
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):
WinCC flexible 2008 Standard
Installation on a computer with regional setting "Turkish"
If the computer is operated with the regional setting "Turkish" at the time of the installation,
WinCC Runtime Professional cannot be started.
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 - character sets
If you have configured different character sets on screen objects for multilingual texts in the
various project languages, you should check the screens after an HMI device replacement
from a panel to a PC-based Runtime. The configured character sets may be changed by the
device replacement.
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
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
32 System Manual, 08/2011,
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.
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 33
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.
Saving the WinCC project
If you save a project in WinCC using the "Save As" command, this has no effect on the
names of the Runtime projects generated for Runtime Professional. 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. Configuration changes from the original project and
configuration changes from the newly saved project may influence each other.
Therefore, change the target path of the devices in the "Extended download to device" dialog.
Texts in the simulation
If a Runtime language which does not correspond to an installed product langauge is used in
the simulation, system texts are shown in an installed product language. Depending on the
operating system and the installed product languages, this will be either English or Chinese.
If you wish to see all texts in Japanese, Korean or Taiwanese in the relevant language in the
simulation, you should first install WinCC without simulation. Then install WinCC Runtime
Professional with the required languages.
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 existing databases in
the SQL Server 2008.
WinCC RT Professional and S7-1200
The use of WinCC RT Professional in conjunction with an S7-1200 CPU is not permitted.
Windows 7 and Windows 7 SP1
WinCC V11 SP1 is released for:
Windows 7
Windows 7 SP1
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
34 System Manual, 08/2011,
WinCC DataMonitor
If Windows Excel reports an error, make sure that the regional settings of the operating system
and the installed Office language match.
Invalid Runtime language
You may only select the Runtime languages for WinCC Professional that are compatible with
the current settings on your PC. The setting is available in the Control Panel, "Regional and
Language Options > Advanced > Languages for non-Unicode programs" dialog.
The default font is marked as invalid if you select an incompatible Runtime language in the
"Runtime settings > Languages & font" editor.
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 35
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.
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".
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
36 System Manual, 08/2011,
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
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\
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 37
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.
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
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
38 System Manual, 08/2011,
Name in the "Properties" tab of the Inspector
window
Name in the "Info" tab of the Inspector window
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
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 39
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)".
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
40 System Manual, 08/2011,
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.
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 41
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
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
42 System Manual, 08/2011,
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
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:
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 43
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".
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
44 System Manual, 08/2011,
One HMI Panel occupies one communication resource per connection.
One RT Advanced occupies one communication resource per connection.
One RT Professional occupies two communication resources per connection.
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
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 45
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.
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".
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
46 System Manual, 08/2011,
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.
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:
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 47
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.
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
48 System Manual, 08/2011,
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.
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.7.4 Notes on operation of Runtime Professional
Contents
Information that could not be included in the online help.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 49
User authorizations within the operating system
1. All user must be added to the "SIMATIC HMI" user group. This also applies to users who
want to open WinCC projects remotely.
2. The storage folders of the projects must have the NTFS authorizations "SIMATIC HMI" with
full access and "SIMATIC HMI Viewer" with read access. The authorizations must be
inherited for all subordinate objects.
3. Members of the Windows user group "SIMATIC HMI" should not simultaneously be
members of the Windows user group "SQLServer2005MSSQLUser$<Computername>
$WINCC". The members of this group have administrator rights to the SQL server.
Therefore remove all Windows users from this group for whom restricted access to the
WinCC database is sufficient.
Windows 7 / Windows Server 2008: Locking key combinations
If you want to lock key combinations under Windows 7 or Windows Server 2008, you must
change the group policies in the administrative tools of the operating system
A detailed description of this can be found in the FAQ with the entry ID "44027453" in the
SIMATIC Customer Online Support:
Internet: WinCC FAQ 44027453 (http://support.automation.siemens.com/WW/view/en/
44027453)
Fault in the connection between the server and the client
If the connection between the server and client is faulty, check the settings of the PG/PC
interface. TCP/IP(Auto) should not be used for the "Interface Parameter Assignment Used".
Used fixed IP addresses instead.
Fault in the connection between the server and the client
If the computer is simultaneously used as a server with the Engineering System and a client
cannot establish the connection to the server, you should check the releases set on the server.
1. Exit Runtime on the server.
2. Select the command "Find computer..." in the shortcut menu of the network environment
on the desktop of the server.
3. Enter the name of the server as the computer to be found.
4. Open the computer found to recognise the released directories.
5. Remove all the releases that begin with "WinCC_Project_HMI". Information on this is
available in the documentation for the operating system.
This malfunction is caused by the use of the command "Save as..." in conjunction with the
startup of the Runtime of this new project. You can make copies of the projects for backup
purposes using the "Save as..." command. You should, however, continue to work with the
original project.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
50 System Manual, 08/2011,
Language setting for Runtime Professional
With Runtime Professional, illegible texts may occur during runtime if the settings in the
operating system for "Language for non-Unicode programs" do not match the selected Runtime
language. This setting must also be the same on the client and the server for client/server
applications.
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 Runtime
language.
Starting WinCC Runtime Professional
If Engineering System and Runtime are operated on a computer, Runtime or simulation for a
project opened in the engineering system should only be started and ended via the TIA portal.
Other options, for example, the symbol in the taskbar information area, should not be used.
Setting the services for the SQL server
In order to ensure the full functionality of the SQL server for WinCC and WinCC Runtime, you
have to check the SQL server settings.
1. Start "Programme > Microsoft SQL Server 2005 > Configuration Tools > SQL Server
Configuration Manager" in the start menu.
2. Click "SQL Server 2005 Services" in the tree.
3. Check the services "SQL Server (WinCC)","SQL Server (WINCCPLUSMIG)" and "SQL
Server Browser". "Automatic" must be entered for "Start Mode". "LocalSystem" must be
entered for "Log On As". Change the settings, if necessary.
4. Click "SQL Server Network Configuration" in the tree.
5. Click "Protocols for WinCC".
6. Check the "TCP/IP" protocol. "Enabled" must be entered for "Status". Change the settings,
if necessary.
WinCC RT Professional and S7-1200
The use of WinCC RT Professional in conjunction with an S7-1200 CPU is not permitted in
productive operation.
"Report system error" in WinCC Runtime Professional
The "Report system error" functionality is limited in WinCC Runtime Professional in conjunction
with an S7-300 or S7-400. In an alarm view, only one alarm is ever displayed for each
diagnostics type. Alarms on other errors of the same diagnostics type are not displayed.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 51
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
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
52 System Manual, 08/2011,
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
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.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 53
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.
2.2.9 Add-ons
2.2.9.1 DataMonitor
Contents
Information that could not be included in the online help.
Special considerations for Windows 7
Time- or event-triggered Excel Workbooks are not released under the Windows 7 operating
system.
Opening Excel workbooks
If you open an Excel workbook from the DataMonitor client, Excel may issue the error message
"File not found". If this happens, proceed as follows:
1. Confirm the error message with "OK".
2. Leave Excel open.
3. Open the Excel workbook again in Internet Explorer.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
54 System Manual, 08/2011,
Opening Excel workbooks with Excel 2010
Due to safety settings, the automatic connection of an Excel workbook with the server does
not work in Excel 2010.
If you wish to enable automatic connection, deactivate the setting "Enable Protected View for
files located in potential unsafe locations" in Excel 2010 under "Files > Options > Trust Center
> ProtectedView".
2.2.9.2 WebNavigator
Contents
Information that could not be included in the online help.
Installation instructions
The installation instructions for the Web Navigator are part of the installation instructions of
WinCC Runtime Professional. They can be found on the DVD of WinCC Runtime Professional.
Access via Web client
A user can only get access via a Web client if a screen released for Web access has been
assigned to him as the start screen in the user administration.
To release a screen for Web access:
1. Select the "Properties" command in the shortcut menu of a screen.
2. Activate the "Web access" option under "Properties > Web access".
To assign a start screen to a user:
1. In the user administration, select the user to whom you would like to assign a start screen.
2. Click "Properties > General" > Web options > Settings in the Inspector window to specify
a start screen. You can only select screens which have been released for Web access.
Readme
2.2 WinCC Readme
WinCC Professional V11.0 SP1
System Manual, 08/2011, 55
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 71)
Starting installation (Page 73)
Displaying the installed software (Page 76)
Modifying or updating installed products (Page 77)
Repairing installed products (Page 79)
Starting to uninstall (Page 80)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 57
3.1.2 WinCC Professional system requirements
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 Professional V11.0 SP1
58 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 Professional V11.0 SP1
System Manual, 08/2011, 59
Installing Microsoft Windows Message Queuing
You can install the Windows Message Queuing component from the Windows Control Panel.
Under Windows XP
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.
Under Windows 7
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
Opening Direct Help
To be able to continue calling WinCC Direct Help, the following components are installed during
the installation of WinCC:
Microsoft Help Engine
Calling the "WinCC Information System" online help
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 61)
Licensing of WinCC Engineering System (Page 63)
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
60 System Manual, 08/2011,
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.
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 Professional V11.0 SP1
System Manual, 08/2011, 61
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 58)
Installing and uninstalling options (Page 62)
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
Simulation for WinCC Runtime Professional
During the installation of WinCC Runtime Professional, the following add-ons are available for
you to select for installation:
SIMATIC WinCC Web Navigator
SIMATIC WinCC Data Monitor
SIMATIC Logon
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.
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
62 System Manual, 08/2011,
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
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 61)
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 one-time option of activating a trial license. Trial licenses for
Engineering editions WinCC Basic, Comfort, Advanced und Professional expire after 21 days.
If the trial license expires, the following scenarios can occur:
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 63
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:
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 58)
Licensing WinCC Runtime on PC-based HMI devices (Page 64)
Licensing of HMI devices (Page 65)
Working with license keys (Page 66)
Licensing WinCC Runtime Professional Asian (Page 69)
Powerpack (Page 70)
Installing a Powerpack (Page 71)
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.
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
64 System Manual, 08/2011,
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 63)
Licensing of HMI devices
Non-PC-based HMI devices are always equipped with the maximum quantity structure. A
license key is not required for runtime operation.
A license is required for each option 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 Plugin" 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.
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 65
Data backup
CAUTION
Destruction of License Keys on non-PC-based HMI Devices
The authorizations and License Keys you installed are destroyed by back-up / restore
processes on the HMI devices listed below.
270 series
370 series
Carry out the following before beginning with 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
In particular, runtime options can also be used without a license. Non-licensed mode is
indicated every 10 minutes by a window, which you must acknowledge.
See also
Licensing of WinCC Engineering System (Page 63)
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.
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
66 System Manual, 08/2011,
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.
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
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 67
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.
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.
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
68 System Manual, 08/2011,
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 63)
Licensing WinCC Runtime Professional Asian
Introduction
If you are using WinCC Runtime Professional in an Asian language, a dongle is additionally
used for the validation of the required license. The dongle comes in the form of a certified USB
stick together with the required license key for WinCC Runtime Professional Asian. The license
key is stored on the certified USB flash drive.
The following Asian languages are protected by a dongle:
Chinese Simplified
Chinese Traditional
Japanese
Korean
Using the dongle for an Asian Runtime Professional
The following is required to operate WinCC Runtime Professional in an Asian language:
The language for programs that do not support Unicode is set to the appropriate Asian
language in the operating system of the machine running WinCC Runtime.
The runtime language of the WinCC project is set to the Asian language.
If the above conditions are met, the validation is performed by querying the license key and
also by querying the dongle.
In order to successfully license a WinCC project in an Asian language, transfer the required
license key from the certified USB stick to the HMI device using the "Automation License
Manager". Plug the USB into the USB port of the HMI device. The USB stick acts as a dongle
during runtime. The dongle must always remain plugged in the USB port in during runtime.
If you remove the dongle during runtime, WinCC Runtime switch to Demo mode.
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 69
The USB sticks supplied for the Asian markets are certified for permanent use in production.
Therefore, you cannot transfer or copy the content to another disk or USB medium. If you lose
the certified USB stick or it becomes defective, you need a new, certified USB stick.
Simulation of a WinCC project in an Asian language
If you want to check a WinCC project in an Asian language with the simulator, the appropriate
Asian language must also be set in the operating system on the configuration PC for programs
that do not support Unicode. You then also need a certified USB stick as dongle for the
simulation. If no dongle is available, the simulation runs in Demo mode.
See also
Licensing of WinCC Engineering System (Page 63)
Powerpack
Introduction
The following upgrades can be performed with a Powerpack:
From a smaller to a larger edition of WinCC
On a runtime system with greater capacity
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 own WinCC Advanced, for example. You can use the "SIMATIC WinCC Professional
Powerpack WinCC Advanced -> WinCC Professional 512 PowerTags V11 " Powerpack to
activate WinCC Professional with 512 tags for use.
Runtime
You own WinCC Runtime Professional with 128 tags, for example. You can use the "SIMATIC
WinCC Runtime Professional 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 63)
Installation
3.1 System requirements for installation
WinCC Professional V11.0 SP1
70 System Manual, 08/2011,
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" section must be fulfilled.
WinCC is installed.
The license key for the license for which you have purchased a Powerpack is available on
the PC.
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 63)
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.
Installation
3.2 Licenses
WinCC Professional V11.0 SP1
System Manual, 08/2011, 71
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 57)
Starting installation (Page 73)
Displaying the installed software (Page 76)
Modifying or updating installed products (Page 77)
Repairing installed products (Page 79)
Starting to uninstall (Page 80)
Installation log (Page 72)
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".
Installation
3.3 Installation log
WinCC Professional V11.0 SP1
72 System Manual, 08/2011,
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 71)
Starting installation (Page 73)
Installing Support Packages (Page 75)
Displaying the installed software (Page 76)
Modifying or updating installed products (Page 77)
Repairing installed products (Page 79)
Starting to uninstall (Page 80)
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.
Installation
3.4 Starting installation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 73
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.
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".
Installation
3.4 Starting installation
WinCC Professional V11.0 SP1
74 System Manual, 08/2011,
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 72)
Notes on the system requirements (Page 57)
Licenses (Page 71)
Displaying the installed software (Page 76)
Modifying or updating installed products (Page 77)
Repairing installed products (Page 79)
Starting to uninstall (Page 80)
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.
Installation
3.5 Installing Support Packages
WinCC Professional V11.0 SP1
System Manual, 08/2011, 75
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 72)
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.
Installation
3.6 Displaying the installed software
WinCC Professional V11.0 SP1
76 System Manual, 08/2011,
See also
Notes on the system requirements (Page 57)
Licenses (Page 71)
Starting installation (Page 73)
Modifying or updating installed products (Page 77)
Repairing installed products (Page 79)
Starting to uninstall (Page 80)
Installation log (Page 72)
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.
Installation
3.7 Modifying or updating installed products
WinCC Professional V11.0 SP1
System Manual, 08/2011, 77
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.
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.
Installation
3.7 Modifying or updating installed products
WinCC Professional V11.0 SP1
78 System Manual, 08/2011,
See also
Notes on the system requirements (Page 57)
Licenses (Page 71)
Starting installation (Page 73)
Displaying the installed software (Page 76)
Repairing installed products (Page 79)
Starting to uninstall (Page 80)
Installation log (Page 72)
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.
Installation
3.8 Repairing installed products
WinCC Professional V11.0 SP1
System Manual, 08/2011, 79
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.
See also
Notes on the system requirements (Page 57)
Licenses (Page 71)
Starting installation (Page 73)
Displaying the installed software (Page 76)
Modifying or updating installed products (Page 77)
Starting to uninstall (Page 80)
Installation log (Page 72)
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.
Installation
3.9 Starting to uninstall
WinCC Professional V11.0 SP1
80 System Manual, 08/2011,
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".
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.
Installation
3.9 Starting to uninstall
WinCC Professional V11.0 SP1
System Manual, 08/2011, 81
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 72)
Notes on the system requirements (Page 57)
Licenses (Page 71)
Starting installation (Page 73)
Displaying the installed software (Page 76)
Modifying or updating installed products (Page 77)
Repairing installed products (Page 79)
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.
Installation
3.10 Installing and uninstalling the migration tool
WinCC Professional V11.0 SP1
82 System Manual, 08/2011,
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.
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 Professional V11.0 SP1
System Manual, 08/2011, 83
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 Professional V11.0 SP1
System Manual, 08/2011, 85
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 90)
Scaling of STEP 7 and WinCC (Page 21)
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.
Migrating projects
4.2 Preparing projects with the migration tool
WinCC Professional V11.0 SP1
86 System Manual, 08/2011,
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.
See also
Migrating projects (Page 85)
Migrating projects (Page 89)
Calling the migration tool (Page 88)
Creating a migration file (Page 88)
Migrating projects
4.2 Preparing projects with the migration tool
WinCC Professional V11.0 SP1
System Manual, 08/2011, 87
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 88)
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.
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.
Migrating projects
4.2 Preparing projects with the migration tool
WinCC Professional V11.0 SP1
88 System Manual, 08/2011,
See also
Migrating projects (Page 89)
Calling the migration tool (Page 88)
Migrating projects with the migration tool (Page 86)
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".
Migrating projects
4.3 Migrating projects
WinCC Professional V11.0 SP1
System Manual, 08/2011, 89
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.
See also
Post-editing integrated projects (Page 139)
Migrating projects with the migration tool (Page 86)
Creating a migration file (Page 88)
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 193)
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
Migrating projects
4.5 Displaying the log file of the migration
WinCC Professional V11.0 SP1
90 System Manual, 08/2011,
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 85)
4.6 Migrating WinCC flexible projects (Professional)
4.6.1 Migrating WinCC flexible 2008 projects
4.6.1.1 Basics (WinCC flexible)
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:
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 91
ProAgent
Open Platform Program - OPP
See also
Basics on migration (WinCC flexible) (Page 92)
Migrating projects from WinCC flexible (WinCC flexible) (Page 94)
Compiling and loading a migrated project (WinCC flexible) (Page 96)
Supported HMI devices (WinCC flexible) (Page 97)
Object support in the migration (WinCC flexible) (Page 101)
Migration of connections (WinCC flexible) (Page 105)
Migration of tags (WinCC flexible) (Page 108)
Migrating runtime data (WinCC flexible) (Page 117)
Migrating integrated projects (WinCC flexible) (Page 120)
Migrating data types (WinCC flexible) (Page 123)
Basics on migration (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 2380) 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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
92 System Manual, 08/2011,
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
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 93
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
Migration (WinCC flexible) (Page 91)
Engineering system (Page 2380)
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.
Information on the migration of integrated project can be found in the Chapter Migrating
integrated projects (WinCC flexible) (Page 120).
If you only want to save the project in migration format, you can use the migration tool. See
Basics on migration (WinCC flexible) (Page 92) 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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
94 System Manual, 08/2011,
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.
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 95
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 91)
Migrating integrated projects (WinCC flexible) (Page 120)
Basics on migration (WinCC flexible) (Page 92)
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.
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
96 System Manual, 08/2011,
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 91)
4.6.1.2 Migrating engineering data (WinCC flexible)
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 by the migration (WinCC flexible) (Page 99) 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:
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 97
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''
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
98 System Manual, 08/2011,
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 91)
HMI device change by the migration (WinCC flexible) (Page 99)
Configuration change after HMI device change (WinCC flexible) (Page 101)
Object support in the migration (WinCC flexible) (Page 101)
Migration of connections (WinCC flexible) (Page 105)
HMI device change by the 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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 99
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
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
100 System Manual, 08/2011,
Unsupported HMI devices Successors
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 97)
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 97)
Object support in the 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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 101
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
System events
System functions
Texts
Text lists
Tags
Connections
Effective ranges
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
102 System Manual, 08/2011,
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
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 103
The connection of the objects and properties to the respective template is automatically
adapted.
See also
Supported HMI devices (WinCC flexible) (Page 97)
Migration (WinCC flexible) (Page 91)
Changes of values of object properties by the migration (WinCC flexible) (Page 104)
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
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 in the migration (WinCC flexible) (Page 101)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
104 System Manual, 08/2011,
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.
Converting the communication driver
The following tables show the mapping of communication drivers from WinCC flexible to
WinCC.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 105
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
See also
Migration (WinCC flexible) (Page 91)
Supported HMI devices (WinCC flexible) (Page 97)
Adaptation of the configuration for non-migrated connection (WinCC flexible) (Page 107)
Migration of area pointers (WinCC flexible) (Page 108)
Migration of tags (WinCC flexible) (Page 108)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
106 System Manual, 08/2011,
Adaptation of the 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 94) for further
information about the migration log.
See also
Migration of connections (WinCC flexible) (Page 105)
Migrating projects from WinCC flexible (WinCC flexible) (Page 94)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 107
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 Adaptation of the configuration for non-migrated connection (WinCC flexible)
(Page 107) for additional information.
See also
Migration of connections (WinCC flexible) (Page 105)
Adaptation of the configuration for non-migrated connection (WinCC flexible) (Page 107)
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 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 Migrating data types (WinCC flexible)
(Page 123) for additional information.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
108 System Manual, 08/2011,
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 105) 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 Basics on migration (WinCC
flexible) (Page 92) for additional information.
See also
Migration of connections (WinCC flexible) (Page 105)
Migration (WinCC flexible) (Page 91)
Migration of alarm classes and alarm groups (WinCC flexible) (Page 110)
Migrating scripts (WinCC flexible) (Page 112)
Migration of language-dependent contents (WinCC flexible) (Page 114)
Migration of libraries (WinCC flexible) (Page 116)
Migrating data types (WinCC flexible) (Page 123)
Basics on migration (WinCC flexible) (Page 92)
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 109
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
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
110 System Manual, 08/2011,
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.
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 111
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.
See also
Migration of tags (WinCC flexible) (Page 108)
Migrating 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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
112 System Manual, 08/2011,
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
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 Basics on migration (WinCC flexible) (Page 92) 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 108)
Basics on migration (WinCC flexible) (Page 92)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 113
Migration of language-dependent contents (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
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
114 System Manual, 08/2011,
the right-hand edge of the TIA portal and select the correct editing language in the "Language
& Resources" area.
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 115
Tamil
Telugu
Urdu
Punjabi
Persian
Syrian
See also
Migration of tags (WinCC flexible) (Page 108)
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 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 108)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
116 System Manual, 08/2011,
4.6.1.3 Migrating runtime data (WinCC flexible)
Migrating 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:
"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 91)
Backing up recipe data and user administration (WinCC flexible) (Page 118)
Restoring recipe data and user administration (WinCC flexible) (Page 119)
Backing up log data (WinCC flexible) (Page 120)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 117
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.
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
Migrating runtime data (WinCC flexible) (Page 117)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
118 System Manual, 08/2011,
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".
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
Migrating runtime data (WinCC flexible) (Page 117)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 119
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
Migrating runtime data (WinCC flexible) (Page 117)
4.6.1.4 Migrating integrated projects (WinCC flexible)
Migrating 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 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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
120 System Manual, 08/2011,
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
Basics on migration (WinCC flexible) (Page 92) 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 91)
Migrating an integrated project (WinCC flexible) (Page 121)
Basics on migration (WinCC flexible) (Page 92)
Migrating an 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
Basics on migration (WinCC flexible) (Page 92) for additional information.
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 121
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.
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.
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
122 System Manual, 08/2011,
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
Migrating integrated projects (WinCC flexible) (Page 120)
Basics on migration (WinCC flexible) (Page 92)
4.6.1.5 Reference (WinCC flexible)
Migrating 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 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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 123
Internal data types WinCC flexible Internal data types WinCC
Double LReal
String WString
DateTime DateTime
Migrating external data types
See the following pages for how to map the available communication drivers.
See also
Migration (WinCC flexible) (Page 91)
Migrating data types of Allen-Bradley DF1 (WinCC flexible) (Page 125)
Migrating data types of Allen-Bradley DF485 (WinCC flexible) (Page 125)
Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible) (Page 126)
Migrating data types of GE Fanuc SNP (WinCC flexible) (Page 126)
Migrating data types of LG GLOFA GM (WinCC flexible) (Page 127)
Migrating data types of Mitsubishi FX (WinCC flexible) (Page 127)
Migrating data types of Modicon Modbus (WinCC flexible) (Page 129)
Migrating data types of Modicon Modbus TCP/IP (WinCC flexible) (Page 129)
Migrating data types of Omron Hostlink/Multilink (WinCC flexible) (Page 130)
Migrating data types of OPC (WinCC flexible) (Page 130)
Migrating data types of SIMATIC 500/505 DP (WinCC flexible) (Page 131)
Migrating data types of SIMATIC 500/505 serial (WinCC flexible) (Page 131)
Migrating data types of SIMATIC S5 AS511 (WinCC flexible) (Page 132)
Migrating data types of SIMATIC S5 DP (WinCC flexible) (Page 133)
Migrating data types of SIMATIC S7 200 (WinCC flexible) (Page 134)
Migrating data types of SIMATIC S7 300/400 (WinCC flexible) (Page 134)
Migrating data types of Telemecanique Uni-Telway (WinCC flexible) (Page 137)
Migrating data types of Mitsubishi Protocol 4 (WinCC flexible) (Page 128)
Migrating data types of SIMATIC HMI HTTP Protocol (WinCC flexible) (Page 132)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
124 System Manual, 08/2011,
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
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 125
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
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
126 System Manual, 08/2011,
See also
Migrating data types (WinCC flexible) (Page 123)
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
Time UDInt
UDInt UDInt
UInt UInt
USInt USInt
Word UInt
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 127
Data type in WinCC flexible Data type in WinCC
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
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
128 System Manual, 08/2011,
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
Float Float
Int Int
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 129
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
DEC UInt
IEEE Real
LDEC UDInt
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
130 System Manual, 08/2011,
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 131
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
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
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
132 System Manual, 08/2011,
Data type in WinCC flexible Data type in WinCC
KH UInt
KM UInt
KT UDInt
KY UInt
KZ UInt
See also
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 133
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
Migrating data types (WinCC flexible) (Page 123)
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
Time Time
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
134 System Manual, 08/2011,
Data type in WinCC flexible Data type in WinCC
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.
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".
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 135
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 (Professional)
WinCC Professional V11.0 SP1
136 System Manual, 08/2011,
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
Migrating data types (WinCC flexible) (Page 123)
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
Migrating data types (WinCC flexible) (Page 123)
Migrating projects
4.6 Migrating WinCC flexible projects (Professional)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 137
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 Professional V11.0 SP1
138 System Manual, 08/2011,
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 139)
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 Professional V11.0 SP1
System Manual, 08/2011, 139
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 141)
Creating an integrated HMI connection (Page 142)
Re-linking HMI tags (Page 144)
Deleting an unspecified connection (Page 145)
Migrating projects
4.7 Post-editing integrated projects
WinCC Professional V11.0 SP1
140 System Manual, 08/2011,
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 Professional V11.0 SP1
System Manual, 08/2011, 141
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 142)
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 Professional V11.0 SP1
142 System Manual, 08/2011,
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 144)
Migrating projects
4.7 Post-editing integrated projects
WinCC Professional V11.0 SP1
System Manual, 08/2011, 143
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 Professional V11.0 SP1
144 System Manual, 08/2011,
See also
Deleting an unspecified connection (Page 145)
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 Professional V11.0 SP1
System Manual, 08/2011, 145
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 Professional V11.0 SP1
System Manual, 08/2011, 147
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 Professional V11.0 SP1
System Manual, 08/2011, 149
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 Professional V11.0 SP1
150 System Manual, 08/2011,
See also
Starting and exiting the TIA Portal (Page 149)
Resetting the user interface layout (Page 177)
Changing the settings (Page 153)
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 Professional V11.0 SP1
System Manual, 08/2011, 151
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 153)
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 153)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
152 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 149)
Overview of the script and text editor settings (Page 151)
Overview of the print settings (Page 152)
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 155) for the selected task.
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 153
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 Professional V11.0 SP1
154 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 157)
Basics of the work area (Page 160)
Inspector window (Page 169)
Basics on task cards (Page 171)
Details view (Page 172)
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 Professional V11.0 SP1
System Manual, 08/2011, 155
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 157)
Work area (Page 160)
Task cards (Page 171)
Details view (Page 172)
Inspector window (Page 169)
Changing to the Portal view (Page 153)
Editor bar
Status bar with progress display
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
156 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 Professional V11.0 SP1
System Manual, 08/2011, 157
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 Professional V11.0 SP1
158 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 162)
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 Professional V11.0 SP1
System Manual, 08/2011, 159
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 153)
Project view (Page 155)
Basics of the work area (Page 160)
Inspector window (Page 169)
Basics on task cards (Page 171)
Details view (Page 172)
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 Professional V11.0 SP1
160 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 Professional V11.0 SP1
System Manual, 08/2011, 161
See also
Maximizing and minimizing the work area (Page 162)
Splitting the work area (Page 164)
Floating the work area elements (Page 164)
Using grouped elements of the work area (Page 165)
Minimizing and maximizing elements of the work area (Page 167)
Switching between the elements in the work area (Page 167)
Saving a layout of editors and tables (Page 168)
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 Professional V11.0 SP1
162 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 160)
Splitting the work area (Page 164)
Floating the work area elements (Page 164)
Using grouped elements of the work area (Page 165)
Minimizing and maximizing elements of the work area (Page 167)
Switching between the elements in the work area (Page 167)
Saving a layout of editors and tables (Page 168)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 163
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 160)
Maximizing and minimizing the work area (Page 162)
Floating the work area elements (Page 164)
Using grouped elements of the work area (Page 165)
Minimizing and maximizing elements of the work area (Page 167)
Switching between the elements in the work area (Page 167)
Saving a layout of editors and tables (Page 168)
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 Professional V11.0 SP1
164 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 160)
Maximizing and minimizing the work area (Page 162)
Splitting the work area (Page 164)
Using grouped elements of the work area (Page 165)
Minimizing and maximizing elements of the work area (Page 167)
Switching between the elements in the work area (Page 167)
Saving a layout of editors and tables (Page 168)
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 Professional V11.0 SP1
System Manual, 08/2011, 165
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 160)
Maximizing and minimizing the work area (Page 162)
Splitting the work area (Page 164)
Floating the work area elements (Page 164)
Minimizing and maximizing elements of the work area (Page 167)
Switching between the elements in the work area (Page 167)
Saving a layout of editors and tables (Page 168)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
166 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 160)
Maximizing and minimizing the work area (Page 162)
Splitting the work area (Page 164)
Floating the work area elements (Page 164)
Using grouped elements of the work area (Page 165)
Switching between the elements in the work area (Page 167)
Saving a layout of editors and tables (Page 168)
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 Professional V11.0 SP1
System Manual, 08/2011, 167
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 160)
Maximizing and minimizing the work area (Page 162)
Splitting the work area (Page 164)
Floating the work area elements (Page 164)
Using grouped elements of the work area (Page 165)
Minimizing and maximizing elements of the work area (Page 167)
Saving a layout of editors and tables (Page 168)
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 160)
Maximizing and minimizing the work area (Page 162)
Splitting the work area (Page 164)
Floating the work area elements (Page 164)
Using grouped elements of the work area (Page 165)
Minimizing and maximizing elements of the work area (Page 167)
Switching between the elements in the work area (Page 167)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
168 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 Professional V11.0 SP1
System Manual, 08/2011, 169
"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 157)
Basics of the work area (Page 160)
Portal view (Page 153)
Project view (Page 155)
Basics on task cards (Page 171)
Details view (Page 172)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
170 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 157)
Basics of the work area (Page 160)
Inspector window (Page 169)
Basics on task cards (Page 171)
Portal view (Page 153)
Project view (Page 155)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 173
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 Professional V11.0 SP1
174 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 Professional V11.0 SP1
System Manual, 08/2011, 175
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 176)
Showing or hiding additional columns (Page 176)
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 174)
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 Professional V11.0 SP1
176 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 174)
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 149)
Introduction to the TIA Portal
6.1 User interface and operation
WinCC Professional V11.0 SP1
System Manual, 08/2011, 177
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 Professional V11.0 SP1
178 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 Professional V11.0 SP1
System Manual, 08/2011, 179
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 Professional V11.0 SP1
180 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 Professional V11.0 SP1
System Manual, 08/2011, 181
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 Professional V11.0 SP1
182 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 Professional V11.0 SP1
System Manual, 08/2011, 183
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 Professional V11.0 SP1
184 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 188)
Introduction to the TIA Portal
6.2 Help on the information system
WinCC Professional V11.0 SP1
System Manual, 08/2011, 185
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 Professional V11.0 SP1
186 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 Professional V11.0 SP1
System Manual, 08/2011, 187
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 Professional V11.0 SP1
188 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 183)
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 Professional V11.0 SP1
System Manual, 08/2011, 189
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 Professional V11.0 SP1
190 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 192)
Opening projects (Page 192)
Saving projects (Page 194)
Deleting projects (Page 195)
WinCC Professional V11.0 SP1
System Manual, 08/2011, 191
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 191)
Opening projects (Page 192)
Saving projects (Page 194)
Deleting projects (Page 195)
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 Professional V11.0 SP1
192 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 191)
Creating a new project (Page 192)
Saving projects (Page 194)
Deleting projects (Page 195)
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 Professional V11.0 SP1
System Manual, 08/2011, 193
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 191)
Creating a new project (Page 192)
Opening projects (Page 192)
Deleting projects (Page 195)
Editing projects
7.2 Creating and managing projects
WinCC Professional V11.0 SP1
194 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 191)
Creating a new project (Page 192)
Opening projects (Page 192)
Saving projects (Page 194)
Editing projects
7.2 Creating and managing projects
WinCC Professional V11.0 SP1
System Manual, 08/2011, 195
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 Professional V11.0 SP1
196 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 149)
Changing the settings (Page 153)
Application examples for multilanguage projects (Page 202)
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 Professional V11.0 SP1
System Manual, 08/2011, 197
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 Professional V11.0 SP1
198 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 Professional V11.0 SP1
System Manual, 08/2011, 199
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 202)
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 Professional V11.0 SP1
200 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 Professional V11.0 SP1
System Manual, 08/2011, 201
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 202)
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 Professional V11.0 SP1
202 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 196)
Exporting and importing project texts (Page 200)
Translating texts using reference texts (Page 199)
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
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 203
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 204)
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.
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 203)
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
204 System Manual, 08/2011,
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:
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 206)
Loading project data to an accessible device (Page 207)
Downloading project data to a memory card (Page 208)
Uploading project data from a device (Page 208)
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 205
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.
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 2800)
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
206 System Manual, 08/2011,
Result
The selected project data was downloaded to the devices.
See also
General information on loading (Page 205)
Loading project data to an accessible device (Page 207)
Downloading project data to a memory card (Page 208)
Uploading project data from a device (Page 208)
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.
Requirement
The accessible devices are displayed.
See also: Displaying accessible devices (Page 2798)
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 207
See also
General information on loading (Page 205)
Downloading project data to a device (Page 206)
Downloading project data to a memory card (Page 208)
Uploading project data from a device (Page 208)
Downloading project data to a memory card
Requirement
The memory card is displayed.
See also: Accessing memory cards (Page 242)
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 205)
Downloading project data to a device (Page 206)
Loading project data to an accessible device (Page 207)
Uploading project data from a device (Page 208)
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:
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
208 System Manual, 08/2011,
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.
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 2800)
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 2798)
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 209
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 2800)
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.
See also
General information on loading (Page 205)
Downloading project data to a device (Page 206)
Loading project data to an accessible device (Page 207)
Downloading project data to a memory card (Page 208)
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
210 System Manual, 08/2011,
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
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 211
See also
Printing project data (Page 229)
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.
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 211)
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
212 System Manual, 08/2011,
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.
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 218)
Creating a cover page (Page 219)
Editing cover pages and frames (Page 220)
Entering document information (Page 216)
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
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 213
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.
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 229)
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:
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
214 System Manual, 08/2011,
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
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 152)
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
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 215
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.
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
216 System Manual, 08/2011,
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.
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
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 217
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.
See also
Library basics (Page 243)
"Libraries" task card (Page 245)
Global library basics (Page 256)
Using ready-made frames and cover pages (Page 219)
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 220)
Creating a cover page (Page 219)
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
218 System Manual, 08/2011,
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.
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 220)
Creating a frame (Page 218)
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.
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 219
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 217)
Editing cover pages and frames (Page 220)
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 219)
Creating a frame (Page 218)
General operation of the documentation editor (Page 221)
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
220 System Manual, 08/2011,
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 Professional V11.0 SP1
System Manual, 08/2011, 221
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 Professional V11.0 SP1
222 System Manual, 08/2011,
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 Professional V11.0 SP1
System Manual, 08/2011, 223
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 220)
Inserting a background image (Page 224)
Specifying the print area (Page 224)
Inserting placeholders for metadata (Page 225)
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 219)
General operation of the documentation editor (Page 221)
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 Professional V11.0 SP1
224 System Manual, 08/2011,
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 218)
General operation of the documentation editor (Page 221)
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 Professional V11.0 SP1
System Manual, 08/2011, 225
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 221)
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 Professional V11.0 SP1
226 System Manual, 08/2011,
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 228)
Editing projects
7.3 Editing project data
WinCC Professional V11.0 SP1
System Manual, 08/2011, 227
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 Professional V11.0 SP1
228 System Manual, 08/2011,
"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 226)
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 Professional V11.0 SP1
System Manual, 08/2011, 229
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 Professional V11.0 SP1
230 System Manual, 08/2011,
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 211)
Revoking access rights for devices (Page 212)
Printout of project contents (Page 213)
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
Editing projects
7.4 Undoing and redoing actions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 231
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.
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 233)
Redoing an action (Page 234)
Editing projects
7.4 Undoing and redoing actions
WinCC Professional V11.0 SP1
232 System Manual, 08/2011,
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.
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 234)
Editing projects
7.4 Undoing and redoing actions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 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.
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 233)
Editing projects
7.4 Undoing and redoing actions
WinCC Professional 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 Professional 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 Professional 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)
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".
Editing projects
7.6 Working with text lists
WinCC Professional V11.0 SP1
System Manual, 08/2011, 237
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.
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 200)
7.6.2 Creating user-defined text lists
Creating text lists
You can create user-defined text lists for individual devices.
Editing projects
7.6 Working with text lists
WinCC Professional V11.0 SP1
238 System Manual, 08/2011,
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.
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.
Editing projects
7.6 Working with text lists
WinCC Professional V11.0 SP1
System Manual, 08/2011, 239
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".
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 Professional V11.0 SP1
240 System Manual, 08/2011,
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 241)
Accessing memory cards (Page 242)
Displaying properties of memory cards (Page 242)
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 Professional V11.0 SP1
System Manual, 08/2011, 241
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 241)
Accessing memory cards (Page 242)
Displaying properties of memory cards (Page 242)
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 241)
Adding a user-defined card reader (Page 241)
Displaying properties of memory cards (Page 242)
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 Professional V11.0 SP1
242 System Manual, 08/2011,
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 241)
Adding a user-defined card reader (Page 241)
Accessing memory cards (Page 242)
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.
Editing projects
7.8 Using libraries
WinCC Professional V11.0 SP1
System Manual, 08/2011, 243
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.
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.
Editing projects
7.8 Using libraries
WinCC Professional V11.0 SP1
244 System Manual, 08/2011,
See also
Project library basics (Page 248)
Global library basics (Page 256)
"Libraries" task card (Page 245)
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 Professional V11.0 SP1
System Manual, 08/2011, 245
Structure of the "Libraries" task card
The "Libraries" task card consists of the following components:
Device view (Page 277), network view (Page 275), topology view (Page 280)
Inspector window (Page 284)
Hardware catalog (Page 285)
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 Professional V11.0 SP1
274 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 284)
Editing devices and networks
8.1 Configuring devices and networks
WinCC Professional V11.0 SP1
310 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 Professional V11.0 SP1
System Manual, 08/2011, 311
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 Professional V11.0 SP1
312 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 Professional V11.0 SP1
System Manual, 08/2011, 313
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 Professional V11.0 SP1
314 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 Professional V11.0 SP1
System Manual, 08/2011, 315
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 Professional V11.0 SP1
316 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 Professional V11.0 SP1
System Manual, 08/2011, 317
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 Professional V11.0 SP1
318 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 313)
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 Professional V11.0 SP1
System Manual, 08/2011, 319
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 Professional V11.0 SP1
320 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 322)
Editing devices and networks
8.1 Configuring devices and networks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 321
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 Professional V11.0 SP1
322 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 321)
Description of the bus parameters (Page 323)
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 Professional V11.0 SP1
System Manual, 08/2011, 323
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 322)
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 Professional V11.0 SP1
324 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 Professional V11.0 SP1
System Manual, 08/2011, 325
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 Professional V11.0 SP1
326 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 Professional V11.0 SP1
System Manual, 08/2011, 327
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 Professional V11.0 SP1
328 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 Professional V11.0 SP1
System Manual, 08/2011, 329
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 Professional V11.0 SP1
330 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 Professional V11.0 SP1
System Manual, 08/2011, 331
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 Professional V11.0 SP1
332 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 Professional V11.0 SP1
System Manual, 08/2011, 333
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 Professional V11.0 SP1
334 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 Professional V11.0 SP1
System Manual, 08/2011, 335
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 Professional V11.0 SP1
336 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 Professional V11.0 SP1
System Manual, 08/2011, 337
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 Professional V11.0 SP1
338 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 Professional V11.0 SP1
System Manual, 08/2011, 339
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 Professional V11.0 SP1
340 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 Professional V11.0 SP1
System Manual, 08/2011, 341
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 Professional V11.0 SP1
342 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 Professional V11.0 SP1
System Manual, 08/2011, 343
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 Professional V11.0 SP1
344 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 Professional V11.0 SP1
System Manual, 08/2011, 345
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 Professional V11.0 SP1
346 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 Professional V11.0 SP1
System Manual, 08/2011, 347
See also
Creating a new connection graphically (Page 345)
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 Professional V11.0 SP1
348 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 Professional V11.0 SP1
System Manual, 08/2011, 349
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 Professional V11.0 SP1
350 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 Professional V11.0 SP1
System Manual, 08/2011, 351
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 Professional V11.0 SP1
352 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 362)
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 Professional V11.0 SP1
System Manual, 08/2011, 353
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 Professional V11.0 SP1
354 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1258 System Manual, 08/2011,
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
Basics on alarm classes (Page 1247)
Alarm states (Page 1245)
Alarm groups (Page 1253)
Overview of the alarm types (Page 1238)
Overview of the alarm types (Page 1240)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1259
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1260 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1261
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1262 System Manual, 08/2011,
See also
Basics on alarm classes (Page 1247)
Predefined alarm classes (Page 1248)
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 configure up to 256 alarm classes per project.
Requirement
The "HMI alarms" editor is open.
The Inspector window is open.
Procedure
To create an alarm class, proceed as follows:
1. Click the "Alarm Classes" tab.
The predefined custom alarm classes are displayed. A table of the pre-defined alarm
classes is shown below:
1. Double-click "<Add>" in the table.
A new alarm class is created. Each new alarm class 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".
Activate the"Log" check box if you want to log the alarms from this alarm class.
3. Select "Properties > Properties > Acknowledgment" in the Inspector window to define the
acknowledgment model for the alarm class and alarm annunciator.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1263
4. You can edit the default text under "Properties > Properties > Status" in the Inspector
window.
This text indicates the status of an alarm in Runtime.
5. You can also change the default background and foreground colors under "Properties >
Properties > Colors" in the Inspector window.
These settings define how alarms from this alarm class are displayed in Runtime.
Additional settings for alarm classes
Comments in Runtime
The user enters a comment for an incoming alarm in Runtime, as required. Using the buttons
of the alarm view, users can show the comments in the "Historical alarm list" display. You can
configure this function in the alarm class. Enter the user in the "User name" system block.
Assign comments to defined user
To assign the comments to the user logged on, proceed as follows:
1. Select the alarm class.
2. Enable "Properties > Properties > Acknowledgment > Settings > Assign comments to
defined user" in the Inspector window.
Any user can enter the first comment if a comment has yet to be entered.
When the first comment has been entered, all other users have read-only access to it.
Use comment of the incoming alarm
Whenever the status of an alarm changes, for example, from "incoming" to "acknowledged"
status, the alarm is output once again with another status. The user only assigns comments
to one incoming alarm. To include comments for alarm output with the new status, proceed as
follows:
1. Select the alarm class.
2. Enable "Properties > Properties > Acknowledgment > Settings > Use comment of the
incoming alarm" in the Inspector window.
See also
Configuring alarm acknowledgment (Page 1346)
Configuring acknowledgment of the alarm annunciator (Page 1349)
Basics on alarm classes (Page 1247)
Predefined alarm classes (Page 1248)
Using common 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1264 System Manual, 08/2011,
Controller alarms are assigned to common alarm classes. If you work with controller alarms,
common alarm classes are automatically loaded in WinCC.
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1265
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1266 System Manual, 08/2011,
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
Basics on alarm classes (Page 1247)
Configuring Alarm Groups
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1267
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.
See also
Alarm groups (Page 1252)
Configuring alarm groups
Introduction
Create custom alarm groups on the "Alarm Groups" tab of the "HMI alarms" editor. The alarm
groups from alarm classes are already created on a separate tab. You acknowledge alarms
from an alarm group together in Runtime. Configure a corresponding group acknowledgment
button for the alarm group, including an additional button for resetting the acknowledgment bit
of the acknowledgment tag.
Requirements
You have created a project.
The "HMI alarms" editor is open.
The Inspector window is open.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1268 System Manual, 08/2011,
Creating a new alarm group
To create an alarm group, proceed as follows:
1. Click the "Alarm Groups" tab.
The existing alarm groups are displayed.
2. Double-click "<Add>" in the table.
A new alarm group is created.
The properties of the new alarm group are shown in the Inspector window.
3. In the Inspector window, click "Properties > Properties > General" and enter a name for the
alarm group.
4. In the Properties window, click "Properties > Properties > Tags" to specify the following
tags and bits:
Status tag for visualizing the alarm states of the alarm group
Acknowledgment tag for acknowledging an alarm group
Lock tag for visualizing the locked status of an alarm group
Display suppression tag for filtering alarms in Runtime by plant status
Creating a child alarm group
To create a child alarm group, proceed as follows:
1. Click the "Alarm Groups" tab.
2. In the work area or in the detail view, select the alarm groups you want to insert as a child
group.
3. Drag and drop the alarm groups onto another alarm group.
The selected alarm groups become a child group in the hierarchy of this alarm group.
If you want to create a parent group for a hierarchy of alarm groups, drag and drop the entire
hierarchy to this alarm group.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1269
Alternative procedure
1. Click the "Alarm Groups" tab.
2. Select the alarm groups for which you want to create a subgroup.
3. In the cell on the left of the selected row, open the shortcut menu and select "Insert child
element".
A new child alarm group is created.
See also
Alarm Group Basics (Page 1253)
Hierarchical alarm groups (Page 1254)
Tags of an alarm group (Page 1256)
Configuring Alarm Display Suppression (Page 1329)
Tag Bit Assignments (Page 1461)
Configure alarms
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1270 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1271
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.
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1272 System Manual, 08/2011,
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
Analog alarms (Page 1241)
Output of a tag value in the alarm text (Page 1276)
Configuring trigger for alarm acknowledgment (Page 1344)
Configuring reporting of alarms (Page 1340)
Formatting alarm text (Page 1275)
Output of texts from a text list in an alarm (Page 1277)
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1273
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.
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1274 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
Discrete alarms (Page 1241)
Configuring trigger for alarm acknowledgment (Page 1344)
Configuring reporting of alarms (Page 1340)
Output of texts from a text list in an alarm (Page 1277)
Formatting alarm text (Page 1275)
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".
Result
The selected characters are displayed in Runtime with the selected formatting.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1275
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.
See also
Overview of alarm configuration tasks (Page 1260)
Configuring Analog Alarms (Page 1270)
Configuring discrete alarms (Page 1273)
Output of a tag value in the alarm text (Page 1276)
Output of texts from a text list in an alarm (Page 1277)
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1276 System Manual, 08/2011,
WinCC inserts a placeholder for the output field into the alarm text: "<tag: n, [tag 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 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.
See also
Configuring Analog Alarms (Page 1270)
Formatting alarm text (Page 1275)
Output of texts from a text list in an alarm (Page 1277)
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1277
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".
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.
See also
Formatting alarm text (Page 1275)
Configuring Analog Alarms (Page 1270)
Configuring discrete alarms (Page 1273)
Output of a tag value in the alarm text (Page 1276)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1278 System Manual, 08/2011,
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".
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1279
See also
Overview of alarm configuration tasks (Page 1261)
System events (Page 1244)
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1280 System Manual, 08/2011,
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
Controller alarms (Page 1242)
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.
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 1244)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1281
Configure alarms
Configuring alarm blocks
Alarm Text Block Basics
Introduction
An alarm display is made up of alarm text blocks. Each alarm text block corresponds to one
column in the table in the alarm view.
There are three groups of alarm text blocks:
System blocks
System blocks contain system data, such as date, time, alarm number and status.
User text blocks
User text blocks contain the alarm text with the description of the cause of a fault and
additional text with information, for example, the location of a fault.
Parameter blocks
Parameter blocks are used to link the alarms to process values, such as current fill levels,
temperatures or speeds. You can configure up to 10 parameter blocks per alarm.
Configuring Alarm Text Blocks
You enable and edit the alarm text blocks on the "Alarm text blocks" tab. To display alarm text
blocks in an alarm view, select the alarm text blocks to be displayed and logged from the
enabled alarm text blocks in the "Screens" editor.
Properties of Alarm Text Blocks
Text length
The maximum text length of a user text block is 255 characters.
The text length of a parameter block can be configured as follows:
Controller alarms: up to 32 characters
Set the length of the parameter block to 32 characters to ensure that all characters will be
displayed.
Other alarm procedures: up to 255 characters
Note
"Status" system block
The status texts of the alarms are displayed in the "Status" system block. This system
block must be configured so that it is long enough to display the status texts in full.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1282 System Manual, 08/2011,
Flashing
An alarm to be acknowledged or single alarm text blocks can be displayed as flashing in
Runtime. They have to meet the following requirements:
The "Flashing" property must be enabled in the alarm class of the alarm. You configure this
property on the "Alarm classes" tab.
The "Flashing" option is enabled in the "Alarm text block" area under "General" in the
Inspector window for alarm text blocks that should flash.
Alignment
On the "Alarm text blocks" tab, you define whether the alarm text block should be right-justified,
left-justified or centered in an alarm view column.
Format
For certain alarm text blocks, you can choose between different display formats.
See also
Setting up flashing alarm text blocks (Page 1284)
Configuring Alarm Text Blocks
Introduction
An alarm is made up of configured alarm text blocks. You enable the alarm text blocks for an
HMI device on the "Alarm text blocks" tab. Then you select, from the enabled alarm text blocks
for each alarm view, which enabled alarm text blocks are to be displayed and logged.
Requirements
The "HMI alarms" editor is open.
The "Alarm text blocks" tab is selected.
Activating alarm text blocks
1. Select the "System blocks", "User text blocks" or "Parameter blocks" tab for the alarm text
blocks.
2. Select the alarm text block to be displayed on your HMI device.
3. In the Inspector window, select "Properties > Properties > General > Alarm text block >
Enable".
4. Under "Properties > Properties > General > Alarm text block" in the Inspector window,
define the text length and alignment of the alarm text block in the alarm view column.
5. In the Inspector window under "Properties > Properties > Settings > Format", select the
format of the alarm text block. This option is not available for every alarm text block.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1283
Under "Shared data > Text lists" in the project navigation, define the display names for the
user text blocks.
Result
The alarm text blocks are enabled and displayed in the Inspector window of the alarm view in
the "Screens" editor.
Disabling alarm text blocks
1. Select the tabs for the alarm text blocks that you want to disable.
2. Disable the alarm text blocks that you no longer want to use for alarm view and alarm
logging.
3. Repeat the process for every alarm text block that you no longer want to display.
See also
Description of the System Blocks (Page 1414)
Setting up flashing alarm text blocks (Page 1284)
Setting up flashing alarm text blocks
Introduction
Whether or not an alarm text block flashes in Runtime depends on the alarm class of the alarm.
The alarm class determines if the alarms it contains flash when acknowledgment is pending.
Requirements
The alarms blocks are enabled for the HMI device.
The alarms blocks are enabled for the respective alarm.
The alarm is assigned to an alarm class with an acknowledgment model, which specifies
whether or not the contained alarms are to flash.
The alarm text blocks are activated in the alarm view.
The "Alarm text blocks" tab is selected.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1284 System Manual, 08/2011,
Procedure
To configure flashing for alarm text blocks in Runtime, proceed as follows:
1. Select the alarm text block to flash in Runtime from the subordinate tabs on the "Alarm text
blocks" tab.
2. In the Inspector window, select "Properties > Properties > General > Alarm text block >
Flash".
3. Repeat this step for all the alarm text blocks that you want to flash in Runtime.
Result
These alarm text blocks flash in Runtime when the alarm is queued for acknowledgment.
See also
Alarm Text Block Basics (Page 1282)
Configuring Alarm Text Blocks (Page 1283)
Configuring analog alarms
Configuring analog alarms
Introduction
In the "HMI alarms" editor, you can configure analog alarms and define their properties. You
can also configure analog alarms in the "HMI tags" editor.
Requirement
The "HMI alarms" editor is open.
The Inspector window is open.
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.
3. To configure the alarm, select "Properties > Properties >General" in the Inspector window:
You can always change the object name of the alarm.
Select the alarm class and the alarm group, if necessary.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1285
4. To display the CPU number or PLC that sends the alarm, enter this under "Connection to
the PLC". This option is only active if you have enabled the "CPU/PLC number" alarm text
block on the "Alarm text blocks > System blocks" tab.
5. In the Inspector window, select the tag that triggers the alarm under "Properties > Properties
> Trigger". Do not use trigger tags for anything else.
6. To configure the alarm text, select "Properties > Properties > Alarm texts".
To enter the alarm text, select "Alarm text".
To create additional alarm texts, select "Additional texts".
Use the functions of the shortcut menu to format text on a character-by-character basis
and to insert output fields for system or alarm parameters.
Note
You can only enter additional text in the rows that you have enabled as user text blocks
on the "Alarm text blocks" tab.
Defining limits
1. Select the analog alarm to which you want to assign the limits.
2. On the bottom of the work area, click <Add> under "Limits for analog alarm".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1286 System Manual, 08/2011,
3. To use a constant as limit:
In the Inspector window, click the button under "Properties > Properties > Trigger
> Value" and select "Constant".
Enter the required limit value.
4. To use a tag as limit:
In the Inspector window, click the button under "Properties > Properties > Trigger
> Value" and select "HMI tag".
Click the button. The object list opens.
Select the tag.
5. Select the trigger mode in the "Mode" field.
"Equal to limit": The alarm is triggered when the limit is reached.
"Not equal to limit": The alarm is triggered when the limit is no longer reached.
"High limit violation": The alarm is triggered if the limit is exceeded.
"Low limit violation": The alarm is triggered if the limit is undershot.
6. You can create additional limits for the alarm, if necessary.
Note
If the object included in the selection does not yet exist, create it in the object list and
change its properties later.
Note
If a process value fluctuates around the limit, the alarm associated with this fault may be
triggered multiple times. In this case, configure a deadband or delay time.
Optional settings for analog alarms
Setting the delay time
To display an alarm after a delay, proceed as follows:
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1287
1. Select the analog alarm.
2. In the Inspector window, select "Properties > Properties > Trigger".
3. Enter a time period under "Delay". The trigger condition must be fulfilled within this time for
the alarm to be triggered.
Setting the deadband
Proceed as follows to enter a tolerance range for the arrival or departure of an alarm:
1. Select the limit to which the deadband is to be assigned.
2. In the Inspector window, select "Properties > Properties > Trigger".
3. Under "Deadband > Mode", select the change to the alarm status to include in the evaluation
of the deadband.
4. Enter a constant under "Deadband > Value".
5. To define the deadband value as a percentage of the limit, activate the "%" check box.
Saving the status of the alarm
To save the alarm states to a tag, proceed as follows:
1. Select the analog alarm.
2. Under "Properties > Properties > Status" in the Inspector window, select the tag and the
bit that triggers saving of the incoming/outgoing alarm states and the acknowledgment
request.
Setting the priority
To set the priority, proceed as follows:
1. Select the analog alarm.
2. Select a value between 0 and 16 under "Properties > Properties > General > Priority" in
the Inspector window, .
If you filter the alarm view by priority, the alarm with priority 0 will appear at the top.
Creating an info text
1. Select the analog alarm.
2. Select "Properties > Properties > Tooltip" in the Inspector window and enter a 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1288 System Manual, 08/2011,
See also
Configuring acknowledgment of the alarm annunciator (Page 1349)
Configuring reporting of alarms (Page 1342)
Configuring alarm acknowledgment (Page 1346)
Parameter output in the analog alarm (Page 1289)
Configuring loop-in alarms (Page 1302)
Alarms in the "HMI tags" Editor (Page 1303)
Configuring Alarm Display Suppression (Page 1329)
Overview of alarm configuration tasks (Page 1261)
Parameter output in the analog alarm
Introduction
To display system or alarm parameters, insert an appropriate output field in the analog alarm.
"Limit", "Deadband" or "Current Value" can be selected as alarm parameters.
The following system blocks can be selected as system parameters:
User Name
Computer name
Comments
Application Name
Requirement
The "HMI alarms" editor is open.
The analog alarm is selected.
Procedure
To output parameters in alarm texts, proceed as follows:
1. Place the cursor at the required position in the alarm text.
2. To output an alarm parameter, select "Insert parameter output field in analog alarm" from
the shortcut menu.
-OR-
Enable the output of system parameters by selecting "Insert system block output field" from
the shortcut menu.
3. Specify the length, number of decimal places, tolerance, and alignment of the output field
for alarm parameters.
To display leading zeros in the output field, enable "Leading zeros".
4. Click to save your entries.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1289
WinCC inserts a placeholder for the output field into the alarm text:
For alarm parameters: "<tag: n, [###]>" whereby n = text length in characters.
For system parameters; "<name of the system parameter>"
Note
If you test a project using the simulator, the output field values are not output in the alarm
texts.
Deleting parameter 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 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.
Configuring discrete alarms
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.
Requirement
The "HMI alarms" editor is open.
The Inspector window is open.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1290 System Manual, 08/2011,
Procedure
To configure a discrete alarm, proceed as follows:
1. Click the "Discrete alarms" tab.
2. To create a new discrete alarm, double-click on "<Add>" in the table.
A new discrete alarm is created.
3. To configure the alarm, select "Properties > Properties >General" in the Inspector window:
You can always change the object name of the alarm.
Select the alarm class and the alarm group, if necessary.
To display the CPU number or PLC that sends the alarm, enter these in the "Connection"
area. This option is only active if you have enabled the "CPU/PLC number" alarm text
block on the "Alarm text blocks" tab.
4. Select "Properties > Properties > Trigger" in the Inspector window to select the tag and the
bit that triggers the alarm. Note the following information:
Use data types "Bool" "USInt", "UInt", or "UDInt".
Use trigger tag bits only for alarms.
Do not use trigger tags for anything else.
Note
If the object does not yet exist in the selection list, create it directly in the object list and change
its properties later.
Note
The trigger bit is not incremented automatically if you generate a discrete alarm by copying
an alarm text to a new table row. Avoid any redundant use of the trigger bit.
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.
1. Select "Mode" to specify whether to trigger the alarm at a rising or falling edge.
2. To configure the alarm text, select "Properties > Properties > Alarm texts".
To enter the alarm text, select "Alarm text".
To create additional alarm texts, select "Additional texts".
Use the functions of the shortcut menu to format text on a character-by-character basis
and to insert parameter output fields.
Note
You can only enter additional text in the rows that you have enabled as user text blocks
on the "Alarm text blocks" tab.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1291
Result
The discrete alarm is created.
Additional settings for discrete alarms
Creating an info text
To configure a tooltip for the alarm, follow these steps:
1. Select the discrete alarm.
2. Select "Properties > Properties > Info text" in the Inspector window and enter the required
tip.
Enabling discrete alarm parameters
To output process values to an output field in the alarm text, assign corresponding tags to the
parameter blocks. Proceed as follows:
1. Select the alarm.
2. In the Inspector window, click "Properties > Properties > Alarm parameters".
3. Enter a value for the alarm parameter, or select a tag.
4. You can enter several alarm parameters.
Insert the activated process values as selection box into an alarm text, or show them as
parameter block in the alarm view.
Note
To show the process values as parameter blocks, the parameter blocks must be enabled
in the alarm view.
You only edit parameters that you have enabled under "Parameter blocks" on the "Alarm
text blocks" tab.
Saving the alarm status
To save the alarm states to a tag, proceed as follows:
1. Select the discrete alarm.
2. Under "Properties > Properties > Status" in the Inspector window, select the tag and the
bit that triggers saving of the incoming/outgoing alarm states and the acknowledgment
request.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1292 System Manual, 08/2011,
See also
Alarms in the "HMI tags" Editor (Page 1303)
Configuring Alarm Display Suppression (Page 1329)
Configuring alarm acknowledgment (Page 1346)
Configuring acknowledgment of the alarm annunciator (Page 1349)
Configuring loop-in alarms (Page 1302)
Configuring reporting of alarms (Page 1342)
Overview of alarm configuration tasks (Page 1261)
Parameter output in discrete alarms
Introduction
To display system or alarm parameters, insert an appropriate output field in the analog alarm.
You can select the parameters configured in "Properties > Properties > Alarm parameters"
for use as alarm parameters.
The following system blocks can be selected as system parameters:
User Name
Computer name
Comment
Application Name
Requirement
The "HMI alarms" editor is open.
The discrete alarm is selected.
Procedure
To output parameters in alarm texts, proceed as follows:
1. Place the cursor at the required position in the alarm text.
2. To enable the output an alarm parameter, select "Insert parameter output field" from the
shortcut menu.
-OR-
Enable the output of system parameters by selecting "Insert system block output field" from
the shortcut menu.
3. Select the parameter.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1293
4. Moreover, you can specify the following data for alarm parameters:
The tag that provides the parameter values.
Enter the tag you configured for the parameter in "Properties > Properties > Alarm
parameters". If you select a different tag, WinCC updates the parameter configuration
in "Properties > Properties > Alarm parameters" accordingly.
The length, number of decimal places, precision, and alignment of the output field
To display leading zeros in the output field, enable "Leading zeros".
5. Click to save your entries.
Note
If you test a project using the simulator, the output field values are not output in the alarm
texts.
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.
See also
Configuring discrete alarms (Page 1290)
Configuring discrete alarms (Page 1303)
Configuring user alarms
Configuring user alarms
Introduction
User alarms serve to to indicate operator actions in Runtime. User alarms are triggered by
means of alarm number. For other custom applications, configure user alarms that are
triggered in Runtime by means of scripts.
Requirement
The "HMI alarms" editor is open.
The Inspector window is open.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1294 System Manual, 08/2011,
Procedure
To configure user alarms, proceed as follows:
1. Click the "User alarms" tab.
2. To create a new user alarm, double-click "<Add>" in the table.
A new user alarm is created.
3. To configure the alarm, select "Properties > Properties >General" in the Inspector window:
You can always change the object name of the alarm.
Select the alarm class and the alarm group, if necessary.
To display the CPU number or PLC that sends the alarm, enter these in the "Connection"
area. This option is only active if you have enabled the "CPU/PLC number" alarm text
block on the "Alarm text blocks" tab.
4. Click "Alarm texts" in the Inspector window and configure the alarm text.
Enter the alarm text.
To create additional alarm texts, select "Additional texts".
You can insert output fields or or additional text into the alarm text.
Note
You can only enter additional text in the rows that you have enabled as user text blocks
on the "Alarm text blocks" tab.
Result
The user alarm is created.
Additional settings for user alarms
Creating a tooltip
To configure a tooltip for the alarm, follow these steps:
1. Select the user alarm.
2. Select "Properties > Properties > Tooltip" in the Inspector window and enter your text.
Enabling user alarm parameters
To output process values to an output field in the alarm text, assign corresponding tags to the
parameter blocks. Proceed as follows:
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1295
1. Select the alarm.
2. In the Inspector window, click "Properties > Properties > Alarm parameters".
3. You can enter several alarm parameters.
Insert the activated process values as selection box into an alarm text, or show them as
parameter block in the alarm view.
Note
To show the process values as parameter blocks, the parameter blocks must be enabled
in the alarm view.
You only edit parameters that you have enabled under "Parameter blocks" on the "Alarm
text blocks" tab.
Saving the alarm status
To save the alarm states to a tag, proceed as follows:
1. Select the user alarm.
2. Select "Properties > Properties > Status" in the Inspector window and select the tag and
the bit that triggers saving of the incoming/outgoing alarm states and the acknowledgment
request.
Configuring event-driven tasks
To configure event-driven tasks, proceed as follows:
1. Select the user alarm.
2. Select "Properties > Events" in the Inspector window and configure a new function list for
the relevant event.
See also
Configuring acknowledgment (Page 1346)
Configuring alarm blocks (Page 1282)
Configuring Alarm Display Suppression (Page 1329)
Configuring alarm acknowledgment (Page 1346)
Configuring acknowledgment of the alarm annunciator (Page 1349)
Parameter output in user alarms
Introduction
To display system or alarm parameters, insert an appropriate output field in the user alarm.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1296 System Manual, 08/2011,
You can select the parameters configured in "Properties > Properties > Alarm parameters"
for use as alarm parameters.
The following system blocks can be selected as system parameters:
User Name
Computer name
Comment
Application Name
Requirement
The "HMI alarms" editor is open.
The user alarm is selected.
Procedure
To output parameters in alarm texts, proceed as follows:
1. Place the cursor at the required position in the alarm text.
2. To enable the output an alarm parameter, select "Insert parameter output field" from the
shortcut menu.
-OR-
Enable the output of system parameters by selecting "Insert system block output field" from
the shortcut menu.
3. Select the parameter.
4. Moreover, you can specify the following data for alarm parameters:
The tag that provides the parameter values.
Enter the tag you configured for the parameter in "Properties > Properties > Alarm
parameters". If you select a different tag, WinCC updates the parameter configuration
in "Properties > Properties > Alarm parameters" accordingly.
The length, number of decimal places, precision, and alignment of the output field
To display leading zeros in the output field, enable "Leading zeros".
5. Click to save your entries.
Note
If you test a project using the simulator, the output field values are not output in the alarm
texts.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1297
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.
Configuring alarm text
Introduction
The alarm text for an alarm is made up of the alarm text, additional texts and output fields. The
alarm text and additional texts are user text blocks. You can use up to 10 user text blocks for
an alarm.
Each alarm text contains up to 255 characters and any number of output fields.
Requirements
The "HMI alarms" editor is open.
You have enabled user text blocks on the "Alarm text blocks" tab.
An alarm has been created.
Procedure
Proceed as follows to assign additional user text blocks to the alarm text for an alarm:
1. Select the alarm that you want to edit on the relevant tab.
2. To enter the alarm text, select "Properties > Properties > Alarm text" in the Inspector
window.
3. You can also add output fields to the alarm text.
4. To enter additional alarm texts, select "Properties > Properties > Alarm text > Additional
text" in the Inspector window.
Enter more additional texts according to which user text blocks you enabled under "User
text blocks" on the "Alarm text blocks" tab.
Note
Use the scroll buttons to view text that is not fully visible in the text box. The additional
text lines are displayed.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1298 System Manual, 08/2011,
Result
You have configured the alarm text with additional texts for this alarm. To display it in Runtime,
enable these user text blocks in an alarm view.
See also
Configuring analog alarms (Page 1285)
Configuring discrete alarms (Page 1290)
Editing system events
Introduction
System events can only be changed to a limited extent. You cannot delete or create new
system events.
Requirements
You have imported the system events.
The "HMI alarms" editor is open.
Procedure
To configure system events, proceed as follows:
1. Click the "System events" tab.
2. Select the system event that you want to edit.
3. Change the editable properties in the Inspector window.
4. Select the system event that you want to edit.
5. Change the editable properties in the Inspector window.
Configuring event-driven tasks
To configure event-driven tasks, proceed as follows:
To configure a function list for the relevant event, select "Properties > Events".
Editing controller alarms
Introduction
Controller alarms are configured in STEP 7. Controller alarms are available in WinCC running
in a STEP 7 environment.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1299
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.
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
Controller alarms (Page 1242)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1300 System Manual, 08/2011,
Configuring Operator Input Alarms for an Alarm View
Introduction
Operator input alarms for the alarm view are preconfigured system alarms. Manage system
alarms using the "HMI alarms" editor.In the "Screens" editor, configure the trigger conditions
for operator input alarms for the alarm view.
Requirement
You have imported the system alarms from the HMI device.
The "Screens" editor is open.
An "Alarm view" object has been created.
Alarm text blocks are activated in the "HMI alarms" editor.
Procedure
To configure operator input alarms for an alarm view, proceed as follows:
1. Select the alarm view.
2. In the Inspector window, click "Properties > Properties > Operator input alarms".
3. Activate the operator action at the alarm view for which an operator input alarm is to be
output.
The alarm number of the preconfigured operator input alarm for this operator action is
displayed in the "Alarm number" output field.
4. To output another alarm for this operator action, enter the alarm number of this alarm.
5. To specify the columns to display in the operator input alarm, click the button in "Alarm
text blocks".
A dialog opens.
6. To enable the alarm text blocks to be output with the operator input alarm, select "Alarm
text blocks".
7. Select "Alarm group of operator input alarm" to specify the alarm text blocks to be output
with the system alarm.Under "Output as", define whether the content of the alarm text block
should be output as text or as a value.
Note
You will find the system alarm and its alarm number on the "System alarms" tab in the
"HMI alarms" editor.
Result
The configured operator input alarm is displayed when the user performs an action on the
alarm view in Runtime.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1301
Configuring loop-in alarms
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".
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1302 System Manual, 08/2011,
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
Using the Alarm Window, Alarm View (Page 1384)
Basic alarm view, using the alarm window (Page 1387)
Alarm view (Page 1393)
Configuring analog alarms (Page 1285)
Configuring discrete alarms (Page 1290)
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1303
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.
Result
The configured discrete alarms are created in the "HMI tags" editor and displayed in the "HMI
alarms" and "HMI tags" editors.
See also
Configuring discrete alarms (Page 1273)
Working with Tags (Page 984)
Parameter output in the analog alarm (Page 1289)
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1304 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1305
See also
Working with Tags (Page 984)
Parameter output in the analog alarm (Page 1289)
Configuring analog alarms (Page 1285)
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1306 System Manual, 08/2011,
See also
Configuring the alarm view (Page 1307)
Configuring the alarm view (Page 1320)
Reporting Alarms (Page 1340)
Configuring the alarm view
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1307
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
System functions for alarms (Page 1410)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1308 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1309
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1310 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1311
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 1262)
Configuring an alarm window (Page 1314)
Displaying Logged Alarms (Page 1319)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1312 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1313
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1314 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 1309)
Creating alarm classes (Page 1262)
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1315
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1316 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1317
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1318 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
See also
I/O field (Page 840)
Working with Tags (Page 984)
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1319
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.
See also
Configuring an alarm view for active alarms (Page 1309)
Configuring the alarm view
Displaying alarms
Options for displaying alarms on the HMI device
WinCC offers the following options for displaying alarms on the HMI device:
Alarm view for pending and outgoing alarms
The alarm view is configured for a screen. More than one alarm can be displayed
simultaneously, depending on the configured size. You can also configure multiple alarm
views with different contents and in different screens. Use the "Historical alarm list (short-
term)" and "Historical alarm list (long-term)" views to display outgoing alarms.
Alarm view for statistical values
The "Alarm statistics" view of the alarm view displays statistical information, such as the
frequency and display duration of alarms.
Status tag of an alarm group
You can visualize the changing alarm states of an alarm group using the status tag of that
alarm group. You can customize the display in the "Screens" editor.
Additional signals
Alarm annunciator
In addition to the alarm view, WinCC displays an alarm in the form of a visual or audible
alarm in the plant. The alarm annunciator may be a hooter, or a warning lamp.
System functions and scripts
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.
To be able to control the alarm view other than via the toolbar, use system functions for
alarms in WinCC.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1320 System Manual, 08/2011,
See also
Bit assignment of status tag (Page 1461)
Tags of an alarm group (Page 1256)
System functions for alarms (Page 1410)
Configuring an alarm view
Introduction
Current, and logged alarms are displayed in the alarm view. Alarms from all alarm classes are
displayed in an alarm view, if necessary. Configure the criteria for alarm filtering.
Requirement
A screen is open.
The "Tools" task card is open.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1321
Procedure
To configure an alarm view, proceed as follows:
1. Insert an "Alarm view" object from the "Tools" task card into the screen.
2. Select the alarm view and click "Properties > Properties > General" in the Inspector window.
Under "Display > Type", select the type of alarms you want to display as default in the
alarm view.
Under "Display > Display" select which alarms are displayed. This shows or hides the
alarms to be suppressed in the display.
Double-click of the operator on an alarm in Runtime starts a specific action. Specify this
action under "Display > Double-click". If you want to trigger the Loop-In-Alarm not only
using the "Loop-In-Alarm" button, select "Loop-In-Alarm".
Select the required time base under "Time base".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1322 System Manual, 08/2011,
3. To specify the appearance of the alarm view, select "Properties > Properties > Appearance"
in the Inspector window.
4. To specify the appearance of the headers, content, and table grid in the alarm view, select
"Properties > Properties > Table" .
To specify the visualization of selected alarms in Runtime, select "Properties >
Properties > Table > Table - Select".
To specify the sorting method for alarms in Runtime, select "Properties > Properties >
Table > Table - Sorting".
5. To specify the sort order of alarms in Runtime, select "Properties > Properties > Alarm list" .
Enabling alarm text blocks for the alarm view
1. Select "Properties > Properties > Alarm text blocks > Inherit project settings for alarm text
blocks" in the Inspector window to specify whether to apply the settings from the "Alarm
text blocks" tab in the "HMI alarms" editor to this alarm view.
2. Select "Properties > Properties > Alarm text blocks" to enable the alarm text blocks to be
visualized in the alarm view. You can specify the following properties for each alarm text
block:
Name
Layout of the header
Layout of content
Alignment
Length
Format
Flashing
Configuring the toolbar and status bar in the alarm view
1. To specify the the toolbar layout, select "Properties > Properties > Toolbar > Toolbar -
General".
2. Select "Properties > Properties > Toolbar > Toolbar - Operator input elements", to enable
the operator input elements to be included in the alarm view toolbar.
3. To specify the the status bar layout, select "Properties > Properties > Status bar > Status
bar - General".
4. Select "Properties > Properties > Toolbar > Toolbar - Operator input elements", to enable
the operator input elements to be included in the status bar of the alarm view.
Result
Alarms of various alarm classes are output in the alarm view during runtime. To change the
view in Runtime, click the configured buttons on the alarm view toolbar.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1323
See also
Configuring filters in the alarm view (Page 1324)
Configuring Alarm Statistics (Page 1326)
Configuring filters in the alarm view
Introduction
WinCC supports the configuration of different filters for the alarm view:
Standard filters
The operator cannot access standard filters in Runtime. You can copy configured standard
filter for use in other alarm views.
Custom filters
The operator can change the custom filter in Runtime. You are using custom filter only in
a single alarm view.
Requirement
The screen with the configured alarm view is open in the "Screens" editor.
The Inspector window is open.
Procedure
1. Select the alarm view and click "Properties > Properties > Filter > Alarm filter" in the
Inspector window.
2. To configure a custom filter, click on the "Custom" tab.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1324 System Manual, 08/2011,
3. Define one or more filters. For each filter, specify one or more filter criteria under
"Expression" with condition and value.
4. To configure a standard filter, select the "Standard" tab.
You can configure several standard filters and activate these for the respective alarm view.
5. Enter the name for the standard filter and a comment.
6. To configure the filter, select the criteria, conditions, and the value for the standard filter in
the "Filter" dialog.
Filter by process values
You cannot enter text as the criterion for a process value. To filter by the text of a parameter
block, or by the process tag represented, proceed as follows:
1. Insert this process value as the alarm text for a user text block in an alarm.
2. In Runtime, filter the alarms by the text in the "Alarm text" alarm text block using the
button.
In multi-user systems, make sure that contents displayed in the "Specify selection" dialog on
a client have the same names on all servers.
Filter by time
When filtering by time, the start and stop values are not adjusted automatically when the time
base of the alarm view is changed.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1325
Example
At a PC location with time zone "UTC + 1h", the alarm view has the "Local time zone" time
base. You should filter by the time 10:00 to 11:00. Convert the time base to "UTC". To display
the same alarms as before, change the start or stop value of the filter to 9:00 and 10:00.
See also
SQL Statements for Filtering the Alarm View (Page 1417)
Configuring Alarm Statistics
Introduction
The alarm statistics contain statistical calculations for the logged alarms in the alarm view. The
alarm statistics also contain a selection of the configured alarm text blocks. If the contents are
dynamic, the alarm text blocks display the data for the last incoming alarm. You can compile
the alarm statistics columns individually.
The alarm statistics contain the following statistical calculations:
Alarm rate
The system counts how often an alarm with the status "Incoming" is included in the log. If
the alarm number does not occur, this alarm number is not included in the statistics.
Total display time of an alarm in seconds.
The following periods between alarm states are available as calculation variables:
"Incoming/Incoming"(sum +/+),
"Incoming/Outgoing"(sum +/-)
"Incoming/Initial acknowledgment"(sum +/*1)
"Incoming/second acknowledgment"(sum +/*2)
Each type of calculation can be represented in a column in the alarm statistics.
Average display time of an alarm in seconds
The following periods between alarm states are available as calculation variables:
"Incoming/Incoming"(mean value +/+),
"Incoming/Outgoing"(mean value +/-)
"Incoming/Initial acknowledgment"((mean value +/*1)
"Incoming/second acknowledgment"((mean value +/*2)
There is one column in the alarm statistics for each type of calculation.
The calculation of the time of acknowledgment includes the "Acknowledged" alarm status. This
status includes both an emergency acknowledgment and an acknowledgment by the PLC.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1326 System Manual, 08/2011,
Requirement
The "Screens" editor is open.
You have created a screen with an alarm view.
Configuring the alarm statistics functions
Proceed as follows to configure the functions of the alarm statistics:
1. Select the alarm view and click "Properties > Properties > Alarm statistics - General" in the
Inspector window.
2. To limit the calculation period, activate the "Use time range" option under "Time range".
Specify the frequency.
3. To define the maximum number of alarms to be processed in the alarm statistics, enter a
value at "Data records > Maximum number of data records".
This setting requires the following conditions to be met:
The number of alarms in the calculation period exceeeds the configured "Maximum
number of data records which can be read".
The calculation period is not configured.
4. To output a warning when this number is exceeded, activate the "Warning when limit is
reached" option.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1327
Setting up the alarm statistics
Proceed as follows to set the columns of the alarm statistics:
1. Select the alarm view and click "Properties > Properties > Alarm statistics - Elements" in
the Inspector window.
2. In the table, enable the alarm statistics columns that are to be displayed in Runtime.
3. To specify the arrangement of columns in the alarm view in Runtime, select a row in the
Inspector window. Move the row to the selected location using the and buttons.
The columns of the alarm statistics are displayed in Runtime in the same order as the rows
are arranged in the Inspector window.
4. Specify the sort direction for each row in "Sort by".
5. Specify the sort order in "Sort order" by assigning values from 1 to 4.
Note
The sort function is only active if the alarm statistics view contains no more than four
columns.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1328 System Manual, 08/2011,
Result
In Runtime, the operator clicks the button in the alarm view to view the "Alarm statistics".
Note
Alarms that have the "acknowledged" and "outgoing" states are only used for the calculation
if a suitable alarm with "incoming" state was found in the amount of the result .
If you acknowledge an alarm with single acknowledgment or dual acknowledgment only once,
the "Incoming/First Acknowledgement" and "Outgoing/Second Acknowledgement" alarm
states are used for the statistical calculation.
If there is an alarm pending at the PLC and Runtime is disabled and enabled several times,
the alarm is entered several times in the log with "incoming" status. The alarm will also be
included multiple times in the evaluation.
Configuring Alarm Display Suppression
Overview of Alarm Display Suppression
Introduction
Suppress the display of alarms to avoid an excessive burden of information for the plant
operator. If only selected alarms are shown, the operator will concentrate his attention on
essential alarms.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1329
Methods for suppressing alarm displays
There are two options for suppressing the display of incoming alarms:
Automatic display suppression
The alarms are displayed in line with the specific plant status. You can enter these plant
states as display suppression masks in each alarm. The design engineer specifies the
values for the plant states.
To transfer the current plant status to the alarm system, create an alarm group with a display
suppression tag. This display suppression tag returns the value of the plant states.
Assign this alarm group the alarms that the system does not display in Runtime at specific
plant states.
Example:
In the "Shutdown" plant status you want to suppress the display of alarms that normally
occur in this status. The "Online connection to the PLC was dropped" alarm will only not
be displayed during "Shutdown".
Note
If you have specified a display suppression mask for an alarm that is not assigned to an
alarm group, this alarm will not be suppressed in Runtime.
Alarms with display suppression masks that are not allocated to any alarm group will not
be suppressed in Runtime. To suppress the display of specific alarms in Runtime, you
always have to assign these to an alarm group.
Note
You only use display suppression tags only for custom alarm groups.
Manual display suppression
To suppress the display of an alarm in Runtime, the operator can click the button in
the alarm view.
He can view the alarm once again by clicking the button.
The system displays the alarms again after a configurable time.
To enable the reporting of manual display suppression, configure a corresponding user
alarm that is triggered when the display is suppressed manually. Configure this user alarm
in the alarm view as an operator input alarm for the "Suppress" operator action.
Properties of alarms whose display is suppressed
The following applies to alarms whose display is suppressed:
In the following alarm view display modes, you can use the following buttons to show the
alarms again:
Display "Current alarms"
Display "Historical alarm list" (short-term)
Display "Historical alarm list" (long-term)
The alarms are recorded and displayed under the "Hidden alarms" display.
The alarms are also logged.
If an alarm annunciator is set up for these alarms, it will not be triggered.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1330 System Manual, 08/2011,
Manual display suppression
The following properties apply only to alarms whose display is suppressed manually.
The alarms are shown again after a set time.
An alarm that requires acknowledgment is acknowledged by the manual suppression of its
display.
To enable the reporting of manual display suppression, configure a corresponding user
alarm that is triggered when the display is suppressed manually.
Automatic display suppression
The following properties apply only to alarms whose display is suppressed automatically.
The display suppression does not trigger an operator input alarm.
The PLC acknowledges alarms that require acknowledgment.
In the time while alarms requiring acknowledgment are suppressed, the PLC acknowledges
the outgoing alarms. If an alarm does not have the "Outgoing" status, the PLC
acknowledges it immediately.
WARNING
With automatic display suppression, alarms requiring acknowledgment no longer have to
be acknowledged. You should therefore only use automatic display suppression for
alarms that do not require operator actions during the configured plant states.
Interaction
The two methods of suppressing alarm displays interact as follows:
When an alarm is automatically suppressed, use the and buttons to show and
hide the alarm as required.
You have manually suppressed the display of an alarm using the button.
When the plant status changes and the conditions for automatic suppression of this alarm
display are not fulfilled, the alarm is displayed once more.
The time defined as the display suppression duration must not have elapsed.
You have suppressed the alarm by pressing the button. The status that was defined
for automatic display suppression using the display suppression tags occurs. After the
specified display suppression timeout was triggered, the alarm nevertheless remains
suppressed.
See also
Tags of an alarm group (Page 1256)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1331
Setting the Display Suppression Timeout
Introduction
You can set the time after which manually-suppressed alarms should be automatically
displayed once more in the alarm settings.
Requirements
The project navigator is open.
Procedure
To set the alarm display suppression timeout, follow these steps:
1. Double-click "Runtime settings > Alarms" in the project navigation.
The alarm settings open.
2. Select "General > Display suppression timeout" to configure the period during which a
manually suppressed alarm remains hidden.
30 minutes are preset.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1332 System Manual, 08/2011,
See also
Configuring Automatic Display Suppression (Page 1333)
Configuring Automatic Display Suppression
Introduction
With automatic display suppression, the alarm is displayed in relation to the status of the PLC.
You define the plant status that causes an alarm to be hidden. Configure automatic display
suppression using the "HMI alarms" editor.You will need to create an alarm group with a
displace suppression tag. In the alarm, you assign the plant statuses using the display
suppression mask. The display suppression tag must assume the value of the display
suppression mask for an alarm so that it is not displayed in Runtime.
Requirements
The "HMI alarms" editor is open.
The "Alarm groups" tab is selected.
Alarms are set up.
The display suppression tag must exist.
Creasing an alarm group for display suppression
1. Double-click "Add" in the table.
A new alarm group is created.
2. Enter a name for the new alarm group.
3. Select the display suppression tag under "Tags" in the Inspector window.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1333
Creating a display suppression mask for the alarm
1. Select the alarm.
2. To select the alarm group for which you created the alarm suppression tag, select
"Properties > Properties > General" in the Inspector window.
3. To enter the display suppression mask, select "Properties > Properties > Display
suppression" in the Inspector window.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1334 System Manual, 08/2011,
Result
The alarm is hidden when the value set in the display suppression mask is activated at the
display suppression tag.This means that the alarm is hidden when the plant is in the specified
status.
Note
Alarms with display suppression masks that are not allocated to any alarm group will not be
suppressed in Runtime. You should therefore always assign alarms to an alarm group if you
want to suppress them.
If an alarm is hidden, it can be shown once more in Runtime by clicking the button.
See also
Setting the Display Suppression Timeout (Page 1332)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1335
Configuring Alarm Alerts
Introduction
In addition to the alarm view, WinCC also supports alarm indication in the plant by means of
visual or audible signals.The alarm annunciator can be a horn, or a warning lamp.
Requirements
The "HMI alarms" editor is open.
Alarms are set up.
The Inspector window is open.
Procedure
To configure an alarm annunciator, proceed as follows:
Select the alarm you want to indicate using an alarm annunciator.
In the Inspector window, select "Properties > Alarm annunciator".
See also
Configuring acknowledgment of the alarm annunciator (Page 1349)
Displaying logged alarms
Introduction
An alarm view displays logged alarms in Runtime according to the configuration. The alarm
view displays alarms from the log in the "Historical alarm list" (short-term) or "Historical alarm
list" (long-term) display. The "Historical alarm list" (short-term) also displays the current alarms.
Requirement
The logged alarms are located on the local log server.
The screen with the configured alarm view is open.
The Inspector window is open.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1336 System Manual, 08/2011,
Procedure
Proceed as follows to configure an "Historical alarm list" (short-term) or "Historical alarm list"
(long-term) display:
1. Select the alarm view.
2. Select "Properties > Properties > General > Active list > "Historical alarm list" (short-term)
or "Historical alarm list" (long-term) in the Inspector window.
3. Configure the alarm view similar to an alarm view for active alarms.
Result
In Runtime, you can view logged alarms using the "Historical alarm list" (short-term) or
"Historical alarm list" (long-term) buttons. To visualize only alarms of the "Errors" alarm
class or alarms at certain plant areas, you can filter or sort the logged alarms.
Note
In the "Historical alarm list" (short-term) display, the new incoming alarms are updated
immediately. In the "Historical alarm list" (long-term), on the other hand, they are not. You
cannot enter or view comments in the "Historical alarm list" (short-term). Comments can only
be entered in the "Historical alarm list" (long-term).
Configuring alarm export
Introduction
To export alarms to a "*.csv" file in Runtime, the operator clicks on the button in the alarm
view.You can configure this function in the alarm view in the "Screens" editor.
Requirements
The screen with the configured alarm view is open.
The Inspector window is open.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1337
Procedure
To configure the export of alarms, proceed as follows:
1. Select the alarm view and configure data export by selecting "Properties > Properties >
Data export" in the Inspector window.
You can specify a custom file name and folder.
At "Scope", specify the data to be exported from the alarm view.
at "CSV format", specify the separator to use in the ".csv" file.
2. Select "Operator input in Runtime" to configure the function of the button in Runtime:
Select "Display dialog" to open the "Default settings data export" dialog.
To export the data directly to the specified export file, disable "Display dialog".
3. Additionally, select "Operator input in Runtime" to specify whether or not the operator is
allowed to rename the file and/or change the folder in Runtime.
Configuring alarm evaluation in Runtime
Introduction
To enable evaluation of the alarms in Runtime, assign a custom C function to the "Status
changed" event of an alarm. Edit the function to suit your requirements for evaluation in
Runtime.
Requirement
The "HMI alarms" editor is open.
A custom function for reading the data has been created.
This function must contain a pointer to a string whose data is mapped by scanf to the
"MSG_RTDATA_STRUCT" structure.
Procedure
To configure the evaluation of an alarm in Runtime, proceed as follows:
1. Select the alarm.
2. In the Inspector window, select "Properties > Events > Status changed".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1338 System Manual, 08/2011,
3. Select the custom function for reading the data.
The alarm data is read in Runtime. Alarm data includes,for example, the alarm number,
time stamp, and alarm state.
4. In the "Scripts" editor, configure evaluation of the alarm data within the function.
Result
When the alarm state changes, the alarm data is read in Runtime and evaluated according to
your configuration.
Example
Use the following, user-defined function "state" to read the status of alarms, for example:
Void state (MSG_RTDATA_STRUCT Parameter)
DWORD state;
state = Parameter.dwMsgState;
printf("Status: %d\r\n", state);
See also
Working with Function Lists (Page 1748)
Working with customized functions (Page 1753)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1339
Reporting Alarms
Configuring reporting of 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1340 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1341
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 1609)
Principles for preparation of reports (Page 1609)
Create a report (Page 1616)
Report output in Runtime Advanced (Page 1631)
Alarm report (Page 1671)
Configuring reporting of alarms
Overview
WinCC logs all system alarms as required.The following options are available:
Output the current display in an alarm view
You can print out a system report. You can also create a custom report, if necessary.In the
print job, specify the print scope, page area, printer, or target file.
Output an alarm sequence report
In Runtime, every alarm is continuously output at a printer.
Requirements
The "Screens" editor is open.
Alarms are configured.
You configured an alarm view with "Print current view" button.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1342 System Manual, 08/2011,
Procedure
To configure the outputting of the current display in an alarm view using your own report,
proceed as follows:
1. Select the required alarm view.
2. To select the print job, select "Properties > Properties > General > Print > Print job" in the
Inspector window.
The default print job is the system print job. You can also select a customized print job, or
a modified system print job.
Result
If the user clicks the button in Runtime, the selected report with the alarms currently
displayed in the alarm view is output to the printer.
Note
Printer settings
Configure the printer in the HMI device's Control Panel. The settings will depend on which
operating system is used on the HMI device.
For more detailed information, refer to the operating instructions for your HMI device.
See also
Working with reports (Page 1609)
9.3.2.4 Configuring acknowledgment
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1343
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1344 System Manual, 08/2011,
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".
See also
Working with screens (Page 637)
Working with Function Lists (Page 1748)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1345
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.
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 acknowledgment
Configuring alarm acknowledgment
Introduction
The alarm classes define how the alarms from an alarm class are to be acknowledged. When
you assign an alarm to an alarm class, you define the acknowledgement model for that alarm.
Requirements
The "HMI alarms" editor is open.
The required alarm class has been created.
The required alarm has been created.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1346 System Manual, 08/2011,
Procedure
To configure the acknowledgement of an alarm, follow these steps:
1. In the "HMI alarms" editor, click the "Alarm class" tab and select the alarm class.
2. To select the acknowledgment model, select "Properties > Properties > Acknowledgment
> Settings" in the Inspector window.
If you enable "Assign comment to defined user", this Runtime user writes a comment
on the alarm acknowledgment that is written to the log file alongside with the alarm.
If you enable "Use comment of the incoming alarm", the same comment is attached to
each status change of this alarm as the one assigned for the "incoming" alarm event.
3. In the "HMI alarms" editor, select the alarm.
4. Select "Properties > Properties > General" in the Inspector window to select the alarm class
of the alarm.
5. Select "Properties > Properties > Acknowledgement > Settings" in the Inspector window to
specify the acknowledgment tag to which the alarm acknowledgment is saved, including
the bit set for this purpose.
6. To exclude the alarm from the group acknowledgment of the alarm view, enable "Single
acknowledgment".
Acknowledging an alarm via a system function
1. In the "HMI alarms" editor, select the alarm.
2. In the Inspector window, click "Properties > Events > Incoming".
The function list opens.
3. In the "Function list" dialog, assign the "SetBit" system function to the "Incoming" event.
4. Enter the acknowledgment tag of the "BOOL" data type as the "Tag (In/Out)" parameter.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1347
Configuring display and control objects for alarm acknowledgment
1. Select the button or function key.
2. Assign the "AcknowledgeAlarm" system function to the "Click" event.
See also
Working with screens (Page 637)
Working with Function Lists (Page 1748)
Configuring alarm group acknowledgment
Introduction
You acknowledge an alarm group using the acknowledgment tag. To set and reset the
acknowledgment bit, configure a display and operating element.
Requirements
The "HMI alarms" editor is open.
You have created the alarm groups.
The required alarm has been created.
Procedure
To configure the acknowledgement of an alarm group, follow these steps:
1. In the "HMI alarms" editor, select the alarm.
2. Under "Properties > Properties > General" in the Inspector window, select the alarm group
to which the alarm belongs.
3. Click the "Alarm groups" tab in the "HMI alarms" editor.
4. Select the alarm group.
5. Under "Properties > Properties > Tags > Settings" in the Inspector window, select the
acknowledgment tag and acknowledgment bit.
6. Open the "Screens" editor and configure a button that sets the acknowledgment bit in
Runtime for the acknowledgment tag.
Result
The user monitors the alarms for a given function together in Runtime. If a user identifies the
cause of a fault, then he or she can acknowledge all alarms for this function using the
configured operator action.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1348 System Manual, 08/2011,
Configuring acknowledgment of the alarm annunciator
Introduction
In addition to the alarm view, WinCC also supports alarm indication in the plant by means of
visual or audible signals.The alarm annunciator can be a horn, or a warning lamp.You can
acknowledge the alarm annunciator in the following ways:
Using the button in the alarm view
This "Acknowledge alarm annunciator" button must be configured in the alarm view. The
button is always active, even if another option for acknowledging the alarm annunciator
has been enabled.
Using a single acknowledgment
You acknowledge the alarm annunciator with the alarm that triggered the alarm
annunciator.The operator acknowledges an individual alarm by clicking the "Single
Acknowledgment" button in the alarm view.
Using a tag
To acknowledge the alarm annunciator, e.g. with a button, use this option.
Requirements
The "HMI alarms" editor is open.
The required alarm class has been created.
The required alarm has been created, and assigned to the alarm class.
Procedure
To configure the acknowledgment of an alarm annunciator, proceed as follows:
1. Click the "Alarm classes" tab in the "HMI alarms" editor.
2. Select the required alarm class.
3. In the Inspector window, select "Properties > Properties > Acknowledgment > Alarm
annunciator" to specify how to acknowledge the alarm annunciator.
Result
The operator acknowledges the alarm annunciator in Runtime as specified for the alarm class
of this alarm.
Configuring the Group Acknowledgement of Alarms
Introduction
You can use the button in the alarm view to acknowledge all pending, and visible alarms
that must be acknowledged in the alarm view. You can exclude individual alarms from group
acknowledgment.After group acknowledgment was triggered, the excluded alarms are still
pending.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1349
Requirement
A screen is open.
An alarm view has been created.
Procedure
To set up a group acknowledgement, follow these steps:
1. Open the "Screens" editor, and select the relevant alarm view.
2. In the Inspector window, select "Properties Properties > Toolbar - Buttons > Group
acknowledgment."
The button appears in the alarm view. All alarms of an alarm view that are not excluded
from group acknowledgment are acknowledged when the operator actuates this button.
Configuring a single acknowledgement
1. Open the "HMI alarms" editor and select the tab that contains the relevant alarm type.
2. Select the alarm that you want to exclude from the group acknowledgement.
3. Enable "Properties > Properties > Acknowledgment > Single acknowledgment" in the
Inspector window.
When you acknowledge all the alarms in an alarm view using the button, any alarms
for which the "Single acknowledgement" option is enabled will be excluded. The operator
acknowledges alarms with "single acknowledgment" option individually.
Configuring the Resetting of the Acknowledgment Bit for Acknowledgment Tags
Introduction
The operator, or the PLC, resets the acknowledgment bit for acknowledgment tags.The
acknowledgment bit is reset directly in the PLC or in WinCC Runtime via a script, for example.
The acknowledgment bit is not automatically reset.
Resetting of the acknowledgment bit by the PLC
You can use an external tag as an acknowledgment tag to allow the PLC to reset the
acknowledgment bit.
If the alarm is acknowledged in Runtime in WinCC, the defined acknowledgment bit is set in
the PLC. In the PLC, the acknowledgment bit is processed as required before it is reset once
more.
In the PLC, an alarm is triggered by a reusable function block or by functions. In this block the
alarm can also be acknowledged or the acknowledgment bit reset.
Evaluation and resetting of the acknowledgment bit by the PLC has the following advantage:
It is easy to cause the acknowledgement with external signals, such as pushbutton units in the
field.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1350 System Manual, 08/2011,
You can acknowledge externally and via the alarm view. Both methods use the same bit in the
automation system for acknowledgement.
Note
To ensure that the alarm view in WinCC reliably acquires the external acknowledgement in
time, configure the resetting by the automation system with a time delay.
Resetting of the acknowledgment bit by the WinCC
If you want to acknowledge an alarm via the acknowledgment tag only, reset the
acknowledgment bit immediately as soon as it is set.
If you acknowledge an alarm via the alarm view, configure the resetting of the acknowledgment
tags separately.
You can reset the acknowledgment bit in the following ways in WinCC:
Button
You can reset the acknowledgment bit using a button.
System function
Use the "ResetBitInTag" system function. If the acknowledgment bit is set, it will be
immediately reset.
Note
If the acknowledgment tag is of the "BOOL" data type, use the "ResetBit" system function.
Note
If lots of alarms are processed using scripts, this places a heavy load on the work memory.
The acknowledgment bit should therefore ideally be reset by the PLC.
9.3.2.6 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1351
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.
See also
Working with Logs (Page 1468)
9.3.3 Alarm Logging
9.3.3.1 Configuring alarm logging
Basics on alarm logging
Introduction
An alarm log is used to record project alarms.
Note
Alarm logging is not available for every HMI device.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1352 System Manual, 08/2011,
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:
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).
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1353
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1354 System Manual, 08/2011,
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
Working with Logs (Page 1468)
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1355
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1356 System Manual, 08/2011,
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.
Create 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
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1357
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1358 System Manual, 08/2011,
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1359
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1360 System Manual, 08/2011,
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
Logging alarms (Page 1361)
Working with Logs (Page 1468)
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1361
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.
See also
Working with Logs (Page 1468)
Create an alarm log (Page 1357)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1362 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1363
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.
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".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1364 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1365
Result
The log data of the log is assigned a checksum in runtime.
See also
GMP-compliant configuration (Page 2413)
Enabling GMP compliant configuration (Page 2416)
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1366 System Manual, 08/2011,
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 2416)
Evaluating Audit Trails in AuditViewer (Page 2434)
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1367
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.2 Configuring alarm logging
Basics on alarm logging
Introduction
An alarm log is used to record project alarms.Alarm logs are created by the system. For
example, after an error has occurred, or a limit was exceeded in Runtime, the corresponding
alarm you configured in the "HMI alarms" editor is output in Runtime.Each alarm event is
logged, e.g., the transition of the alarm from "incoming" to "acknowledged" status.
You can store the alarm events in a log database and/or log them to hardcopy in an alarm
report. You can output the alarms stored in the database in Runtime, for example, in an alarm
view.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1368 System Manual, 08/2011,
The logged alarms are stored in a circular log that consists of multiple single segments. The
size of all the segments and of an individual segment is defined under "Alarm log" in the log
settings.
You should configure backups to save the data at regular intervals.
Configuration steps
To log an alarm, follow these configuration steps:
1. Configuring "Log settings"
You define the settings for the alarm logging in the log settings.
2. Enable alarm logging
You specify that alarms of particular alarm classes will be logged.
3. Assigning an alarm to a loggable alarm class
Content of the alarm log
The alarm logs are used to store all alarm data, including configuration data. You can read all
alarm properties from the log files, e.g. the alarm class, the timestamp, and the alarm texts.A
new log segment with the new configuration data is generated whenever you edit configuration
data of an alarm. This function prevents any change from having an influence on alarms logged
previously.
The possible number of logged alarms depends on the server used.
Note
The time stamp of a logged alarm is always specified in standard UTC format (Universal Time
Coordinated).
As alarm configuration is language-specific, the logs contain a configuration data table for each
language configured.
Storage media and location
Log data are stored in a database. You can further process the saved data in other programs
for analysis purposes, for example.
Backup for log segments
Take backups of your log segments to ensure complete documentation of your process. You
define the settings under "Log settings".
Displaying logged data
You can view the logged data on the HMI device.Configure a corresponding alarm view that
displays the log data, or use buttons to show the "Historical alarm list" (short-term), or the
"Historical alarm list" (long-term) in Runtime.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1369
See also
Working with Logs (Page 1470)
Logging alarms
Introduction
Specify the size and time range for the alarm log segments in the log settings.By specifying
their size, you also define the number of segments.
The segments are filled successively with data in Runtime.The next segment is used on
overflow of a segment.You can also configure a time-dependent segment change.If you specify
a time for the segment change, the next log segment is filled after this time was reached.
Note
Ensure that the log size does not exceed memory resources. The log manager does not
validate the selected settings.A large number of linked log segments might lead to longer
waiting periods in the system during the startup and shutdown of Runtime.
Overview
To log alarms, follow these configuration steps:
Configure the alarm log in the log settings.
Define the size and segmentation.
Configure a loggable alarm class.
Assign the alarm to a loggable alarm class.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1370 System Manual, 08/2011,
Requirements
An alarm class has been created.
Configuring an alarm log
To configure the alarm log, proceed as follows:
1. Double-click "Runtime settings" in the project navigation.
2. Double-click "Logging" in the area navigator.
The alarm settings open.
3. Click "Properties > General" in the Inspector window and specify the following:
Enter the values for "Time period of all segments" and "Maximum size of all segments".
Define the size of the log database by entering the accumulated time period for all
segments and the maximum segment size.A new segment is started if either one of
these criteria is exceeded. The oldest segment is overwritten after all segments were
filled with data.
Enter your values at "Time period covered by a single segment" and "Maximum size of
a segment".
You include the size and number of single segments when entering the time period for
single segments and their maximum size. A new single segment is started if either one
of those conditions is exceeded. In addition, the oldest single segment is deleted after
the criterion for "Time period of all segments" is exceeded.
Select the date and time for the start of the first segment change at "Time of first segment
change".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1371
The segment is changed even if the configured size is exceeded after Runtime starts.
In this case, the oldest individual segment is also deleted.
Create alarm class with logging
To create an alarm class with logging, proceed as follows:
1. Open the "HMI alarms" editor.
2. Click the "Alarm Classes" tab.
3. Select the alarm class whose alarms are logged.
4. In the Inspector window, select "Properties > Properties > General > Settings > Alarm log".
5. Assign the alarm to be logged to this alarm class.
Example for the timing of the first segment change
A segment changes for the first time at 23:59 on January 17. The next time, the segment
changes at the configured time in the cycle defined in "Time period contained in a single
segment". If the cycle setting is "1 day", then the change will take place at 23:59 every day. If
the cycle is set to "1 month", the segment will change at 23.59 on the 17th day of the next
month.
See also
Working with Logs (Page 1470)
Logging Settings (Page 1154)
Defining the Log Size and Segmentation (Page 1155)
Configuring the Alarm Log Backup
Principle
Make regular backups of your log data to ensure complete documentation of your process.
Note
The backup normally starts 15 minutes after the first time-related segment change. To start
the backup and the segment synchronously with Runtime, define the time for the segment
change before you start Runtime.
You can enter comments for alarms displayed in the alarm view in Runtime. If the log segment
in which the alarm is stored has already been swapped out, the comment will not be accepted
in the swapped-out log. The comment will only be in the local log segment.
If the archive segment has not yet been moved out, then the changed comment is accepted
permanently.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1372 System Manual, 08/2011,
Requirement
The settings for logging are open.
Procedure
To create a backup of the log segments, proceed as follows:
1. Double-click "Logging" in the area navigator.
2. Enable "Alarm log > Backup".
3. In the Inspector window, click "Properties > General > Settings Backup > Path".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1373
4. Click and look for an existing folder in which to store the backup file. Use "Make New
Folder" to create a new folder, if necessary. You can also use a network path as the storage
location.
5. Activate "Backup" to generate a backup copy of logged data.
Also activate "Backup to both paths" if a backup copy of logged data is to be saved to the
"Path" and to the "Alternative path" folders.
You can also use a network path as the storage location.
If the "Backup to both paths" option is not enabled, the second backup file is used in the
following situations:
If the storage space on a backup medium is full.
The original storage location is unavailable due to network failure, for example.
An alarm is output if a storage location was not found, provided you configured
corresponding system alarms.
6. Activate the "Sign" check box if the backup file must be saved with signature.
When the connection to WinCC is reestablished, the signature is used to detect whether
any changes have been made to a backup file since it was swapped out.
Note
The "Sign" option puts a load on the RAM. If you use log signing, the maximum size of a
single segment must not exceed 200 MB.
Result
The log segment backup is stored in the specified location.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1374 System Manual, 08/2011,
Structure of the Backup File
A backup file for an alarm log has the following structure:
Extension
A log segment backup consists of two files in "*.LDF" and "*.MDF" format. To transfer a
backup to another PC, simply copy both files.
File name
The file name is in the following form:
"<Computer_name>_<Project_name>_<Type>_<Time_from>_<Time_to>".
Component Explanation Example
Computer name FLEX-LOG2
Project ID The project ID is assigned by the
system. Underscores are
replaced with "#".
HMI#4ZQV
Type The type identification of the
alarm log is "ALG" (Archive Log).
Time_from The time period is specified in
yyyymmddhhmm format.
200812021118 for December 2,
2008, 11:18.
Time_to
Example of the complete file name of a backup file:
FLEX-LOG2_HMI#4ZQV_ALG_200811291414_200812030502.ldf
Note
Assignment to project
The project name cannot be seen in the file name of the generated project ID.
To be able to allocate the backup files to the project, assign a path name to the storage
location that contains the project name.
Signing the Backup File
If signing and backup are enabled, each log backup file is signed when swapped out. When
the file is reconnected to WinCC, it is thus determined whether the file was changed after being
swapped out.
If you use log signing, the maximum size of a single segment must not exceed 200 MB.
The "Enable signing" check box must be enabled for data verification. When signing is enabled,
it takes longer to link the log backup file to WinCC. Up to 500 values are logged per second.
Note
If you disable signing off to establish a fast connection to the backup files, for example, you
should avoid segment changes while it is disabled. After having closed the connection, re-
enable signing so that the data to be logged is assigned a signature.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1375
See also
Working with Logs (Page 1470)
Connecting and Disconnecting the Alarm Log Backup
Introduction
To access the data in a swapped-out alarm log in Runtime, connect the log backup to the
project. You can configure an automatic connection or connect the alarm log to the project via
a script. The archived alarms are displayed in Runtime in the alarm view.
If you no longer want to access the backup of a log segment in Runtime, disconnect the log
backup from the project.
Requirement
The relevant backup files in "*. ldf" and "*.mdf" format are stored locally.
The project is in Runtime.
Display Time Range
The alarms are only displayed in Runtime if the time window in the alarm view has been
configured accordingly.
Example
You have configured a time window to display only the alarms of the past 24 hours. If you
connect to a log backup containing alarms that are older than 24 hours, these alarms are not
included in the alarm view.
Connecting to the alarm log automatically
To automatically connect to the alarm log backup, proceed as follows:
1. Insert the log backup files in the "RuntimeProjectPath\ProjectName\CommonArchiving"
folder.
2. In Runtime, the alarm log is automatically connected to the project.
If signing is enabled, signed log backup files that are changed will not be connected
automatically. A WinCC system alarm is generated and an entry is added to the Windows
event log in the "Application" section.
Connecting to the alarm log using a script
Using the "AlarmLogs" VBS object, you can link the log backup files to the project using a
script. The log segments are then copied with the "Restore" VBS method to the Common
Archiving folder of the Runtime project. For additional information, see the description of the
"AlarmLogs" VBS object and the "Remove" VBS method.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1376 System Manual, 08/2011,
Automatically disconnecting the alarm log
To automatically disconnect the alarm log backup from the project, proceed as follows:
1. Go to the folder "RuntimeProjectPath\ProjectName\CommonArchiving".
2. Remove the log backup files from the folder.
Disconnecting the alarm log using a script
Using the "AlarmLogs" VBS object, you can disconnect the log backup files from the project
using a script. The log segments are then removed with the "Remove" VBS method from the
Common Archiving folder of the Runtime project. For additional information, see the description
of the "AlarmLogs" VBS object and the "Remove" VBS method.
Accessing the Log Database Directly with C-API/ODK
Introduction
Various providers offer interfaces that you can use to access databases. These interfaces also
allow you to directly access the WinCC log databases. Using direct access you can, for
example, read process values to process them further in spreadsheet programs.
Accessing the log database with C-API/ODK
You can use the "WinCC Open Development Kit" option to access WinCC data and functions
via open application programmer interfaces.
Additional information
You will find further information on this topic in the documentation for the WinCC Open
Development Kit.
Accessing the Log Database Directly with ADO/OLE DB
Introduction
Various providers offer interfaces that you can use to access databases. These interfaces also
allow you to directly access the WinCC log databases. Using direct access you can, for
example, read process values to process them further in spreadsheet programs.
Accessing the log databases with ADO/OLE DB
Some process values are stored in the log databases in compressed format. Use the WinCC
OLE DB Provider to access these compressed process values. For non-compressed data and
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1377
data from the alarm log, you can also use the Microsoft ADO/OLE DB interfaces, for example.
You can use Visual Basic, Visual C++, etc., as the programming language.
Note
If you access the log database directly using ADO/OLE DB, remember that the log structure
may be different in a new version of WinCC.
Additional information
You will find more detailed information on this topic on the Internet at:
msdn.microsoft.com (http://msdn.microsoft.com/en-us/library/default.aspx)
Configuring the Reloading of Alarms after a Power Failure
Introduction
Configure the reloading of alarms so that the most recent alarms are displayed in Runtime
once more after a power failure. In the event of a power failure, the number of alarms that you
configured is read from the alarm log. This allows the most recent process image to be
reconstructed.
Procedure
To define the number of alarms that are reloaded after a power failure, follow these steps:
1. Double-click "Runtime settings" in the project navigation under your HMI device.
2. Double-click "Alarms" in the area navigator.
3. Select "Properties > General > Number of alarm list entries after power failure" in the
Inspector window to enter the number of alarms to be reloaded after power failure.
Result
After power failure, the number of alarms you configured is reloaded to the alarm view and
displayed in Runtime.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1378 System Manual, 08/2011,
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:
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1379
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.
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:
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1380 System Manual, 08/2011,
Date
Time of day
Alarm text
Location of fault
Status
Alarm class
Alarm number
Alarm group
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1381
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1382 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. 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:
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1383
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.
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1384 System Manual, 08/2011,
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1385
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1386 System Manual, 08/2011,
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1387
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1388 System Manual, 08/2011,
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1389
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1390 System Manual, 08/2011,
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 Using Alarms in Runtime
9.3.5.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:
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
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".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1391
"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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1392 System Manual, 08/2011,
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.5.2 Alarm view
Introduction
The "Alarm view" object displays alarms that occur during the process in a plant. You also
use the alarm view to display alarms in list form. WinCC offers various views, such as "Current
alarms" or "Historical alarm list" (short-term).
In Runtime, you can use the <TAB> key to jump to different objects in succession to enter
values, or click buttons. Alternatively you can use the alarm view with the mouse.
Note
An alarm appears in the alarm view with the date and time stamp crossed out in the following
situations:
A locked alarm is unlocked.
An alarm is reloaded after a power failure. This applies only to chronological messaging.
The AS is restarted. This applies only to chronological messaging.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1393
Requirement
Cursor mode is set to "Tab cursor" for the screen.
The objects are enabled for operation.
The operator authorization is assigned.
Operation using the mouse
1. Click on the alarm to be edited.
2. Click on the operator control whose function you wish to use.
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 operator control element you wish to use is selected.
4. Press <Enter>.
Alternative operation
Depending on the configuration, you can also operate the alarm view via the function keys.
Example: Change the order of the columns
The function can be configured. It is only available in Runtime if you have activated the alarm
view "Font table > Header column > Sort" in the Inspector window.
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".
Example: Change the order of the columns
The function can be configured. It is only available in Runtime if you have activated the alarm
view "Font table > Header column > Sort by column headers" in the Inspector window.
1. Click on the column header.
2. Click the same column header again to reverse the sort order.
Example: Loop-In-Alarm
Loop-In-Alarm triggers the configured change of screen to the screen containing information
about the alarm.
1. Click on the alarm to be edited.
2. Click the button.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1394 System Manual, 08/2011,
Operation behavior
When Loop-In-Alarm is triggered for an unacknowledged alarm, it is acknowledged
automatically.
9.3.5.3 Alarm View Buttons
Introduction
The alarm view displays specific alarm lists in order to provide a better overview of the active
alarms. These lists filter, and sort alarms by certain properties. You can individually define
these properties, and how the lists are presented when you configure the alarm view.
Lists in the alarm view
You can display six different lists in the alarm window. To display the alarm lists in the alarm
view, click the associated button on the alarm view's toolbar.
List Description
Alarm list Shows the pending alarms.
Short-term archive list Shows the logged alarms.
The display is updated immediately when new incoming
alarms occur.
Long-term archive list Shows the logged alarms.
The display is not updated immediately when new incoming
alarms occur.
Lock list Shows the locked alarms.
Alarm statistics Shows statistical information.
List of Hidden Alarms Shows the hidden alarms. Hidden alarms are also logged.
Filtered alarm list
You use the filter of the alarms view to configure alarm views in which you display specific
alarm lists. You can configure a filter for any alarm list. Configure a separate alarm view for
each filtered alarm list.
Note
An alarm appears in the alarm list with the date and time stamp crossed out in the following
situations:
A locked alarm is unlocked.
An alarm is reloaded after a power failure; for chronological alarms only.
The AS is restarted; for chronological alarms only.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1395
See also
Filtering Alarms in Runtime (Page 1396)
9.3.5.4 Filtering Alarms in Runtime
Introduction
In Runtime, you can set specific criteria that define the alarms to be displayed in the alarm
view. In the example below, only alarms that contain the alarm text "Motor on" are displayed.
Requirement
The "Filter alarms" button is configured in the alarm view.
Procedure
To filter alarms in the alarm view, proceed as follows:
1. Click in Runtime.
The "Specify selection" dialog opens.
2. Double-click the "Text Blocks" folder in the tree structure, and click "Alarm Text". In the right
pane, select the "Search string" option, and double-click "Search string".
3. The "Text input" dialog opens. Enter the search string "Motor on" and click "OK" to confirm.
4. In the "Specify selection" dialog, click "OK" to confirm your entries.
The alarm view only shows the selected alarms.
In the "Specify selection" dialog, specify the start and end times, or search strings, for alarm
text blocks such as the "Date" and "Time" system blocks. Your input must be in the format
required in the dialog.
The following settings are available in the "Specify selection" dialog:
Field Description
Text filter by
exact match
If the "Text filter by exact match" option is not enabled, all text blocks that contain
the specified string of characters are selected.
If the "Text filter by exact match" option is enabled, all text blocks that correspond
exactly to the specified string of characters are selected.
Persistence in
RT
If the "Persistence in RT" option is enabled, changes to criteria are retained even
after a screen change.
Persistence in
CS and RT
If the "Persistence in RT and CS" option is enabled, the modified settings are also
applied to the Engineering System. To do this, you must open the screen in the
"Screens" editor, and save it again. The changed settings will also be used when
you reactivate the project.
Delete filter Use this button to delete all configured criteria.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1396 System Manual, 08/2011,
Filter by process values
You cannot enter text as the criterion for a process value.
To filter by the text of a process value block, or the process tags it represents, proceed as
follows:
1. Insert this process value as the alarm text for a user text block in an alarm.
2. In Runtime, filter the alarms by the text in the "Alarm text" text block.
Note
In multi-user systems, make sure that contents displayed in the "Specify selection" dialog
on a client have the same names on all servers.
When filtering by time, the start and stop values are not adjusted automatically when the
timebase of the alarm view is changed.
Example: At the PC location with time zone "UTC + 1h", the alarm view has the "Local
time zone" time base. You should filter by the time 10:00 to 11:00. Change the timebase
from "Local time zone" to "UTC". If you want to display the same alarms, change the filter
to 9:00 to 10:00.
9.3.5.5 Sorting Alarms in Runtime
Introduction
In Runtime, you can sort the alarms in the alarm view by column header.
Examples for sorting alarms:
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1397
In descending order by date, time, and alarm number. The most recent alarm is displayed
at the top.
By priority
You must have defined the priority of the alarms in the "HMI alarms" editor and configured
the "Priority" alarm text block in the alarm view. As a result, in a single-line alarm view, only
the top-priority alarm appears in the alarm window. A lower-priority alarm will not be
displayed, even if it is more recent. The alarms are displayed in chronological order.
The "Alarm status" alarm text block is sorted by the type of state and not by the configured
status texts. For an ascending sort order, the following order is used:
Incoming
Outgoing
Acknowledged
Locked
Enabled
Automatic acknowledgment
Emergency acknowledgment
Incoming/outgoing
Note
Specifying sorting criteria in the ES for the alarm view
You can set the sort criteria to configure the alarm view as required. In the Inspector
window of the alarm view, select "Properties > Properties > View > Columns".
Sorting alarms
To sort the alarm view by column, define the sort order over up to four columns. An arrow and
a number are shown on the right in the column header. The arrow indicates the sort order
(ascending or descending). The number beside the arrow indicates the sort order of the column
headers.
Requirement
"Sort by click" or "Sort by double-click" is selected in the alarm view.
Click on "Properties > Properties > Table > Table - Sorting > Settings".
The "Autoscroll" button is activated in the alarm view.
Click "Properties > Properties > Toolbar > Toolbar buttons".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1398 System Manual, 08/2011,
Procedure
To sort alarms in the alarm view by column, proceed as follows:
1. Click or double-click the column header by which you want to sort the alarms first.
The number "1" is displayed, and the arrow points upwards for ascending sort order.
If sort order "Up and down" is enabled in the alarm view, each click or double-click in
the column header toggles the sorting between the ascending and descending mode.
If sort order "Up, down, none" is enabled, then the sort order is cancelled after the 3rd
click.
2. If you want to sort by several columns, click the column header in the required order.
Note
Sorting is not affected by events or changes to the alarm text block configuration.
An alarm text block corresponds to a field in an alarm. If you define an alarm text block
as sorting criterion in the sort dialog and then remove this block from the alarm line under
"Properties> Properties > Columns", the defined sort order remains unchanged. In the
sort dialog, a blank field is displayed instead of the deleted alarm text block.
If you do not define another sort order order and reactivate the removed alarm text block
in the alarm text block configuration, the alarms will be sorted in the original sort order
once more.
9.3.5.6 Toggling the Alarm View in Runtime
Introduction
You filter the alarms to be displayed in the alarm view using preconfigured buttons.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1399
Requirements
The six buttons needed to display a certain selection of alarms are configured in the alarm
view.
Procedure
To display a certain selection of alarms in the alarm view, follow these steps:
Click on one of the following buttons in the alarm view:
Alarm list, to view alarms pending
Historical alarm list (short-term), to view logged alarms
The display is updated immediately when new incoming alarms occur.
Historical alarm list (long-term), to view logged alarms
Lock list, to view the locked alarms
Alarm statistics, to view statistical information
List of hidden alarms, to view alarms which are logged but not visible.
9.3.5.7 Displaying logged alarms in Runtime
Introduction
In Runtime, the alarm view displays alarms from the log, in addition to the current alarms.
Requirements
All the archived data that you intend to display in Runtime must be stored locally on the
archive server. The SQL server does not allow access to backup files held elsewhere, such
as another computer on the network.
The and buttons are configured in the alarm view.
Procedure
To logged alarms in Runtime, follow these steps:
1. In the alarm view, click on the "Short-term archive list" button to display the logged
and current alarms. Any new incoming alarms will be immediately updated in the historical
alarm list (short-term).
-OR-
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1400 System Manual, 08/2011,
1. In the alarm view, click on the "Long-term archive list" button to display only logged
alarms. The historical alarm list (long-term) only displays logged alarms. You can enter or
view comments in the historical alarm list (long-term).
9.3.5.8 Printing Alarms in Runtime
Introduction
You have the following options for printing alarms in Runtime, depending on the settings made
in the "HMI alarms" and "Reports" editors:
Print alarm sequence report
If the alarm sequence report is activated, all alarm status transitions in Runtime are output
continuously to a printer. No operator input is needed in Runtime.
Printing report
The operator input in Runtime depends on your configuration. Your options for printing an
alarm report in Runtime are as follows:
Time-driven output
One-off, time-driven output, e.g. at the start of a shift
Repeated output at specific intervals, such as every two hours
Event-driven output
Change in value of a tag
By clicking a configured button in a screen
Click the button in the alarm view
Overflow of a log
Script
Requirement
Several alarms are displayed on the HMI device.
Procedure
To print the current view in the alarm window in Runtime, follow these steps:
1. Filter the alarm view using the alarm view controls, if necessary.
2. Click the button in the alarm view.
Result
The alarms displayed in the alarm window are output to the printer that you configured in the
"Reports" editor.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1401
Printer settings
Configure the printer in the HMI device's Control Panel. The settings will depend on which
operating system is used on the HMI device. For detailed information, refer to the operating
instructions of your HMI device and to the "Reporting alarms" chapter.
See also
Working with reports (Page 1609)
9.3.5.9 Locking Alarms in Runtime
Locking Single Alarms
Introduction
If you lock an alarm, this alarm will not be displayed, and will not be logged. You can lock single
alarms, alarm classes or alarm groups as required.
Note
Locked alarm:
Locked alarms are automatically unlocked when WinCC Runtime restarts. Only alarms that
are locked directly in the AS by means of data blocks will continue to be locked (locking at
source).
Locked alarm classes / alarm groups:
The locked state of alarm classes and alarm groups is not affected by a restart of WinCC
Runtime.
Requirement
The alarm view has been configured.
The alarm view is displayed in Runtime.
The "Lock alarm / Unlock alarm" button / is configured.
You are authorized to lock, and unlock alarms.
Note
The "Lock alarm", and "Unlock alarm" authorizations must be configured directly one
above the other. This is necessary because the authorization level used automatically for
the "Unlock alarms" authorization is directly below the "Lock alarms" authorization.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1402 System Manual, 08/2011,
Procedure
To lock alarms and prevent them being displayed using the button, follow these steps:
1. Select the alarm that you want to lock from the alarm view.
2. Click the button.
The alarm is removed from the alarm list.
3. Click on the button to view all locked alarms.
The lock list is displayed.
4. Select the alarm that you want to unlock.
5. Click the button.
The alarm is displayed again and removed from the lock list.
Note
Locking/unlocking an Alarm_8(P) alarm by means of S7PMC always causes all 8 alarms
of this block to be locked, or unlocked.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1403
Locking alarms by means of alarm number
Requirements
The "Lock dialog" button is configured in the alarm view.
Procedure
Proceed as follows to lock alarms and prevent them being displayed using the alarm number:
1. Click the button.
The "Configure Lock List" dialog opens.
2. Click a server in the server list, or click the local PC for single-user projects.
3. Click the "Add" button. In the subsequent dialog, enter the alarm number that you want to
lock.
4. You can lock multiple alarms at the same time. To do this, enter the alarm numbers,
separated by commas. Enter a range of numbers in the format "5-10". Only contiguous
number ranges are locked. If there are gaps in the specified range, an "Invalid range"
message is output.
5. To unlock a locked alarm, select the alarm from the list of locked alarms, and click the
"Delete" button.
Note
You cannot lock, or unlock more than 50 alarms at the same time.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1404 System Manual, 08/2011,
Locking Alarms using the Alarm Class or Alarm Group
Introduction
You can also lock alarms to prevent them from being displayed by locking the entire alarm
class, or the alarm group to which the alarm belongs. None of the alarms from these locked
alarm groups and alarm classes will be displayed.
Requirements
The "Lock dialog" button is configured in the alarm view.
Procedure
To lock, or unlock alarms via the alarm class, or the alarm group, proceed as follows:
1. In the alarm view, click the button.
The "Configure Lock List" dialog opens.
2. Click a server in the server list, or click the local PC for single-user projects.
3. In the tree structure, select an alarm class or user-defined alarm group that you want to
lock.
4. Click the "Lock" button.
All alarms from this alarm class or user-defined alarm group are locked.
To unlock the alarms, select the alarm class or user-defined alarm group and click on the
"Unlock" button.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1405
Operator input alarm when an alarm is locked
You can define in the alarm view, whether an operator input alarm is generated when an alarm
is locked or unlocked. You should configure the operator input alarm yourself if needed. The
operator input alarm contains the following objects by default:
A time stamp
The user logged on
The time stamp for the alarm originates as follows:
From the alarm source (such as an AS) for active locking.
Actively-locked alarms are visible, and can be used on all HMI devices.
9.3.5.10 Acknowledgement of Alarms
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
With customized buttons
If an operator authorization is configured for an individual control, the alarms can only be
acknowledged by authorized users.
To bypass the acknowledgement in Runtime, WinCC contains system functions and scripts
that allow you to acknowledge alarms automatically.
Acknowledgement variants
You acknowledge individual alarms or multiple alarms together in Runtime. The following
options are possible:
Single acknowledgment
Acknowledgment of an alarm using a button or a function key.
Acknowledge alarm groups
Acknowledgement of all the alarms of an alarm group using a button, or a function key.
Group acknowledgement
Acknowledgement of all pending alarms in the alarm view that require acknowledgement
using the button in the alarm view.
Dual-mode acknowledgment
If an alarm requires dual-mode acknowledgment, you acknowledge both the incoming, and
the outgoing alarm.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1406 System Manual, 08/2011,
Requirement
An alarm is displayed on the HMI device.
Procedure
To acknowledge an alarm, follow these steps:
Select the alarm.
Click the button in the alarm view.
Result
The alarm status is set to "Acknowledged". If the trigger condition for an alarm no longer
applies, the alarm status is also set to "outgoing" and no longer displayed on the HMI device.
Group Alarm Acknowledgement
Introduction
The acknowledgement of all pending, and visible alarms in the alarm window that need to be
acknowledged is known as a group acknowledgement. If the "Single alarm" option is not
selected for an alarm, you can trigger a group acknowledgment.
Requirement
There are several alarms that require acknowledgement in the alarm view.
Procedure
To group-acknowledge an alarm, follow these steps:
1. Read the alarm texts of the queued alarms and initiate remedial action, if necessary.
2. In the alarm view, click the button.
Result
All queued alarms with the following properties are acknowledged:
Requires acknowledgement
Does not require acknowledgement
Visible
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1407
Emergency acknowledgment of alarms
Introduction
In exceptional situations, the operator acknowledges an alarm based on its alarm number. The
acknowledgment bit is sent to the AS even if the alarm is currently not pending. This function
is only intended for use in imminent emergency situations.
Requirement
The button is configured in the alarm view.
Procedure
To acknowledge an alarm in Runtime using an emergency acknowledgement, follow these
steps:
1. Click the button in the alarm view.
The "Emergency Acknowledgment for Alarms" dialog opens.
2. Select a server.
3. To enter the alarm number, select "Alarm number".
4. Click the "Send acknowledge job" button.
The alarm then appears in the alarm view in the color that you defined for an acknowledged
alarm.
Note
In the dialog for selecting the servers, only server projects whose "Packages" are loaded
onto the PC are shown.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1408 System Manual, 08/2011,
Acknowledging an alarm annunciator
Introduction
The way you acknowledge an alarm annunciator in Runtime will depend on how you configured
its acknowledgement.
Requirements
The alarm annunciator and its acknowledgment are configured.
The alarm annunciator is triggered.
Acknowledgment using a separate key
To acknowledge the alarm annunciator, click the button in the alarm view.
You only acknowledge the alarm annunciator. The alarm that triggered the alarm
annunciator is still set to "incoming" status.
Single acknowledgment
To acknowledge the alarm annunciator, select the current alarm, and click the button
in the alarm view.
You thereby acknowledge the alarm annunciator and the alarm that triggered the alarm
annunciator.
Acknowledgment tag
If the alarm annunciator is acknowledged using a tag, acknowledge the alarm annunciator
using a customized button or function key, etc.
Result
This sets the acknowledgment bit of the alarm annunciator.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1409
9.3.6 Reference
9.3.6.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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1410 System Manual, 08/2011,
Note
Device dependency
The following system functions are not available for all HMI devices:
SetAlarmReportMode
AlarmViewUpdate
ShowSystemEvent
9.3.6.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
See also
Events (Page 1839)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1411
9.3.6.3 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
Status changed
Alarm view Enabling
Loaded
ToolbarButtonClicked
PropertyChanged
ToolbarButtonPropertyChanged
AlarmBlockPropertyChanged
AlarmColumnPropertyChanged
HitlistColumnPropertyChanged
OperatorAlarmPropertyChanged
See also
Events (Page 1839)
9.3.6.4 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1412 System Manual, 08/2011,
Function name Function method
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.6.5 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";
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)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1413
Parameters Description
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)
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.6.6 Description of the System Blocks
Introduction
System blocks allow you to specify predefined information that is not freely utilizable, such as
date, time and duration.
The value of the alarm text block (such as the time of day) is displayed in the alarm. The
description of the system blocks provides information on the individual system blocks.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1414 System Manual, 08/2011,
Overview
System block Description Default
length
Date Date of the "incoming", "outgoing", and "acknowledged"
alarm statuses.
8
Time of day Time of the "incoming", "outgoing", and "acknowledged"
alarm statuses.
Accuracy of a WinCC time stamp: 1 s.
Display accuracy: 10 ms.
9
Duration Time period between the "incoming", "outgoing", and
"acknowledged" statuses.
There is only one column for duration:
The column remains blank for alarms with "incoming"
status.
For alarms with "outgoing" status, the time that
elapses between "incoming" and "outgoing" is
displayed.
When alarms are acknowledged, the time between
"incoming" and "outgoing" is displayed.
8
Daylight Saving Time/
Standard Time
Indicates whether daylight saving time is set. 1
Status Indicates the alarm status, such as "Incoming" or
"Outgoing".
The letters displayed in this system block to indicate the
alarm status (such as "Q") are assigned in the alarm class.
1
Acknowledgment status Indicates whether an alarm has been acknowledged.
The letters that are displayed in this system block to
indicate the acknowledgment status are configured in the
alarm class.
1
Number Alarm number 3
Class Alarm class
The text is user-defined.
8
Category Alarm types 8
PLC/CPU number
Number of the CPU and AS in which the alarm was
triggered.
In Runtime, the value of this system block is not taken
from the AS but rather is taken from the configured data
for the alarm. The value has no function in communication
with the AS.
2
Tag The "Tag" system block is not yet supported. 1
Log ID ID indicating whether the alarm is to be logged. 1
Report ID ID indicating whether the alarm is to be reported.
The report ID depends on the alarm number. You only
have read access to the report ID.
1
Comment Indicates whether there is a comment for this alarm. A
comment is the users input about an alarm, such as "This
alarm occurred today because...".
1
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1415
System block Description Default
length
Tooltip Indicates whether there is a tooltip for this alarm. Tooltips
contain information about the alarm, limited to 255
characters, such as "This alarm may occur if ...". Tooltip
cannot be edited in Runtime.
1
Loop-In-Alarm Indicates whether Loop-In-Alarm function is enabled. 1
Computer Name Indicates the name of the PC:
If the user has entered a comment in the "Historical
alarm list" (long-term) and then changed the view, the
name of the PC used appears in the "Historical alarm
list" (short-term) and "Historical alarm list" (long-term).
If an alarm was acknowledged on a PC, the name of
the PC appears in the "Historical alarm lists" (short
and long-term) in the operator input alarm. The
operator input alarm must be enabled under
"Operator input alarm" in the Inspector window for the
alarm view.
10
User Name Indicates the name of the user (login name):
If you enter a comment in the "Historical alarm list"
(long-term) and then exit the view, your user name is
displayed in the "Historical alarm list" (short-term) and
"Historical alarm list" (long-term).
If an alarm was acknowledged by a user logged on to
WinCC, the user name is displayed in the "Historical
alarm lists" (short and long-term) in the operator input
alarm. The operator input alarm must be enabled
under "Operator input alarm" in the Inspector window
for the alarm view.
10
Priority Defines the priority of an alarm. You can sort the alarms
in the alarm view by priority. By sorting by priority, you
can ensure that, in a single-line alarm view, the most
important alarm (high priority) is shown in the display
area. A lower-priority alarm will not be displayed, even if
it is more recent.
Range: 0 - 16
In WinCC, the value corresponding to the highest priority
is not specified. In the PCS7 environment, the value 16
corresponds to the highest priority.
3
Note
If you enabled the "Change ISO8601 format on all components" option in the shortcut menu
of WinCC RT Professional, "Properties > Time settings > Central date and time formatting",
the date and time are also displayed in the system blocks of the alarms in ISO8601 format.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1416 System Manual, 08/2011,
9.3.6.7 SQL Statements for Filtering the Alarm View
Introduction
In the alarm view, you can only use SQL statements that can be generated using the "Specify
selection" dialog. The following conditions apply to WinCC:
Structure: "Field", "Address", and "Value"
Separate individual parameters with spaces.
Example:
DATETIME >= '2006-12-21 00:00:00' AND MSGNR >= 100
All alarms from 21.12.2006 with an alarm number greater than or equal to 100
The following information is entered in single quotes:
Character strings
Date
Time of day
In the DATETIME argument, the date and time of day are separated by a blank. Regardless
of the time base setting in the object properties, the output of DATETIME is based on the
time base Local Time. The exception to this is when "UTC" is set as the time base. In this
case, output is based on the time base "UTC".
Permissible Arguments
Name SQL name Type Data Example
Date/time DATETIME Date 'YYYY-MM-DD
hh:mm:ss.msmsms'
DATETIME >= '2007-05-03
16:00:00.000'
Outputs alarms as of 05/03/2007, 16:00
hours.
Number MSGNR Integer Alarm number MSGNR >= 10 AND MSGNR <= 12
Outputs the alarms with alarm numbers
10 - 12.
Class CLASS IN Integer Alarm class ID 1-256 and
"System" alarm classes 17 + 18
CLASS IN ( 1 )
Outputs alarms of alarm class 1.
Status STATE Integer Value "ALARM_STATE_xx"
Only the operands "=" and "IN(...)"
are permitted.
ALARM_STATE_1
ALARM_STATE_2
ALARM_STATE_3
ALARM_STATE_4
ALARM_STATE_10
ALARM_STATE_11
ALARM_STATE_16
ALARM_STATE_17
STATE IN(1,2,3)
Outputs all alarms that came in, went out
and were acknowledged.
Possible values:
1 = incoming alarms
2 = outgoing alarms
3 = acknowledged alarms
4 = blocked alarms
10 = hidden alarms
11 = displayed alarms
16 = alarms acknowledged by the
system
17 = Emergency-acknowledged alarms
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1417
Name SQL name Type Data Example
Priority PRIORITY Integer Alarm priority 0 - 16 PRIORITY >= 1 AND PRIORITY =< 5
Outputs alarms that have a priority
between 1 and 5.
Controller
number
AG_NR Integer Controller number AG_NR >= 2 AND AG_NR <= 2
Outputs alarms with the Controller
number 2.
CPU number CPU_NR Integer AG sub-number CPU_NR >= 5 AND CPU_NR <= 5
Outputs alarms with AG sub-number 5.
Instance INSTANCE Text Instance -
Block: 1
...
Block: 10
TEXTxx Text Search string for Text1 - Text10 TEXT2 = "Error"
Outputs the alarms whose Text2
corresponds with "Error".
TEXT2 IN ('Error','Fault')
Outputs the alarms whose Text2
corresponds with the text "Error" or
"Fault".
TEXT2 LIKE 'Error'
Outputs the alarms whose Text2
includes the text "Error".
Process value: 1
...
Process value:
10
PVALUExx Double Search value for PVALUE1-
PVALUE10
PVALUE1 >= 0 AND PVALUE1 <= 50
Outputs process value 1 with start value
0 and stop value 50.
Permissible Operands
>= , <= , = , > , <
IN(...) : Several values as an array, separated by commas, e.g.: CLASS IN( 1 ,2 ,3 ).
LIKE : Text must contain string, e.g.: TEXT1 LIKE 'Error' relays alarm where Text1 contains
the search string "Error". The operand LIKE is only allowed for "text" type arguments.
Illegal arguments and operands
Only the arguments indicated in the table and operands from the list are permitted.
Grouping arguments, with brackets, for example, is not permitted.
9.3.6.8 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1418 System Manual, 08/2011,
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.
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-2 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1419
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.
Table 9-3 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1420 System Manual, 08/2011,
Table 9-4 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.
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-5 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-6 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. --
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1421
60000 - Win32 function alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-7 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-8 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1422 System Manual, 08/2011,
Number Effect/causes Remedy
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1423
Number Effect/causes Remedy
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1424 System Manual, 08/2011,
Number Effect/causes Remedy
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.
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-9 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1425
Number Effect/causes Remedy
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.
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.
--
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1426 System Manual, 08/2011,
Number Effect/causes Remedy
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1427
90000 - FDA alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-10 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1428 System Manual, 08/2011,
Number Effect/causes Remedy
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.
110000 - Offline function alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-11 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1429
Table 9-12 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.
130000 - System information alarms
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-13 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1430 System Manual, 08/2011,
Number Effect/causes Remedy
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.
140000 - Connection alarms: Connection + device
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-14 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.).
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1431
Number Effect/causes Remedy
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1432 System Manual, 08/2011,
Number Effect/causes Remedy
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.
160000 - Connection alarms: OPC: Connection
Meaning of the system events
All system events that can be displayed are listed below.
Table 9-15 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1433
Number Effect/causes Remedy
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.
Table 9-16 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1434 System Manual, 08/2011,
Table 9-17 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.
Table 9-18 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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1435
Number Effect/causes Remedy
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.
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1436 System Manual, 08/2011,
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.
--
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.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1437
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.
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.
--
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1438 System Manual, 08/2011,
Number Effect/causes Remedy
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.
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1439
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1440 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1441
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1442 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1443
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1444 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1445
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1446 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1447
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1448 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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1449
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 (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1450 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
9.3.6.9 System events for Runtime Professional
Introduction
The system events generated by the various WinCC modules are described below. You can
integrate these events into your alarm system using the "WinCC - System Events" menu
command.
Note
You can obtain additional information on the system events in the "Comment" block of the
active alarm.
WinCC system events
Number Error message / description
1000000 WCCRT:Error
1000001 WCCRT:Error on loading the object engine
1000002 WCCRT:Channel could not be loaded
1000003 WCCRT:Tag - Violated lower limit
1000004 WCCRT:Tag - Violated upper limit
1000005 WCCRT:Error on formatting a tag
1000006 WCCRT:Error on scaling a tag
1000100 WCCRT:Driver error
1000200 WCCRT:Status
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1451
Number Error message / description
1000201 WCCRT:Object engine has been loaded
1000202 WCCRT:Runtime has been activated
1000203 WCCRT:Runtime has been deactivated
1000204 WCCRT:Connection not established
1000205 WCCRT:Connection established
1000206 WCCRT:Client connection established
1000207 WCCRT:Client connection disconnected
1000208 WCCRT:Client connection broken
1000209 WCCRT:Connection deleted
1000210 WCCRT:Connection modified
1000211 WCCRT:Connection reestablished
1000300 WCCRT:Driver status
1000800 PACKAGE:Import
1000801 PACKAGE:Export
1000802 PACKAGE:Delete
1000803 PACKAGE:New
1000804 PACKAGE:Reload
1000805 PACKAGE:DefaultServer
1000806 PACKAGE:Implicit update
1000807 PACKAGE:Update
1000900 PERFMON: is low
1000901 PERFMON: is OK
1000902 PERFMON: is high
1000903 PERFMON: is OK
1000904 PERFMON: is low
1000905 PERFMON: is OK
1000906 PERFMON: is high
1000907 PERFMON: is OK
1000908 PERFMON: is low
1000909 PERFMON: is OK
1000910 PERFMON: is high
1000911 PERFMON: is OK
1000912 PERFMON:Redundancy loss of terminal adapter @2%s@
1000913 PERFMON:Redundancy of terminal adapter @2%s@ restored
1000914 PERFMON:Terminal adapter @2%s@ connected.
1000915 Terminal adapter @2%s@ separated. @2%s@: MAC address of the network card
1001000 PDLRT: General error
1001001 PDLRT: Operator action not active
1001002 PDLRT: Wrong picture format
1001003 PDLRT: Picture not found
1001004 PDLRT: No dynamic active in picture
1001005 PDLRT: Tag could not be written
1001006 PDLRT: Dynamic actions in picture are not active
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1452 System Manual, 08/2011,
Number Error message / description
1002000 TLGRT: General error
1002001 TLGRT: Error during initialization
1002002 TLGRT: Error loading the runtime data
1002003 TLGRT: Error changing languages
1002004 TLGRT: Error accessing the database
1002005 TLGRT: Error creating runtime objects
1002006 TLGRT: Error in online configuration
1002007 TLGRT: Error in client/server environment
1002008 TLGRT: Error in memory management
1002009 TLGRT: Error compiling measured values
1002010 TLGRT: Error processing measured values
1002011 TLGRT: Error archiving measured values
1002012 TLGRT: Error in Normalization DLL
1002013 TLGRT: Error in user recipe option
1002014 TLGRT: Error in process controlled archiving
1002015 TLGRT: Error in API
1002016 TLGRT: Error in application window
1002017 TLGRT: System fault
1002018 TLGRT: Error overflow in database queue
1002019 TLGRT: Error overflow in notification queue
1002020 TLGRT: Error overflow of the Normalization DLL queue - loss of data!
1002021 TLGRT:Problem with the connection to the central log server!
1002022 TLGRT:The error in the connection to the central log server has been eliminated
1003018 ALGRT:Alarm does not require acknowledgment.
An attempt was made to acknowledge a alarm that does not require acknowledgment.
1003019 ALGRT:Alarm has already been acknowledged
An attempt was made to acknowledge a alarm that has already been acknowledged.
1003020 ALGRT:Alarm class for the alarm not found
The alarm class associated with the alarm does not exist.
1003021 ALGRT:Alarm status cannot be processed
The alarm status (Incoming, Outgoing, Acknowledged, ...) could not be interpreted.
1003022 ALGRT:Alarm is locked
This alarm occurs if you attempt to trigger a locked alarm via the API.
1003023 ALGRT:Alarm date/time-stamp invalid
The date/time stamp from the AS could not be interpreted.
1003032 ALGRT:Alarm window template name unknown
This error occurs when a alarm window that was previously configured in the Graphics
Design is deleted subsequently.
In the case of client/server projects, this alarm could also be triggered by a communication
error in the network.
1003033 ALGRT:Alarm window could not be created
1003034 ALGRT:Alarm window - data invalid
Incorrect project data.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1453
Number Error message / description
1003048 ALGRT:bit is outside the tag range
For example, an attempt was made to trigger the 18th bit of a 16-bit tag.
1003049 ALGRT:No tag change
1003050 ALGRT:Alarm tag (bit) already occupied by a alarm
The bit of the alarm tag has already been interconnected to a alarm.
1003051 ALGRT:Acknowledgment tag (bit) already occupied by a alarm
The acknowledgment tag bit has already been interconnected to a alarm.
1003052 ALGRT:Status tag already occupied by a alarm
The bit of the status tag has already been interconnected to a alarm.
1003053 ALGRT:Error during conversion of the variant data type
1003054 ALGRT:Alarm tag (bit) already occupied-->different type
1003055 ALGRT:Event - invalid tag or data type
The data type of the alarm tag is invalid. You may have used a tag with sign.
1003056 ALGRT:Invalid acknowledgment tag or data type
The data type of the acknowledgment tag is invalid. You may have used a tag with sign.
1003057 ALGRT:Status - invalid tag or data type
The data type of the status tag is invalid. You may have used a tag with sign.
1003058 ALGRT:Handle invalid
This error message can occur during accesses via the API.
1003059 ALGRT:Selection criteria invalid
This error message can occur during accesses via the API.
1003060 ALGRT:Resources - DLL for language not found
One of the language-dependent files is missing.
1003061 ALGRT:Error while creating the memory mapped files
This internal error indicates a problem involving the memory.
1003062 ALGRT:Error while creating the synchronization mechanism.
This error occurs when the operating system is overloaded.
1003063 ALGRT:Wrong parameter
This error message can occur during accesses via the API.
1003064 ALGRT:Transfer buffer too small
This error message can occur during accesses via the API.
1003065 ALGRT:This function is not available at this time
This error message can occur during accesses via the API.
1003066 ALGRT:Format DLL send data cannot be evaluated
1003067 ALGRT:Format DLL. Do not execute function
1003068 ALGRT:No alarm text blocks in the report
Check the alarm sequence report.
1003069 ALGRT:Invalid reporting
1003070 ALGRT:Report printout is already active
An attempt was made to restart an active report.
1003071 ALGRT:Alarm system runtime <Server> not installed
The server reports that the project was activated without the runtime component of Alarm
Logging.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1454 System Manual, 08/2011,
Number Error message / description
1003072 ALGRT:Printout of the alarm sequence report has not been started.
1003073 ALGRT:Printout of the short-term archive report has not been started.
1003074 ALGRT:Printing of the log segment report has not started.
1003075 ALGRT:Maximum number of alarms that can be configured online
The maximum number of alarms that can be configured online (default setting is 600) has
been exceeded.
1003076 NRMS7:Parameter error for S7 message frame
A parameter error has occurred on the interface to S7.
1003077 NRMS7:Parameter error for ALGRT
A parameter error has occurred on the interface to ALGRT.
1003078 NRMS7:Parameter error for TLGRT
A parameter error has occurred on the interface to TLGRT.
1003079 NRMS7:Parameter error in additional data
The additional data of the alarms are faulty.
1003080 NRMS7:Parameter error in AR_SEND structure
The structure of the AR-SEND user data is faulty.
1003081 NRMS7:General error
An internal error of unknown cause has occurred.
1003082 NRMS7:Alarm loss on the automation system
1003083 NRMS7:Connecting and updating of the automation system is underway
1003084 NRMS7:Connecting and updating of the automation system is finished
1003085 NRMS7:System change during operation (CiR) is underway
1003086 NRMS7:System change during operation (CiR) is finished
1003087 NRMS7:Error while logging on to receive alarm
1003098 ALGRT:Alarm archiving overflow - alarms will be lost
1003099 ALGRT:[Computer Name]:Locked alarms [alarm number] [alarm text of locked alarm]
This alarm occurs when a alarm is locked.
1003100 ALGRT:[Computer Name]:Alarm [alarm number] unlocked [alarm text of unlocked alarm]
This alarm occurs when a alarm is unlocked.
1003101 ALGRT:Acknowledgment request for alarm [alarm number] was issued
This alarm occurs when a alarm is acknowledged.
1003102 ALGRT:[Computer Name]:Alarm group [alarm group number] locked
This alarm occurs when a alarm group is locked.
1003103 ALGRT:[Computer Name]:Alarm group [alarm group number] unlocked
This alarm occurs when a alarm group is unlocked.
1003104 ALGRT:[Computer Name]:Alarm archiving overflow ended - no further alarms will be lost
1003105 ALGRT:[Computer Name]:Incoming alarm queue has reached critical value
1003106 ALGRT:[Computer Name]:Incoming alarm queue has reached normal value
1003107 ALGRT:[ComputerName]:Alarm [AlarmNumber] hidden:@1%s@
1003108 ALGRT:[ComputerName]:Alarm [AlarmNumber] shown:@1%s@
1003109 ALGRT:Connection to master is down.
1003110 ALGRT:Found incomplete configuration data for alarm @10%d@. Status: @1%d@.
1004000 RPTRT:General error
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1455
Number Error message / description
1004001 RPTRT:PRT_OUT directory full
1004002 RPTRT:Spool directory full
1004003 RPTRT:Report was not printed. PRT_OUT directory full
1004004 RPTRT:Report was not printed. Spool directory full
1004005 RPTRT:Alarm sequence report is reprinted
1004006 RPTRT:Spool directory full
1004007 RPTRT:Hardcopy was not printed. Spool directory full
1005000 TXTRT:General error
1005001 TXTRT:Error while logging off the runtime applications.
1005002 TXTRT:Error while logging on the runtime applications.
1005003 TXTRT:Error during initialization of the MMF.
A memory error has occurred.
1005004 TXTRT:Error while loading the MMF.
Error while accessing the database.
1005005 TXTRT:Error while opening the MMF.
A memory error has occurred.
1005006 TXTRT:Error while creating the service window.
1005007 TXTRT:No language found.
1005008 TXTRT:Text ID not found.
The requested Text ID could not be found in the text library.
1005009 TXTRT:Read access to the MMF refused.
1005010 TXTRT:Language not found
The requested language has not been configured in the text library.
1005011 TXTRT:Language table could not be opened.
Either the data are faulty or the table is locked in the database.
1005012 TXTRT:Text table could not be opened.
Either the data are faulty or the table is locked in the database.
1005013 TXTRT:Invalid language specified
The Language ID specified is invalid.
1005014 TXTRT:DBConnect error
No connection to the database could be set up.
1006000 GSCRT:Error
1007000 SCRIPT:Overflow
Overload: either there are too many actions running in a cycle that is too small, or an action
is suspended (endless loop, dialog output). All the other actions are in the queue and cannot
be processed.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1456 System Manual, 08/2011,
Number Error message / description
1007001 SCRIPT:Action error
One of the following errors has occurred:
Exception in the action (specific cause unknown)
Exception when accessing the return result (char* associated memory invalid)
Stack overflow upon execution of the action
The action contains a division by 0
The action contains an access to a non-existing symbol
The action contains an access violation
In WinCC version 4.0 and higher, you can integrate the OnErrorExecute function in
your script, which allows for a detailed analysis of errors.
1007002 SCRIPT:Overflow
Internal lists have overflowed.
1007003 SCRIPT:Connection error
The connection to the server is broken.
1007004 SCRIPT:Action error 1
The called function is not known. Check the notation of the function call and implementation
of the function.
1007005 SCRIPT:Action error 2
This error can have several causes:
The action does not contain a P code. Recompile the action.
The function could not be loaded, for example, due to incorrect function name.
The type of return value of the function is invalid.
In WinCC version 4.0 and higher, you can integrate the OnErrorExecute function in
your script, which allows for a detailed analysis of errors.
1007006 SCRIPT:Tag error
A requested tag was not supplied by WinCC Explorer within 10 seconds. Check the spelling
of the tag name. In the case of external tags, there may be a communication problem
between the WinCC Explorer and the PLC.
From WinCC version 4.0, you have the option to incorporate the OnErrorExecute function
into your script, which allows for a detailed analysis of errors.
1007007 SCRIPT: Info
Additional information under "Diagnostics of WinCC / Runtime Monitoring for Actions".
1007009 SCRIPT:Error in Thread
Additional information under "Diagnostics of WinCC / Runtime Monitoring for Actions".
1008000 USERT:Connection to the smart card reader interrupted
1008001 USERT:Incorrect login name/password
1008002 USERT:Incorrect login name/password by smart card
1008003 USERT:Manual logon
1008004 USERT:Logon using a smart card
1008005 USERT:Manual logoff
1008006 USERT:Logoff using a smart card
1008007 USERT:Automatic logoff via a timer
1008008 USERT:Authorizations effective for service user/group '@102%s@'
1009000 LBMRT:Error
1009999 LBMRT:Tag @2%s@ does not exist
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1457
Number Error message / description
1010000 STRRT:Error
1010101 CAS:Starts archive service
1010102 CAS:Archive service has been started
1010103 CAS:Archive service could not be started, error
1010104 CAS:Stops archive service
1010105 CAS:Archive service could not be stopped, error
1010106 CAS:Media backup completed successfully
1010107 CAS:Backup process failed, error
1010108 CAS:Backup medium created
1010109 CAS:Backup medium closed
1010110 CAS:Backup connected
1010111 CAS:Backup connection failed, error
1010112 CAS:Backup disconnected
1010113 CAS:Backup disconnection failed, error
1010114 CAS:Import of archive started
1010115 CAS:Import of archive failed, error
1010116 CAS:Import of archive completed
1010117 CAS:Archive failed, error
1010118 CAS:Archive completed
1010119 CAS:Starts processing of log
1010120 CAS:Data backup started
1010121 CAS:Data backup completed successfully
1010122 CAS:The server station could not be assigned a symbolic name
1010123 CAS:Warning: No license found: SIMATIC PCS7 StoragePlus Server. Historical alarm list
(long-term) disabled.
1010124 CAS:Log file '@2%s@' could not be verified.
1010130 StoragePlus: Directory cannot be created, error
1010131 StoragePlus: File cannot be moved, error
1011000 CSIG:Group display error at start up
1011001 CSIG:Group display hierarchy not updated
1011002 Group display: Connection fault
1011003 Group display: Tag does not exist
1011101 PTM: Error during start up
1011201 SSM: Error during start up
1011202 The fill level of the project drive is over 80%
1011203 The project was created with the wrong WinCC version
1012001 SYNC:Switched to master operation
1012002 SYNC:Cannot issue time message frame
1012003 SYNC:Time receipt service: Poor or failed signal
1012004 SYNC:Cannot receive time message frame
1012005 SYNC:Cannot receive any time message frame on redundant bus
1012006 SYNC:No time message frame. Switch to redundant device
1012007 SYNC:Can issue time message frame properly
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1458 System Manual, 08/2011,
Number Error message / description
1012008 SYNC:Time reception service functions properly
1012009 SYNC:Can receive time message frame properly
1012010 SYNC:Can receive time message frame properly on redundant bus
1012011 SYNC:Switched to slave operation
1012012 SYNC:Time-of-day synchronization deactivated
1012013 SYNC:Time-of-day synchronization activated
1012014 SYNC:DCF77 client service failure
1012015 SYNC:DCF77 client service functions correctly
1012016 SYNC:@2%s@ switched to master mode @3%s@
1012017 SYNC:@2%s@ switched to slave mode @3%s@
1012018 SYNC:@2%s@ cannot transmit time frame
1012019 SYNC:@2%s@ can successfully transmit the time frame
1012020 SYNC:@2%s@ sets the local time
1012021 SYNC:LAN-Sync: Error in time synchronization with PC @2%s@
1012022 SYNC:LAN-Sync: Time synchronization set on PC @2%s@
1012023 SYNC:LAN-Sync: Time synchronization with PC @2%s@ completed
1012024 SYNC:Configured device names of time synchronization do not match the PC installation
1012025 SYNC:LAN-Sync: Time cannot be accepted from connected WinCC Server
1012026 SYNC:Time jump noted - switched to permanent slave mode
1012027 SYNC:Time jump noted - time synchronization permanently disabled
1012028 SYNC:Time receipt service not started
1012029 SYNC:Time receipt service running
1012030 SYNC:Time-of-day synchronization disabled
1012200 REDRT:Partner station has failed
1012201 REDRT:Partner station restarted
1012202 REDRT:Projects are not functionally identical
1012203 REDRT:Archive synchronization failed
1012204 REDRT:Internal error in Redundancy
1012205 REDRT:Connection to partner disturbed
1012206 REDRT:Connection to partner reestablished
1012207 REDRT:Partner server - WinCC has not been started
1012208 REDRT:Archive synchronization starts
1012209 REDRT:Archive synchronization ends
1012210 REDRT:Tag Logging synchronization starts
1012211 REDRT:Tag Logging synchronization ends
1012212 REDRT:Alarm Logging synchronization starts
1012213 REDRT:Alarm Logging synchronization ends
1012214 REDRT:User Archive synchronization starts
1012215 REDRT:User Archive synchronization ends
1012216 REDRT:Synchronization was interrupted
1012217 REDRT:Partner server project not activated
1012218 SWITCH:Client switched automatically
1012219 SWITCH:Client switched manually
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1459
Number Error message / description
1012220 REDRT:Synchronization not ready for all user archives
1012221 REDRT:Synchronization ready for all user archives
1012222 SWRED:Main connection disturbed
1012223 SWRED:Main connection operational
1012224 SWRED:Backup connection disturbed
1012225 SWRED:Backup connection operational
1012226 REDRT:Partner server project activated
1012227 REDRT:Error: Partner computer is not a server
1012228 REDRT:CAS: Log synchronization starts '@2%s@'
1012229 REDRT:CAS: Log synchronization ends '@2%s@'
1012240 REDRT:RedundancyControl error triggered switching
1012241 REDRT:RedundancyControl: Switch to status
1012242 DELTALOADER:Delta transfer has been started
1012243 DELTALOADER:Delta transfer has been terminated
1012244 REDRT:Overload during online synchronization of Alarm Logging
1012245 REDRT:RedundancyControl: Loss of serial connection
1012246 REDRT:RedundancyControl: Serial connection reestablished
1012247 REDRT: OS server (standby) redundancy error
1012248 REDRT: OS server (standby) redundancy reestablished
1012250 AM:Possible inconsistency of the log databases
1012251 AM:Internal error
1012252 AM:Backup:Error while writing to backup path
1012253 AM:Backup:Insufficient memory space on target drive
1012254 AM:No connection to WriteArchiveServer
1012255 AM:No connection to Microsoft Message Queue
1012256 AM:No connection to WinCC project
1012257 AM:No connection to the database
1012258 AM:No connection to the text library
1012259 AM:Error while creating the TagLogging data
1012260 AM:Error while creating the AlarmLogging data
1012261 AM:Warning: Backup is delayed until partner server restarts.
1012265 AM:Database verification failed
1012301 CA:No access to SQL server (risk of data loss)
1012348 AM:Insufficient free memory space on project drive
1012349 REDRT: Loss of connection via network adapter (MAC) address
1012350 REDRT: Connection reestablished via network adapter (MAC) address
1012351 REDRT:RedundancyControl: System blockage detected. Switch to fault status
1012352 REDRT:RedundancyControl: System blockage detected. Restart the computer as soon as
possible.
1012400 WEBRT:WebClient @1%s@ Connection is up (User=@2%s@)
1012401 WEBRT:WebClient @1%s@ Connection is down (User=@2%s@)
1900000 ESIG:Electronic signature of user @2%s@ successful.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1460 System Manual, 08/2011,
Number Error message / description
1900001 ESIG:Electronic signature of user @2%s@ unsuccessful.
1900002 ESIG:Electronic signature of user @2%s@ cancelled.
9.3.6.10 Tag Bit Assignments
Tags for Alarm Groups and Alarms
Bit assignment of status tag
Introduction
In WinCC you can define a status tag for an alarm or an alarm group. The status tag for am
alarm group represents the states of the alarms and child alarm groups it contains.
Description
The following states of an alarm or alarm group are stored in a status tag:
Incoming/outgoing alarm (status bit)
Alarm queued for acknowledgment / acknowledged (acknowledgment bit)
Data type of a status tag
The status tag is an internal or external WinCC tag. You can use the following data types for
status tags:
Unsigned 8-bit value
The data type represents the states of up to four alarms.
Unsigned 16-bit value
The data type represents the states of up to eight alarms.
Unsigned 32-bit value
The data type represents the states of up to 16 alarms.
Each alarm or alarm group occupies 2 bits in the status tag.
Note
A status bit of a status tag can only be assigned to one alarm.
Acknowledgment bit of the status tag of an alarm
When an incoming alarm is received and is not acknowledged, the acknowledgment bit has
status "1".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1461
If the alarm was acknowledged, the acknowledgment bit status changes to "0".
Alarm event Acknowledgment bit
Incoming alarm was not acknowledged 1
Alarm acknowledged 0
Acknowledgment bit of the status tag of an alarm group
When at least one incoming alarm is received and is not acknowledged, the acknowledgment
bit status in an alarm group changes to "1".
If all the alarms for the alarm group were acknowledged, the acknowledgment bit is reset to
"0".
Status bit for the status tags of an alarm or alarm group
If an incoming alarm or alarm group is received and has not yet gone, the acknowledgment
bit has status "1". If the alarm has gone, the acknowledgment bit status changes to "0".
Alarm event Status bit
Incoming alarm or alarm group 1
Alarm gone 0
Note
Alarms whose alarm class has the "Alarm without status" property cannot be displayed in a
status tag.
Status tag of a locked alarm
If you lock an alarm in Runtime, the bits in the status tags will be reset or not set, regardless
of the alarm status. The "locked" status of an alarm is not indicated in the status tag.
Note
To visualize the locked status of an alarm group, use the locked tag for the alarm group.
Status tag for chronological alarms
You can use a structure tag to represent the status of a chronological alarm. In the structure
tag, the "EventState" element, for example, represents the status of a chronological alarm.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1462 System Manual, 08/2011,
Position of the Status and Acknowledgment Bit
You can define the position of the status bit within a status tag. The acknowledgment bit must
be a certain distance from this bit. The following definitions apply to the data type:
Data type Position of status bit Distance Position of acknowledgment
bit
Unsigned 8-bit value 0 - 3 4 4 - 7
Unsigned 16-bit value 0 - 7 8 8 - 15
Unsigned 32-bit value 0 - 15 16 16 - 31
Examples
Status Tag of Data Type "32 Bit Unsigned"
Status bit = Position 9
Distance = 16 positions
Acknowledgment bit = Position 25
Status Tag of Data Type "16 Bit Unsigned"
Status bit = 6
Distance = 8 positions
Acknowledgment bit = Position 14
Status Tag of Data Type "8 Bit Unsigned"
Status bit = 2
Distance = 4 positions
Acknowledgment bit = Position 6
Configuring Function Lists for a Change in Value
You can configure a list of functions for the "Value change" event for the tag. You can hide
any non-relevant bits of the tag to reduce the number of possible signal states for the tag. You
can configure the hiding of the non-relevant bits using a C or VB script.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1463
It is not necessary to hide the non-relevant bits if the following condition is fulfilled:
You are using a separate status tag for each alarm.
The non-relevant bits of these status tags always have the value "0".
See also
Tags of an alarm group (Page 1256)
Bit assignment for acknowledgment tags
Introduction
In WinCC you can define an acknowledgment tag for an alarm or alarm group.
Description
Use the acknowledgment tag to:
Acknowledge an alarm
Acknowledge an alarm group
The acknowledgment tag of an alarm group acknowledges all the alarms and alarm
subgroups it contains.
Displaying the acknowledgment status of an alarm group
Linking the acknowledgment to other WinCC components
You can use the acknowledgment tag to link the acknowledgment to other WinCC
components.
If the operator acknowledges an alarm or alarm group in Runtime, then the associated
acknowledgment bit will be set.
Using acknowledgment tags
You have the following options available for configuring acknowledgment tags:
You can configure a separate acknowledgment tag for each alarm or alarm group.
You can compile several alarms or alarm groups in an acknowledgment tag. The
acknowledgment bit allows you to distinguish between alarms and alarm groups.
Each alarm occupies one bit in the acknowledgment tag.
Data Type of an acknowledgment tag
The structure of the acknowledgment tag is not specified. The data type depends on the
number of alarms that you want to represent in the acknowledgment tag.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1464 System Manual, 08/2011,
Resetting the Acknowledgment Bit for acknowledgment tags
You configure the setting or resetting of the acknowledgment bit in WinCC using a button or
via the PLC.
Note
When you acknowledge an alarm group in Runtime, the acknowledgment bit does not indicate
this acknowledgment in the alarm view.
See also "Resetting the acknowledgment bit"
See also "Tags of an alarm group"
See also
Tags of an alarm group (Page 1256)
Tags for Alarm Groups
Bit assignment for lock tags
Introduction
In WinCC you can define a lock tag for an alarm group.
Description
The lock tag of an alarm group is used to evaluate the locked status of that alarm group. You
can define a lock bit in the lock tag for this purpose.
Using the Lock Tag
You have the following options for configuring lock tags:
You can configure a separate lock tag for each alarm group.
You can compile several alarm groups in a lock tag. The lock bit allows you to distinguish
between alarm groups.
When you lock an alarm group in Runtime, the associated lock bit is set in the configured tag.
Data Type of a Lock Tag
The structure of the lock tag is not specified. The data type depends on the number of alarms
that you want to represent in the lock tag.
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1465
See also
Tags of an alarm group (Page 1256)
Bit assignment for display suppression tags
Introduction
In WinCC you can define a display suppression tag for a custom alarm group. The display
suppression tag saves the potential plant states. Only one plant state can be active at one
time. The display suppression tag is therefore set by only one bit.
Description
In the display suppression mask, you can specify which alarm of an alarm group is to be
suppressed for specific plant states in Runtime.
Data type of the display suppression tag
The display suppression tag is an external WinCC tag that stores the plant state. You can use
the following data types for display suppression tags:
Unsigned 8-bit value
Unsigned 16-bit value
Unsigned 32-bit value
Display suppression mask
In the Inspector window of an alarm, you can use the display suppression mask to define the
plant states at which the alarm is not shown. The project engineer sets the bits that define
specific plant states. A plant can have a maximum of 32 states.
You enter the selected plant states as hexadecimal value in the Inspector window of the alarm
under "Display suppression > Mask".
The display suppression tag saves the plant state. When a plant state listed in the mask occurs,
the alarm is no longer displayed. To view the alarms currently hidden due to a plant state, you
can switch the alarm view in Runtime to "Alarms with display suppression".
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
1466 System Manual, 08/2011,
Example
Five examples for the display suppression mask are offered below:
Display suppression mask 0x0. The alarm is displayed.
Display suppression mask 0x1. If the "1" bit is set in the display suppression tag, the alarm
is not displayed.
Display suppression mask 0xD. If the "1", "3" or "4" bit is set in the display suppression tag,
the alarm is not displayed.
Display suppression mask 0x80000008. If the "4" or "32" bit is set in the display suppression
tag, the alarm is not displayed.
Display suppression mask 0xFFFFFFFF. If any bit is set in the display suppression tags,
the alarm is not displayed.
See also
Tags of an alarm group (Page 1256)
Visualizing processes (Professional)
9.3 Working with alarms
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1467
9.4 Working with logs
9.4.1 Working with Logs
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 (Professional)
9.4 Working with logs
WinCC Professional V11.0 SP1
1468 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 "Basic principles for data logging (Page 1107)" and "Basics on alarm logging
(Page 1352)" for more details.
Note
You can use system functions to control the restarting of a log in Runtime.
Visualizing processes (Professional)
9.4 Working with logs
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1469
See also
Log Basics (Page 1468)
Basic principles for data logging (Page 1107)
Basics on alarm logging (Page 1352)
9.4.2 Working with Logs
9.4.2.1 Log basics
Introduction
WinCC provides the following types of logs for logging process data in Runtime Professional:
Fast data log
Slow data log
Alarm logs
Data logs are used to log process data from an industrial plant.
Alarm logs are used to log alarms that occur in the monitored process.
Principle
The different types of logs all have roughly the same structure and largely work in the same
way. They are very clear and easy to configure. With all three types of log you define the same
properties for the log type.
All three log types can be broken down into individual segments. Segmenting can be made
based on size or time.
There are two types of logs available for data logs:
Fast data log
This type of log is used to log process data that change rapidly with a cycle time <= 1 min.
Slow data logs
This type of log is used to log all process data not covered by the "Fast data log" type. In
the configuration, you can specify several parameters to define the tag values to be saved
in a certain type of log.
The alarm log settings are independent of the data log settings.
Visualizing processes (Professional)
9.4 Working with logs
WinCC Professional V11.0 SP1
1470 System Manual, 08/2011,
9.4.2.2 Properties of logs
Introduction
You can configure the basic properties of logs in Runtime Professional, such as the segment
size, in the "Runtime settings > Logging" dialog. The settings configured in this dialog apply
to all the logs in the project.
You configure the special properties for the individual log types either directly in the table of
the respective editor or in the log properties of the Inspector window.
You configure the logical organization of data logs and compressed logs in the "Historical Data"
editor. See "Data logging (Page 1127)" for more details.
There are no comparable logical structures within the log for alarm logs. This means there is
no separate "Alarm log" editor in Runtime Professional. You can only specify whether or not
an alarm should be logged. You configure logging of alarms in the "HMI alarms" editor in the
"Alarms classes" tab. For detailed information, refer to "Basics on alarm logging (Page 1368)".
Properties
The following properties are available for segmenting:
Time period of all segments
Maximum size of all segments
Time period contained in one single segment
Maximum size of a single segment
Time of first segment change
You can also specify how and when backups are to be created.
Additional properties are available for the "Fast data" log type which you can use to divide the
process data between the "Fast" or "Slow" log types.
See "Logging Settings (Page 1154)" for more details.
See also
Data logging (Page 1127)
Configuring alarm logging (Page 1368)
Data logging (Page 1127)
Basics on alarm logging (Page 1368)
Logging Settings (Page 1154)
Log basics (Page 1470)
Visualizing processes (Professional)
9.4 Working with logs
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1471
9.5 Working with recipes
9.5.1 Working with recipes
9.5.1.1 Basics
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1472 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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1473
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1474 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.
Display of recipes
Introduction
You can display recipes in the following ways:
Recipe view
Recipe screen
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1475
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1476 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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1477
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1478 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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1479
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1480 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1481
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1482 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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1483
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1484 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"
"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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1485
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1486 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
9.5.1.2 Displaying and Editing Recipes in Runtime
Recipe screen and recipe view
You can display and edit recipes on the HMI device with a recipe view or recipe screen.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1487
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.
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.
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1488 System Manual, 08/2011,
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 901)
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1489
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:
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".
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1490 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1491
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
Display data record number
Display label
Display table
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:
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1492 System Manual, 08/2011,
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.
See also
Recipe view (Page 901)
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1493
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.
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".
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1494 System Manual, 08/2011,
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".
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.
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1495
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.
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.
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:
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1496 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1497
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.
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
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1498 System Manual, 08/2011,
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.1.3 Configuring Recipes
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.
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1499
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).
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.
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1500 System Manual, 08/2011,
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.
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".
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1501
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1502 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1503
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1504 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1505
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1506 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1507
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1508 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1509
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1510 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1511
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1512 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1513
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1514 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.
6. Click "Export" to start the operation.
Result
The configuration is exported as a CSV file.
9.5.1.4 Using Recipes in Runtime
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.
The table below shows the operation of the display area.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1515
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1516 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1517
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1518 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1519
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1520 System Manual, 08/2011,
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.
Advanced recipe view
Description of the advanced recipe view
Application
The recipe view is used to display, edit and manage data records.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1521
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1522 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1523
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1524 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1525
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1526 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1527
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1528 System Manual, 08/2011,
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1529
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.1.5 Examples
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1530 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1531
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1532 System Manual, 08/2011,
"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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1533
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1534 System Manual, 08/2011,
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.
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1535
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1536 System Manual, 08/2011,
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1537
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.
9.5.2 Working with recipes
9.5.2.1 Principles
Definition and applications
Introduction
Recipes are collections of related data, for example, machine parameter settings or production
data.
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.
Data from technical processes that is continuously stored at longer intervals.
A recipe has a fixed data structure. The structure of a recipe is defined once at the configuration
stage. A recipe contains recipe data records. These differ in terms of their values, but not their
structure.
The project data is stored in an SQL database. Recipe data records are always transferred
completely and in a single pass between the HMI device and the PLC. You can import the
production data in Runtime additionally by a CSV file.
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.
Saving project data
You are using a recipe which is not interconnected with the PLC to save project data. Project
data saved to the recipe can be accessed using scripts in Runtime.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1538 System Manual, 08/2011,
Views
Views relate data from existing recipes that have at least one common feature. They are used
to compile data from the recipes.
Display recipes and views
The recipes and views can be displayed and edited on the HMI device in the following ways:
A recipe view within a process screen
A recipe screen
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:
Enter the data during configuration
If the production data exists already, enter it in the "Recipes" editor during recipe
configuration.
Entering the data in Runtime
Frequent adaptations of production data should be handled directly in Runtime.
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.
You import the recipe data from already swapped-out CSV files.
See also
Recipe view in reports (Page 1678)
Recipe report (Page 1679)
Recipe structure
Introduction
The basic structure of a recipe is illustrated with reference to a 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. The complete data of a manufacturer variant are contained
on one file 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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1539
Recipe
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 elements
Each index card in a drawer is printed identically. All the index cards contain fields for the
different ingredients. Each field corresponds to a recipe element. Each recipe data record
contains the same elements. The records differ, however, in the value of the individual
elements.
Example:
All beverages contain the same elements:
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 (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1540 System Manual, 08/2011,
Recipe Recipe data record Recipe elements Value
Drinks 1 Item Juice
Water 5
Sugar 30
Flavoring 23
Concentrate 80
Coloring F30
2 Item Nectar
Water 15
Sugar 35
Flavoring 20
Concentrate 70
Coloring F35
Recipe collections
A recipe collection is a recipe whose elements are made up from different recipes. Example:
Recipe collection element1 = Recipe1_Recipeelement3
Recipe collection element2 = Recipe3_Recipeelement7
Recipe collection element3 = Recipe2_Recipeelement10
The used recipes must already exist.
A recipe collection is displayed in a recipe view. However, a recipe collection does not have
its own data records but combines all the recipe data records of the used recipes. Example:
If up to 10 recipe data records exist for every recipe in the above example, the recipe collection
covers 10*10*10 = 1,000 data records. You can define a relation in the recipe collection to limit
these data records. Example:
Recipe collection element2 = Recipe collection element3
The relation acts as a filter for the recipe view (see also example below).
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1541
Example
A recipe collection "Label" is created from the "Drinks" and "Order" recipe for label printing.
Fill quantity
Data elements
Number
Data elements
Order Customer
Item
Quantity
Fill quantity
Recipe
Data elements
Drinks
Water
Sugar
Flavoring
Concentrate
Coloring
Best before
Recipe
Item
Label Item
Best before
View
Coloring
Sugar
The figure below shows the "Label" recipe collection. The necessary information for the label
is contained in the "Drinks" and "Order" recipes. The recipe elements "Article", "Sugar",
"Colorant" and "Best before" from the "Drinks" recipe are transferred to the "Label" recipe
collection, the recipe elements "Article" and "Net weight" from the "Order" recipe.
The "Article" recipe element is double:
Drinks.Article, Order.Article, Drinks.Water, Order.Net weight...
The recipe view first shows every combination of these data in its own line. However, the recipe
data of the ordered article and not of another article must be on the label which is ensured by
the following condition:
Drinks.Article = Order.Article
The recipe view is filtered and only the ordered articles with their recipe data displayed line by
line.
Displaying Recipes in Runtime
You have the following options of displaying recipe data in Runtime:
In I/O fields at any position in plant screens
In a recipe view in table format
You can connect a recipe view to a selected recipe or view during configuration. The recipe
view can only access this recipe or view.
Enable the recipe or the view for access.
You can assign various authorizations for access.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1542 System Manual, 08/2011,
Communication with the PLC
Introduction
Data are transmitted in two ways between recipes and the PLC:
By recipe tags with the aid of control tags
By message frames with the aid of raw data tags
"Control tags" communication type
A complete recipe data record is transferred to the recipe tags and vice versa by control tags.
The recipe tags have a communication connection to the PLC
"Raw data tag" communication type
The PLC and the HMI device exchange raw data tags as message frames with a fixed structure.
Raw data tags offer the following advantages:
Several data records transferred between the PLC and the HMI device.
Parts of a recipe data record transmitted.
Use the same raw data tag for several recipes.
See also
Overview (Page 1565)
"Recipes" Editor
Introduction
You can create, configure and edit the following objects in the "Recipes" editor.
Recipes and the corresponding recipe elements and recipe data records.
Recipe collections and the corresponding recipe collection elements and relations
The "Recipes" editor also allows you to enter values in recipe data records.
Structure of the "Recipes" editor
The upper area of the working area in the "Recipes" editor contains the "Recipes" and "Recipe
collections" tabs.
Create the recipes and recipe views using the "Recipes" and "Recipe collections" tabs and
configure these in the Inspector window.
The tab called in the upper area of the working area determines the tabs to display in the
bottom area of the working area.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1543
"Recipes" tab
Recipe 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".
Recipe data records
Define the values of the data records of the selected recipe using the table cells provided
here.
"Recipe collections" tab
Recipe collection elements
Here you define the recipe collection elements of the selected recipe collection by the table
cells. You move recipe collections and recipe collection elements within the table by using
the "Up" and "Down" shortcut menu items.
You define the relations between the recipe collection elements in the "Conditions" box.
Inspector window
Select the Inspector window to configure the corresponding element selected from one of the
tables, for example a recipe collection or recipe data record.
Settings
Recipes
The following settings are available for recipes:
Setting Description
Recipe name 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. Enter meaningful names or
designations which you can assign directly to a product, such as
"Fruit_juice_Orange".
Recipe number This is a unique identification for the recipe within the HMI device.
For the "Raw data tag" communication type, the "PLC" field in the message
frame must correspond to a valid recipe number.
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 not saved in a file
but in a database.
Type You can limit the recipe data records to a maximum number you select
yourself.
Maximum number of
data records
Maximum number of data records in a recipe. This limits the required recipe
memory of the HMI device. The value "0" appears for the "Unlimited" size type.
Communication type Define how the HMI device and PLC exchange recipe data as a rule:
No communication
Raw data tags
Tags
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1544 System Manual, 08/2011,
Setting Description
Raw data tag Tag which is transmitted between the PLC and the HMI device as a message
frame in the "raw data tag" communication type.
Control tag task, ID,
field, value
Four tags which control the data transmission between the recipe and recipe
tags and therefore the PLC in the "tags" communication type.
For reading
For writing
Name of the authorization which has read, write access to the recipe in
runtime.
Last modification
Last user
Change information of a recipe is displayed in Runtime.
Tooltip Help text for the recipe which is shown to the operator in Runtime.
Recipe elements
You can make the following settings on the "Elements" tab:
Setting Description
Recipe element name 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. Enter meaningful names or
designations which you can assign directly to a product, such as
"Fruit_juice_Orange".
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 Data length of the recipe tag, depending on the data type.
Default value This is used as the default entry when you create a new recipe data record.
Minimum value The smallest representable value of a number-based recipe tag, depending
on the type of data.
Maximum value The largest representable value of a number-based recipe tag, depending
on the type of data.
For reading
For writing
Name of the authorization which has read, write access to the recipe in
runtime.
Value required The recipe element has a value other than zero.
Unique values A value for the recipe element may only occur once in all recipe data records.
Example recipe element "Order number".
Fast search The value of the recipe element is indexed for faster searching.
Tooltip Infotext about the recipe element that the operator sees in Runtime.
Recipe data records
You can make the following settings on the "Data records" tab:
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1545
Setting Description
Recipe data record
name
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. Enter meaningful names or labels that
you can assign directly to a product, such as "Product_numbers".
Recipe data record
number
Identifies a recipe data record uniquely within the recipe.
Recipe element name Name of the created recipe element The values which the recipe element
has in the different recipe data records (lines) are saved under this name. A
value forms a recipe data record respectively with the values of the other
recipe elements in a line. You can already save the values during the
configuring.
Last modification
Last user
Modification information items of a recipe data record are displayed in
runtime.
Comment Comment about the recipe data record
9.5.2.2 Configuring Recipes
General configuration procedure
Configuring steps
Follow the steps outlined below to create a recipe:
Step Task
1 Define the structure of the recipe.
2 Define the communication mode for the recipe.
3 Define the control tags or raw data tags according to the communication mode
selected.
4 Create the recipe and define its properties.
5 Create the recipe elements in accordance with the structure planned.
6 Create the recipe data records.
7 Configure views of multiple recipes, if required.
8 Configure a screen which contains a recipe view and interconnect this recipe
view with the recipe or view.
Or:
Configure a screen which contains I/O fields and buttons. Configure button
functions for reading and writing the values of recipe data records.
Note
Runtime API
The Runtime API provides you with extensive uaArchive functions to edit recipes and recipe
views (see section "Interfaces > Runtime API", subsection "Auto-Hotspot").
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1546 System Manual, 08/2011,
Configuring Recipes and Elements
Creating a New Recipe
Introduction
Create the new recipes using the "Recipes" tab of the "Recipes" editor.
Naming the recipe
Do not use keywords or reserved words of the SQL database language for recipe names (see
subsection "SQL keywords (Page 1601)").
Recipes with date or time stamp
If you use data or time data, make sure that the system setting for time and date on the
configuring computer matches that on the target system. Example: You load a recipe data
record on the target system at 13:55 in which the processing time 14 h is stored. If it already
14:05 on the target computer, the recipe will not be processed. If an operator processes the
recipe, modification information is 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.
Requirement
You have created the control tags or the raw data tag.
The "Recipes" editor is open.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1547
Procedure
Create a recipe as follows:
1. Double-click the first empty table row in the "Recipes" tab of the "Recipes" editor.
2. Select "Properties > General > Settings > Name" in the Inspector window and enter a
descriptive recipe name.
The name identifies the recipe uniquely within the project.
3. Select the "Display name" field to enter the language-specific name to be displayed in
Runtime.
4. Define whether or not the recipe data records are limited to a specified maximum number
in the area "Size" under "Type".
5. If the size type is limited, specify the maximum number of recipe data records of a recipe
under "Number of data records".
6. Specify the "Communication type" under "Properties > Communication":
If you have selected "Raw data tag", create a raw data tag and select it under "Raw data
tag".
Select "No communication" if you use the recipe only to save project data.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1548 System Manual, 08/2011,
7. Select the control tags for access to the recipe under "Properties > Control tags" if you have
selected the "Tags" communication type.
8. Define under "Properties > Security" which operator authorizations have read and write
access to the recipe in Runtime.
9. Under "System fields", specify whether to display the "Last modification" and "Last user"
entries.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1549
Result
You have created the recipe.
Creating Recipe Elements and Data Records
Introduction
Select the "Recipe elements" tab in the bottom area of the "Recipes" editor to set up the
elements for the selected recipe. You can also enter the recipe element values in the "Recipe
data records" tab.
Requirement
The tags for the recipe have been created.
You have created the recipe.
The recipe is selected in the "Recipes" editor.
Procedure
Create a recipe element as follows:
1. Double-click the first empty table row in the "Recipe elements" tab.
2. Select "Properties > General > Settings > Name" in the Inspector window and enter a
descriptive name for the recipe element. This name must be unique within a recipe.
3. Select the "Display name" to enter the language-specific name to be displayed in Runtime.
4. When the recipe has the "Tags" communication type:
To link the recipe element to a tag, select a tag under "Properties > Values > Settings". The
data type will be displayed below.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1550 System Manual, 08/2011,
5. For a "String" data type, also specify the maximum length of the string under "Data length".
The "Settings" area on the right shows the value range for number-based data types, for
which you can also specify a default value.
6. When the recipe has the "Raw data tag" communication type or "No communication": Select
the "Data type" and also the "Data length" of the recipe element for the "String" data type.
7. Define under "Properties > Security" which operator authorizations have read and write
access to the recipe element in Runtime.
8. Define in "Properties > Extras" which conditions the values of the recipe element must
satisfy. For faster search, the values can be indexed:
9. Double-click the first empty table row in the "Recipe data records" tab to set up a recipe
data record.
10.Enter the desired value for the recipe element in the table editor.
Result
The recipe element and a corresponding recipe data record are created with one value.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1551
Importing recipes into the configuration and exporting them again
Introduction
You can export recipes as a CSV file and import them again into the configuration.
Note
You cannot import or export data records from recipe views.
Application case
You export recipe data to store and back up recipe data long-term on a computer.
You export the recipe data to an HMI device to standardize and distribute recipe data. You
change the CSV file Microsoft Excel and import the CSV file to all HMI devices which require
the same recipe data.
You want to exchange recipe data between different projects. You change the recipe data in
Runtime. To transfer the changed recipe data to WinCC ES, export the recipe data records to
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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1552 System Manual, 08/2011,
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. Select the desired CSV file with the recipe data under "File name".
4. Under "Strategy", define whether a recipe data record in the CSV file overwrites an existing
recipe data record in WinCC with the same recipe data record number.
5. 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.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1553
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. Select a path for the CSV file under "File name".
4. Select the desired recipe under "Recipe name".
5. Select all recipe data records or limit the selection to certain recipe data record numbers
under "Select content".
6. Click "Export" to start the operation.
Result
The configuration is exported as a CSV file. The list separator is the semicolon
"RecipeElement_1;RecipeElement_2". The decimal separator is a period, e.g. "3.14".
Procedure for changing the recipe structure
Introduction
Different recipe structures can occur in the following situations:
Due to changes during commissioning
If a machine is upgraded by the machine manufacturer (retrofit)
When CSV files are imported, the structure of the CSV file can differ from the recipe
structure.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1554 System Manual, 08/2011,
Nevertheless, you can still use any recipe data records already created.
CAUTION
When a tag is renamed, the assignment is lost.
Effects
If the structure of the CSV file differs from the structure of the recipe, deviations are handled
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.
Configuring recipe views
Creating a recipe view
Introduction
A recipe view is a set of recipe elements from different recipes. Example: Recipe view "Water
consumption".
Water from the "Fruit juice drink" recipe
Water from the "Juice" recipe
Water from the "Nectar" recipe
You can link recipe elements to form relations, such as "Nectar.Water >
FruitJuiceDrink.Water". In recipe view only those data records will be displayed in Runtime
that satisfy the relation. In the example, these are the records in which the water requirement
of the "Nectar" recipe is greater than that for "Fruit juice drink".
Assemble the recipe views from the recipe elements in the "Recipe views" tab of the "Recipes"
editor. Select the recipe elements from the recipes to be included in the recipe view and set
their relation. The relation expresses a condition. Only those combinations of recipe elements
which satisfy the condition (true) are displayed in the recipe view.
You can also edit recipe view data in Runtime. The data you have edited are applied to the
original recipe in Runtime.
The recipe view does not support the following actions:
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1555
Creating new recipe data
Deleting recipe data
Requirement
You have created at least two recipes.
The recipes are in the same database on the same HMI device.
The recipes have at least one identical recipe element in the same data format.
Creating recipe views
Create a recipe view as follows:
1. Double-click the first empty table row in the "Recipe views" tab of the "Recipes" editor.
A new recipe view is generated.
2. Enter a name for the recipe view under "Properties > General > Name " which indicates its
function.
3. Select the "Display name" to enter the language-specific name to be displayed in Runtime.
Creating recipe view elements and relations
Proceed as follows to create a new element for the recipe view and the relation:
1. Double click the first free table line in the "Recipe view elements" tab.
2. Under "Properties > General > Recipe element", select the recipe element to insert in the
view.
3. Create other recipe view elements as required.
4. Select the recipe view in the "Recipe views" tab.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1556 System Manual, 08/2011,
5. Select a recipe view element and the desired operator as a left and right operand in the
inspector window under "Properties > Relation > Relation".
6. Click the "Add" button.
The relation appears under "Condition". If a condition was already defined there, the new
relation with the logical operator "AND" is added. You can edit the condition.
7. Change the order of the recipe view elements as required with drag&drop.
Result
The recipe view is created and a condition defined. Only those combinations of recipe elements
which satisfy the condition are displayed.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1557
9.5.2.3 Configuring the visualization of recipes
Displaying recipes
Introduction
Recipes and recipe views are displayed on the HMI device as follows:
In a recipe view
In individual I/O fields
Recipe view
The recipe view displays the recipes and views in table format. Each recipe data record uses
one line.
The picture below contains an example of a recipe view.
Operators use the recipe view in Runtime and, for example, create new data records or import
recipes. You transfer a recipe data record to the recipe tags and vice versa with two buttons
in the recipe view.
Note
You select a recipe or recipe view in the configuration of a recipe display. The operator can
change the selection and other properties in Runtime.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1558 System Manual, 08/2011,
NOTICE
Data source
The recipe display only accesses one recipe or recipe view respectively.
Recipe view
An operator can only change the displayed recipe data in Runtime. The creation and deletion
of data records and their transfer from/to the PLC is not possible.
Recipes in the screen
You can show recipe elements in I/O fields alternatively instead of a preconfigured recipe
display. The following screen shows an example for a screen with configured I/O fields in the
"Tags" communication type.
The blue fields at the top show the values of the recipe tags which have a communication
connection with the PLC. The yellow fields at the bottom show the contents of the four control
tags. In the example the blue recipe values were written into recipe data record number 3 (task
= 6) and the number of errors = 0 returned.
See also
Control tags (Page 1567)
Properties of the recipe view
Introduction
The recipe view visualizes recipe elements in table format on the screens. Operators can edit
recipe data in the recipe view in Runtime.
Configuration of the recipe view
The following optional recipe view configurations are available:
General > Display: You select a recipe or recipe view as a data source and define whether
recipe data records can be edited, inserted or deleted.
General > Print job
The recipe view is automatically linked by logical operation with the system print job for
recipe views. Create a logical link to the recipe view for any custom print jobs or system
print jobs.
General > Time
Define the time base for the "Last access" display, for example the coordinated universal
time (UTC). You can include the time base selected for output in Runtime.
Appearance, layout, text format
You define colors and design, size and position of the recipe display, font type and font size.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1559
Window
You define the font size, window header of the recipe display and other window properties.
Table
You define the appearance of the column headers, table and boundary lines and the
behavior for selecting and sorting data records.
Table > Mark
Determine whether lines or only cells can be marked with the mouse.
Configure the properties of the selection rectangle which can be shown around the marked
cells or lines of the table.
Configure the marking colors for the markable cells and/or lines as required. The color
defined by the system for the marking is used with the "Automatic coloring" property.
Table > Sorting
Determine whether sorting is to take place and if so, with click or double click on the column
header. Define the order of sorting which is to run cyclically when clicking or double clicking
the column header: either sorting ascending - descending or ascending - descending - no
sorting
Configure the sorting symbol and sorting index which are to be shown right-justified in the
column header. You show sorting sequence and sorting order of the columns.
If you activate the "Use sorting key" option, the sorting symbol is displayed as a sorting key
above the vertical scrollbar. You sort the selected column in the configured sorting order
with a mouseclick on the sorting key. The sorting key is not displayed if there is no vertical
scrollbar in the table.
Columns
You determine which recipe elements are displayed in what order in Runtime. You apply
write protection to certain elements and determine the width and formatting.
Some columns can also show the content and header as symbols. Determine how these
columns are displayed in the "Layout" field. The text and symbol can be displayed together.
Filter
As a filter criterion you define a condition for a recipe element and link several conditions.
The data record is not displayed until all the filter criteria are satisfied.
Toolbar
In addition to the appearance of the toolbar you define which buttons are visible in what
order in Runtime and with what operator authorization they can be operated.
Activate the buttons in the list which you need for operating the WinCC-Control in Runtime.
Information about the function of the individual buttons can be found in the subsection
"Operation in Runtime"
Define a hotkey for a button if necessary.
If you assign operator authorizations to the individual buttons, the button is only released
in Runtime for the users who have the appropriate operator authorization.
If you deactivate the "Active" option for a button, the activated button is displayed in Runtime
but cannot be operated.
Status bar
In addition to the appearance of the status line, you define what information is displayed in
the status line in Runtime, e.g. the recipe data record number.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1560 System Manual, 08/2011,
Data export
A standard file name and a standard directory are already entered by switch tags. However,
you can assign your own file names and directory names.
You can use the following switch tags.
@OBJECTNAME: Object name of the recipe display, see "Properties > Miscellaneous"
@PROJECTPATH: Project directory
@CURRENTDATE: Current date
@CURRENTTIME: Current time
Safety
You determine whether and how changes to the properties of the recipe display can be
saved in Runtime and after a screen change and which authorization is necessary for
changing.
Miscellaneous
You define the visibility and layer for the recipe display.
Configuring a recipe view
Requirement
You have created a recipe or a view.
You have created a screen and the "Screens" editor is open.
Procedure
Configure a recipe view as follows:
1. Drag the "Recipe display" object from the "Controls" palette of the "Tools" task card into
the screen.
2. Select the desired recipe or view in the inspector window under "General > View".
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1561
3. Define the write and read rights for the recipe display in Runtime under "General > Allow
in Runtime".
4. Select "Appearance," "Layout," and "Text format" to define additional display options for
the recipe view.
5. Select "Properties" > Columns" to define the recipe elements which will be visible and write-
protected in Runtime.
6. Select "Toolbar" to define the recipe view buttons to be available in Runtime.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1562 System Manual, 08/2011,
7. Select "Status bar" to define the scope of information to display in the status bar in Runtime.
8. Select "Filter" to define the filter criteria for recipe elements in Runtime.
9. Select "Sort" to define the sorting criteria for recipe elements in Runtime.
Result
The recipe view is configured.
Exporting recipe data in Runtime
Introduction
In Runtime you export the recipe data with a button in the recipe display. You configure
operation of the data export in Runtime.
How to configure the operation of the data export
1. Define a file name and a directory for the export file under "Properties > Data export".
The file name may be made up of names you select yourself and the following switch tags:
@OBJECTNAME: Object name of the recipe display
@PROJECTPATH: Project directory
@CURRENTDATE: Current date
@CURRENTTIME: Current time
1. Define the file extension, e.g. "CSV".
2. Define the scope of the data export:
All Runtime data are exported.
Selected Runtime data are exported.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1563
3. Configure the operation of the data export during runtime. Define:
The "Data export defaults" are displayed in runtime.
The user may change the file name or the directory.
4. If "Show dialog" is deactivated, the data are exported immediately to the defined export file
on pressing the "Export log" button.
5. Save the project.
6. Activate the "Export log" button under "Properties > Toolbar".
Results
In Runtime you can export all or selected recipe data to a defined file with the button.
Configuring persistence
Introduction
A user can configure WinCC-Controls in Runtime. You define what effect the online
configuration has in Runtime.
The changes configured in Runtime are saved separately from the screen in the engineering
system. The screen is thus retained in its original configuration.
Procedure
1. Select "Properties > Safety > Persistence > Online configuration" which you can only
operate in the engineering system. The online configuration can then be defined
permanently in Runtime:
"No persistence" The online configurations are not retained in Runtime. This default
leaves the user no option in Runtime. The online configurations are lost the next time
the screen changes and with deactivate/activate.
"Persistence" This default leaves the user the options of "reject", "retain" or "reset". With
the "retain" option the online configurations are retained the next time the screen
changes and with deactivate/activate.
"Persistence in Runtime". This default leaves the user the options of "reject", "retain" or
"reset". With the "retain" option the online configurations are retained the next time the
screen changes but are lost when the project is deactivated/activated.
NOTICE
In case of a user change, the different configurations are not saved until you have
executed a screen change.
2. Define what operator authorization the user must have to carry out online configuration.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1564 System Manual, 08/2011,
3. "Screen change characteristics" can be operated in the engineering system and in Runtime
with the defaults "Persistence" and "Persistence during Runtime". The "reset" option can
only be operated in Runtime because the original configuration is in the engineeringm
system.
Select one of the three effects of the online configuration in the next screen change:
Activate "Reject changes" so that the online configuration only exists for as long as the
screen is selected. The changes are rejected at the next screen change. The recipe
display appears as configured if you select the screen again.
Activate "Retain changes" so that the online configuration is not lost at the next screen
change.
Activate "Reset" so that the configured screen is saved again in Runtime. All online
configured changes are lost.
NOTICE
The screen is also replaced in Runtime when saving the screen or in Delta compiling
(change loading). All online configured changes are lost.
4. Save the configuration.
9.5.2.4 Data transfer to the PLC
Overview
The options for transferring recipe values between the PLC and HMI device are as follows:
No data transfer
"Tags" communication type
"Raw data tag" communication type
No data transfer
The recipe is not used for transferring recipe data to the PLC but as a data memory and user
log: You store values which belong together in data records to which you have multiple access.
In the simplest case an operator switches between the recipes in a recipe view. The respective
recipe data are loaded into the recipe tags and processed further there.
"Tags" communication type
Recipe tags transfer the recipe values to the PLC. Vice versa the values from the PLC are
written into a recipe data record by recipe tags. Control tags control the data transfer. The
following tasks are started automatically by the desired entry into the corresponding control
tags.
Write data records into the recipe tags and therefore into the PLC
Read data records out of the recipe tags and therefore out of the PLC
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1565
Delete data records
Create new data records
Note
A complete data record is always transferred in the "Tags" communication type. Transfer
of recipe data from a recipe collection is not possible.
"Raw data tag" communication type
The automation system sends the raw data tag as a message frame to the HMI device as an
active partner. The message frame contains the following:
Desired target recipe
Desired target recipe data records
Job e.g. "Read", "Write" or "Delete"
New recipe values, e.g. for "Write" job
The HMI device returns recipe and acknowledgement data as a message frame.
The "BSEND/BRCV" function of the S7 communication is used for the data exchange. The
consecutive number of the recipe serves to identify the recipe uniquely in the PLC (PLCID).
The PLC requires a user program which executes the following in Runtime:
Collect data if necessary via I/O fields in the HMI device.
Check data.
Create raw data tag as a message frame.
Send message frame.
If you want to start creation of the message frame from the HMI device, you configure functions
in the screen which start the user program.
Note
The following is possible in the "Raw data tag" communication type:
Transfer of an individual recipe element
Transfer of an entire recipe data record
Transfer of multiple recipe data records
Data transfer from the recipe view or by control tags is not possible.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1566 System Manual, 08/2011,
Control tags
Introduction
With the "Tags" communication type in the recipe, you transfer the recipe data between the
PLC and the HMI device using recipe tags. The data transfer is controlled by four control tags
which are assigned fixed to a recipe. Other control tags can be assigned to another recipe.
Data transfer is started automatically once you have entered the required value at the
corresponding control tag.
NOTICE
All four control tags must always be specified in a recipe to ensure that it works. Do not change
the data type of the control tags.
Note
You must implement access protection for the control tags of a protected recipe separately
using the object properties of the screen, I/O field or button, for example.
Control tags
Control tag Required data type Meaning
ID Long Number of the recipe data record within the assigned recipe
Job Long Read out of the recipe tags, write into
the recipe memory:
6
Read out of the recipe memory, write
into the recipe tags:
7
Delete in the recipe memory: 8
After the job has been carried out, an error ID can be seen in the "Job" control
tag:
No error 0
Error -1
Field String The name of the recipe element
Value String The value of the recipe element
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1567
Requirement
Communication type is set to "Tags" in the recipe.
You have configured a process screen with all I/O fields required for process tags and
control tags of the recipe.
Example:
Inserting the control tag
The following control tag combinations are supported:
"ID" and "Job" control tags
The control tag "ID" indicates the number of the recipe data record which is transferred.
The "Job" control tag indicates whether the selected recipe data record is written, read or
deleted (6, 7, 8) in the recipe memory of the HMI device.
"Job", "Field" and "Value" control tags
The recipe data record is selected for the data transfer whose recipe element "Field" has
the recipe value "Value". Example field = "Water", value = "5 liters".
The "Job" control tag indicates whether the selected recipe data record is written, read or
deleted (6, 7, 8) in the recipe memory of the HMI device.
NOTICE
Different data records may not contain the same recipe value in the "Field" recipe element
You have to activate the "Unique values" checkbox under "Properties > Options" for the
recipe element. Otherwise no clear assignment of the recipe data record by the value is
possible and the first data record which satisfies the "Value in field" condition is used.
If the type "String" is assigned to the element, you must enclose the entry in the "Value"
I/O field in inverted commas (such as 'Cola Light').
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1568 System Manual, 08/2011,
More combinations of values for the "ID" and "Job" control tags
ID Job = 6 Job = 7 Job = 8
-1 Data record from the recipe tags is
read and appended to the end in the
recipe in the recipe memory.
- Data record with the lowest ID is
deleted in the recipe in the recipe
memory.
-6 Data record from the recipe tags is
read and written into the recipe data
record with the lowest ID in the recipe.
Data record with the lowest ID is
written in the recipe into the recipe
tags.
Data record with the lowest ID is
deleted in the recipe in the recipe
memory.
-9 Data record from the recipe tags is
read and written into the recipe data
record with the highest ID in the recipe.
Data record with the highest ID is
written in the recipe into the recipe
tags.
Data record with the highest ID is
deleted in the recipe in the recipe
memory.
See also
Displaying recipes (Page 1558)
Using the recipe screen (Page 1590)
Raw data tag
Data Transfer via Raw Data Tags
This section describes the transfer of recipe data between the HMI device, and PLC using raw
data tags. The BSEND/BRCV function is used in the PLC. The message frame containing the
raw data tag is actively sent by the PLC.
The message frames may contain one or more write or read jobs.
Data transfer procedure
1. The PLC sends the message frame to the HMI device.
2. The HMI device returns the following:
Data, if requested
A processing acknowledgement
The HMI device returns a separate acknowledgement for every job.
Note
The PLC is the active partner in this data transfer, so it is the PLC that must start the required
function. On the HMI device, you can start the required function by means of a change in
value of an external tag, for example, and the corresponding analysis in the PLC.
Do not use the "Job type" parameter to start the data transfer. The "Job type" parameter used
in the job, or acknowledgement header only works with respect to recipes.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1569
Message Frame Structure for Jobs
General message frame structure
Structure of a message frame for sending jobs:
Length
Message frame header 16 bytes
Job header 1 12 bytes
Data for job 1 n bytes
Job header 2 12 bytes
Data for job 2 n bytes
Job header n 12 bytes
Data for job n n bytes
Example
The total length of a message frame with a job, and 10 bytes of job data is 38 bytes.
16 bytes +12 bytes +10 bytes = 38 bytes
Structure of the message frame header
16 bytes are needed for a message frame header.
Function of the field Comment Byte
Message frame length in bytes LSB
1
) Max. length 4091 bytes 1
Message frame length in bytes 2
Message frame length in bytes 3
Message frame length in bytes MSB
2
) 4
Transfer type "1" from the HMI device
"2" from the PLC
5
Reserved 6
Number of jobs in the message frame
LSB
1
)
7
Number of jobs in the message frame
MSB
2
)
8
Number of the recipe (PLCID) 1. character, in ASCII 9
Number of the recipe (PLCID) 2. character, in ASCII 10
Number of the recipe (PLCID) 3. character, in ASCII 11
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1570 System Manual, 08/2011,
Function of the field Comment Byte
Number of the recipe (PLCID) 4. character, in ASCII 12
Number of the recipe (PLCID) 5. character, in ASCII 13
Number of the recipe (PLCID) 6. character, in ASCII 14
Number of the recipe (PLCID) 7. character, in ASCII 15
Number of the recipe (PLCID) 8. character, in ASCII 16
Least significant byte
Most significant byte
Note
The number of the recipe is defined automatically in the "Recipes" editor during configuration,
but can later be changed as needed. Enter the number in ASCII format in the message frame.
Structure of a job header
12 bytes are needed for a job header.
Function of the field Comment Byte
Job length in bytes LSB
1
) 1
Job length in bytes MSB
2
) 2
Job type see
"Description of job types and error codes"
3
Reserved 4
Field number LSB
1
) 5
Field number MSB
2
) 6
Data record number LSB
1
) 7
Data record number 8
Data record number 9
Data record number MSB
2
) 10
Selection criterion LSB
1
) Element value entered or element number as selection
criterion.
11
Selection criterion MSB
2
) not if 0 12
Least significant byte
Most significant byte
The field number corresponds to the consecutive number of the recipe element.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1571
Message Frame Format for Acknowledgements
General Structure of an Acknowledgement Message Frame
Structure of the acknowledgment message frame to the PLC:
Length
Acknowledgement header 24 bytes
Acknowledgement data
Structure of an acknowledgment header
24 bytes are needed for an acknowledgement header
Function of the field Comment Byte
Message frame length in bytes LSB
1
) Max. length 4091 bytes 1
Message frame length in bytes 2
Message frame length in bytes 3
Message frame length in bytes MSB
2
) 4
Transfer type "1" from HMI device,
"2" from the PLC
5
Reserved 6
Job type See
Description of "Job Types and Error Codes"
7
Error code See
Description of "Job Types and Error Codes"
8
Reserved 9
Reserved 10
Field number LSB
1
) 11
Field number MSB
2
) 12
Data record number LSB
1
) 13
Record number 14
Record number 15
Data record number MSB
2
) 16
Number of the recipe (PLCID) 1st character, in ASCII 17
Number of the recipe (PLCID) 2nd character, in ASCII 18
Number of the recipe (PLCID) 3rd character, in ASCII 19
Number of the recipe (PLCID) 4th character, in ASCII 20
Number of the recipe (PLCID) 5th character, in ASCII 21
Number of the recipe (PLCID) 6th character, in ASCII 22
Number of the recipe (PLCID) 7th character, in ASCII 23
Number of the recipe (PLCID) 8th character, in ASCII 24
Least significant byte
Most significant byte
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1572 System Manual, 08/2011,
Acknowledgement data
The acknowledgement can contain the following:
The required recipe data record
The required content of the element
No data
Configuring raw data tag
Raw data tags of the "SIMATIC S7" channel
Introduction
A tag of the type raw data type is a data telegram on a transport level. The contents of the raw
data tag are not fixed and therefore only the sender and the receiver can interpret the
transmitted data. There are no format changes in WinCC for this data type. Maximum length
is 65535 Byte.
WinCC distinguishes between two types of raw data tags: Raw data tag for free application
use and raw data tag for handling S7 functions.
Raw data tag for free application use
Raw data tags for free application use are used for transferring user data blocks between
WinCC and PLC and handle only user data. It distinguishes between:
Raw data tag as byte array
Raw data tag for BSEND/BRCV functions
Raw data tag for handling S7 functions
These raw data tags do not have any channel-specific header and are normally used by the
message system and for process data entry in WinCC.
No further description is needed here as these are tags and functions internal to the channel.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1573
Creating raw data tag
Procedure
1. Create a new connection, for example, "SIMATICS7".
2. In the "Parameters" tab, select "WinCC RT Prof connection > Send/receive raw data block".
3. Under "Connection", specify the hexadecimal value of the connection ID for the connection
resource that was assigned during the configuration of the controller.
4. Create a new tag "Raw data tag_1".
5. Select "SIMATICS7" as "Connection".
6. Select the "Raw" "Data type" and specify a sufficient "Length" in bytes.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1574 System Manual, 08/2011,
7. Select "BSEND / BRCV" under "Raw data."
8. Specify the "R_ID" parameter, which was assigned in the configuration of the controller.
9. Create a new recipe.
10.In the Inspector window under "Properties > Communication" select "Raw data tag" as
communication type and "Raw data tag_1" as raw data tag.
11.Create the recipe elements and recipe data records. Ensure that the recipe number
matches the "PLC" field in the message frame.
Raw data tag for BSEND/BRCV functions of S7 communication
Introduction
Raw data tags for "BSEND/BRCV" functions are used for transferring user data blocks between
WinCC and AS and handle only user data.
This raw data type can be used to access the "BSEND/BRCV" functions of S7 communication.
The functions are available in a S7-400 or a S7-300 using CP343. The initiative of data transfer
always lies with the sending partner; hence "BSEND/BRCV" functions can also be used to
implement event-controlled or sporadic data block transfers.
For resource reasons, it is advisable to keep the number of BSEND/BRCV raw data tags low.
Resource limitations for using S7 functions "AR_SEND" and "BSEND/BRCV" for
communication with S7-400
The maximum data volume that can be sent simultaneously using AR_SEND and/or BSEND/
BRCV functions from AS to WinCC is limited to 16 kByte.
Example:
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1575
1x BSEND with a max. of 16 Kbytes
1x AR_SEND with 8 kBytes + 1x BSEND with 8 kBytes
1x AR_SEND with 10 Kbytes + 1x AR_SEND with 2 Kbytes + 1x BSEND with 4 Kbytes
Note
If the data block of a write job is transferred to AS and has not yet been deleted or fully
deleted from the receiving buffer, then the next write job will be rejected with an error
message. During such an error display, write jobs with R_ID > 0x8000 0000 are written
to a connection-specific queue and the system tries to repeat the write job for 6 seconds.
The responsibility for time co-ordination for transfer rests with the user and needs to be
noted as shorter time intervals for write jobs.
Configuring a PBK Connection for Using "BSEND/BRCV" functions
"BSEND/BRCV" functions can only be used via a "hard-configured connection", a so-called
PBK connection (programmed component communication). To configure a hard-configured
connection, you must mention a connection resource (hex: 10 ... DF) in the connection
parameters. This connection resource will be assigned by STEP 7 when the connection is
configured within the PLC. The connection must be configured in AS as passive connection
end-point.
A hard-configured connection can also be used to handle "normal" read and write jobs. If very
large data areas are to be transferred via the connection, then the data blocks are transferred
in multiple PDUs. For performance reasons, it would therefore be better to create a separate
connection for "BSEND/BRCV" functions.
Raw data tag for "BSEND/BRCV" functions with the "R_ID" parameter
Raw data tags for transferring "BSEND/BRCV" data blocks are configured as raw data of type
"BSEND/BRCV" with a "R_ID". The data length is derived implicitly from the sent or received
data volume.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1576 System Manual, 08/2011,
A decimal value of 1 to 999999 must be specified for "R_ID". The R_ID is assigned at the time
of configuration in AS and is used for distinguishing multiple data block transfers over one
connection. The send and receive calls are always notified with reference to this R_ID in the
underlying communication sub-system (SIMATIC Device Drivers). A raw data tag is thus
assigned to one unique R_ID.
Sending a "BSEND/BRCV" raw data tag
Sending a "BSEND/BRCV" raw data tag takes place in the same way as writing a "normal"
process tag. After sending the data block and receiving a positive acknowledgement from AS,
the data block is transferred to the image of the Data Manager.
Receiving a "BSEND/BRCV" raw data tag
"BSEND/BRCV" raw data is sproradically sent to the channel on the initiative of the AS. Hence
it is not possible to explicitly read S7 raw data tags.
The BSEND/BRCV mechanisms do not include any synchronization functions. If no user has
logged in to receive the data during the start-up phase, the data blocks sent by AS will bounce
on the receiver side. Hence, the user has to take care of the synchronization and, for e.g.,
release the sending direction on the AS by setting a flag with a data word.
Job types and error codes
Description of the job types
Type Description
4 The existence of the recipe is checked.
5 All data records are deleted from the recipe.
6 The data record is requested from the HMI device and is written to the PLC.
7 The data record from the PLC is written to the required data record.
8 The data record is deleted from the recipe.
9 The element of the required data record is requested from the HMI device and is written
to the PLC.
10 The element of the required data record is written to the required data record.
Description of the error codes
Group No. Description Possible Fault Causes
General 0 The function has been executed. --
Recipe 2 Data not available No recipe configured with this PLCID.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1577
Data record 101 Data not allowed Recipe structure does not tally, such as
number or type of fields.
Failed data record insertion or update.
Possible causes:
Recipe is of the "limited" type.
A min. or a max. value is configured
for a field.
Incorrect criterion
Data record 102 Data not available For job type 6 only:
No data available
Criterion is incorrect.
Field 201 Data not allowed For job type 10 only:
Criterion is incorrect.
Possible causes:
Field not found.
A min. or a max. value is configured
for a field.
Field 202 Data not available For job type 9 only:
Criterion is incorrect.
No field found corresponding to
criterion.
General 254 Function not found --
General 255 Undefined error --
Differences between data formats
Introduction
The data formats in WinCC conform to the Intel and Microsoft data formats. The least significant
byte is saved first and the most significant byte is saved last. This data format is very common
and is generally known as the "Intel format".
The data formats in WinCC differ fundamentally from the data formats in the PLCs.
Intel format
In the Intel format, the decimal number 300 is stored as follows:
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Binary 0 0 0 0 0 0 0 1 0 0 1 0 1 1 0 0
Hex 0 1 2 C
According to the Intel Format, the decimal number 300 corresponds to the hex-number 12C
(1*256 + 2*16 + 12*1).
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1578 System Manual, 08/2011,
SIMATIC format
In SIMATIC format, the least significant byte is are stored in the most significant digits. In
SIMATIC format, decimal number 300 is stored as follows:
Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Binary 0 0 1 0 1 1 0 0 0 0 0 0 0 0 0 1
Hex 2 C 0 1
According to the SIMATIC format, decimal number 300 corresponds to hex number 2C01.
If hex number 2C01 is interpreted according to Intel format, it corresponds to decimal number
11265.
There are function blocks that convert the data for PLCs from the SIMATIC S7 series. You
must always call up the blocks before and after data transfers between the PLC and WinCC.
The function blocks are available for download from the Siemens Customer Support website
in the Internet. The compressed file ANSI_S5.EXE is then loaded. ANSI_S5.EXE contains the
"IEEE:GP" function block.
Active sending is described in the reference manuals for the PLCs or CPs (communication
processors).
9.5.2.5 Operation in Runtime
Recipe view
Functional scope
The recipe view offers access to user logs, the recipes and recipe collections. In runtime, you
can:
Online configuration of recipe view
Create, delete or modify new data records
Scrolling in recipes
Read and write tags for direct tag link
Importing and exporting recipes
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1579
Defining selection criteria to display only a certain part of the recipes
Defining sorting conditions for the displayed recipe elements
Properties
You connect a recipe view with a recipe or recipe collection in the configuration. The online
configuration and changing of selected recipe values in Runtime can be protected against
unauthorized access respectively by own operator authorizations. If you cancel the access
protection, you must reconnect the recipe view with the recipe in the configuration dialog box.
The access protection is queried when the recipe view screen opens.
If the user has no authorization to read a recipe element, the corresponding column is not
displayed in the table.
If the user has no authorization to write a recipe element, the user cannot edit the data of
the the corresponding column in the table.
Access protection for the control tags must be configured separately by the object properties,
e.g. of a screen, an I/O field or a button.
Using the Recipe View
Mouse and keyboard operation
Introduction
You operate the recipe view in Runtime by buttons in the toolbar. If you do not want to use the
toolbar for operation, you can write the "ID" of the desired button in the "ToolbarButtonClick"
object property with any dynamization type.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1580 System Manual, 08/2011,
Overview
Symbol Description ID
"Help"
Calls the help for the recipe view.
1
"Configuration dialog"
Opens the configuration dialog box in which you change the properties of
the recipe view.
2
"Select data connection"
Opens a dialog box for selecting a recipe or recipe collection. The recipe
data are then shown in the table of the recipe view.
3
"First line"
The first data record is displayed in the table by the button.
4
"Previous line"
The previous data record is displayed in the table by the button.
5
"Next line"
The next data record is displayed in the table by the button.
6
"Last line"
The last data record is displayed in the table by the button.
7
"Delete lines"
The content of the marked lines are deleted.
8
"Cut lines"
The content of the marked lines are cut out.
9
"Copy lines"
The content of the marked lines are copied.
10
"Insert lines"
The content of the copied or cut-out lines is inserted starting from the marked
line.
11
"Read tags"
The contents of the connected WinCC tags are read and written into the
recipe elements by the button. The "Tags" communication type must be
activated in the displayed recipe to be able to use the button. The recipe
elements must be connected with tags.
12
"Write tags"
The contents of the recipe elements are written into the connected WinCC
tags. The "Tags" communication type must be activated in the displayed
recipe to be able to use the button. The recipe elements must be connected
with tags.
13
"Import Archive"
A CSV file is imported from the "ua" directory of the project folder into the
table of the recipe view by the button.
14
"Export archive"
The original contents of the table are exported with table headers by the
button when loading. The recipe is stored as a CSV file in the "ua" directory
of the project folder.
15
"Sort dialog"
Opens a dialog box for setting a customized sorting of the displayed columns.
16
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1581
"Print"
Starts the printout of the displayed values. The print job used for printing is
defined in the configuration dialog on the "General" tab.
18
"Export data"
You export the recipe or recipe collection with the button as configured into
a CSV file but with the current Runtime data. If the option "Display dialog" is
active, a dialog opens in which you can view the settings for exporting and
can start the export. With the appropriate operator authorizations you can
also select the file and the directory for the export.
If no dialog box is displayed, the data export to the preset file starts
immediately.
20
"Time base dialog"
Opens a dialog box for setting the time base for the used times.
19
"User-defined 1"
Displays the first button created by the user. The function of the button is
customized.
1001
Possible elements of the status bar
The following elements may appear in the status bar of the recipe view:
Symbol Name Description
Archive name Displays the name of the selected recipe or recipe collection.
Row Shows the number of the marked line.
column Shows the number of the marked column.
Date Shows the system date.
Time Shows the system time.
Time Base Shows the time base used in the display of times.
Navigation in the table
You can navigate in the table as follows:
You enter the next cell with the "ENTER" key or with the "Right" cursor key.
You enter the previous cell with "SHIFT+ENTER" key or with the "Left" cursor key.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1582 System Manual, 08/2011,
You enter the next line by clicking with the mouse in the line or with the "Down" cursor key.
You enter the previous line by clicking with the mouse in the line or with the "Up" cursor
key.
Note
If the "Error while connecting the data!" error message appears when starting Runtime,
the recipe view has no binding to a recipe or recipe collection. Check the following:
The name is specified correctly.
The configuration is not changed.
The connected recipe or recipe collection still exists.
Editing recipe data
Introduction
You can edit data in the Data recipe view. The following options are available:
Enter new data
Change existing data
Delete lines
Cut-out, copy and insert lines
Requirement
You have permitted editing in the configuration dialog on the "General" tab.
You have deactivated the "Write-protected" property for the column to be edited in the
configuration dialog on the "Columns" tab.
The "ID" column cannot be edited.
If the recipe view is connected with a view, you cannot delete and cut out a line.
Entering new data in the table
1. Click on to move to the last line. The line is marked.
2. Double-click on the first cell of the marked line. You can also press on "F2", "Alt+Enter" or
Ctrl+Enter" in the cell.
3. You enter the values in the cells one after the other and confirm each time by pressing
Enter. After you have entered all values in the line and selected another line, the new data
record is written into the recipe. You move to another line by clicking with the mouse, with
the "ENTER" key or with the "Up" and "Down" cursor keys.
4. You can copy the data of a marked line with "CTRL+C" or "CTRL+X" into the clipboard.
The copied data is inserted into a marked line with "CTRL+V".
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1583
Changing existing data in the table
1. Click on or to move to the desired line. You can also use the scrollbars to move
to the desired line.
2. Double-click on the desired cell of the marked line. You can also press on "F2", "Alt+Enter"
or Ctrl+Enter" in the cell.
3. You enter the values in the cells one after the other and confirm each time by pressing
Enter. After you have entered all values in the line and selected another line, the changed
data record is written into the recipe.
Deleting a line in the table
1. Click on or to move to the desired line. You can also use the scrollbars to move
to the desired line.
2. Click on to delete the marked line.
Cutting, copying and inserting lines
1. Click on or to move to the desired line. You can also use the scrollbars to move
to the desired line.
2. Click on or to cut or copy the data of the line. As an alternative, you can also use
key combination "CTRL+ALT+X" or "CTRL+ALT+C".
3. Go to the desired line into which you want to copy the data. Click on to insert the cut-
out or copied data. If you do not want to overwrite the data of the marked line, move into
the last line to insert the data.
Selecting and configuring data
Introduction
The recipe view shows the data of the connected recipe in a table. The displayed content of
the table is determined by the selected columns and the selection of contents of the columns.
Requirement
You have created one or more recipes or recipe collections.
You have connected the recipe view with a recipe or recipe collection.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1584 System Manual, 08/2011,
Configuring the columns
1. Go to the "Columns" tab.
2. In the "Columns" list you can see the fields of the connected recipe or recipe collection. If
a check mark is set in the option check box in front of the name of the column, the column
is displayed in the table. Deactivate the check box if you do not want it to appear.
3. Determine the order of the columns in the table using the "Up" and "Down" buttons.
4. Select a column to configure the properties and the format.
5. If necessary, change the width of the column in the table. Enter a value in the "Length in
chars" field.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1585
6. Some columns can also show the content and the header as a symbol. Determine how
these columns are displayed in the "Display" field. Text and symbols can be displayed at
the same time.
7. Save the configuration.
Selection of column content that will be displayed in the table
Configure criteria used to display the content in the columns in the "Selection" area.
Procedure
1. Click "Edit...". The selection dialog is opened.
2. Specify the criteria for the display. More information on the selection of columns can be
found under Select data (Page 1587).
3. Click "OK" to close the selection dialog. The selection is considered at the start of Runtime
in the table of the recipe view.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1586 System Manual, 08/2011,
Configuring the Sorting of Columns
You configure the sorting of the columns in the table in the "Sorting" area. You can also specify
the sorting criteria in Runtime using the key functions.
1. Click "Edit...". The sorting dialog opens.
2. Set a sorting sequence. More information on the sorting of columns can be found under
Auto-Hotspot.
3. Click "OK" to close the sorting dialog.
4. Save the configuration of the contents.
See also
Select data (Page 1587)
Select data
Introduction
Which contents of the recipe you want to show or export in the recipe view table can be defined
in Runtime by the selection dialog box. In the selection dialog box you defie selection criteria
with regard to the displayed columns of the recipe.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1587
Requirement
The selection dialog is open (see paragraph "Selecting and configuring data (Page 1584)").
Procedure
Proceed as follows:
1. Double-click in the first empty line in the "Criteria" column. The list with the columns of the
recipe view is shown. Select the desired columns, e.g. "field1".
2. Double-click in the "Operand" column to select an operand.
3. Double-click in the "Setting" column to enter a comparison value.
4. Double click in the "Logic operator" column to select an "AND" or "OR" function.
5. Repeat the procedure if you want to define further criteria.
6. Click "OK" to close the selection dialog. The selection is displayed in the table of the recipe
view.
NOTICE
Ensuring the display of column content
Make sure of proper use of the settings and connections of criteria.
Incorrect logical operations can lead to the data of the connected recipe not being
displayed in the recipe view.
Therefore test every criterion separately before the logical operation and then the logically
operated criteria respectively. Check that all expected contents are also displayed in
combination.
This ensures that the selection is displayed completely in the recipe view.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1588 System Manual, 08/2011,
Sorting data
Introduction
The data in the recipe view can be sorted by columns in Runtime. You sort the columns either
via the "Sort dialog" button function or directly via the column headers.
Note
You can define the sorting criteria already in the configuration in the recipe view by clicking
the "Edit..." button under "Sorting" on the "Columns" tab.
How to sort with the Sort dialog
Requirement
You have activated the "Sorting dialog" button on the "Toolbar" tab of the UserArchive
Control.
Procedure
1. Click the "Sort Dialog" button .
2. Select the column of the connected recipe from the "Sort by" list which is to be used for
sorting first. Select the relevant check box to specify sorting in ascending or descending
order. If you want to sort by more than one column, select the other columns in the desired
order in the "Then sort by" lists.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1589
How to sort the column contents with the column heading
When sorting using the column header, you are able to specify the sort order for more than
four columns. A sorting icon and sorting index, displayed with right-justification in the column
heading, show sorting order and sorting sequence of the column contents.
Requirement
You have allowed sorting in the list field "Sort by column header" by click or double click
on the "Parameters" tab of the recipe view.
You have activated the "Show sorting icon" and "Show sorting index" checkboxes.
Procedure
1. Click the column header of the column you want to sort as first column. The sorting index
"1" is displayed, and the sorting icon points upwards for ascending sort order.
2. If you want to sort in descending order, click the column header again.
3. If the sorting order has been defined with "up/down/none", you can undo the sorting of the
column with a third click.
4. If you want to sort several message blocks, click the respective header columns in the
desired sequence.
Using the recipe screen
Introduction
You use the recipe screen with the control objects you have configured. The paragraph
describes the operation of the recipe screen with control tags from the section "Control tags
(Page 1567)".
Note
Runtime API
The Runtime API provides you with extensive uaArchive functions to edit recipes and recipe
collections in Runtime (see section "Interfaces > Runtime API", subsection "Control tags").
Requirement
Communication type is set to "Tags" in the recipe.
The "Unique values" checkbox is activated under "Options" in the properties of the recipe
element "Coloring 7".
Recipe tags and control tags are set up.
A process screen with the required I/O fields is configured.
The I/O fields are connected with the recipe tags and control tags.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1590 System Manual, 08/2011,
Example:
Procedure
To transfer recipe data to the recipe memory of the HMI device, follow these steps:
1. Enter the recipe values displayed in the blue fields "Water", "Sugar", "Aroma", "Coloring 7"
and "Concentrate". The recipe values form the recipe data record you want to transfer.
2. Enter "3" as "ID" for the target recipe data record.
3. Enter "6" as job for reading in the "Instruction" field.
The entered recipe data are transferred as complete data record. The recipe data record
number 3 is overwritten in the recipe memory. The job mailbox returns the value "0" (no error)
in the "Job" control tag.
Alternative procedure
1. Enter new recipe values in the blue fields " Water", "Sugar", "Aroma", "Coloring 7" and
"Concentrate".
2. Enter the recipe element "Coloring 7" as the "Field".
3. Enter the recipe element "020" as the value in the "Value" field.
4. Enter "6" as job for reading in the "Instruction" field.
The entered recipe data are transferred as complete data record. The recipe data record whose
recipe element " Coloring 7" has the recipe value "020" - in the example the recipe data record
number 3 in the recipe memory - will be overwritten. The job mailbox returns the value "0" (no
error) in the "Job" control tag.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1591
See also
Displaying recipes (Page 1558)
9.5.2.6 Examples
Example: Creating recipes
Task
In this example, you will create two recipes.
A "Beverage" recipe for drinks. The drinks mixing plant produces various drinks. You create
a recipe data record for each item.
An "Orders" recipe for orders. The orders contain the current order data.
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
article Yes DB 120, DBW 0 String
litrewater Yes DB 120, DBW 4 Integer
kilosugar Yes DB 120, DBW 8 Integer
gramaroma Yes DB 120, DBW 12 Integer
litreconcentrate Yes DB 120, DBW 16 Integer
coloring Yes DB 120, DBW 20 Integer
customer Yes DB 120, DBW 24 String
numbercustomer Yes DB 120, DBW 28 String
numberorder Yes DB 120, DBW 32 Integer
quantitiy Yes DB 120, DBW 36 Integer
filling Yes DB 120, DBW 40 Integer
dateorder Yes DB 120, DBW 44 Date
status Yes DB 120, DBW 48 Integer
"Beverage" recipe:
Recipe element Associated tag
Article article
Water litrewater
Sugar kilosugar
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1592 System Manual, 08/2011,
Recipe element Associated tag
Aroma gramaroma
Concentrate litreconcentrate
Coloring coloring
Data record ID 1 2 3
Article Juice Nectar Cola Light
Water 5 50 72
Sugar 5 10 35
Aroma 100 300 240
Concentrate 95 50 35
Coloring FS 0063 FS 0063 FS 1007
"Orders" recipe:
Recipe element Associated tag
Customer customer
Number numbercustomer
Order numberorder
Article article
Quantitiy quantitiy
Filling filling
Status status
Date dateorder
Procedure
1. Create the tags listed above with the settings described above.
2. Create the "Beverage" and "Orders" recipes with the settings indicated above.
3. Select the following properties for the recipes:
Under "General > Size" the "Unlimited" type
Under "Communication > Communication type" the "Tags" communication type
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1593
4. Create the recipe entries in each recipe.
5. Activate the "Unique values" check box for the following elements in the property window
under "Extras".
In the "Beverage" recipe for the "Article" recipe element
In the "Orders" recipe for the "Order" recipe element
6. Create the data records indicated above in the "Beverage" recipe. Enter the values
indicated above in each of the data records.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1594 System Manual, 08/2011,
Result
The "Beverage" and "Orders" recipes are created.
See also
Example: Configuring a recipe view (Page 1596)
Example: Creating a recipe view
Task
In this example you create the "Label" recipe view. The following recipe elements are displayed
in the recipe view.
Recipe element Recipe
Article Beverage, Orders
Customer Orders
Status Orders
Order Orders
Filling Orders
Sugar Beverage
Coloring Beverage
The "Article" recipe element is contained as a common element of both recipes.
Requirements
The "Beverage" and "Orders" recipes are created.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1595
Procedure
1. Create the "Label" recipe view. Create the elements listed above.
2. Enter the following conditions under "Properties > Relations":
Beverage.Article = Orders.Article
Result
The "Label" view is created.
Example: Configuring a recipe view
Task
In this example, you will add a plant screen with recipe view to the "Label" view.
Requirement
The examples "Create recipes" and "Create recipe view" are created.
You have created and opened the "Drinks mixing plant" process screen.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1596 System Manual, 08/2011,
Procedure
1. Insert the recipe view in the process screen. You will find the recipe display in the toolbox
under "Controls".
2. Select the "Recipe view" type in the inspector window in the "General > View" group in the
"Data source" input field with the arrow".
3. Select the "Label" recipe view.
4. Define additional display options for the recipe view in the "Properties" > "Appearance"
group in the Inspector window.
5. Go to the "Properties" > "Columns" group in the inspector window.
Activate the check box in the "Visible" and "Protected" columns for all recipe elements.
6. In the Inspector window, switch to the "Properties" > "Toolbar" group. Activate the check
box in the "Visible" column for the following buttons under "Toolbar - Buttons".
"First line"
"Previous line"
"Next line"
"Last line"
"Sort dialog"
"Selection dialog"
7. Go to the "Properties" > "Columns" group in the inspector window. Enter the following
sorting in the "Sort" column.
By job number
Ascending
Result
The recipe display is opened with the "Label" recipe view in Runtime in the process screen
"Drinks mixing plant". The data records are displayed sorted by job number. You can use the
buttons to switch between the data records.
Use the "Status" data field to display the current job or jobs that have been run.
You can adapt the recipe display to the data records as required with the "Sort dialog" and
"Selection dialog" buttons.
See also
Example: Creating recipes (Page 1592)
Using control tags
Example for the use of control tags:
You need to perform the following steps to work through the example with the control tags:
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1597
Requirement
You have created the "Drinks" recipe.
Properties of the "Cola" recipe
Log type "Unlimited"
Communication "Tags"
Data type for the "ID" control tag Long
Data type for the "Job" control tag Long
Data type for the "Field" control tag String (1 character)
Data type for the "Value" control tag String (1 character)
Procedure
1. Create the control tag with the following properties:
Control tag Data Format Output format
ID decimal 0999
Job decimal s9
Field String *
Value String *
1. Select the "Update for changes" object property for each control tag.
2. Connect the control tags to the "Drinks" recipe.
3. Create a new screen and add a recipe view.
Select the "Drinks" recipe.
Check the "Paste", "Change" and "Delete" check boxes under "General".
4. Create an I/O field for every configured recipe element.
5. Connect the I/O fields to the associated tags.
For example, connect the I/O field for "Coloring" to the "Coloring" process tag.
Create a text field for the label of every configured I/O field.
By doing so, you assign the I/O fields to the individual recipe elements in Runtime.
6. Create an I/O field for every control tag.
Create a text field for the label of every configured I/O field.
By doing so, you assign the I/O fields to the individual control tags in Runtime.
7. Start Runtime or load the project into the HMI device and start the project.
Result
The configuration for the recipe is completed.
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1598 System Manual, 08/2011,
Accessing the recipe
You can now access the recipe in the following ways:
In the table view of the recipe view
Using the configured I/O fields
Write the data record to the process tags using the ID
Enter the ID "3" in the "ID" I/O field and enter a "7" in the "Job" I/O field.
The values of data record "3" will be written to the process tags in the I/O fields and displayed
in the I/O fields.
If the data record values were read without error from the recipe, error number "0" is
displayed in the "Job" field.
Error number "-1" is output if an error occurs.
The "Field" and "Value" control tags are not required.
Note
The current contents of the process tags are read into the recipe by entering the ID "-1"
and the job "6". The new values are appended at the end of the table. The data record
IDs are continuously incremented.
Read the process tags via the ID
Change the values in the I/O fields of the process tags and enter a "5" in the "ID" field. Enter
"6" in the "Job" I/O field.
The changed values of the process tag are written to data record "5" of the recipe. The
values that were previously contained in this data record are overwritten.
The "Field" and "Value" control tags are not required.
Write a data record to the process tag using the "Field" and "Value" control tags
Note
For an element that is referenced with the "Value" control tag, you must select the "Field must
posses an unique value" check box under "Properties" > "Memory options". Otherwise it will
not be possible to create a unique assignment between the recipe data record and the value
in the element.
If text is entered in the "Value" I/O field, it must be enclosed in inverted commas (such as
'Nectar').
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1599
In the "Field" I/O field, enter the word "Item" and write "Cola Light" to the "Value" I/O field.
Enter "7" in the "Job" I/O field.
The values of the "Cola Light" data record will be written to the process tags in the I/O fields
and displayed in the I/O fields.
The "ID" control tag is not needed, so it must be set to 0.
9.5.2.7 SQL language
SQL (Structured Query Language) is an efficient and widely distributed database language.
The SQL language is used for database queries in the functions of the WinCC script language.
You will find further information in the relevant technical manuals.
In some standard functions and some functions in the "Recipes" editor, you must specify
conditions in the database language SQL to specify the data records to be edited. A few
examples of how provide an SQL instruction are given below:
NOTICE
Name convention
Prefixes, suffixes and the name of a recipe, recipe view or a recipe element may only consist
of letters, numbers and underscores "_" and may not exceed a length of 20 characters. The
first character must always be a letter.
FieldA > '1992-12-31 23:45:12.12'
The instruction selects all data records whose value in the "FieldA" column is greater than
the specified value. FieldA is is of the data type DB_TYP_TIME.
FieldB like 'tank%'
Then the data records for which the "FieldB" column contains the value "tank1" or "tank4"
or "tank12" etc. are selected for example. FieldB is of the data type DB_TYP_CHAR.
FieldC > 100
With a condition of this type, all data records are selected for which the "FieldC" column
contains a value greater than 100. FieldC is of the data type DB_TYP_INTEGER.
BETWEEN FieldC = 20 AND FieldC = 200
The statement selects all data records for which the "FieldC" column contains a value
between 20 and 200. FieldC is of the data type DB_TYP_INTEGER.
FieldD
Sorting then takes place by column "FieldD".
FieldE desc
Sorting then takes place by column "FieldE" in reverse alphabetical order (descending
order).
See also
SQL keywords (Page 1601)
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
1600 System Manual, 08/2011,
9.5.2.8 SQL keywords
SQL keywords
NOTICE
Do not use the following terms and keywords as names for recipe, recipe view or recipe
element:
"Archive"
"View"
"Field"
"ViewCol"
Keywords of the SQL language
add all alter and
any as asc begin
between binary break by
call cascade cast char
char_convert character check checkpoint
close comment commit connect
constraint continue convert create
cross current cursor date
dba dbspace deallocate dec
decimal declare default delete
desc distinct do double
drop else elseif encrypted
end endif escape exception
exec execute exists fetch
first float for foreign
from full goto grant
group having holdlock identified
if in index inner
inout insert instead int
integer into is isolation
join key left like
lock long match membership
message mode modify named
natural noholdlock not null
numeric of off on
open option options or
order others out outer
passthrough precision prepare primary
print privileges proc procedure
Visualizing processes (Professional)
9.5 Working with recipes
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1601
Keywords of the SQL language
raiserror readtext real reference
references release remote rename
resource restrict return revoke
right rollback save savepoint
schedule select set share
smallint some sqlcode sqlstate
start stop subtrans subtransaction
synchronize syntax_error table temporary
then time tinyint to
tran trigger truncate tsequal
union unique unknown update
user using validate values
varbinary varchar variable varying
view when where while
with work writetext
See also
SQL language (Page 1600)
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).
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1602 System Manual, 08/2011,
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.
Moreover, you can specify whether to output the different pages with or without watermark
in the reports for Runtime Professional.
Content
In the work area, specify the content of the report, for example, the alarms of a shift. To
this purpose, insert the corresponding objects into the detail page(s).
You can also design the title page, back page, headers, and footers as you please. For
watermarked pages, create additional pages to be included as "background image" in the
output.
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, report output is event-driven or time-driven.
Time-driven: Automatic print at specific dates, times or intervals.
Event-driven: Printing is initiated by specific events, e.g. click on a button, or a limit is
exceeded.
The configuration of report output differs depending on the Runtime version.
In Runtime Advanced, the configured reports are output on the default printer of the HMI device.
For Runtime Professional, make the following decisions with the help of a print job:
Output of selected pages, or of all pages of the report
Output of all data, or only the data of a specific period
Output of the report to a printer or file
Whether the operator is allowed to select a printer or modify the scope of pages for report
output
Whether the report that is output is displayed in the print job list of an application window
configured accordingly
Print function of screen objects
Certain screen objects of Runtime Professional, e.g. the alarm view, contain a default button
function (printer icon) for the report output. WinCC employs predefined system reports for the
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1603
output. You can can customize these to suit your requirements, or replace them with a report
of your individual design.
See also
Structure of reports (Page 1604)
Create a report (Page 1616)
Print job/Script diagnostics (Page 837)
Principles for preparation of reports (Page 1612)
Principles for report output (Page 1632)
Basics for system traces and system print jobs (Page 1637)
9.6.1.2 Structure of reports
Introduction
A report in WinCC consists of several sections that can be enabled or disabled, as required.
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1604 System Manual, 08/2011,
Sections of a report
The following figure shows an example of the different sections of a report in the "Reports"
editor.
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.
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1605
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
Create a report (Page 1616)
Principles for preparation of reports (Page 1609)
9.6.1.3 Structure of reports
Introduction
A report in WinCC consists of several sections that can be enabled or disabled, as required.
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1606 System Manual, 08/2011,
Sections of a report
The following figure shows an example of the different sections of a report in the "Reports"
editor.
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1607
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. The
page has a precise length and no page break, regardless of whether you configured a dynamic
object to be output on that page.
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
project name, report name, page numbers or the date in the header or footer.
Watermarks
The title, detail and back pages can be output with a watermark. The page is printed with its
superimposed watermark.
With the help of a watermark, output an object "A" next to an object of variable length "B"
without displacing object "A". Example: You want to output an output field (A) next to a table
(B) on all pages.
The title and back pages, as well as the detail pages have separate watermarks.
See also
Reports (Page 1602)
Principles for preparation of reports (Page 1612)
Create a report (Page 1616)
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1608 System Manual, 08/2011,
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 (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1609
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 (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1610 System Manual, 08/2011,
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
Configuring reporting of alarms (Page 1340)
Structure of reports (Page 1604)
Create a report (Page 1616)
Administration of detail pages (Page 1629)
Objects in reports (Page 1655)
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1611
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
Watermarks for title page, back page, detail page
Procedure
The following figure shows the general procedure for creating a report:
Create report
Create print job
Assign name
Title page
lnsert additional
detail pages
n x detail
pages
Configure object
1)
lnsert watermark
Optional
Optional
Optional
lnsert object on
detail page
Create "print job"
type task
Header/footer
Configure back
page
1) Settings depend on the report object used.
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1612 System Manual, 08/2011,
Tools for the design of reports
The objects that you can use to design the reports are available in the "Tools" task card.
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.
Positioning objects
Insert the objects at the position where you want them to be output in the report. However,
you should be aware that WinCC ignores white spaces at the start of the detail page when the
report is output. The top object marks the start of the detail page on the printed copy.
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
To include a white space in the output, extend the header accordingly. You can also place an
"invisible" object on the detail page at the required start. For example a white line that is not
visible on white paper.
Size of objects
Objects are output in their configured size.
On the detail pages, configure "controls" and "report objects" for the output of Runtime data.
WinCC aligns the Runtime data to fit the object frame with one special feature: If you configure
an object like a table with dynamic length, WinCC automatically adjusts the height of the table
to fit the amount of data to print. The table can be continued on the next page. WinCC adapts
no more than the object height and places all following objects underneath the the object, as
configured in the detail page.
The following figure shows an example of a detail page in the report and its output in Runtime:
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1613
Detail page in the report Report output in Runtime
Usually, the "controls" and "report objects" are assigned a dynamic length and output Runtime
data in tabular format. The following objects are included:
Recipe report
Alarm report
Table view
ODBC database table
Alarm sequence report
CSV provider tables
Control Hardcopy
Control Data
Control information
Objects next to dynamic objects
In a detail page, do not place other objects next to objects that have a dynamic length. Given
the fact that the position of the objects cannot be clearly defined, WinCC possibly outputs these
with errors. Instead, configure the objects as watermark.
The following figure shows an example of a watermark and a detail page in the report and the
output in Runtime:
Visualizing processes (Professional)
9.6 Working with reports
WinCC Professional V11.0 SP1
1614 System Manual, 08/2011,
Watermark and detail page in the report Report output in Runtime
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.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1810 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1811
9.8.1.8 Examples of VBS
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1812 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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1813
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1814 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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1815
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1816 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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1817
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.
See also
Configuring a function list (Page 1750)
9.8.1.9 Examples of VBS
Overview
Introduction
You can find the following examples for VBS:
Access to objects in the "Screens" editor (e.g., color or text change)
Determining color of objects
Configuring a language switch
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1818 System Manual, 08/2011,
Deactivating Runtime
Configuring a screen change via a property
Configuring diagnostic output via a trace
Writing tag values
Reading tag values
Writing object properties
Configuring a recipe view
Configuring an alarm view
Drawing a trend
Evaluating tag values statistically
See also
Example of configuring the recipe view (Page 1830)
Example of configuring the alarm view (Page 1831)
Example of statistically evaluating tag values (Page 1832)
Example of accessing objects in the Screens editor
Introduction
To make the graphic Runtime environment dynamic, you can use VBS scripting to access all
objects in the "Screens" editor in WinCC. In doing so, you can make graphic objects dynamic
in response to an operator input, e.g., in response to a mouse click or depending on tag values.
Procedure
In the following example, the radius of a circle is set to 20 in Runtime per mouse click:
'VBS121
Dim objCircle
Set objCircle= ScreenItems("Circle1")
objCircle.Radius = 20
Example of defining object colors
Introduction
The object colors are defined by means of RGB values (Red/Green/Blue). The color values
for graphic objects can be set or read.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1819
Procedure
The following example defines the fill color for "ScreenWindow1" to blue:
'VBS122
Dim objScreen
Set objScreen = HMIRuntime.Screens("ScreenWindow1")
objScreen.FillColor = RGB(0, 0, 255)
Example of configuring a language switch
Introduction
The Runtime language can be changed by means of VBS. Use buttons with corresponding
country markings that you place on the start page of your project.
Using VBS, define the Runtime language by means of country code, e.g., 1031 for German -
Default, 1033 for English - USA, etc. An overview of all country codes is available in the Basics
of VBScript, "Regional Scheme ID (LCID) Diagram".
Procedure
Configure a local VBS script for a "Mouse click" event on a button and enter the following code
to change the Runtime language to German:
'VBS123
HMIRuntime.Language = 1031
Example of deactivating Runtime
Introduction
You can use VBS to exit Runtime, e.g. by means of mouse click, or depending on tag values,
or on other events.
Procedure
The following example terminates WinCC Runtime:
'VBS124
HMIRuntime.Stop
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1820 System Manual, 08/2011,
Example of configuring a screen change via a property
Introduction
If using split screens in your configuration, e.g. the title and operating bar for the user interface
in a basic screen and an embedded screen window for the actual screen display, configure a
screen change using the properties of the screen window.
The property of screen window "ScreenName" must be changed so that the other screen is
displayed. The local script and the screen window must be configured in the same screen.
Procedure
In the following example you show the "test" screen in a "ScreenWindow" when executing the
local VB script:
'VBS126
Dim objScrWindow
Set objScrWindow = ScreenItems("ScreenWindow")
objScrWindow.ScreenName = "test"
Example of configuring a diagnostics output via a trace
Introduction
If you have inserted the Print job/Script diagnostics" object in your screen, you can use the
trace command to display diagnostics outputs in the diagnostics window in Runtime.
Print job/Script diagnostics returns the trace methods contained in the user-defined functions
in the order in which they were called. This also applies to trace instructions in functions that
are called in user-defined functions. The targeted use of trace instructions allows you to trace
the flow of user-defined functions and the functions called therein. You enter the trace
instruction in the form "HMIRuntime.Trace<Output>".
The "Print job/Script diagnostics" object displays trace outputs from C and VBS.
Outputting text
The following example writes a text in the diagnostics window:
'VBS127
HMIRuntime.Trace "Customized error message"
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1821
Outputting alarms
The following example writes the alarms of a "Control2" alarm view to the diagnostics window:
Sub TraceMsg
Dim objAlarmControl
Dim lIndex
Dim lCellIndex
'create reference to the alarm control
Set objAlarmControl = ScreenItems("Control2")
'enumerate and trace out row numbers
For lIndex = 1 To objAlarmControl.GetRowCollection.Count
HMIRuntime.Trace "Row: " & (objAlarmControl.GetRow(lIndex).RowNumber) & " "
'enumerate and trace out column titles and cell texts
For lCellIndex = 1 To objAlarmControl.GetRow(lIndex).CellCount
HMIRuntime.Trace objAlarmControl.GetMessageColumn(lCellIndex -1).Name & " "
HMIRuntime.Trace objAlarmControl.GetRow(lIndex).CellText(lCellIndex) & " "
Next
HMIRuntime.Trace vbNewLine
Next
End Sub
Output information about HMI tags
The following example uses the "VarArch100" log tag to write information to the diagnostics
window:
Sub ReadTagInfo
Dim Tag
Set Tag = HMIRuntime.Tags("TagLoggingfast\VarArch100")
HMIRuntime.Trace "LastError = " + CStr(Tag.LastError) + vbNewLine
HMIRuntime.Trace "Name = " + Tag.Name + vbNewLine
HMIRuntime.Trace "QualityCode = " + CStr(Tag.QualityCode) + vbNewLine
End Sub
See also
Diagnostics (Page 1804)
Example of writing tag values
Introduction
You can use VBScript to write the tag value to the PLC, for example, by mouse click on a
setpoint button or to set internal tag values for triggering other user-defined functions.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1822 System Manual, 08/2011,
Various write variations are mentioned and explained below.
Simple writing
In the following example, a value is written to the "Tag1" tag:
'VBS128
HMIRuntime.Tags("Tag1").Write 6
This is the simplest form of writing since no object reference is generated.
Writing with object reference
In the following example, a local copy of the tag object is generated and a value is written to
"Tag1":
'VBS129
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Write 7
Referencing offers the advantage of being able to work with the tag object before writing. You
can read the tag value, perform calculations, and write the tag value again.
'VBS130
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Read
objTag.Value = objTag.Value + 1
objTag.Write
Synchronous writing
The value to be written is usually transferred to tag management and execution of the script
is continued. In certain cases, however, it must be ensured that the value has actually been
written before script execution continues.
This type of writing is realized by specifying the value 1 for the additional, optional parameters:
'VBS131
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Write 8.1
or
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1823
'VBS132
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Value = 8
objTag.Write ,1
Note
Note that the call takes longer in comparison to the standard call. The duration is also
dependent on the channel and AS, among other things.
This type of writing corresponds to the SetTagXXXWait() call in C scripting.
Writing with status handling
In order to ensure that a value has been written successfully, you perform an error check or
evaluate the tag status after the write operation was completed.
This is done by checking the value of the LastError property after writing. The tag status is
checked if the check was completed successfully, i.e., if the job was successfully output.
In the case of a write job, the current status from the process is not determined. To determine
this, it is necessary to read the tag. The value specified in the QualityCode property after the
read process provides an indication of the tag status and, if necessary, makes reference to a
failed AS connection.
In the following example, the "Tag1" tag is written. If an error occurs during writing, the error
value and error description appear in the Global Script diagnostics window. Finally, the
QualityCode is checked. If the QualityCode is not OK (0x80), it will be displayed in the
diagnostics window.
'VBS133
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Write 9
If 0 <> objTag.LastError Then
HMIRuntime.Trace "Error: " & objTag.LastError & vbCrLf & "ErrorDescription: " &
objTag.ErrorDescription & vbCrLf
Else
objTag.Read
If &H80 <> objTag.QualityCode Then
HMIRuntime.Trace "QualityCode: 0x" & Hex(objTag.QualityCode) & vbCrLf
End If
End If
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1824 System Manual, 08/2011,
Note
After writing a tag, the QualityCode property of the local tag object is set to "BAD Out of
Service" because it is not known which QualityCode the tag handles in the process. The new
QualityCode can be determined by reading again.
The Quality Code cannot be written from VBS.
Example of reading tag values
Introduction
VBS can be used to read and further process a tag value. This allows you to click a button, for
example, to obtain information on the system status or to perform calculations.
Various read variations are mentioned and explained below.
Simple reading
In the following example, the value of "Tag1" is read and displayed in the Global Script
diagnostics window:
'VBS134
HMIRuntime.Trace "Value: " & HMIRuntime.Tags("Tag1").Read & vbCrLf
This is the simplest form of reading since no object reference is generated.
Reading with object reference
In the following example, a local copy of the tag object is created, and the tag value is read
and displayed in the "Print job/Script diagnostics" object:
'VBS135
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
HMIRuntime.Trace "Value: " & objTag.Read & vbCrLf
Referencing offers the advantage of being able to work with the tag object. You can read the
tag value, perform calculations, and write the tag value again.
'VBS136
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Read
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1825
objTag.Value = objTag.Value + 1
objTag.Write
Using the Read method, process tags that have been read are added to the image, from this
moment on they are cyclically requested from the automation system (AS). If the tag is already
in the image, the value it contains is returned.
When the screen is exited, the tags are logged off.
Note
If a tag is requested in a function, it remains logged on as long as WinCC Runtime is running.
Direct reading
Normally, the tag values are read from the tag image. In certain situations, however, it may be
necessary to read the value directly from the AS, e.g., to synchronize fast processes.
The tag is not logged on cyclically if you set the optional parameter to 1 when reading the
value. Instead, the value is requested once from the AS.
'VBS137
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
HMIRuntime.Trace "Value: " & objTag.Read(1) & vbCrLf
Note
Note that the call takes longer in comparison to the standard call. The duration is also
dependent on the channel and AS, among other things.
This type of call must be avoided in cyclic C scripts as this is the major cause of performance
problems.
This read mode corresponds to the GetTagXXXWait() call used in C scripting.
Reading with status handling
Always validate the value after reading it. This occurs by checking the QualityCode.
In the following example, the "Tag1" tag is read and the QualityCode then checked. When the
Quality Code does not correspond to OK (0x80) the LastError, ErrorDescription, and
QualityCode properties are displayed in the Global Script diagnostics window.
'VBS138
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1826 System Manual, 08/2011,
Dim objTag
Set objTag = HMIRuntime.Tags("Tag1")
objTag.Read
If &H80 <> objTag.QualityCode
Then
HMIRuntime.Trace "Error: " & objTag.LastError & vbCrLf & "ErrorDescription: " &
objTag.ErrorDescription & vbCrLf & "QualityCode: 0x" & Hex(objTag.QualityCode) & vbCrLf
Else
HMIRuntime.Trace "Value: " & objTag.Value & vbCrLf
End If
Note
If an error occurs during reading, QualityCode is set to BAD Out of Service". Therefore, it is
sufficient to check the QualityCode following reading.
Example of writing object properties
Introduction
VBS provides access to the properties of all display and operating objects in the "Screens"
editor. You can read out properties or change them during Runtime.
The following examples illustrate various forms of access.
Simple setting of a property
In the next example, the background color of the "Rectangle1" object in the screen is set to
red:
'VBS139
ScreenItems("Rectangle1").BackColor = RGB(255,0,0)
This is the simplest form of writing since no object reference is generated.
Note
If you are working without an object reference, only the standard properties are provided by
autocompletion.
The mode of expression used in this example can only be executed in the "Screens" editor.
By analogy, you address the objects in the scheduler using the HMIRuntime object.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1827
Setting a property with object reference
In the following example, a reference is created to the "Rectangle1" object contained in the
picture and the background is set to red using the VBS standard function RGB():
'VBS140
Dim objRectangle
Set objRectangle = ScreenItems("Rectangle1")
objRectangle.BackColor = RGB(255,0,0)
Additional information on RGB is available in "VBScript for Windows".
Referencing is useful if you want to edit several object properties. In this way all of the
properties of the object will be listed with the autocompletion feature.
Note
The mode of expression used in this example can only be executed in the "Screens" editor.
By analogy, you address the objects in the scheduler using the HMIRuntime object.
Setting properties across screen windows
VBS in the "Screens" editor offers two options of global screen addressing:
Using the screen object of a screen window with "ScreenItems"
From the root screen with "HMIRuntime.Screens"
Referencing via the screen window
In the following example, the color of a rectangle is changed in an subordinate screen window.
The user-defined VB function is executed in the "BaseScreen" screen in which
"ScreenWindow1" is located. The screen window displays a screen, which contains an object
of the type "Rectangle" with the name "Rectangle1".
'VBS199
Sub OnLButtonUp(ByVal Item, ByVal Flags, ByVal x, ByVal y)
Dim objRectangle
Set objRectangle = ScreenItems("ScreenWindow1").Screen.ScreenItems("Rectangle1")
objRectangle.BackColor = RGB(255,0,0)
End Sub
Referencing from the root screen
You can reference the screen with the object to be modified via HMIRuntime.Screens. The
specification of the screen is defined relative to the root screen via the following access code:
[<Root screen name>.]<Screen window name>[:<Screen name>]... .<Screen window
name>[:<Screen name>]
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1828 System Manual, 08/2011,
In the following example, a reference is created to the "Screen2" object contained in the
"Rectangle1" picture and the background color is set to red.
The screen "Screen2", in this case, is in "Screen1". "Screen1" is displayed in the "BaseScreen"
root screen.
'VBS141
Dim objRectangle
Set objRectangle =
HMIRuntime.Screens("BaseScreen.ScreenWindow1:Screen1.ScreenWindow1:Screen2").ScreenItems("
Rectangle1")
objRectangle.BackColor = RGB(255,0,0)
It is not necessary to specify the screen name. It is possible to address a screen uniquely using
the screen window name. Therefore, it is sufficient to specify the name of the screen window,
as in the following example:
'VBS142
Dim objRectangle
Set objRectangle =
HMIRuntime.Screens("ScreenWindow1.ScreenWindow2").ScreenItems("Rectangle1")
objRectangle.BackColor = RGB(255,0,0)
This type of addressing enables objects in screen windows to be addressed in different
pictures. This is a particularly interesting aspect for the faceplate system.
Making the property dynamic using the return value
In addition to initiating local scripts for properties by means of an event trigger or cyclic trigger,
you can also make properties dynamic directly by means of a local script.
In the next example, the background color of an object made dynamic by means of return
value. The value transferred can be derived from the evaluation of events in the PLC, for
example, and can be used for graphic visualization of an operating state:
'VBS146
Function BackColor_Trigger(ByVal Item)
BackColor_Trigger = RGB(125,0,0)
End Function
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1829
NOTICE
If you use a user-defined function to make an object property dynamic by means of the return
value of a user-defined function, the value of the object property is only written if it has
changed compared to the last function session. It is not considered if the value had been
changed from another location.
For this reason, properties that have been made dynamic by means of the return value with
user-defined functions must not be changed from another location (e.g. other user-defined
functions). Incorrect values could be displayed if you ignore this rule.
Example of configuring the recipe view
Introduction
Recipe data records are output in the recipe view.
You can add, copy, edit or delete data records.
Loading and displaying a recipe
The following example loads the "Juice" recipe in the "Control1" recipe view. The recipe is
displayed in the recipe view.
Sub loadUserArchive()
Dim objUAC
Set objUAC = ScreenItems("Control1")
objUAC.BorderColor = RGB(255,0,0)
objUAC.BorderWidth = 3
objUAC.Closeable = False
objUAC.Datasource = "Juice"
End Sub
Copying a recipe data record
The following example copies the recipe data record of line 3. The copy is inserted at the end
of the table.
Sub CopyRow
Dim objUAC
Set objUAC = ScreenItems("Control1")
Dim iRowCount
objUAC.AutoCompleteRows = True
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1830 System Manual, 08/2011,
objUAC.SelectRow(3)
objUAC.CopyRows
iRowCount = objUAC.GetRowCollection.Count
objUAC.SelectRow(iRowCount + 1)
objUAC.PasteRows
objUAC.SelectRow(1)
objUAC.UnselectAll
End Sub
See also
Overview (Page 1818)
Example of configuring the alarm view
Introduction
The alarm view displays alarms. You can show, hide, sort, and filter alarms.
Filtering alarms
In this example, only the alarms of alarm number 2 are displayed in the "Control2" alarm view.
Sub Filter
Dim objAlarmControl
'create reference to AlarmControl
Set objAlarmControl = ScreenItems("Control2")
'set / reset the filter and create a trace
If (objAlarmControl.MsgFilterSQL = "") Then
objAlarmControl.MsgFilterSQL = "MSGNR = 2"
Else
objAlarmControl.MsgFilterSQL = ""
End If
End Sub
Removing alarms
In this example, alarms 1-3 will be removed from the alarm view.
Sub ResetAlarm
Dim objAlarm
'reset alarm 1 - 3
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1831
Set objAlarm = HMIRuntime.Alarms(1)
objAlarm.State = 2 'hmiAlarmStateGone
objAlarm.Create
Set objAlarm = HMIRuntime.Alarms(2)
objAlarm.State = 2 'hmiAlarmStateGone
objAlarm.Create
Set objAlarm = HMIRuntime.Alarms(3)
objAlarm.State = 2 'hmiAlarmStateGone
objAlarm.Create
End Sub
Adding alarms
In this example, alarms 1-3 will be added to the alarm view. Alarms 1-3 must be created.
Sub SetAlarm
Dim objAlarm
'create Alarm 1 - 3
Set objAlarm = HMIRuntime.Alarms(1)
objAlarm.State = 1 'hmiAlarmStateCome
objAlarm.Create
Set objAlarm = HMIRuntime.Alarms(2)
objAlarm.State = 1 'hmiAlarmStateCome
objAlarm.Create
Set objAlarm = HMIRuntime.Alarms(3)
objAlarm.State = 1 'hmiAlarmStateCome
objAlarm.Create
End Sub
See also
Overview (Page 1818)
Example of statistically evaluating tag values
Introduction
You can use the value table to display the coordinates of trends and the statistical evaluation
of tag values in tabular form. You connect the value table to the corresponding object for this
purpose. The evaluated data can be printed out and exported.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1832 System Manual, 08/2011,
Procedure
In the following example, the tag values of the f(t) trend view "Control2" are statistically
evaluated. To display the result in the statistics area window of the value table, you set the
following in the value table properties:
Data source: "Control2"
Mode: "Statistic area" window"
Add a new button in f(t) trend view and configure the user-defined VB function for it.
Sub OnToolbarButtonClicked(ByVal Item, ByVal lId)
Dim objTrend
Set objTrend = ScreenItems("Control2")
objTrend.CalculateStatistic()
End Sub
See also
Overview (Page 1818)
9.8.1.10 Examples of C
Overview
Introduction
You can find examples for C functions:
Access to objects in the "Screens"editor (e.g. color or text change)
Determining color of objects
Configuring a language switch
Deactivating Runtime
Configuring a screen change via a property
Configuring diagnostic output via a trace
Writing tag values
Reading tag values
Writing object properties
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1833
See also
Example of accessing objects in the Screens editor (Page 1834)
Example of defining object colors (Page 1834)
Example of configuring a language switch (Page 1835)
Example of deactivating Runtime (Page 1835)
Example of configuring a screen change via a property (Page 1836)
Example of configuring a diagnostics output via a trace (Page 1836)
Example of writing tag values (Page 1837)
Example of reading tag values (Page 1837)
Example of writing object properties (Page 1838)
Example of accessing objects in the Screens editor
Introduction
To make the graphic Runtime environment dynamic, you can use C scripting to access all
objects in the "Screens" editor in WinCC. In doing so, you can make graphic objects dynamic
in response to an operator input, e.g., in response to a mouse click or depending on tag values.
Procedure
In the following example, the radius of a circle is set to 10 in Runtime per mouse click:
'C121
SetPropDouble(screenName,"Kreis_1","Radius",10);
See also
SetPropDouble (Page 1897)
Overview (Page 1833)
Example of defining object colors
Introduction
The object colors are defined by means of RGB values (Red/Green/Blue). The color values
for graphic objects can be set or read.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1834 System Manual, 08/2011,
Procedure
The following example defines the fill color for "Roundbutton1" to blue:
'C122
SetPropertyByConstant (screenName, " Roundbutton1", "FillPatternColor", "65035");
See also
SetPropertyByConstant (Page 1899)
Overview (Page 1833)
Example of configuring a language switch
Introduction
The Runtime language can be changed by means of VBS. Use buttons with corresponding
country markings that you place on the start page of your project.
Define the Runtime language by means of country code, for example, 1031 for German -
Default, 1033 for English - USA etc. An overview of all country codes is available in the basics
of VBScript, "Regional Scheme ID (LCID) Diagram".
Procedure
Create a user-defined C function for a button for the "Mouse click" event, and enter the following
code to switch the Runtime language to German:
'C123
SetLanguageByLocaleID(1033);
See also
SetLanguageByLocaleID (Page 1895)
Overview (Page 1833)
Example of deactivating Runtime
Introduction
You can use C functions to exit Runtime, for example, by means of mouse click, or depending
on tag values, or on other events.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1835
Procedure
The following example terminates WinCC Runtime:
'C124
StopRuntime(hmiStopRuntime);
See also
StopRuntime (Page 1918)
Overview (Page 1833)
Example of configuring a screen change via a property
Introduction
If using split screens in your configuration, for example, the title and operating bar for the user
interface in a basic screen and an embedded screen window for the actual screen display,
configure a screen change using the properties of the screen window.
The property of screen window "ScreenName" must be changed so that the other screen is
displayed. The C function and screen window must be configured in the same screen.
Procedure
In the next example, the "test" screen is displayed in a "ScreenWindow" when you execute
the C function:
'C126
ActivateScreenInScreenWindow (screenName, "ScreenWindow", "test");
See also
ActivateScreenInScreenWindow (Page 1858)
Overview (Page 1833)
Example of configuring a diagnostics output via a trace
Introduction
If you have inserted a GSC diagnostics window in your screen, you can use the trace command
to display diagnostics outputs in the diagnostics window in Runtime.
GSC diagnostics returns the trace methods contained in the functions in the order in which
they were called. This also applies to trace instructions in functions that are called in user-
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1836 System Manual, 08/2011,
defined functions. The targeted use of trace instructions allows you to trace the flow of user-
defined functions and the functions called therein. You enter the trace instruction in the form
"printf(<Output>)".
The GSC diagnostics window displays trace outputs of C functions.
Outputting text
The following example writes a text in the diagnostics window:
'C127
printf("Customized C script error message\r\n");
See also
Overview (Page 1833)
Example of writing tag values
Introduction
You can use C functions to write the tag value to the PLC, foe example, by mouse click on a
setpoint button, or to set internal tag values for triggering other functions.
Simple writing
In the following example, a value is written to the "Tag1" tag:
'C128
int value;
value = 7;
SetTagSDWord("Tag1", value);
See also
SetTag (Page 1902)
Overview (Page 1833)
Example of reading tag values
Introduction
C functions can be used to read and further process a tag value. This allows you to click a
button, for example, to obtain information on the system status or to perform calculations.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1837
Simple reading
In the following example, the value of "Tag1" is read and displayed in the Global Script
diagnostics window:
'C134
int value;
value = GetTagGetTagSDWord("Tag1");
See also
GetTag (Page 1868)
Overview (Page 1833)
Example of writing object properties
Introduction
C functions provide access to the properties of all display and operating objects in the
"Screens" editor. You can read out properties or change them during Runtime.
The following example shows how to access a property.
Simple setting of a property
In the next example, the background color of the "Button1" object in the screen is set to red:
'C139
SetPropLong("Screen_1","Button1","ForeColor",65333);
See also
SetPropLong (Page 1898)
Overview (Page 1833)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1838 System Manual, 08/2011,
9.8.2 Reference (Panels, RT Advanced)
9.8.2.1 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
Cleared (Page 1845) -- -- -- -- --
Activate (Page 1845) -- -- -- -- -- --
Adjust (Page 1845) -- -- -- -- -- --
Loaded (Page 1846) -- -- -- -- --
Execute (Page 1846) -- -- -- -- --
Selection changed (Page 1846) -- -- -- -- -- --
When dialog is opened (Page 1846) -- -- -- -- --
When dialog is closed (Page 1847) -- -- -- -- --
User change (Page 1847) -- -- -- -- --
Screen change (Page 1847) -- -- -- -- --
Deactivate (Page 1847) -- -- -- -- -- --
Double-click (Page 1848) -- -- -- -- -- --
Press (Page 1848) -- -- -- -- -- --
On Finish Input (Page 1849) -- -- -- -- -- --
Press ESC twice (Page 1849) -- -- -- -- -- --
Outgoing (Page 1849) -- -- -- -- --
Incoming (Page 1850) -- -- -- -- --
In the event of high limit violation (Page 1850) -- -- -- -- --
Click (Page 1850) -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1839
Click when flashing (Page 1851) -- -- -- -- -- --
Loop-in alarm (Page 1851) -- -- -- -- --
Release (Page 1851) -- -- -- -- -- --
Alarm buffer overflow (Page 1852) -- -- -- -- --
In the event of low limit violation (Page 1852) -- -- -- -- --
Acknowledge (Page 1852) -- -- -- -- --
Reach margin (Page 1852) -- -- -- -- -- --
Runtime Stop (Page 1853) -- -- -- -- --
Press key (Page 1853) -- -- -- -- -- --
Release key (Page 1854) -- -- -- -- -- --
Overflow (Page 1854) -- -- -- -- --
Switching (Page 1854) -- -- -- -- -- --
Switch OFF (Page 1855) -- -- -- -- -- --
Switch ON (Page 1855) -- -- -- -- -- --
Low free storage space (Page 1855) -- -- -- --
Free space critically low (Page 1855) -- -- -- --
Value change (Page 1855) -- -- -- -- --
Time expired (Page 1856) -- -- -- -- -- --
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
Cleared (Page 1845) -- -- -- -- -- -- -- --
Activate (Page 1845) -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1840 System Manual, 08/2011,
Adjust (Page 1845) -- -- -- -- -- -- -- --
Loaded (Page 1846) -- -- -- -- -- -- -- --
Execute (Page 1846) -- -- -- -- -- -- -- --
Selection changed (Page 1846) -- -- -- -- -- -- -- --
When dialog is opened (Page 1846) -- -- -- -- -- -- -- --
When dialog is closed (Page 1847) -- -- -- -- -- -- -- --
User change (Page 1847) -- -- -- -- -- -- -- --
Screen change (Page 1847) -- -- -- -- -- -- -- --
Deactivate (Page 1847) -- -- -- -- -- -- -- --
Double-click (Page 1848) -- -- -- -- -- -- -- --
Press (Page 1848) -- -- -- -- -- -- -- --
On Finish Input (Page 1849) -- -- -- -- -- -- -- --
Press ESC twice (Page 1849) -- -- -- -- -- -- -- --
Outgoing (Page 1849) -- -- -- -- -- -- -- --
Incoming (Page 1850) -- -- -- -- -- -- -- --
Click (Page 1850) -- -- -- -- -- -- -- --
Click when flashing (Page 1851) -- -- -- -- -- -- -- --
Loop-in alarm (Page 1851) -- -- -- -- -- -- -- --
Release (Page 1851) -- -- -- -- -- -- -- --
In the event of high limit violation (Page 1850) -- -- -- -- -- -- -- --
Alarm buffer overflow (Page 1852) -- -- -- -- -- -- -- --
In the event of low limit violation (Page 1852) -- -- -- -- -- -- -- --
Acknowledge (Page 1852) -- -- -- -- -- -- -- --
Reach margin (Page 1852) -- -- -- -- -- -- -- --
Runtime Stop (Page 1853) -- -- -- -- -- -- -- --
Press key (Page 1853) -- -- -- -- -- -- -- --
Release key (Page 1854) -- -- -- -- -- -- -- --
Overflow (Page 1854) -- -- -- -- -- -- -- --
Switching (Page 1854) -- -- -- -- -- -- -- --
Switch OFF (Page 1855) -- -- -- -- -- -- -- --
Switch ON (Page 1855) -- -- -- -- -- -- -- --
Low free storage space (Page 1855) -- -- -- -- -- -- -- --
Free space critically low (Page 1855) -- -- -- -- -- -- -- --
Value change (Page 1855) -- -- -- -- -- -- -- --
Time expired (Page 1856) -- -- -- -- -- -- -- --
Elements
Introduction
The following table shows which events occur on which objects.
Technical data subject to change.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1841
Icon Object
IO field
Button
Symbolic IO field
Graphic IO field
Date/time field
Bar
Switch
Symbol library
Slider
Gauge
Clock
Cleared (Page 1845) -- -- -- -- -- -- -- -- -- -- --
Activate (Page 1845) -- -- -- --
Adjust (Page 1845) -- -- -- -- -- --
Loaded (Page 1846) -- -- -- -- -- -- -- -- -- -- --
Execute (Page 1846) -- -- -- -- -- -- -- -- -- -- --
Selection changed (Page 1846) -- -- -- -- -- -- -- -- -- -- --
When dialog is opened (Page 1846) -- -- -- -- -- -- -- -- -- -- --
When dialog is closed (Page 1847) -- -- -- -- -- -- -- -- -- -- --
User change (Page 1847) -- -- -- -- -- -- -- -- -- -- --
Screen change (Page 1847) -- -- -- -- -- -- -- -- -- -- --
Deactivate (Page 1847) -- -- -- --
Double-click (Page 1848) -- -- -- -- -- -- -- -- -- --
Press (Page 1848) -- -- -- -- -- -- -- -- --
On Finish Input (Page 1849) -- -- -- -- -- -- -- --
Press ESC twice (Page 1849) -- -- -- -- -- -- -- -- -- -- --
Outgoing (Page 1849) -- -- -- -- -- -- -- -- -- -- --
Incoming (Page 1850) -- -- -- -- -- -- -- -- -- -- --
Click (Page 1850) -- -- -- -- -- -- -- -- --
Click when flashing (Page 1851) -- -- -- -- -- -- -- -- -- -- --
Loop-in alarm (Page 1851) -- -- -- -- -- -- -- -- -- -- --
Release (Page 1851) -- -- -- -- -- -- -- -- --
In the event of high limit violation
(Page 1850)
-- -- -- -- -- -- -- -- -- -- --
Alarm buffer overflow (Page 1852) -- -- -- -- -- -- -- -- -- -- --
In the event of low limit violation
(Page 1852)
-- -- -- -- -- -- -- -- -- -- --
Acknowledge (Page 1852) -- -- -- -- -- -- -- -- -- -- --
Reach margin (Page 1852) -- -- -- -- -- -- -- -- -- -- --
Runtime Stop (Page 1853) -- -- -- -- -- -- -- -- -- -- --
Press key (Page 1853) -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1842 System Manual, 08/2011,
Release key (Page 1854) -- -- -- -- -- -- -- -- -- -- --
Overflow (Page 1854) -- -- -- -- -- -- -- -- -- -- --
Switching (Page 1854) -- -- -- -- -- -- -- -- -- -- --
Switch OFF (Page 1855) -- -- -- -- -- -- -- -- -- --
Switch ON (Page 1855) -- -- -- -- -- -- -- -- -- --
Low free storage space (Page 1855) -- -- -- -- -- -- -- -- -- --
Free space critically low (Page 1855) -- -- -- -- -- -- -- -- -- --
Value change (Page 1855) -- -- -- -- -- -- -- -- -- -- --
Time expired (Page 1856) -- -- -- -- -- -- -- -- -- -- --
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
Cleared (Page 1845) -- -- -- -- -- -- -- -- -- -- --
Activate (Page 1845) -- -- --
Adjust (Page 1845) -- -- -- -- -- -- -- -- -- -- --
Loaded (Page 1846) -- -- -- -- -- -- -- -- -- -- --
Execute (Page 1846) -- -- -- -- -- -- -- -- -- -- --
Selection changed (Page 1846) -- -- -- -- -- -- -- -- -- --
When dialog is opened (Page 1846) -- -- -- -- -- -- -- -- -- -- --
When dialog is closed (Page 1847) -- -- -- -- -- -- -- -- -- -- --
User change (Page 1847) -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1843
Screen change (Page 1847) -- -- -- -- -- -- -- -- -- -- --
Deactivate (Page 1847) -- -- -- --
Double-click (Page 1848) -- -- -- -- -- -- -- -- -- -- --
Press (Page 1848) -- -- -- -- -- -- -- -- -- -- --
On Finish Input (Page 1849) -- -- -- -- -- -- -- -- -- --
Press ESC twice (Page 1849) -- -- -- -- -- -- -- -- -- -- --
Outgoing (Page 1849) -- -- -- -- -- -- -- -- -- -- --
Incoming (Page 1850) -- -- -- -- -- -- -- -- -- -- --
Click (Page 1850) -- -- -- -- -- -- -- -- -- --
Click when flashing (Page 1851) -- -- -- -- -- -- -- -- -- --
Loop-in alarm (Page 1851) -- -- -- -- -- -- -- -- -- -- --
Release (Page 1851) -- -- -- -- -- -- -- -- -- -- --
In the event of high limit violation
(Page 1850)
-- -- -- -- -- -- -- -- -- -- --
Alarm buffer overflow (Page 1852) -- -- -- -- -- -- -- -- -- -- --
In the event of low limit violation
(Page 1852)
-- -- -- -- -- -- -- -- -- -- --
Acknowledge (Page 1852) -- -- -- -- -- -- -- -- -- -- --
Reach margin (Page 1852) -- -- -- -- -- -- -- -- -- -- --
Runtime Stop (Page 1853) -- -- -- -- -- -- -- -- -- -- --
Press key (Page 1853) -- -- -- -- -- -- -- -- -- --
Release key (Page 1854) -- -- -- -- -- -- -- -- -- --
Overflow (Page 1854) -- -- -- -- -- -- -- -- -- -- --
Switching (Page 1854) -- -- -- -- -- -- -- -- -- -- --
Switch OFF (Page 1855) -- -- -- -- -- -- -- -- -- -- --
Switch ON (Page 1855) -- -- -- -- -- -- -- -- -- -- --
Low free storage space (Page 1855) -- -- -- -- -- -- -- -- -- -- --
Free space critically low (Page 1855) -- -- -- -- -- -- -- -- -- -- --
Value change (Page 1855) -- -- -- -- -- -- -- -- -- -- --
Time expired (Page 1856) -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1844 System Manual, 08/2011,
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1845
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.
Execute
Description
Occurs when the scheduled task has been executed.
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1846 System Manual, 08/2011,
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1847
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1848 System Manual, 08/2011,
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1849
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.
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:
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1850 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1851
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.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1852 System Manual, 08/2011,
Note
A user-defined function must not be configured for the "Boundary reached" event.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1853
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.
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.
Switching
Description
Occurs when the user toggles a display and operating object, e.g. a switch from "ON" to "OFF".
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1854 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1855
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.3 Reference (RT Professional)
9.8.3.1 C scripting
System functions
ActivateNextScreen
Description
WinCC saves the names of the screens opened by the user during runtime as well as the
sequence in which these screens were opened.
Can only be used in C scripting.
The maximum number of screen names is specified in the "Runtime settings > Screens >
Screen buffer" editor.
The ActivateNextScreen system function now opens the screen that was opened before the
last call of ActivatePreviousScreen.
Syntax
BOOL ActivateNextScreen();
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1856 System Manual, 08/2011,
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
See also
ActivatePreviousScreen (Page 1857)
ActivatePreviousScreen
Description
WinCC saves the names of the screens opened by the user during runtime as well as the
sequence in which these screens were opened.
The system function can be used in C scripting only.
The maximum number of screen names is specified in the "Settings > Screens" editor.
The ActivatePreviousScreen system function now opens the screen which was opened before
the currently open screen.
Syntax
BOOL ActivatePreviousScreen();
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
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 (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1857
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 "Auto-Hotspot".
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.
ActivateScreenInScreenWindow
Description
Performs a screen change to the specified screen in a specified screen window.
Use in the function list
ActivateScreenInScreenWindow (Screen name, Screen window, New screen name)
Use in user-defined functions
ActivateScreenInScreenWindow (Screen_name, Screen_window, New_screen_name)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1858 System Manual, 08/2011,
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Screen name
Name of the screen to be displayed in the screen window.
Screen window
Name of the screen window in which the new screen is to be displayed.
New screen name
Name of the new screen to be displayed in the screen window.
See also
Example of configuring a screen change via a property (Page 1836)
ActivateStartScreen
Description
Opens the entered start picture.
Can only be used in C scripting.
Syntax
BOOL ActivateStartScreen();
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
ActivateStoredScreen
Description
Opens the screen saved with the StoreScreen system function.
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1859
Syntax
BOOL ActivateStoredScreen();
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
See also
StoreScreen (Page 1919)
DecreaseTag
Description
Subtracts the given value from the tag value.
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, auxiliary tags must be used. You can use the "SetTag" system
function to assign the tag value to the auxiliary tags.
If you configure the system function for events of an alarm and the tag is not being used in the
current screen, it is not ensured that the actual tag value 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 "Auto-Hotspot".
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1860 System Manual, 08/2011,
Parameters
Tag
The tag from which the given value is subtracted.
Value
The value that is subtracted.
GetLocalScreen
Description
Returns a pointer to the screen name.
Can only be used in C scripting.
Syntax
char* GetLocalScreen(char* Screen name);
Parameters
Screen name
Pointer on the screen
Return value
Pointer on the name of the picture.
Note
The syntax of the transferred call parameterScreen name must correspond to that formed by
the graphics system for the screen paths:
<RootScreenName>.<ScreenWindowName>:<ScreenName>. ... .<ScreenWindowName>:<
ScreenName>.
Example:
In a basic picture "AAA" there is a picture window "bbb" in which a picture "CCC" is called
which itself contains a picture window "ddd" in which a picture "EEE" is called.
Then the system function GetLocalScreen(Screen name) returns the pointer to the
screen name:
"EEE" if the system function is called in the picture "EEE";
"CCC" if the system function is called in the picture "CCC";
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1861
"AAA" if the system function is called in the picture "AAA".
GetLinkedTag
Description
Returns the name of the tag which is logically linked to the specified object property.
Can only be used in C scripting.
Syntax
char* GetLinkedTag(char* Screen Name, char* Object, char* Name of Property);
Parameters
Screen Name
Pointer to the screen
Object
Pointer to the object
Name of Property
Pointer to the object property
Return value
Pointer to the name of the tag which is logically linked to the specified object property.
GetLanguageByLocaleID
Description
Determines the current Runtime language.
Can only be used in C scripting.
Syntax
DWORD GetLanguageByLocaleID ();
Return value
Language ID.
The following assignments are valid (hexadecimal language code):
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1862 System Manual, 08/2011,
Symbolic name Value(hexadecimal
)
Abbreviation
LANG_ARABIC 0x0401
LANG_AFRIKAANS 0x0436
LANG_ALBANIAN 0x041C
LANG_BASQUE 0x042D
LANG_BULGARIAN 0x0402
LANG_BYELORUSSIAN 0x0423
LANG_CATALAN 0x0403
LANG_CHINESE 0x0404
LANG_CROATIAN 0x041A
LANG_CZECH 0x0405 CSY
LANG_DANISH 0x0406 DAN
LANG_DUTCH 0x0413 NLD
LANG_ENGLISH 0x0409 ENU
LANG_ESTONIAN 0x0425
LANG_FAEROESE 0x0438
LANG_FARSI 0x0429
LANG_FINNISH 0x040B FIN
LANG_FRENCH 0x040C FRA
LANG_GERMAN 0x0407 DEU
LANG_GREEK 0x0408
LANG_HEBREW 0x040D
LANG_HUNGARIAN 0x040E HUN
LANG_ICELANDIC 0x040F ISL
LANG_INDONESIAN 0x0421
LANG_ITALIAN 0x0410 ITA
LANG_JAPANESE 0x0411
LANG_KOREAN 0x0412
LANG_LATVIAN 0x0426
LANG_LITHUANIAN 0x0427
LANG_NORWEGIAN 0x0414 NOR
LANG_POLISH 0x0415 PLK
LANG_PORTUGUESE 0x0416 PTB
LANG_ROMANIAN 0x0418
LANG_RUSSIAN 0x0419 RUS
LANG_SLOVAK 0x041B SKY
LANG_SLOVENIAN 0x0424
LANG_SORBIAN 0x042E
LANG_SPANISH 0x040A ESP
LANG_SWEDISH 0x041D SVE
LANG_THAI 0x041E
LANG_TURKISH 0x041F TRK
LANG_UKRAINIAN 0x0422
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1863
GetParentScreen
Description
Returns a pointer to the screen name.
Can only be used in C scripting.
Syntax
char* GetParentScreen(char* Screen name);
Parameters
Screen name
Pointer to the screen
Return value
Name of the current screen if the system function is called in the basic picture.
Name path of the higher-level screen if the system function is called in a screen window.
Note
The syntax of the transferred call parameter Screen name must correspond to that formed
by the graphics system for the screen paths:
<RootScreenName>.<ScreenWindowName>:<ScreenName>. ... .<ScreenWindowName>:<
ScreenName>.
GetParentScreenWindow
Description
Provides a pointer to the name of the picture window.
Can only be used in C scripting.
Syntax
char* GetParentScreenWindow(char* Screen name);
Parameters
Screen name
Pointer to the screen
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1864 System Manual, 08/2011,
Return value
Pointer to the name of the screen window if the system function is called in a screen which is
displayed in the screen window of a parent screen.
Call parameter "Screen name" unchanged if the system function is called in the basic screen.
Note
The syntax of the transferred call parameter Screen name must correspond to that formed
by the graphics system for the screen paths:
<RootScreenName>.<ScreenWindowName>:<ScreenName>. ... .<ScreenWindowName>:<
ScreenName>.
Example
In a basic picture "Picture_1" there is a picture window "Picture_window_1" in which a picture
"Picture_2" is called.
In the picture "Picture_2" there is a picture window "Picture_window_2" in which a picture
"Picture_3" is called.
Then the system function GetParentScreenWindow(Screen name) returns the pointer to
the screen window name:
"Screen_2", if the system function is called in "Screen_3";
"Screen_window_1", if the system function is called in "Screen_2";
"Screen_1", if the system function is called in "Screen_1".
GetProp
GetPropBOOL
Description
Returns the current status of a property of data type "BOOL".
Can only be used in C scripting.
Syntax
BOOL GetPropBOOL(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property)
Parameters
Screen name
Screen name
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1865
Object
Object name
Name of the Property
Name of the object property
Return value
Value of the property in data type "BOOL".
GetPropChar
Description
Returns the current value of a property of data type "Char".
Can only be used in C scripting.
Syntax
Char* GetPropChar(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property)
Parameters
Screen name
Screen name
Object
Object name
Name of the Property
Name of the object property
Return value
Value of the property in data type "Char".
GetPropDouble
Description
Returns the value of a property of data type "Double".
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1866 System Manual, 08/2011,
Syntax
double GetPropDouble(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property)
Parameters
Screen name
Screen name
Object
Object name
Name of the Property
Name of the object property
Return value
Value of the property in data type "Double".
GetPropLong
Description
Returns the status of a property of data type "long".
Can only be used in C scripting.
Syntax
long GetPropLong(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property)
Parameters
Screen name
Screen name
Object
Object name
Name of the Property
Name of the object property
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1867
Return value
Value of the property in data type "long".
GetServerTagPrefix
Description
In order for a WinCC client in a distributed system to access tags of the associated server, the
tag names must be expanded to include the server prefix.
Note
This system function is not supported at present.
A pointer of type "char" to ServerPrefix, TagPrefix, and WindowPrefix is returned in each case.
The user is not permitted to change the memory (including no strcat) or release it.
Can only be used in C scripting.
Syntax
void GetServerTagPrefix (char** ppszServerPrefix, char** ppszTagPrefix, char**
ppszWindowPrefix);
Return value
ppszServerPrefix
Pointer to a pointer that references the server prefix
ppszTagPrefix
Pointer to a pointer that references the tag prefix
ppszWindowPrefix
Pointer to a pointer that references the window prefix
GetTag
GetTagXXX
Description
The GetTagXXX function determines the value of a tag of a specified data type.
Can only be used in C scripting:
The following table shows the different GetTag functions for reading the tag value:
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1868 System Manual, 08/2011,
Type Function
name
Parameters PLC data type HMI data type
BOOL GetTagBit Tag Tag_Name Binary tag Bool
BYTE GetTagByt
e
Tag Tag_Name Unsigned 8-bit UByte
char* GetTagCh
ar
Tag Tag_Name Text tag 8-bit or
text tag 16-bit
String
double GetTagDo
uble
Tag Tag_Name Floating point 64-bit Double
DWOR
D
GetTagD
Word
Tag Tag_Name Unsigned 32-bit UInteger
float GetTagFlo
at
Tag Tag_Name Floating point 32-bit Float
BOOL GetTagRa
w
Tag Tag_Name,
BYTE* pValue,
DWORD size
Raw data type Raw
char GetTagSB
yte
Tag Tag_Name Signed 8-bit Byte
long int GetTagSD
Word
Tag Tag_Name Signed 32-bit Integer
short
int
GetTagS
Word
Tag Tag_Name Signed 16-bit Short
WORD GetTagWo
rd
Tag Tag_Name Unsigned 16-bit UShort
Syntax
<Type><FunctionName><(Parameter)>;
Example: BYTE GetTagByte (Tag Tag_Name);
Parameters
Tag_Name
Name of the tags
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
Value of the tags in the specified type.
The system function "GetTagChar" returns a pointer on the string that contains the value of
the tags.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1869
The "GetTagRaw" system function returns TRUE or FALSE:
TRUE: The system function has been completed without any errors.
FALSE: An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
Access to HMI tags (Page 1758)
GetTagMultiStateQCWait
Description
The values, status, and quality code of several tags are established and saved in the repsective
addresses in the specified format . The values are read explicitly from the AS.
Two DWORD arrays are transferred, in the member of which the status and quality codes of
the individual tags will be located after the system function has been called. The size of the
arrays must be large enough to provide sufficient storage space for the status and quality
codes.
Can only be used in C scripting.
Syntax
BOOL GetTagMultiStateQCWait (DWORD* pdwState, DWORD* pdwQualityCode, const
char* pFormat, ...);
Parameters
pdwState
Field in which the status of the individual tags is created after the system function cycle.
pdwQualityCode
Field in which the quality code of the individual tag is created after the system function cycle.
pFormat
Format description for all the requested tags along with the name and address of the value for
each tag.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1870 System Manual, 08/2011,
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
GetTagMultiStateWait
Description
The values and status of several tags are determined and saved in the respective addresses
in the specified format. The values are read explicitly from the AS.
The system function must be given a DWORD array, in the member of which the status of the
individual tags will be located after the system function has been called. The size of the array
must be large enough to provide sufficient storage space for the status.
Can only be used in C scripting.
Syntax
BOOL GetTagMultiStateWait(DWORD* pdwState, const char* pFormat);
Parameters
pdwState
Field in which the tag status is saved.
pFormat
Format description for all the requested tags along with the name and address of the value for
each tag.
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1871
GetTagMultiWait
Description
The values of several tags are determined and saved in the respective addresses in the
specified format. The value is read explicitly from the AS. The memory for the tag value is
created by the system function with SysMalloc.
Can only be used in C scripting.
Syntax
BOOL GetTagMultiWait(const char* pFormat,...);
Parameters
pFormat
Format description for all requested tags along with name and address of the value for each
tag.
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
GetTagStateXXX
Description
The GetTagStateXXX function determines the value of a tag of a specified data type. It also
returns the status of the tags.
Can only be used in C scripting.
The following table shows the different GetTagStateXXX functions for reading the tag value:
Type Function
name
Parameters PLC data type HMI data type
BOOL GetTagBitSt
ate
Tag Tag_Name, PDWORD
lp_dwstate
Binary tag Bool
BYTE GetTagByte
State
Tag Tag_Name, PDWORD
lp_dwstate
Unsigned 8-bit Byte
char* GetTagChar
State
Tag Tag_Name, PDWORD
lp_dwstate
Text tag 8-bit or text tag 16-
bit
String
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1872 System Manual, 08/2011,
Type Function
name
Parameters PLC data type HMI data type
double GetTagDou
bleState
Tag Tag_Name, PDWORD
lp_dwstate
Floating point 64-bit Double
DWORD GetTagDWo
rdState
Tag Tag_Name, PDWORD
lp_dwstate
Unsigned 32-bit UInteger
float GetTagFloat
State
Tag Tag_Name, PDWORD
lp_dwstate
Floating point 32-bit Float
BOOL GetTagRaw
State
Tag Tag_Name, BYTE*
pValue, DWORD size,
PDWORD lp_dwstate
Raw data type Raw
char GetTagSByt
eState
Tag Tag_Name, PDWORD
lp_dwstate
Signed 8-bit Byte
long int GetTagSD
WordState
Tag Tag_Name, PDWORD
lp_dwstate
Signed 32-bit Integer
short int GetTagSWo
rdState
Tag Tag_Name, PDWORD
lp_dwstate
Signed 16-bit Short
WORD GetTagWor
dState
Tag Tag_Name, PDWORD
lp_dwstate
Unsigned 16-bit UShort
Syntax
<Type><FunctionName><(Parameter)>;
Example: BOOL GetTagBitState (Tag Tag_Name, PDWORD lp_dwstate);
Parameters
Tag_Name
Name of the tags
lp_dwstate
Pointer on a DWORD in which the status of the tag is created after the system function cycle.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
Value of the tags in the specified type.
The system function "GetTagCharState" returns a pointer on the value of the tags in the "char"
data type.
The "GetTagRawState" system function returns TRUE or FALSE:
TRUE: The system function has been completed without any errors.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1873
FALSE: An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
GetTagStateQC
Description
The GetTagStateQC function determines the value of a tag of a specified data type. It also
returns the status and quality code of the tags.
Can only be used in C scripting.
The following table shows the different GetTagStateQC functions for reading the tag value:
Type Function
name
Parameters PLC data type HMI data type
BOOL GetTagBitStat
eQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Binary tag Bool
BYTE GetTagByteSt
ateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Unsigned 8-bit UByte
char* GetTagCharS
tateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Text tag 8-bit or text tag
16-bit
String
double GetTagDoubl
eStateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Floating point 64-bit Double
DWO
RD
GetTagDWor
dStateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Unsigned 32-bit UInteger
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1874 System Manual, 08/2011,
Type Function
name
Parameters PLC data type HMI data type
float GetTagFloatS
tateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Floating point 32-bit Float
BOOL GetTagRawSt
ateQC
Tag Tag_Name,
BYTE pValue[],
DWORD size,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Raw data type Raw
signed
char
GetTagSByte
StateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Signed 8-bit Byte
long GetTagSDWo
rdStateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Signed 32-bit Integer
short GetTagSWor
dStateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Signed 16-bit Short
WOR
D
GetTagWord
StateQC
Tag Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCode
Unsigned 16-bit UShort
Syntax
<Type><FunctionName><(Parameter)>;
Example: BOOL GetTagBitStateQC (Tag Tag_Name, PDWORD lp_dwstate, PDWORD
pdwQualityCode);
Parameters
Tag_Name
Name of the tag
lp_dwstate
Pointer on a DWORD in which the status of the tag is created after the system function cycle.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1875
pdwQualityCode
Pointer on a DWORD in which the quality code of the tag is created after the system function
cycle.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
Value of the tags in the specified type.
The system function "GetTagCharStateQC" returns a pointer on the value of the tags in the
"char" data type.
The "GetTagRawStateQC" system function returns TRUE or FALSE:
TRUE: The system function has been completed without any errors.
FALSE: An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
GetTagStateQCWait
Description
The GetTagStateQCWait function determines the value of a tag of a specified data type. The
value is read explicitly from the AS. It also returns the status and quality code of the tags.
Can only be used in C scripting.
The following table shows the different GetTagStateQCWait functions for reading the tag value:
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1876 System Manual, 08/2011,
Type Function name Parameters PLC data type HMI data type
BOOL GetTagBitStateQ
CWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Binary tag Bool
BYTE GetTagByteState
QCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Unsigned 8-bit UByte
char* GetTagCharStat
eQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Text tag 8-bit or text tag
16-bit
String
double GetTagDoubleSt
ateQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Floating point 64-bit Double
DWOR
D
GetTagDWordSt
ateQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Unsigned 32-bit UInteger
float GetTagFloatStat
eQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Floating point 32-bit Float
BOOL GetTagRawState
QCWait
Tag
Tag_Name,
BYTE pValue[],
DWORD size,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Raw data type Raw
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1877
Type Function name Parameters PLC data type HMI data type
signed
char
GetTagSByteStat
eQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Signed 8-bit Byte
long GetTagSDWordS
tateQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Signed 32-bit Integer
short GetTagSWordSt
ateQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Signed 16-bit Short
WORD GetTagWordStat
eQCWait
Tag
Tag_Name,
PDWORD
lp_dwstate,
PDWORD
pdwQualityCod
e
Unsigned 16-bit UShort
Syntax
<Type><FunctionName><(Parameter)>;
Example: BOOL GetTagBitStateQC (Tag Tag_Name, PDWORD lp_dwstate, PDWORD
pdwQualityCode);
Parameters
Tag_Name
Name of the tags
lp_dwstate
Pointer on a DWORD in which the status of the tag is created after the system function cycle.
pdwQualityCode
Pointer on a DWORD in which the quality code of the tag is created after the system function
cycle.
pValue
Pointer to a byte field containing the value of the raw data tags.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1878 System Manual, 08/2011,
size
Size of the byte field in bytes
Return value
Value of the tags in the specified type.
The system function "GetTagCharStateQCWait" returns a pointer on the value of the tags in
the "char" data type.
The "GetTagRawStateQCWait" system function returns TRUE or FALSE:
TRUE: The system function has been completed without any errors.
FALSE: An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
GetTagStateWait
Description
The GetTagStateWait function determines the value of a tag of a specified data type. The value
is read explicitly from the AS. It also returns the status of the tags.
Can only be used in C scripting.
The following table shows the different GetTagStateWait functions for reading the tag value:
Type Function name Parameters PLC data type HMI data type
BOOL GetTagBitStat
eWait
Tag Tag_Name,
PDWORD lp_dwstate
Binary tag Bool
BYTE GetTagByteSt
ateWait
Tag Tag_Name,
PDWORD lp_dwstate
Unsigned 8-bit UByte
char* GetTagCharSt
ateWait
Tag Tag_Name,
PDWORD lp_dwstate
Text tag 8-bit or text tag
16-bit
String
double GetTagDouble
StateWait
Tag Tag_Name,
PDWORD lp_dwstate
Floating point 64-bit Double
DWO
RD
GetTagDWord
StateWait
Tag Tag_Name,
PDWORD lp_dwstate
Unsigned 32-bit UInteger
float GetTagFloatSt
ateWait
Tag Tag_Name,
PDWORD lp_dwstate
Floating point 32-bit Float
BOOL GetTagRawSt
ateWait
Tag Tag_Name,
BYTE* pValue,
DWORD size,
PDWORD lp_dwstate
Raw data type Raw
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1879
Type Function name Parameters PLC data type HMI data type
char GetTagSByteS
tateWait
Tag Tag_Name,
PDWORD lp_dwstate
Signed 8-bit Byte
long
int
GetTagSDWor
dStateWait
Tag Tag_Name,
PDWORD lp_dwstate
Signed 32-bit Integer
short
int
GetTagSWord
StateWait
Tag Tag_Name,
PDWORD lp_dwstate
Signed 16-bit Short
WOR
D
GetTagWordSt
ateWait
Tag Tag_Name,
PDWORD lp_dwstate
Unsigned 16-bit UShort
Syntax
<Type><FunctionName><(Parameter)>
Example: BOOL GetTagBitStateWait (Tag Tag_Name, PDWORD lp_dwstate).
Parameters
Tag_Name
Name of the tags
lp_dwstate
Pointer on a DWORD in which the status of the tag is created after the system function cycle.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
Value of the tags in the specified type.
The system function "GetTagCharStateWait" returns a pointer on the value of the tags in the
"char" data type.
The "GetTagRawState" system function returns TRUE or FALSE.
TRUE: The system function has been completed without any errors.
FALSE: An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1880 System Manual, 08/2011,
GetTagValue
Description
Enables the transfer of a value in the form of a variant. Determines the pointer on the results
structure that contains the value.
Can only be used in C scripting.
Syntax
BOOL GetTagValue(LPDM_VARKEY lpdmVarKey, LPDM_VAR_UPDATE_STRUCT
lpdmresult, LPCMN_ERROR lpdmError);
Parameters
lpdmVarKey
Pointer on a structure of data type "DM_VARKEY"
lpdmresult
Pointer on the value of data type "DM_VAR_UPDATE_STRUCT"
lpdmError
Pointer on the structure that contains the error description.
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
GetTagValueStateQC
Description
Enables the transfer of a value in the form of a variant. Determines the pointer on the results
structure that contains the value. It also returns the status and quality code of the tags.
The system function can be used in C scripting only.
Syntax
BOOL GetTagValueStateQC (LPDM_VARKEY, lpdmVarKey,
LPDM_VAR_UPDATE_STRUCTEX lpdmresult, LPCMN_ERROR lpdmError);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1881
Parameters
lpdmVarKey
Pointer on a structure of data type "DM_VARKEY"
lpdmresult
Pointer on the value of data type "DM_VAR_UPDATE_STRUCTEX"
lpdmError
Pointer on the structure that contains the error description.
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
GetTagValueStateQCWait
Description
Enables the transfer of a value in the form of a variant. Determines the pointer on the results
structure that contains the value. The value is read explicitly from the AS. It also returns the
status and quality code of the tags.
Can only be used in C scripting.
Syntax
BOOL GetTagValueStateQCWait (LPDM_VARKEY lpdmVarKey,
LPDM_VAR_UPDATE_STRUCTEX lpdmresult, LPCMN_ERROR lpdmError);
Parameters
lpdmVarKey
Pointer on a structure of data type "DM_VARKEY"
lpdmresult
Pointer on the value of data type "DM_VAR_UPDATE_STRUCTEX"
lpdmError
Pointer on the structure that contains the error description.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1882 System Manual, 08/2011,
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
GetTagValueWait
Description
Enables the transfer of a value in the form of a variant. Determines the pointer on the results
structure that contains the value. The value is read directly from the AS.
Can only be used in C scripting.
Syntax
BOOL GetTagValueWait(LPDM_VARKEY lpdmVarKey, LPDM_VAR_UPDATE_STRUCT
lpdmresult, LPCMN_ERROR lpdmError);
Parameters
lpdmVarKey
Pointer on a structure of data type "DM_VARKEY"
lpdmresult
Pointer on the value of data type "DM_VAR_UPDATE_STRUCT"
lpdmError
Pointer on the structure that contains the error description
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1883
GetTagWait
Description
The GetTagWait function establishes the value of a tag of a specified data type. The value is
read explicitly from the AS.
Can only be used in C scripting.
The following table shows the different GetTagWait functions for reading the tag value:
Type Function
name
Parameters PLC data type HMI data type
BOOL GetTagBitW
ait
Tag Tag_Name Binary tag Bool
BYTE GetTagByte
Wait
Tag Tag_Name Unsigned 8-bit UByte
char* GetTagChar
Wait
Tag Tag_Name Text tag 8-bit or text tag
16-bit
String
double GetTagDoub
leWait
Tag Tag_Name Floating point 64-bit Double
DWOR
D
GetTagDWor
dWait
Tag Tag_Name Unsigned 32-bit UInteger
float GetTagFloat
Wait
Tag Tag_Name Floating point 32-bit Float
BOOL GetTagRaw
Wait
Tag Tag_Name,
BYTE* pValue,
DWORD size
Raw data type Raw
char GetTagSByt
eWait
Tag Tag_Name Signed 8-bit Byte
long int GetTagSDW
ordWait
Tag Tag_Name Signed 32-bit Integer
short
int
GetTagSWor
dWait
Tag Tag_Name Signed 16-bit Short
WORD GetTagWord
Wait
Tag Tag_Name Unsigned 16-bit UShort
Syntax
<Type><FunctionName><(Parameter)>;
Example: BYTE GetTagByteWait (Tag Tag_Name);
Parameters
Tag_Name
Name of the tags
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1884 System Manual, 08/2011,
pValue
Pointer to a byte field containing the value of the raw data tags.
Return value
Value of the tags in the specified type.
The system function "GetTagCharWait" returns a pointer on the string that contains the value
of the tags.
The "GetTagRawWait" system function returns TRUE or FALSE:
TRUE: The system function has been completed without any errors.
FALSE: An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
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, auxiliary tags must be used. You can use the "SetTag" system
function to assign the tag value to the auxiliary tags.
If you configure the system function for events of an alarm and the tag is not being used in the
current screen, it is not ensured that the actual tag value 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 "Auto-Hotspot".
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1885
Parameters
Tag
The tag to which the given value is added.
Value
The value that is added.
InquireLanguage
Description
Determines all languages configured in the text library for the runtime.
Use Pointer to a counter to specify the storage location for language IDs.
The system function can be used in C scripting only.
Syntax
DWORD* InquireLanguage (DWORD* Pointer to a counter);
Parameters
Pointer to a counter
Pointer to the number of language IDs found
Return value
Pointer to a field containing the established language IDs.
The following assignments apply (hexadecimal language code):
Symbolic description Value(hexadecimal
)
Abbreviation
LANG_ARABIC 0x0401
LANG_AFRIKAANS 0x0436
LANG_ALBANIAN 0x041C
LANG_BASQUE 0x042D
LANG_BULGARIAN 0x0402
LANG_BYELORUSSIAN 0x0423
LANG_CATALAN 0x0403
LANG_CHINESE 0x0404
LANG_CROATIAN 0x041A
LANG_CZECH 0x0405 CSY
LANG_DANISH 0x0406 DAN
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1886 System Manual, 08/2011,
Symbolic description Value(hexadecimal
)
Abbreviation
LANG_DUTCH 0x0413 NLD
LANG_ENGLISH 0x0409 ENU
LANG_ESTONIAN 0x0425
LANG_FAEROESE 0x0438
LANG_FARSI 0x0429
LANG_FINNISH 0x040B FIN
LANG_FRENCH 0x040C FRA
LANG_GERMAN 0x0407 DEU
LANG_GREEK 0x0408
LANG_HEBREW 0x040D
LANG_HUNGARIAN 0x040E HUN
LANG_ICELANDIC 0x040F ISL
LANG_INDONESIAN 0x0421
LANG_ITALIAN 0x0410 ITA
LANG_JAPANESE 0x0411
LANG_KOREAN 0x0412
LANG_LATVIAN 0x0426
LANG_LITHUANIAN 0x0427
LANG_NORWEGIAN 0x0414 NOR
LANG_POLISH 0x0415 PLK
LANG_PORTUGUESE 0x0416 PTB
LANG_ROMANIAN 0x0418
LANG_RUSSIAN 0x0419 RUS
LANG_SLOVAK 0x041B SKY
LANG_SLOVENIAN 0x0424
LANG_SORBIAN 0x042E
LANG_SPANISH 0x040A ESP
LANG_SWEDISH 0x041D SVE
LANG_THAI 0x041E
LANG_TURKISH 0x041F TRK
LANG_UKRAINIAN 0x0422
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1887
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 "Auto-Hotspot".
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.
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).
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1888 System Manual, 08/2011,
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 "Auto-Hotspot".
Parameters
Tag
The tag whose bit is set.
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 "Auto-Hotspot".
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1889
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.
IsUserAuthorized
Description
Authentication of users.
Can only be used in C scripting.
Syntax
BOOL IsUserAuthorized (DWORD AuthorizationNumber);
Parameters
AuthorizationNumber
Authorization (numerical) to be verified.
Return value
TRUE
The user has the specified authorization.
FALSE
The user does not have the specified authorization.
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1890 System Manual, 08/2011,
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 "Auto-Hotspot".
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.
ReportJob
Description
A print job, or the preview for a print job is started depending on the value of the Name of
method parameter.
Can only be used in C scripting.
Syntax
void ReportJob(LPCSTR Print job name, LPCSTR Name of method)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1891
Parameters
Print job name
Pointer to the name of the print job
Name of method
Defines whether to start the print job or a print job preview:
PRINTJOB: Print job is started
PREVIEW: Print job preview is started
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 "Auto-Hotspot".
Parameters
Tag
The BOOL type tag which is set to 0 (FALSE).
ResetBitInTag
Description
Sets a bit in the specified tag to 0 (FALSE).
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1892 System Manual, 08/2011,
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)
Use in user-defined functions
ResetBitInTag (Tag, Bit)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
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.
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 "Auto-Hotspot".
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1893
Parameters
Tag
The BOOL type tag which is set to 1 (TRUE).
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 "Auto-Hotspot".
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).
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1894 System Manual, 08/2011,
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.
SetLanguageByLocaleID
Description
Changes the language setting in Runtime.
Can only be used in C scripting.
Syntax
BOOL SetLanguageByLocaleID (DWORD dwLocaleID);
Parameters
dwLocaleID
Language ID of the language to be set
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
See also
Example of configuring a language switch (Page 1835)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1895
SetProp
SetPropBOOL
Description
Sets an object property of data type "BOOL".
Can only be used in C scripting.
Syntax
BOOL SetPropBOOL(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property, BOOL Value)
Parameters
Screen name
Screen name
Object
Object name
Name of the Property
Name of the object property The parameter Name of the property = NULL must be set if the
function call refers to the screen object.
Value
Value assigned to the object property of data type "BOOL".
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
SetPropChar
Description
Sets an object property of data type "char".
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1896 System Manual, 08/2011,
Syntax
BOOL SetPropChar(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property, char* Value)
Parameters
Screen name
Screen name
Object
Object name
Name of the Property
Name of the object property The parameter Name of the property = NULL must be set if the
function call refers to the screen object.
Value
Value assigned to the object property of data type "char".
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
SetPropDouble
Description
Sets an object property of data type "Double".
Can only be used in C scripting.
Syntax
BOOL SetPropDouble(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property, double Value)
Parameters
Screen name
Screen name
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1897
Object
Object name
Name of the Property
Name of the object property The parameter Name of the property = NULL must be set if the
function call refers to the screen object.
Value
Value assigned to the object property of data type "double".
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
See also
Example of accessing objects in the Screens editor (Page 1834)
SetPropLong
Description
Sets an object property of data type "long".
Can only be used in C scripting.
Syntax
BOOL SetPropLong(LPCTSTR Screen name, LPCTSTR Object, LPCTSTR Name of the
property, long Value)
Parameters
Screen name
Screen name
Object
Object name
Name of the Property
Name of the object property The parameter Name of the property = NULL must be set if the
function call refers to the screen object.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1898 System Manual, 08/2011,
Value
Value assigned to the object property of data type "long".
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
See also
Example of writing object properties (Page 1838)
Accessing objects with C (Page 1772)
SetPropertyByConstant
Description
Specifies the value of an object property as a string.
Use in the function list
SetPropertyByConstant (Screen name, Object, Name of the property, Value)
Use in user-defined functions
SetPropertyByConstant
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Screen name
Name of the screen that contains the object.
Object
Name of the object whose property is changed.
Name of the property
Name of the property that will be changed.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1899
Value
The value assigned to the property.
See also
Example of defining object colors (Page 1834)
SetPropertyByProperty
Description
Specifies the value of an object property with another object property.
Use in the function list
SetPropertyByProperty (Screen name, Object, Name of the property, Destination screen
name, Destination object, Destination property name)
Use in user-defined functions
SetPropertyByProperty (Screen_name, Screen_object, Property_name,
Source_screen_name, Source_screen_object, Source_property_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Screen name
Name of the screen that contains the object.
Object
Name of the object whose property is transferred to the destination object.
Name of the property
Name of the property that will be transferred to the destination object.
Destination screen name
Name of the screen that contains the destination object.
Destination object
Name of the destination object to which the property is transferred.
Destination property name
Name of the property that will be changed.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1900 System Manual, 08/2011,
SetPropertyByTag
Description
Specifies the value of an object property with a tag value.
Use in the function list
SetPropertyByTag (Screen name, Object, Name of the property, Tag name)
Use in user-defined functions
SetPropertyByTag (Screen_name, Screen_object, Property_name, Tag_name)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Screen name
Name of the screen that contains the object.
Object
Name of the object whose property you want to set with a tag value.
Name of the property
Name of the property that is set with the tag value.
Tag name
Name of the tag that contains the value of the property.
SetPropertyByTagIndirect
Description
Specifies the value of an object property with a tag. The tag contains the tag name that specifies
the object property.
Use in the function list
SetPropertyByTagIndirect (Screen name, Object, Name of property, Tag name)
Use in user-defined functions
SetPropertyByTagIndirect (Screen_name, Screen_object, Property_name, Tag_name)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1901
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Screen name
Name of the screen that contains the object.
Object
Name of the object whose property you want to set with a tag value.
Name of the property
Name of the property that is set with the tag value.
Tag name
Name of the tag that, in turn, contains the name of the tag that specifies the object property.
SetTag
SetTagXXX
Description
The SetTagXXX function sets the value of a tag of the specified data type.
Can only be used in C scripting.
The following table shows the different SetTag functions for setting the tag value:
Function
name
Parameters PLC data type HMI data type
SetTagBit Tag Tag_Name, short int value Binary tag Bool
SetTagByt
e
Tag Tag_Name, BYTE value Unsigned 8-bit UByte
SetTagCh
ar
Tag Tag_Name, LPSTR value Text tag 8-bit or text tag 16-
bit
String
SetTagDo
uble
Tag Tag_Name, double value Floating point 64-bit Double
SetTagD
Word
Tag Tag_Name, DWORD
value
Unsigned 32-bit UInteger
SetTagFlo
at
Tag Tag_Name, float value Floating point 32-bit Float
SetTagRa
w
Tag Tag_Name, BYTE*
pValue, DWORD size
Raw data type Raw
SetTagSB
yte
Tag Tag_Name, char value Signed 8-bit Byte
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1902 System Manual, 08/2011,
Function
name
Parameters PLC data type HMI data type
SetTagSD
Word
Tag Tag_Name, long int value Signed 32-bit Integer
SetTagS
Word
Tag Tag_Name, short int value Signed 16-bit Short
SetTagWo
rd
Tag Tag_Name, WORD value Unsigned 16-bit UShort
Syntax
BOOL<FunctionName><(Parameter)>;
Example: BOOL SetTagBit (Tag Tag_Name, short int value);
Parameters
Tag_Name
Name of the tags
value
Value of the tags of a specified type.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
Access to HMI tags (Page 1758)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1903
SetTagMultiStateWait
Description
Sets the values of several tags. The system function will end only after the AS has reported
the acceptance of the value.
The system function can be used in C scripting only.
The system function must be given a DWORD array, in the member of which the status of the
individual tags will be located after the system function has been called. The size of the array
must be large enough to provide sufficient storage space for the status.
Syntax
BOOL SetTagMultiStateWait(DWORD* pdwState, const char* pFormat,...);
Parameters
pdwState
Field in which the tag status is saved.
pFormat
Format description for all the requested tags along with the name and value for each tag.
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
SetTagMultiWait
Description
The values of several tags are set in the specified format. The system function will end only
after the AS has reported the acceptance of the value.
Can only be used in C scripting.
Syntax
BOOL SetTagMultiWait(const char* pFormat,...);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1904 System Manual, 08/2011,
Parameters
pFormat
Format description for all the requested tags along with the name and value for each tag.
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
SetTagStateXXX
Description
Sets the value of a tag of a specified data type. It also returns the status of the tags.
Can only be used in C scripting.
The following table shows the different SetTagStateXXX functions for setting the tag value:
Function name Parameters PLC data type HMI data type
SetTagBitState Tag Tag_Name, short
int value, PDWORD
lp_dwstate
Binary tag Bool
SetTagByteStat
e
Tag Tag_Name, BYTE
value, PDWORD
lp_dwstate
Unsigned 8-bit UByte
SetTagCharStat
e
Tag Tag_Name, LPSTR
value, PDWORD
lp_dwstate
Text tag 8-bit or text tag 16-
bit
String
SetTagDoubleSt
ate
Tag Tag_Name, double
value, PDWORD
lp_dwstate
Floating point 64-bit Double
SetTagDWordSt
ate
Tag Tag_Name,
DWORD value,
PDWORD lp_dwstate
Unsigned 32-bit UInteger
SetTagFloatStat
e
Tag Tag_Name, float
value, PDWORD
lp_dwstate
Floating point 32-bit Float
SetTagRawStat
e
Tag Tag_Name, BYTE*
pValue, DWORD size,
PDWORD lp_dwstate
Raw data type Raw
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1905
Function name Parameters PLC data type HMI data type
SetTagSByteSt
ate
Tag Tag_Name, signed
char value, PDWORD
lp_dwstate
Signed 8-bit Byte
SetTagSDWord
State
Tag Tag_Name, long int
value, PDWORD
lp_dwstate
Signed 32-bit Integer
SetTagSWordSt
ate
Tag Tag_Name, short
int value, PDWORD
lp_dwstate
Signed 16-bit Short
SetTagWordSta
te
Tag Tag_Name, WORD
value, PDWORD
lp_dwstate
Unsigned 16-bit UShort
Syntax
BOOL <FunctionName><(Parameter)>;
Example: BOOL SetTagBitState (Tag Tag_Name, short int value, PDWORD lp_dwstate);
Parameters
Tag_Name
Name of the tags
value
Value of the tags of a specified type.
lp_dwstate
Pointer on a DWORD in which the status of the tag is created after the system function cycle.
pFormat
Format description for all the requested tags along with name and value for each tag.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1906 System Manual, 08/2011,
FALSE
An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
SetTagStateWaitXXX
Description
Sets the value of a tag of a specified data type. The system function will end only after the AS
has reported the acceptance of the value. It also returns the status of the tags.
Can only be used in C scripting.
The following table shows the different SetTagState functions for setting the tag value:
Function name Parameters PLC data type HMI data type
SetTagBitStateWa
it
Tag Tag_Name, short
int value, PDWORD
lp_dwstate
Binary tag Bool
SetTagByteState
Wait
Tag Tag_Name, BYTE
value, PDWORD
lp_dwstate
Unsigned 8-bit UByte
SetTagCharState
Wait
Tag Tag_Name,
LPSTR value,
PDWORD lp_dwstate
Text tag 8-bit or text tag 16-
bit
String
SetTagDoubleStat
eWait
Tag Tag_Name, double
value, PDWORD
lp_dwstate
Floating point 64-bit Double
SetTagDWordStat
eWait
Tag Tag_Name,
DWORD value,
PDWORD lp_dwstate
Unsigned 32-bit UInteger
SetTagFloatState
Wait
Tag Tag_Name, float
value, PDWORD
lp_dwstate
Floating point 32-bit Float
SetTagRawState
Wait
Tag Tag_Name, BYTE*
pValue, DWORD size,
PDWORD lp_dwstate
Raw data type Raw
SetTagSByteState
Wait
Tag Tag_Name, char
value, PDWORD
lp_dwstate
Signed 8-bit Byte
SetTagSDWordSt
ateWait
Tag Tag_Name, long
int value, PDWORD
lp_dwstate
Signed 32-bit Integer
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1907
Function name Parameters PLC data type HMI data type
SetTagSWordStat
eWait
Tag Tag_Name, short
int value, PDWORD
lp_dwstate
Signed 16-bit Short
SetTagWordState
Wait
Tag Tag_Name,
WORD value,
PDWORD lp_dwstate
Unsigned 16-bit UShort
Syntax
BOOL<FunctionName><(Parameter)>;
Example: BOOL SetTagBitStateWait (Tag Tag_Name, short int value, PDWORD lp_dwstate);
Parameters
Tag_Name
Name of the tags
value
Value of the tags of a specified type.
lp_dwstate
Pointer on a DWORD in which the status of the tag is created after the system function cycle.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1908 System Manual, 08/2011,
SetTagValue
Description
Enables the transfer of a value in the form of a variant and sets the pointer on the value of the
"Variant" data type.
Can only be used in C scripting.
Syntax
BOOL SetTagValue (LPDM_VARKEY lpdmVarKey, LPVARIANT lpdmValue, PDWORD
dwState, LPCMN_ERROR lpdmError);
Parameters
lpdmVarKey
Pointer on a structure of data type "DM_VARKEY"
lpdmValue
Pointer on the value of data type "Variant". For a description of the VARIANT data type see
the relevant specialist literature.
lpdmError
Pointer on the structure that contains the error description.
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
SetTagValueWait
Description
Enables the transfer of a value in the form of a variant and sets the pointer on the value of the
"Variant" data type. The system function will end only after the AS has reported the acceptance
of the value.
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1909
Syntax
BOOL SetTagValueWait(LPDM_VARKEY lpdmVarKey, LPVARIANT lpdmValue, PDWORD
dwState, LPCMN_ERROR lpdmError);
Parameters
lpdmVarKey
Pointer on a structure of data type "DM_VARKEY"
lpdmValue
Pointer on the value of data type "Variant". For a description of the VARIANT data type see
the relevant specialist literature.
dwState
Status of the tags that is returned after the system function cycle.
lpdmError
Pointer on the structure that contains the error description.
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
SetTagWaitXXX
Description
Sets the value of a tag of a specified data type. The system function will end only after the AS
has reported the acceptance of the value.
Can only be used in C scripting.
The following table shows the different SetTagWait functions for setting the tag value:
Function name Parameters PLC data type HMI data type
SetTagBitWait Tag Tag_Name, short
int value
Binary tag Bool
SetTagByteWait
Tag Tag_Name, BYTE
value
Unsigned 8-bit UByte
SetTagCharWai
t
Tag Tag_Name, char*
value
Text tag 8-bit or text tag 16-
bit
String
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1910 System Manual, 08/2011,
Function name Parameters PLC data type HMI data type
SetTagDoubleW
ait
Tag Tag_Name, double
value
Floating point 64-bit Double
SetTagDWordW
ait
Tag Tag_Name,
DWORD value
Unsigned 32-bit UInteger
SetTagFloatWai
t
Tag Tag_Name, float
value
Floating point 32-bit Float
SetTagRawWait
Tag Tag_Name, BYTE*
pValue, DWORD size
Raw data type Raw
SetTagSByteW
ait
Tag Tag_Name, char
value
Signed 8-bit Byte
SetTagSDWord
Wait
Tag Tag_Name, long int
value
Signed 32-bit Integer
SetTagSWordW
ait
Tag Tag_Name, short
int value
Signed 16-bit Short
SetTagWordWai
t
Tag Tag_Name, WORD
value
Unsigned 16-bit UShort
Syntax
BOOL <FunctionName><(Parameter)>;
Example: BOOL SetTagBitWait (Tag Tag_Name, short int value);
Parameters
Tag_Name
Name of the tags
value
Value of the tags of a specified type.
pValue
Pointer to a byte field containing the value of the raw data tags.
size
Size of the byte field in bytes
Return value
TRUE
The system function itself has been completed without any errors.
There is no check to see if the tag was written without any errors.
FALSE
An error has occurred.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1911
See also
Data types for SIMATIC S7 300/400 (Page 1048)
Data types for OPC-DA (Page 1070)
Data types for OPC-XML-DA (Page 1076)
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 "Auto-Hotspot".
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1912 System Manual, 08/2011,
SetTagByProperty
Description
Specifies a tag value with the value of an object property. The change is also logged in the
alarm system.
Use in the function list
SetTagByProperty (Tag name, Screen name, Object, Name of the property, With or without
operator event)
Use in user-defined functions
SetTagByProperty (Tag_name, Screen_name, Screen_object, Property_name,
With_or_without_operator_event)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name
Name of the tag whose value is specified by the object property.
Screen name
Name of the screen that contains the object.
Object
Name of the object whose property supplies the tag value.
Name of the property
Name of the property that supplies the tag value.
With or without operator input
0 (hmiWithoutOperatorEvent) = Without operator input
1 (hmiWithOperatorEvent) = With operator input
SetTagByTagIndirect
Description
Specifies the tag value with the value of an indirect tag. The change is also logged in the alarm
system.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1913
Use in the function list
SetTagByTagIndirect (Tag name, Tag name, With or without operator event)
Use in user-defined functions
SetTagByTagIndirect (Tag_name, Source_tag_name, With_or_without_operator_event)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name
Name of the tag whose value is specified by an indirect tag.
Tag name
Name of the indirect tag that supplies the tag value.
With or without operator input
0 (hmiWithoutOperatorEvent) = Without operator input
1 (hmiWithOperatorEvent) = With operator input
SetTagIndirect
Description
Specifies the indirect name for a tag.
Use in the function list
SetTagIndirect (Tag name (output), LpValue)
Use in user-defined functions
SetTagIndirect (Tag_name, Value, With_or_without_operator_event)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name (output)
Name of the tag to which the tag name is written.
LpValue
Name of the tag written to the tag.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1914 System Manual, 08/2011,
SetTagIndirectByProperty
Description
Specifies a tag name with the value of an object property. The change is also logged in the
alarm system.
Use in the function list
SetTagIndirectByProperty (Tag name, Screen name, Screen object, Name of the property,
With or without operator event)
Use in user-defined functions
SetTagIndirectByProperty (Tag_name, Screen_name, Screen_object, Property_name,
With_or_without_operator_event)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name
Name of the tag whose tag name is specified by the object property.
Screen name
Name of the screen that contains the object.
Screen object
Name of the object whose property returns the tag name.
Name of the property
Name of the property that returns the tag name.
With or without operator input
0 (hmiWithoutOperatorEvent) = Without operator input
1 (hmiWithOperatorEvent) = With operator input
SetTagIndirectByTagIndirect
Description
Specifies the tag value with the value of an indirect tag. The change is also logged in the alarm
system.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1915
Use in the function list
SetTagIndirectByTagIndirect (Tag name, Tag name, With or without operator event)
Use in user-defined functions
SetTagIndirectByTagIndirect (Tag_name, Source_tag_name,
With_or_without_operator_event)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name
Name of the indirect tag whose value is specified by an indirect tag.
Tag name
Name of the indirect tag that supplies the tag value.
With or without operator input
0 (hmiWithoutOperatorEvent) = Without operator input
1 (hmiWithOperatorEvent) = With operator input
SetTagIndirectWithOperatorInputAlarm
Description
Specifies the indirect name for a tag. The change is also logged in the alarm system.
Use in the function list
SetTagIndirectWithOperatorInputAlarm (Tag name (output), LpValue)
Use in user-defined functions
SetTagIndirectWithOperatorInputAlarm
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name (output)
Name of the tag to which the tag name is written.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1916 System Manual, 08/2011,
LpValue
Name of the tag written to the tag.
SetTagWithOperatorEvent
Description
Specifies the value for a tag. The change is also logged in the alarm system.
Use in the function list
SetTagWithOperatorInputAlarm (Tag name (output), LpValue)
Use in user-defined functions
SetTagWithOperatorEvent (Tag_name, Value)
Can be used if the configured device supports user-defined functions. Additional information
is available under "Auto-Hotspot".
Parameters
Tag name (output)
Name of the tag whose value is to be set.
LpValue
Value written to the tag.
StartProgram
Description
Starts the specified program with the specified parameters.
The system function can be used in C scripting only
Syntax
void StartProgram(Program_name,Program_parameter,Display_mode,
Wait_for_program_end);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1917
Parameters
Program_name
Path and name of the program to be started.
Program_parameters
Parameters to be used for start-up. Information on the possible parameters can be found in
the description of the program to be started.
Display_mode
Defines the display mode in which the program is started:
0 (hmiShowNormal) = Display in window
1 (hmiShowMinimized) = Display in minimized window
2 (hmiShowMaximized) = Display in maximized window
3 (hmiShowMinimizedAndInaktive) = Display in inactive and minimized window
Wait_for_program_end
The parameter is not evaluated by WinCC Runtime Professional.
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 "Auto-Hotspot".
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)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1918 System Manual, 08/2011,
See also
Example of deactivating Runtime (Page 1835)
StoreScreen
Description
Saves the current screen; this saved screen can then be opened with the
ActivateStoredScreen system function.
Can only be used in C scripting.
Return value
TRUE
The system function has been completed without any errors.
FALSE
An error has occurred.
See also
ActivateStoredScreen (Page 1859)
UA (Recipe)
uaAddArchive
Description:
Adds a new recipe. This corresponds to the configuration of a new recipe using the "Recipes"
editor.
Can only be used in C scripting.
Syntax
LONG uaAddArchive (
UAHCONFIG hConfig,
UACONFIGARCHIVE* pArchive )
Parameters:
UAHCONFIG hConfig
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1919
Configuration handle for the recipe. This handle is generated with "uaQueryConfiguration".
UACONFIGARCHIVE* pArchive
Pointer to buffer for the recipe configuration memory
Return value
Index of the new recipe. An error corresponds to "-1".
See also
UaQueryConfiguration (Page 1953)
uaAddField
Description:
Adds a new data field.
Can only be used in C scripting.
Syntax
LONG uaAddField (
UAHCONFIG hConfig,
long lArchive,
UACONFIGFIELD* pField )
Parameters:
UAHCONFIG hConfig,
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
UACONFIGFIELD* pArchive
Pointer to buffer of the field configuration.
Return value:
Index of the new field. A value of "-1" indicates an error.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1920 System Manual, 08/2011,
uaArchiveClose
Description:
Terminates the connection to the current recipe.
Can only be used in C scripting.
Syntax
BOOL uaArchiveClose (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE: Successful closing of the recipe
FALSE: Error
uaArchiveDelete
Description
Deletes the data from a recipe. The configured recipe, however, is retained.
Can only be used in C scripting.
Syntax
BOOL uaArchiveDelete (
UAHARCHIVE hArchive,
LPCSTR pszWhere )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszWhere
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1921
This string contains the SQL selection expression. It defines which data records are to be
deleted. The expression is identical to the one in the "DELETE FROM <archive> WHERE
pszWhere" SQL statement.
Warning! If this string is empty, the entire recipe will be deleted.
Return value:
TRUE: Successful deletion of the recipe
FALSE: Error
uaArchiveExport
Description:
Exports the current recipe to a log in CSV format.
Can only be used in C scripting.
Syntax
BOOL uaArchiveExport (
UAHARCHIVE hArchive,
LPCSTR pszDestination,
LONG lType,
LONG lOptions )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszDestination
File name of the target archive.
LONG lType
Data format of the target archive. Two formats are available:
UA_FILETYPE_DEFAULT = 0: Default file format = CSV
UA_FILETYPE_CSV = 1: CSV file format
LONG lOptions
Reserved for later expansions. Must be 0.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1922 System Manual, 08/2011,
Return value:
TRUE: Successful export of the recipe
FALSE: Error
uaArchiveGetCount
Description:
Reads the number of data records.
Can only be used in C scripting.
Syntax
LONG uaArchiveGetCount(
UAHARCHIVE hArchive,
LONG * plCount )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG plCount
Pointer to a tag in which the number of data records should be stored.
Return value:
Number of data records.
0 = Log is empty or error has occurred. Query using uaGetLastError() is required.
uaArchiveGetFieldLength
Description:
Reads the length of a field in the current data record.
Can only be used in C scripting.
Syntax
LONG uaArchiveGetFieldLength(
UAHARCHIVE hArchive,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1923
LONG lField )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
Return value:
Length of the current field.
uaArchiveGetFieldName
Description:
Reads the name of a field in the current data record.
Can only be used in C scripting.
Syntax
VOID uaArchiveGetFieldName (
UAHARCHIVE hArchive,
LONG lField,
LPCSTR pszName,
LONG cMaxLen )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
LPCSTR pszName
Field Name
LONG cMaxLen
Maximum length
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1924 System Manual, 08/2011,
uaArchiveGetFields
Description:
Reads the number of configured data fields, which also includes the "ID", "Last User", and
"Last Access" fields. In the Runtime calls, the indexes of the configured fields are indicated 1
to N. The field ID has the index 0. The fields "Last User" and "Last Access" are appended to
the end of the configured fields.
Can only be used in C scripting.
Syntax
LONG uaArchiveGetFields (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
Number of configured fields.
uaArchiveGetFieldType
Description:
Reads the type of a field in the current data record.
Can only be used in C scripting.
Syntax
LONG uaArchiveGetFieldType (
UAHARCHIVE hArchive,
LONG lField )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1925
The field number; if lField = 1 the first field is addressed.
Return value:
Type of the current field.
The symbolic definitions of the field types are:
UA_FIELDTYPE_INTEGER
UA_FIELDTYPE_DOUBLE
UA_FIELDTYPE_STRING
UA_FIELDTYPE_DATETIME
uaArchiveGetFieldValueDate
Description:
Reads the date and time of a field in the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveGetFieldValueDate (
UAHARCHIVE hArchive,
LONG lField,
LPSYSTEMTIME pstDateTime )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
LPSYSTEMTIME pstDateTime
Pointer to tag of the SYSTEMTIME type
Return value:
TRUE: Successful reading of date and time
FALSE: Error
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1926 System Manual, 08/2011,
uaArchiveGetFieldValueDouble
Description:
Reads the Double value of a field in the current data record.
The system function can be used in C scripting only.
BOOL uaArchiveGetFieldValueDouble (
UAHARCHIVE hArchive,
LONG lField,
double* pdValue )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
double* pdValue
Pointer to tag for the current field content.
Return value:
TRUE: Successful reading of field value
FALSE: Error
uaArchiveGetFieldValueFloat
Description:
Reads Float value of a field in the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveGetFieldValueFloat (
UAHARCHIVE hArchive,
LONG lField,
FLOAT* pfValue )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1927
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
FLOAT* pfValue
Pointer to Float tag for the current field content.
Return value:
TRUE : Successful reading of field value
FALSE : Error
uaArchiveGetFieldValueLong
Description:
Reads the Long Integer value of a field in the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveGetFieldValueLong (
UAHARCHIVE hArchive,
LONG lField,
LONG* pdValue )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
LONG* pdValue
Pointer to Long tag for the current field content.
Return value:
TRUE : Successful reading of field value
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1928 System Manual, 08/2011,
FALSE : Error
uaArchiveGetFieldValueString
Description:
Reads the string of a field in the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveGetFieldValueString (
UAHARCHIVE hArchive,
LONG lField,
LPSTR pszString,
LONG cMaxLen )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first field is addressed.
LPCSTR pszString
Field value as string.
LONG cMaxLen
Maximum length of the string.
Return value:
TRUE : Successful reading of field value
FALSE : Error
uaArchiveGetFilter
Description:
Reads the filter of the current data record. Additional information can be found in the appendix
under "SQL Statements".
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1929
Syntax
VOID uaArchiveGetFilter (
UAHARCHIVE hArchive,
LPSTR pszFilter,
LONG cMaxLen )
The system function can be used in C scripting only.
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPSTR pszFilter
Read filter.
LONG cMaxLen
Maximum length
uaArchiveGetID
Description:
uaArchiveGetID reads the ID of the recipe.
Can only be used in C scripting.
Syntax
LONG uaArchiveGetID (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
ID of the recipe
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1930 System Manual, 08/2011,
uaArchiveGetName
Description:
Reads the name of the recipe.
Can only be used in C scripting.
Syntax
VOID uaArchiveGetName (
UAHARCHIVE hArchive,
LPSTR pszName,
LONG cMaxLen )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPSTR pszName
Pointer to buffer for recipe name.
LONG cMaxLen
Maximum length
Example:
char Filling [40];
uaArchiveGetName( hArchive, Filling, 39 );
uaArchiveGetSor
Description:
uaArchiveGetSort reads the sorting of the recipe.
Can only be used in C scripting.
Syntax
VOID uaArchiveGetSort (
UAHARCHIVE hArchive,
LPSTR pszSort,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1931
LONG cMaxLen )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszSort
Sort
LONG cMaxLen
Maximum length
uaArchiveImport
Description:
uaArchivImport imports a recipe using the CSV data format. The structure of the destination
recipe must be identical to that of the imported recipe.
Syntax
BOOL uaArchiveImport (
UAHARCHIVE hArchive,
LPCSTR pszSource,
LONG lType,
LONG lOptions )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszSource
File name of the source archive.
LONG lType
Data format of the source archive. Two formats are available:
UA_FILETYPE_DEFAULT = 0: Default file format = CSV
UA_FILETYPE_CSV = 1: CSV file format
LONG lOptions
Reserved for later expansions. Must be 0.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1932 System Manual, 08/2011,
Return value:
TRUE: Successful import of the recipe.
FALSE: Error
uaArchiveInsert
Description:
Inserts the local data record buffer into the current database. To have useful data in the new
data record, the fields of the local data record buffer must be written with the
"uaArchiveSetFieldValue..." system functions before calling "uaArchiveInsert".
The internal column "ID" must be written into the current data record with the system function
"uaArchiveSetFieldValueLong". Can only be used in C scripting.
Syntax
BOOL uaArchiveInsert (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE: Successful insertion of the data record.
uaArchiveMoveFirst
Description:
Goes to the first data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveMoveFirst (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1933
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE : Successful jumping in the recipe
FALSE : Error
uaArchiveMoveLast
Description:
Goes to the last data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveMoveLast (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE : Successful jumping in the recipe
FALSE : Error
uaArchiveMoveNext
Description:
Goes to the next data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveMoveNext (
UAHARCHIVE hArchive )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1934 System Manual, 08/2011,
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE : Successful jumping in the recipe
FALSE : Error
uaArchiveMovePrevious
Description:
Goes to the previous data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveMovePrevious (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE : Successful jumping in the recipe
FALSE : Error
uaArchiveOpen
Description:
uaArchiveOpen opens an existing recipe. uaArchiveOpen must always be called when read
or write operations are to be performed on this recipe. uaArchiveOpen must, for example, be
called before calling the uaArchiveMoveFirst, uaArchiveMoveLast, uaArchiveMoveNext,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1935
uaArchiveMovePrevious, uaArchiveDelete, uaArchiveUpdate, and uaArchiveInsert system
functions.
Note
Sort and filter recipes
You can use the "uaArchiveSetSort" and "uaArchiveSetFilter" system functions on a recipe
without opening the recipe using "uaArchiveOpen".
Can only be used in C scripting.
Syntax
BOOL uaArchiveOpen (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE: Successful opening of the recipe
FALSE: Error
uaArchiveReadTagValues
Description:
Reads the current value from the field tag.
Can only be used in C scripting.
Syntax
BOOL uaArchiveReadTagValues (
UAHARCHIVE hArchive,
LONG* pnFields,
LONG cFields,
LONG lOptions )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1936 System Manual, 08/2011,
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG* pnFields
Reserved for future applications (NULL).
LONG cFields
Number of field indices transferred (size of array pnFields).
Reserved for future applications (0).
LONG lOptions
Reserved for future applications (0).
In the case of all other values of lOptions, the data is inserted at the position of the pointer.
Return value:
TRUE : Successful reading in the recipe
FALSE : Error
uaArchiveReadTagValuesByName
Description:
Reads the tag values in the current data.
Can only be used in C scripting.
Syntax
BOOL uaArchiveReadTagValuesByName (
UAHARCHIVE hArchive,
LPCSTR pszFields,
LONG lOptions )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszFields
Reserved for future applications (NULL).
LONG lOptions
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1937
Reserved for future applications (0).
Return value:
TRUE : Successful reading in the recipe
FALSE : Error
uaArchiveRequery
Description:
After the call of uaArchiveSetFilter and uaArchiveSetSort, the recipe must be reloaded with
uaArchiveRequery.
Note
Sort and filter recipes
You can use the "uaArchiveSetSort" and "uaArchiveSetFilter" system functions on a recipe
without opening the recipe using "uaArchiveOpen". In this case, do not call the
"uaArchiveRequery" system function.
Call up the uaArchiveRequery in the following cases:
If you have made inputs in the recipe view.
If you have made inputs in the "Recipes" editor that are to be transferred to the table cell.
Syntax
BOOL uaArchiveRequery(
UAHARCHIVE hArchive )
Can only be used in C scripting.
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE: Successful requery
FALSE: Error
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1938 System Manual, 08/2011,
uaArchiveSetFieldValueDate
Description:
Writes the date and time into a field of the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveSetFieldValueDate (
UAHARCHIVE hArchive,
LONG lField,
LPSYSTEMTIME pstDateTime )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first configured field is addressed. If lField = 0, the ID field is
addressed.
LPSYSTEMTIME pstDateTime
Date and Time
Return value:
TRUE: Successful writing of date and time
FALSE: Error
uaArchiveSetFieldValueDouble
Description:
Writes a Double value into a field of the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveSetFieldValueDouble (
UAHARCHIVE hArchive,
LONG lField,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1939
double dValue )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first configured field is addressed. If lField = 0, the ID field is
addressed.
double dValue
Field value
Return value:
TRUE : Successful writing of field value
FALSE : Error
uaArchiveSetFieldValueFloat
Description:
Writes a Float value into a field of the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveSetFieldValueFloat (
UAHARCHIVE hArchive,
LONG lField,
float fValue )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first configured field is addressed. If lField = 0, the ID field is
addressed.
float fValue
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1940 System Manual, 08/2011,
Field value
Return value:
TRUE : Successful writing of field value
FALSE : Error
uaArchiveSetFieldValueLong
Description:
Writes a Long Integer value into a field of the current data record.
Can only be used in C scripting.
Syntax
BOOL uaArchiveSetFieldValueLong (
UAHARCHIVE hArchive,
LONG lField,
LONG dValue )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first configured field is addressed. If lField = 0, the ID field is
addressed.
LONG dValue
Field value
Return value:
TRUE : Successful writing of field value
FALSE : Error
uaArchiveSetFieldValueString
Description:
Writes a String into a field of the current data record.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1941
Can only be used in C scripting.
Syntax
BOOL uaArchiveSetFieldValueString (
UAHARCHIVE hArchive,
LONG lField,
LPCSTR pszString )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG lField
The field number; if lField = 1 the first configured field is addressed. If lField = 0, the ID field is
addressed.
LPCSTR pszString
Field value
Return value:
TRUE : Successful writing of field value
FALSE : Error
uaArchiveSetFilter
Description:
Sets the filter. You can call the system function without opening the recipe using
"uaArchiveOpen".
Note
If you have opened the recipe using "uaArchiveOpen", then reload the recipe after filtering
using "uaArchiveRequery".
Can only be used in C scripting.
Syntax
VOID uaArchiveSetFilter (
UAHARCHIVE hArchive,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1942 System Manual, 08/2011,
LPSTR pszFilter )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPSTR pszFilter
Filter to be set.
uaArchiveSetSort
Description:
Sets the sorting of the recipe. You can call the system function without opening the recipe
using "uaArchiveOpen".
Note
If you have opened the recipe using "uaArchiveOpen", then reload the recipe after sorting
using "uaArchiveRequery".
Can only be used in C scripting.
Syntax
BOOL uaArchiveSetSort (
UAHARCHIVE hArchive,
LPSTR pszSort )
The system function can be used in C scripting only.
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszSort
Sort
Return value:
TRUE: Successful setting of the sorting
FALSE: Error
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1943
uaArchiveUpdate
Description:
Updates the open recipe. All data changes of a recipe are transferred to the database. The
configuration of the recipe remains unchanged.
Can only be used in C scripting.
Syntax
BOOL uaArchiveUpdate (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE: Successful update of the recipe
FALSE: Error "Update_failed" = 106
This error occurs when there is a consistency violation. Example: The "Field requires a value"
flag is set in a field, but no value has been entered there.
uaArchiveWriteTagValues
Description:
Writes the values of the current data record into the tags.
Can only be used in C scripting.
Syntax
BOOL uaArchiveWriteTagValues (
UAHARCHIVE hArchive,
LONG* pnFields,
LONG cFields,
LONG lOptions )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1944 System Manual, 08/2011,
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LONG* pnFields
Reserved for future applications (NULL).
LONG cFields
Reserved for future applications (0).
LONG lOptions
Reserved for future applications (0).
Return value:
TRUE: Successful reading in the recipe
FALSE: Error
uaArchiveWriteTagValuesByName
Description:
Writes the values of the current data record into the tags. The access is based on the names
of the recipe and field.
Can only be used in C scripting.
Syntax
BOOL uaArchiveWriteTagValuesByName (
UAHARCHIVE hArchive,
LPCSTR pszFields,
LONG lOptions )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
LPCSTR pszFields
Reserved for future applications (NULL)
LONG lOptions
Reserved for future applications (0)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1945
Return value
TRUE : Successful reading in the recipe
FALSE : Error
uaConnect
Description:
Establishes connection to recipes (Runtime).
Can only be used in C scripting.
Syntax
BOOL uaConnect (
UAHCONNECT* phConnect )
Parameters:
UAHCONNECT* phConnect
Pointer to handle for newly connected recipe.
Return value
TRUE: Successful connection of a recipe
FALSE: Error
uaDisconnect
Description:
If a connection to recipes (Runtime) exists, it will be disconnected.
Can only be used in C scripting.
Syntax
BOOL uaDisconnect (
UAHCONNECT hConnect )
Parameters:
UAHCONNECT hConnect
Handle for the connected recipe (Runtime). This handle is generated with "uaConnect".
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1946 System Manual, 08/2011,
Return value
TRUE: Successful disconnection of a recipe
FALSE: Error
uaGetArchive
Description:
Reads the recipe configuration.
Can only be used in C scripting.
Syntax
BOOL uaGetArchive (
UAHCONFIG hConfig,
long lArchive,
UACONFIGARCHIVE* pArchive )
Parameters:
UAHCONFIG hConfig,
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
UACONFIGARCHIVE* pArchive
Pointer to buffer for receiving the recipe configuration
Return value
TRUE: Successful access to the recipe
FALSE: Error
uaGetField
Description:
Reads the field configuration.
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1947
Syntax
BOOL uaGetField (
UAHCONFIG hConfig,
long lArchive,
long lField,
UACONFIGFIELD* pField )
Parameters:
UAHCONFIG hConfig,
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
long lField,
The field number; if lField = 0 the first field is addressed.
UACONFIGFIELD* pArchive
Pointer to buffer for receiving the field configuration.
Return value:
TRUE: Successful access to the recipe
FALSE: Error
uaGetLastError
Description:
The system functions of the WinCC script language return a BOOL value, whereby TRUE
corresponds to error-free processing. If FALSE is returned, the error of the last system function
can be read with "uaGetLastError()" and "uaGetLastHResult()".
Can only be used in C scripting.
If "uaGetLastError()" is called after running several system functions, "uaGetLastError()" will
return the error that occurred last. To be certain of the system function in which the error
occurred, "uaGetLastError()" and "uaGetLastHResult()" should be called every time a system
function returns FALSE.
Example:
if ( uaArchiveGetFieldValueLong ( hArchive, Index, &IntValue ) ==
TRUE )
printf( "Field Value = %u\n", IntValue );
else
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1948 System Manual, 08/2011,
printf("Error calling uaArchiveGetFieldValueLong: %d / %08lx\n",
uaGetLastError(), uaGetLastHResult());
With system functions which do not return a value (VOID), there should be a request via
uaGetLastError() in any case.
Example:
uaArchiveGetFilter(hArchive, pszFilter, cMaxLen);
INT nUAError = uaGetLastError ( );
if ( UA_ERROR_SUCCESS != nUAError)
{
printf( "Filter = [%s]\n", pszFilter );
}
else
{
printf("Error calling uaArchiveGetFilter: %d, hr=0x%08lX\n",
nUAError, uaGetLastHResult());
}
INT uaGetLastError()
Return value:
Error status of the last system function executed. The following errors can be returned by
"uaGetLastError()":
UA_ERROR_SUCCESS
UA_ERROR_GENERIC
UA_ERROR_CONNECT_FAILED
UA_ERROR_OPEN_FAILED
UA_ERROR_CLOSE_FAILED
UA_ERROR_REQUERY_FAILED
UA_ERROR_MOVE_FAILED
UA_ERROR_INSERT_FAILED
UA_ERROR_UPDATE_FAILED
UA_ERROR_DELETE_FAILED
UA_ERROR_IMPORT_FAILED
UA_ERROR_EXPORT_FAILED
UA_ERROR_READ_FAILED
UA_ERROR_WRITE_FAILED
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1949
UA_ERROR_GET_FAILED
UA_ERROR_SET_FAILED
UA_ERROR_INVALID_NAME
UA_ERROR_INVALID_TYPE
UA_ERROR_INVALID_NUMRECS
UA_ERROR_INVALID_COMMTYPE
UA_ERROR_INVALID_LENGTH
UA_ERROR_INVALID_PRECISION
UA_ERROR_NULL_POINTER
UA_ERROR_INVALID_POINTER
UA_ERROR_INVALID_HANDLE
UA_ERROR_INVALID_INDEX
UA_ERROR_SERVER_UNKNOWN
These error constants, as well as the predefines of the user archives routines, are located in
CCUACAPI.H.
uaGetLastHResult
Description:
Reads the last occurred COM error. This system function is mainly used to diagnose
incompatibilities during COM implementation or to detect registration and communication
errors.
This system function is basically used in addition to UAGetLastError, if a user archive system
function (e.g. uaConnect) signals an error with "FALSE".
Can only be used in C scripting.
Syntax
LONG uaGetLastHResult()
Return value
Last occurred COM error
uaGetNumArchives
Description:
Reads the number of recipes currently configured.
Can only be used in C scripting.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1950 System Manual, 08/2011,
Syntax
LONG uaGetNumArchives (
UAHCONFIG hConfig )
Parameters:
UAHCONFIG hConfig
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
Return value:
Number of recipes currently configured. In case of an error, -1 will be returned.
uaGetNumFields
Description:
Supplies the number of the configured fields. The "ID", "Last User" and "Last Access" fields
are not included. In the configuration calls, the indexes are indicated from 0 to
"uaGetNumFields() -1".
Can only be used in C scripting.
Syntax
LONG uaGetNumFields (
UAHCONFIG hConfig,
long lArchive )
Parameters:
UAHCONFIG hConfig,
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
Return value:
Number of configured fields. In case of an error, -1 will be returned.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1951
uaQueryArchive
Description:
Establishes a connection to the recipe for Runtime operation. UaQueryArchive creates the
handle UAHARCHIVE.
Can only be used in C scripting.
Syntax
BOOL uaQueryArchive (
UAHCONNECT hConnect,
LONG lArchive,
UAHARCHIVE* phArchive )
Parameters:
UAHCONNECT hConnect
Handle of the connected recipe (Runtime). This handle is generated with "uaConnect".
LONG lArchive
Archiv Index (0... uaGetNumArchives() -1)
UAHARCHIVE* phArchive
Pointer to handle of the recipe
Return value:
TRUE: Successful generation of the handle to the recipe.
FALSE: Error
Comment:
If you use User Archives functions in a client project that works with redundant server pairs,
the user archives connection cannot be switched automatically to the new master when
switching masters. In this case, all user archive calls deliver the LastError
UA_ERROR_SERVER_UNKNOWN = 1004. As a result, user programs must run a new
uaQueryArchive() or uaQueryArchiveByName() and uaArchiveOpen().
uaQueryArchiveByName
Description:
Establishes a connection to a recipe for Runtime operation using the recipe name.
UaQueryArchiveByName creates the UAHARCHIVE handle for the recipe.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1952 System Manual, 08/2011,
Can only be used in C scripting.
Syntax
BOOL uaQueryArchiveByName (
UAHCONNECT hConnect,
LPCSTR pszName,
UAHARCHIVE* phArchive )
Parameters:
UAHCONNECT hConnect
Handle of the connected recipe (Runtime). This handle is generated with "uaConnect".
LPCSTR pszName
Name of the recipe. With a client project, you can add a server prefix with :: to the recipe
name as a separator, if a server other than the default server is used.
UAHARCHIVE* phArchive
Pointer to handle of the recipe
Return value:
TRUE: Successful generation of the handle to the recipe.
FALSE: Error
Comment:
If you use User Archives functions in a client project that works with redundant server pairs,
the user archives connection cannot be switched automatically to the new master when
switching masters. In this case, all user archive calls deliver the LastError
UA_ERROR_SERVER_UNKNOWN = 1004. As a result, user programs must run a new
uaQueryArchive() or uaQueryArchiveByName() and uaArchiveOpen().
UaQueryConfiguration
Description:
Establishes a connection to the recipe for the configuration.
Can only be used in C scripting.
Syntax
BOOL uaQueryConfiguration (
UAHCONFIG* phConfig )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1953
Parameters:
UAHCONFIG* phConfig,
Pointer to handle of the recipe.
Return value
TRUE: Successful access to recipe
FALSE: Error
See also
uaAddArchive (Page 1919)
uaReleaseArchive
Description:
Releases the connection to the current recipe.
Can only be used in C scripting.
Syntax
BOOL uaReleaseArchive (
UAHARCHIVE hArchive )
Parameters:
UAHARCHIVE hArchive
Handle of the recipe. This handle is generated with "uaQueryArchive" or
"uaQueryArchiveByName".
Return value:
TRUE: Successful release of connection to the recipe.
FALSE: Error
Comment
The handle "hArchive" must be set to "ZERO" with successful disengagement, so that the error
"UA_ERROR_INVALID_HANDLE" will certainly appear if the no longer valid handle is
continuously used, without the respective function starving in the COM interfaces for a long
time.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1954 System Manual, 08/2011,
uaReleaseConfiguration
Description:
Releases connection to recipes (configuration).
Can only be used in C scripting.
Syntax
BOOL uaReleaseConfiguration (
UAHCONFIG hConfig,
BOOL bSave )
Parameters:
UAHCONFIG hConfig
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
BOOL bSave
Saves changes made to the configuration before releasing the connection to recipes for the
configuration.
TRUE = Save Changes, FALSE = Discard Changes
Warning: Save changes (bSave = TRUE) may only be used when Runtime
is not active! You can check whether Runtime is active by requesting uaIsActive().
Return value
TRUE: Successful connection release
FALSE: Error
uaRemoveAllArchives
Description:
Deletes all recipes that are not used in views.
Can only be used in C scripting.
Syntax
BOOL uaRemoveAllArchives
( UAHCONFIG hConfig )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1955
Parameters:
UAHCONFIG hConfig
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
Return value
TRUE: Successful deletion
FALSE: Error
Comment
After that, you can use "uaGetNumArchives()" to determine whether all recipes were deleted.
uaRemoveAllFields
Description:
Removes all fields.
Can only be used in C scripting.
Syntax
BOOL uaRemoveAllFields (
UAHCONFIG hConfig,
long lArchive )
Parameters:
UAHCONFIG hConfig,
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
Return value:
TRUE: Successful deletion of fields
FALSE: Error
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1956 System Manual, 08/2011,
uaRemoveArchive
Description:
uaRemoveArchive deletes the entire configured recipe.
Can only be used in C scripting.
Syntax
BOOL uaRemoveArchive (
UAHCONFIG hConfig,
long lArchive )
Parameters:
UAHCONFIG hConfig,
Configuration handle of the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
Return value
TRUE: Successful deletion of the recipe.
FALSE: Error
uaRemoveField
Description:
Removes a field.
Can only be used in C scripting.
Syntax
BOOL uaRemoveField (
UAHCONFIG hConfig,
long lArchive,
long lField )
Parameters:
UAHCONFIG hConfig,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1957
Configuration handle for the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
long lField,
The field number; if lField = 0 the first field is addressed.
Return value:
TRUE: Successful deletion of field
FALSE: Error
uaSetArchive
Description:
Sets the configuration of a recipe.
Can only be used in C scripting.
Syntax
BOOL uaSetArchive (
UAHCONFIG hConfig,
long lArchive,
UACONFIGARCHIVE* pArchive
)
Parameters:
UAHCONFIG hConfig,
Configuration handle for the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
UACONFIGARCHIVE* pArchive
Pointer to pArchive buffer with the recipe configuration.
Return value:
TRUE: Successful access to recipe.
FALSE: Error
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1958 System Manual, 08/2011,
uaSetField
Description:
Sets the field configuration.
Can only be used in C scripting.
Syntax
BOOL uaSetField (
UAHCONFIG hConfig,
long lArchive,
long lField,
UACONFIGFIELD* pField )
Parameters:
UAHCONFIG hConfig,
Configuration handle for the recipe. This handle is generated with "uaQueryConfiguration".
long lArchive,
Log index (0 to (uaGetNumArchives()-1))
long lField,
The field number; if lField = 0 the first field is addressed.
UACONFIGFIELD* pField
Pointer to buffer of the field configuration.
Return value:
TRUE : Successful access to recipe.
FALSE : Error
c_bib
ctype functions
Function overview
The following ctype functions are available:
long int isalnum (long int x);
long int isalpha (long int x);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1959
long int isdigit (long int x);
long int isgraph (long int x);
long int islower (long int x);
long int isprint (long int x);
long int ispunct (long int x);
long int isspace (long int x);
long int isupper (long int x);
long int isxdigit (long int x);
long int tolower (long int x);
long int toupper (long int x);
For a description of the ctype functions see the specialist literature on programming language
C.
The functions can be used in C scripts only.
Function group c_bib
Introduction
The c_bib function group contains C functions from the C library and is divided into:
ctype
math
memory
stdio
stdlib
string
time
stdio itself is again divided into:
char_io
directio
error
file
file_pos
output
For a description of these functions see the relevant specialist literature.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1960 System Manual, 08/2011,
Specific features of WinCC functions
The localtime function behaves as follows when the date is issued:
The counting of the months begins with 0.
The years are counted as of 1990, starting with 0.
Only 360 characters of the functions of the C library printf(), sprintf(), fprintf() can be edited in
WinCC.
math functions
Function overview
The following math functions are available:
double acos (double x);
double asin (double x);
double atan (double x);
double atan2 (double x, double y);
double ceil (double x);
double cos (double x);
double cosh (double x);
double exp (double x);
double fabs (double x);
double floor (double x);
double fmod (double x, double y);
double frexp (double x, long int* y);
double ldexp (double x, long int y);
double log (double x);
double log10 (double x);
double modf (double x, double* y);
double pow (double x, double y);
double sin (double x);
double sinh (double x);
double sqrt (double x);
double tan (double x);
double tanh (double x);
For a description of the math functions see the specialist literature on programming language
C.
The functions can be used in C scripts only.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1961
memory functions
Function overview
The following memory functions are available:
long int memcmp (const void* cs, const void* ct, size_t n);
void* memchr (const void* cs, long int c, size_t n);
void* memcpy (void* s, const void* ct, size_t n);
void* memmove (void* s, const void* ct, size_t n);
void* memset (void* s, long int c, size_t n);
For a description of the memory functions see the specialist literature on programming
language C.
The functions can be used in C scripts only.
multibyte functions
Function overview
The following multibyte functions are available:
int _ismbcalnum( unsigned int c )
int _ismbcalpha( unsigned int c )
int _ismbcdigit( unsigned int c )
int _ismbcgraph( unsigned int c )
int _ismbclower( unsigned int c )
int _ismbcprint( unsigned int c )
int _ismbcpunct( unsigned int c )
int _ismbcspace( unsigned int c )
int _ismbcupper( unsigned int c )
int _mbscmp(const unsigned char *string1, const unsigned char *string2 )
int _mbsncmp( const unsigned char *string1, const unsigned char *string2, size_t count )
int _mbsrchr( const unsigned char *string, unsigned int c )
size_t _mbscspn( const unsigned char *string, const unsigned char *strCharSet )
size_t _mbsspn( const unsigned char *string, const unsigned char *strCharSet )
size_t _mbstrlen( const char *string )
size_t _mbslen( const unsigned char *string )
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1962 System Manual, 08/2011,
unsigned char *_mbscat( unsigned char *strDestination, const unsigned char *strSource)
unsigned char *_mbschr( const unsigned char *string, unsigned int c )
unsigned char *_mbscpy( unsigned char *strDestination, const unsigned char *strSource )
unsigned char *_mbsdec( const unsigned char *start, const unsigned char *current )
unsigned char *_mbsinc( const unsigned char *current ) size_t _mbclen( const unsigned
char *c );
unsigned char *_mbsncat( unsigned char *strDest, const unsigned char *strSource, size_t
count)
unsigned char *_mbsncpy( unsigned char *strDest, const unsigned char *strSource, size_t
count)
unsigned char *_mbspbrk( const unsigned char*string, const unsigned char *strCharSet )
unsigned char *_mbsstr( const unsigned char *string, const unsigned char *strCharSet )
unsigned char *_mbstok( unsigned char*strToken, const unsigned char *strDelimit )
A description of the multibyte functions can be found in the specialist literature on programming
language C.
The functions can be used in C scripts only.
stdio functions
Function overview
The following stdio functions are available:
char* fgets (char* s, long int n, FILE* stream);
char* tmpnam (char* s);
FILE* fopen (const char* name, const char* mode);
FILE* freopen (const char* filename, const char* mode, FILE* stream);
FILE* tmpfile ();
fprintf();
long int fclose (FILE* stream);
long int feof (FILE* stream);
long int ferror (FILE* stream);
long int fflush (FILE* stream);
long int fgetc (FILE* stream);
long int fgetpos (FILE* stream, fpos_t* ptr);
long int fputc (long int c, FILE* stream);
long int fputs (const char* s, FILE* stream);
long int fseek (FILE* stream, long int offset, long int origin);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1963
long int fsetpos (FILE* stream, const fpos_t* ptr);
long int ftell (FILE* stream);
long int getc (FILE* stream);
long int putc (long int c, FILE* stream);
long int remove (const char* filename);
long int rename (const char* oldname, const char* newname);
long int setvbuf (FILE* stream, char* buf, long int mode, size_t size);
long int ungetc (long int c, FILE* stream);
long int vfprintf (FILE* stream, const char* format, va_list arg);
long int vsprintf (char* s, const char* format, va_list arg);
printf();
size_t fread (void* ptr, size_t size, size_t nobj, FILE* stream);
size_t fwrite (void* ptr, size_t size, size_t nobj, FILE* stream);
void clearerr (FILE* stream);
void rewind (FILE* stream);
void setbuf (FILE* stream, char* buf);
For a description of the studio functions see the specialist literature on programming language
C.
The functions can be used in C scripts only.
stdlib functions
Function overview
The following stdlib functions are available:
char* getenv (const char* name);
div_t div (long int num, long int denom);
double atof (const char* s);
double strtod (const char* s, char** endp);
ldiv_t ldiv (long int num, long int denom);
long int abs (long int n);
long int atoi (const char* s);
long int atol (const char* s);
long int labs (long int n);
long int rand ();
long int srand (unsigned long int seed);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1964 System Manual, 08/2011,
long int strtol (const char* s, char** endp, long int base);
long int system (const char* s);
unsigned long int strtoul (const char* s, char** endp, long int base);
void abort ();
void* bsearch (const void* key, const void* base, size_t n, size_t size, long int(* cmp) (const
void* calloc (size_t nobj, size_t size);
void exit (long int status);
void free (void* p);
void* keyval, const void* datum));
void* malloc (size_t size);
void qsort (void* base, size_t n, size_t size, long int* cmp, const void* , const void* );
void* realloc (void* p, size_t size);
For a description of the stdlib functions see the specialist literature on programming language
C.
The functions can be used in C scripts only.
string functions
Function overview
The following string functions are available:
char* strcat (char* s, const char* ct);
char* strchr (const char* cs, long int c);
char* strcpy (char* s, const char* ct);
char* strerror (size_t n);
char* strncat (char* s, const char* ct, size_t n);
char* strncpy (char* s, const char* ct, size_t n);
char* strpbrk (const char* cs, const char* ct);
char* strrchr (const char* cs, long int c);
char* strstr (const char* cs, const char* ct);
char* strtok (char* s, const char* ct);
long int strcmp (const char* cs, const char* ct);
long int strncmp (const char* cs, const char* ct, size_t n);
size_t strcspn (const char* cs, const char* ct);
size_t strlen (const char* cs);
size_t strspn (const char* cs, const char* ct);
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1965
For a description of the string functions see the specialist literature on programming language
C.
The functions can be used in C scripts only.
time functions
Function overview
The following time functions are available:
char* asctime (const struct tm* tp);
char* ctime (const time_t* tp);
clock_t clock ();
double difftime (time_t time2, time_t time1);
size_t strftime (char* s, size_t smax, const char* fmt, const struct tm* tp);
struct tm* gmtime (const time_t* tp);
struct tm* localtime (const time_t* tp);
time_t mktime (struct tm* tp);
time_t time (time_t* tp);
For a description of the time functions see the specialist literature on programming language
C.
The functions can be used in C scripts only.
Structure definitions
Structure definition CCAPErrorExecute
typedef struct {
DWORD dwCurrentThreadID; Thread ID of the current thread
DWORD dwErrorCode1; Error code 1
DWORD dwErrorCode2; Error code 2
BOOL bCycle; cycle/acycle
char* szApplicationName; Name of the application
char* szFunctionName; Name of the function
char* szTagName; Name of the tag
LPVOID lpParam; Pointer to the action stack
DWORD dwParamSize; Size of the action stack
DWORD dwCycle; Cycle of the tag
CMN_ERROR* pError; Pointer to CMN_ERROR
} CCAPErrorExecute;
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1966 System Manual, 08/2011,
Members
The meaning of the individual error IDs and the structure elements depending on them are
specified in the following table:
100700
1
0 x x x x x Action requires exception
100700
1
1 x x x x x Exception when
accessing the return
result
100700
1
4097 x x x x x Stack overflow while
executing the action
100700
1
4098 x x x x x The action contains a
division by 0
100700
1
4099 x x x x x The action contains an
access to a non-existing
symbol
100700
1
4100 x x x x x The action contains an
access violation
100700
4
0 x x x Function is not known
100700
5
1 x x Action does not include a
P code.
100700
5
2 x x Incorrect function name
100700
5
4 x x x x x Return value type is
invalid
100700
5
32768f
f
x x x x x Ciss Compiler error when
loading the action
100700
6
0 x x x x x x x Tag is not defined
100700
6
1 x x x x x x x Tag timeout
100700
6
2 x x x x x x x x Tag cannot be returned in
the desired format
100700
6
3 x x x x x x x x Tag returns status
violation, status present
in
CMN_ERROR.dwError1
100700
7
1 x x x x x x Error with
PDLRTGetProp
100700
7
2 x x x x x x Error with PDLRTSetProp
100700
7
3 x x x x x x Error with DM call
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1967
Error structure
The OnErrorExecute function uses the error structure to evaluate or to output error messages,
if marked by an "x" in the pError column.
Structure definition CCAPTime
typedef struct {
DWORD dwCurrentThreadID; ThreadID of the current Thread
DWORD dwCode; Code
BOOL bCycle; cycle/acycle
char* szApplicationName; Name of the Application
char* szFunctionName; Name of the Function
LPVOID lpParam; Pointer to the Action-Stack
DWORD dwParamSize; size of the Action-Stack
double dblTime;
DWORD dwFlags; flags
} CCAPTime;
Members
dwCode
The structure element dwCode provides information on calling of OnTime:
dwCode = 113 Call with time definition for each action
dwCode = 114 Call with time monitoring for each action
dwFlags
The structure element dwFlags provides information on the output type:
dwFlags = TRUE The results are output to a file
dwFlags = FALSE The results are output to the diagnostics window
Structure definition CMN_ERROR
struct CMNERRORSTRUCT {
DWORD dwError1,
DWORD dwError2,
DWORD dwError3,
DWORD dwError4,
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1968 System Manual, 08/2011,
DWORD dwError5;
TCHAR szErrorText[MAX_ERROR_LEN];
}
CMN_ERROR
Description
The extended error structure contains the error code and an error text for the error that has
occurred. Each application can use the error structure to evaluate or to output error messages.
Members
dwError1 .. dwError5
These entries can be used in any way by the API functions.
The API descriptions inform about the values the respective entries contain in case of an error.
If not specified otherwise, the error codes are present in dwError1.
szErrorText
Buffer for the text description of the error cause
The content is determined from the resources and therefore language-dependent.
Structure definition DM_TYPEREF
typedef struct {
DWORD dwType;
DWORD dwSize;
char szTypeName[MAX_DM_TYPE_NAME + 1];
}
DM_TYPEREF;
Members
dwType
Specifies the tag type
dwType PLC data type HMI data type
DM_VARTYPE_BIT Binary tag Bool
DM_VARTYPE_SBYTE Signed 8-bit value Byte
DM_VARTYPE_BYTE Unsigned 8-bit value UByte
DM_VARTYPE_SWORD Signed 16-bit value Short
DM_VARTYPE_WORD Unsigned 16-bit value UShort
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1969
dwType PLC data type HMI data type
DM_VARTYPE_SDWORD Signed 32-bit value Integer
DM_VARTYPE_DWORD Unsigned 32-bit value UInteger
DM_VARTYPE_FLOAT Floating-point number 32-bit IEEE 754 Float
DM_VARTYPE_DOUBLE Floating-point number 64-bit IEEE 754 Double
DM_VARTYPE_TEXT_8 Text tag, 8-bit character set Char
DM_VARTYPE_TEXT_16 Text tag, 16-bit character set String
DM_VARTYPE_RAW Raw data type Raw
DM_VARTYPE_STRUCT Structure tag Struct
DM_VARTYPE_TEXTREF Text reference tag String
dwSize
Specifies the length of the data type in bytes.
szTypeName
In the case of structure tags, contains the name of the structure type
Structure definition DM_VAR_UPDATE_STRUCT
typedef struct {
DM_TYPEREF dmTypeRef;
DM_VARKEY dmVarKey;
VARIANT dmValue;
DWORD dwState;
}
DM_VAR_UPDATE_STRUCT;
Members
dmTypeRef
Contains information on the data type. For performance reasons, nothing is entered into this
structure in case of cyclic requests.
dmVarKey
Specifies the tags to be edited.
dmValue
Tag value
Upon access to the value of the VARIANT a ".u." has to be inserted between the name of the
VARIANT and the name of the member.
Example
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1970 System Manual, 08/2011,
// Supply variant
myVariant.vt = VT_I4;
myVariant.u.lVal = 233;
A description of the data type VARIANT can be found in the associated documentation. The
VARIANT dmValue must be initialized with VariantInit() before first use and enabled again with
VariantClear(&dmValue) after use. For this reason, the structure
DM_VAR_UPDATE_STRUCT must not be deleted with ZeroMemory() or memset().
dwState
Identifies the tag status.
Structure definition DM_VAR_UPDATE_STRUCTEX
typedef struct {
DM_TYPEREF dmTypeRef;
DM_VARKEY dmVarKey;
VARIANT dmValue;
DWORD dwState;
DWORD dwQualityCode;
}
DM_VAR_UPDATE_STRUCTEX;
Members
dmTypeRef
Contains information on the data type. For performance reasons, nothing is entered into this
structure in case of cyclic requests.
dmVarKey
Specifies the tags to be edited.
dmValue
Tag value
Upon access to the value of the VARIANT a ".u." has to be inserted between the name of the
VARIANT and the name of the member.
Example
// Supply variant
myVariant.vt = VT_I4;
myVariant.u.lVal = 233;
A description of the data type VARIANT can be found in the associated documentation. The
VARIANT dmValue must be initialized with VariantInit() before first use and enabled again with
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1971
VariantClear(&dmValue) after use. For this reason, the structure
DM_VAR_UPDATE_STRUCTEX must not be deleted with ZeroMemory() or memset().
dwState
Identifies the tag status.
dwQualityCode
Identifies the QualityCode tag.
Structure definition DM_VARKEY
typedef struct {
DWORD dwKeyType;
DWORD dwID;
char szName[ MAX_DM_VAR_NAME + 1 ];
LPVOID lpvUserData;
}
DM_VARKEY;
Members
dwKeyType
Defines whether the tag is to be addressed by a key ID or by its name.
DM_VARKEY_ID Specification via key ID
DM_VARKEY_NAME Specification via tag name
dwID
Contains the key ID of the tags if dwKey type is set accordingly.
szName
Contains the name of the tag if dwKey type is set accordingly.
lpvUserData
Pointer to application-specific data
Structure definition LINKINFO
typedef struct {
LINKTYPE LinkType;
DWORD dwCycle;
TCHAR szLinkName[256];
}
LINKINFO;
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1972 System Manual, 08/2011,
Members
LinkType
LinkType are enumeration constants defined in the "Trigger.h" file. They are to be integrated
into your script with the "#include "Trigger.h" command and the corresponding enumeration
constants.
BUBRT_LT_NOLINK 0 no shortcut
BUBRT_LT_VARIABLE_DIRECT 1 direct tag
BUBRT_LT_VARIABLE_INDIRECT 2 indirect tag
BUBRT_LT_ACTION 3 C action
BUBRT_LT_ACTION_WIZARD 4 Dynamic Dialog
BUB_LT_DIRECT_CONNECTION 5 Direct connection
BUBRT_LT_ACTION_WIZARD_INPROC 6 Dynamic Dialog
For the SetLink function, only the enumeration constants BUBRT_LT_VARIABLE_DIREKT
and BUBRT_LT_VARIABLE_INDIRECT may be used. The GetLink function allows to return
all listed enumeration constants.
dwCycle
Update cycle time
255 Picture cycle
235 Window Cycle
0 Upon change
1 250ms
2 500 ms
3 1 s
4 2 s
5 5s
6 10s
7 1min
8 5min
9 10min
10 1h
11-1
5
User cycle 1-5
szLinkName
Tag name
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1973
Structure definition MSG_FILTER_STRUCT
typedef struct {
CHAR szFilterName[MSG_MAX_TEXTLEN+1];
WORD dwFilter;
SYSTEMTIME st[2];
DWORD dwMsgNr[2];
DWORD dwMsgClass;
DWORD dwMsgType[MSG_MAX_CLASS];
DWORD dwMsgState;
WORD wAGNr[2];
WORD wAGSubNr[2];
DWORD dwArchivMode;
char szTB[MSG_MAX_TB][
MSG_MAX_TB_CONTENT+1]
DWORD dwTB;
Double dPValue[MSG_MAX_PVALUE][2];
DWORD dwPValue[2];
DWORD dwMsgCounter[2];
DWORD dwQuickSelect;
}
MSG_FILTER_STRUCT;
Description
In this structure the criteria are specified.
Members
dwFilter
The filter conditions are defined by means of the following constants from the file "m_global.h":
MSG_FILTER_DATE_FROM Date from
MSG_FILTER_DATE_TO Date to
MSG_FILTER_TIME_FROM Time from
MSG_FILTER_TIME_TO Time to
MSG_FILTER_NR_FROM Message number from
MSG_FILTER_NR_TO Message number to
MSG_FILTER_CLASS Message classes
MSG_FILTER_STATE Message status
MSG_FILTER_AG_FROM AS number from
MSG_FILTER_AG_TO AS number to
MSG_FILTER_AGSUB_FROM AG subnumber from
MSG_FILTER_AGSUB_TO AG subnumber to
MSG_FILTER_TEXT Message texts
MSG_FILTER_PVALUE Process values
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1974 System Manual, 08/2011,
MSG_FILTER_COUNTER_FROM Internal message counter from
MSG_FILTER_COUNTER_TO Internal message counter to
MSG_FILTER_PROCESSMSG Process messages
MSG_FILTER_SYSMSG System messages
MSG_FILTER_BEDMSG Operator messages
MSG_FILTER_DATE Date from to
MSG_FILTER_TIME Time from to
MSG_FILTER_NR Message number from to
MSG_FILTER_VISIBLEONLY Display visible messages
MSG_FILTER_HIDDENONLY Display hidden messages
st
Date/time from - to
Where st[0] is the start time (from), st[1] the end time (to)
Assign these fields for the criteria: MSG_FILTER_DATE, MSG_FILTER_DATE_FROM,
MSG_FILTER_DATE_TO, MSG_FILTER_TIME, MSG_FILTER_TIME_FROM, bzw.
MSG_FILTER_TIME_TO
If the current time is needed to pass a SYSTEMTIME- parameter, use the GetLocalTime
function and not GetSystemTime.. There is usually a considerable difference between these
two functions.
dwMsgNr
Message number from - to
Where dwMsgNr[0] is start no. (from), dwMsgNr[1] the end no. (to)
Assign these fields for the criteria: MSG_FILTER_NR, MSG_FILTER_NR_FROM bzw.
MSG_FILTER_NR_TO
dwMsgClass
Message classes bit-coded.
Assign this field for the criterion: MSG_FILTER_CLASS
dwMsgType
Message type per alarm class, bit-coded
Assign this field for the criterion: MSG_FILTER_CLASS
dwMsgState
Message status bit-coded.
Assign this field for the criterion: MSG_FILTER_STATE
wAGNr
AGNr from - to
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1975
Assign these fields for the criteria: MSG_FILTER_AG_FROM or MSG_FILTER_AG_TO
wAGSubNr
AGSubNr from - to
Assign this field for the criteria: MSG_FILTER_AGSUB_FROM or MSG_FILTER_AGSUB_TO
dwArchivMode
Logging / reporting
Must be assigned 0.
szTB
Texts of the text blocks
Assign these fields for the criterion: MSG_FILTER_TEXT
dwTB
Active text blocks (from - to, bit-coded)
Assign this field for the criterion: MSG_FILTER_TEXT
dPValue
Process values from - to
Assign these fields for the criterion: MSG_FILTER_PVALUE
dwPValue
Active process values (from - to, bit-coded)
Assign this field for the criterion: MSG_FILTER_PVALUE
dwMsgCounter
Internal message counter from - to
Assign these fields for the criteria: MSG_FILTER_COUNTER_FROM,
MSG_FILTER_COUNTER_TO
dwQuickSelect
Quick selection for hour, day, month
The parameter is reserved for future upgrades and must be preset to 0.
Assign this field for the criterion: MSG_FILTER_QUICKSELECT
LOWORD Type:
MSG_FILTER_QUICK_MONTH Quick selection last n months
MSG_FILTER_QUICK_DAYS Quick selection last n days
MSG_FILTER_QUICK_HOUR Quick selection last n hours
HIWORD Number: 1...n
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1976 System Manual, 08/2011,
The end time of the quick selection refers to the current system time of the local computer.
The start time is calculated back n * ( months, days, hours ).
Structure definition MSG_RTDATA_STRUCT
typedef struct {
DWORD dwMsgState;
DWORD dwMsgNr;
SYSTEMTIME stMsgTime;
DWORD dwTimeDiff;
DWORD dwCounter;
DWORD dwFlags;
WORD wPValueUsed;
WORD wTextValueUsed;
double dPValue[MSG_MAX_PVALUE];
MSG_TEXTVAL_STRUCT mtTextValue[MSG_MAX_PVALUE];
}
MSG_RTDATA_STRUCT;
Members
dwMsgState
Message status
MSG_STATE_COME 0x00000001 Message came in
MSG_STATE_GO 0x00000002 Message went out
MSG_STATE_QUIT 0x00000003 Message acknowledged
MSG_STATE_LOCK 0x00000004 Message locked
MSG_STATE_UNLOCK 0x00000005 Alarm locked
MSG_STATE_QUIT_SYSTEM 0x00000010 Message acknowledged by system
MSG_STATE_QUIT_EMERGENCY 0x00000011 Emergency acknowledgement
MSG_STATE_QUIT_HORN 0x00000012 Alarm alert acknowledgment
MSG_STATE_COMEGO 0x00000013 Message came in and went out, only displayed in the "Current
messages" display
MSG_STATE_UPDATE 0x00010000 Bit for message update
MSG_STATE_RESET 0x00020000 Bit for message reset
MSG_STATE_SUMTIME 0x00040000 Bit active for daylight savings time
MSG_STATE_INSTANCE 0x00080000 Bit for instance message (n messages of a no.)
dwMsgNr
Message number
stMsgTime
Date/Time: Telegram time depending on the calling function
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1977
dwTimeDiff
Duration coming/Telegram time in seconds
dwCounter
Internal message counter
dwFlags
Message flags in the database
MSG_FLAG_SUMTIME 0x00000001 Daylight savings time active
MSG_FLAG_COMMENT 0x00000002 Message has comments
MSG_FLAG_ARCHIV 0x00000004 Archiving
MSG_FLAG_PROTOCOL 0x00000008 Logging
MSG_FLAG_TEXTVALUES 0x00000010 Message has values accompanying the text
MSG_FLAG_TIMEINVALID 0x00000020 Bit for invalid date/time stamp
MSG_FLAG_INSTANCE 0x00000040 Instance message identification (185269)
wPValueUsed
Process values used, bit-coded. Every bit may only be set in one of the two structure elements
"wPValueUsed" or "wTextValueUsed". An accompanying value may either be a number or a
text.
wTextValueUsed
text values used, bit-coded. Every bit may only be set in one of the two structure elements
"wPValueUsed" or "wTextValueUsed". An accompanying value may either be a number or a
text.
9.8.3.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
Logs
Scheduler
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1978 System Manual, 08/2011,
Play ended (Page 1989) -- -- -- --
Activate (Page 1989) -- -- --
Adjust (Page 1990) -- -- -- --
Loaded (Page 1990) -- -- --
Execute (Page 1990) -- -- --
Selection changed (Page 1990) -- -- -- --
Double-click (Page 1991) -- -- -- --
Press (Page 1991) -- -- -- --
Operator input alarm property changed (Page 1991) -- -- -- --
Block property changed (Page 1992) -- -- -- --
Property diagram changed (Page 1992) -- -- -- --
Property changed (Page 1992) -- -- -- --
Trend property changed (Page 1993) -- -- -- --
Column property changed (Page 1993) -- -- -- --
Alarm statistics column property changed (Page 1993) -- -- -- --
Statistics area column name property changed (Page 1994) -- -- -- --
Change property status bar element (Page 1994) -- -- -- --
Change property toolbar button (Page 1994) -- -- -- --
Change property value axis (Page 1995) -- -- -- --
Change property value column (Page 1995) -- -- -- --
X-axis property changed (Page 1995) -- -- -- --
Y-axis property changed (Page 1996) -- -- -- --
Change property time axis (Page 1996) -- -- -- --
Change property time column (Page 1996) -- -- -- --
Outgoing (Page 1997) -- -- --
Incoming (Page 1997) -- -- --
In the alarm range (Page 1997) -- -- -- --
In the tolerance range (Page 1998) -- -- -- --
In the warning range (Page 1998) -- -- -- --
Click (Page 1998) -- -- --
Shortcut menu (Page 1999) -- -- -- --
Volume (Page 1999) -- -- -- --
Change layout (Page 1999) -- -- -- --
Change ruler (Page 2000) -- -- -- --
Press left mouse button (Page 2000) -- -- --
Release left mouse button (Page 2000) -- -- --
Loop-in alarm (Page 2001) -- -- --
Release (Page 2001) -- -- -- --
Move mouse (Page 2001) -- -- -- --
Medium opened (Page 2002) -- -- -- --
Medium closed (Page 2002) -- -- -- --
Object changed (Page 2002) -- -- --
Pause (Page 2003) -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1979
Acknowledge (Page 2003) -- --
Press right mouse button (Page 2003) -- -- --
Release right mouse button (Page 2004) -- -- --
Runtime Stop (Page 2004) -- -- -- --
Click toolbar button (Page 2004) -- -- -- --
Change slider (Page 2005) -- -- -- --
StepForward (Page 2005) -- -- -- --
StepBack (Page 2005) -- -- -- --
Lock changed (Page 2006) -- -- --
Status changed (Page 2006) -- -- --
Stop (Page 2006) -- -- -- --
Switch toolbar (Page 2007) -- -- -- --
Press key on keyboard (Page 2007) -- -- --
Release key on keyboard (Page 2007) -- -- --
Change video format (Page 2008) -- -- -- --
Full screen (Page 2008) -- -- -- --
Exit full screen (Page 2008) -- -- -- --
Replay (Page 2009) -- -- -- --
Basic objects
Introduction
The following table shows which events occur on which objects.
Technical data subject to change.
Icon Object
Line
Polyline
Polygon
Ellipse
Ellipse segment
Circle segment
Ellipse arc
Circular arc
Circle
Rectangle
Connector
Text field
Graphic view
Pipe
Double T-piece
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1980 System Manual, 08/2011,
Icon Object
T piece
Pipe bends
Play ended
(Page 1989)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Activate (Page 1989)
Adjust (Page 1990) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Loaded (Page 1990) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Execute (Page 1990) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Selection changed
(Page 1990)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Double-click
(Page 1991)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press (Page 1991) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Operator input alarm
property changed
(Page 1991)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Block property changed
(Page 1992)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Property diagram
changed (Page 1992)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Property changed
(Page 1992)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Trend property
changed (Page 1993)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Column property
changed (Page 1993)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Alarm statistics column
property changed
(Page 1993)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Statistics area column
name property
changed (Page 1994)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property status
bar element
(Page 1994)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property
toolbar button
(Page 1994)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property value
axis (Page 1995)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property value
column (Page 1995)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
X-axis property
changed (Page 1995)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1981
Y-axis property
changed (Page 1996)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property time
axis (Page 1996)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property time
column (Page 1996)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Outgoing (Page 1997) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Incoming (Page 1997) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
In the alarm range
(Page 1997)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
In the tolerance range
(Page 1998)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
In the warning range
(Page 1998)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Click (Page 1998)
Shortcut menu
(Page 1999)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Volume (Page 1999) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change layout
(Page 1999)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change ruler
(Page 2000)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press left mouse button
(Page 2000)
Release left mouse
button (Page 2000)
Loop-in alarm
(Page 2001)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Release (Page 2001) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Move mouse
(Page 2001)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Medium opened
(Page 2002)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Medium closed
(Page 2002)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Object changed
(Page 2002)
Pause (Page 2003) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Acknowledge
(Page 2003)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press right mouse
button (Page 2003)
Release right mouse
button (Page 2004)
Runtime Stop
(Page 2004)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1982 System Manual, 08/2011,
Click toolbar button
(Page 2004)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change slider
(Page 2005)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
StepForward
(Page 2005)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
StepBack (Page 2005) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Lock changed
(Page 2006)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Status changed
(Page 2006)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Stop (Page 2006) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Switch toolbar
(Page 2007)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press key on keyboard
(Page 2007)
Release key on
keyboard (Page 2007)
Full screen
(Page 2008)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Exit full screen
(Page 2008)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change video format
(Page 2008)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Replay (Page 2009) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Elements
Introduction
The following table shows which events occur on which elements.
Technical data subject to change.
Icon Object
IO field
Editable text field
List box
Combo box
Button
Round button
Symbolic IO field
Graphic IO field
Bar
Symbol library
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1983
Icon Object
Slider
Scroll bar
Check box
Option button
Gauge
Clock
Disk space view
Play ended
(Page 1989)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Activate (Page 1989)
Adjust (Page 1990) -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Loaded (Page 1990) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Execute (Page 1990) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Selection changed
(Page 1990)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Double-click
(Page 1991)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press (Page 1991) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Operator input alarm
property changed
(Page 1991)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Block property
changed (Page 1992)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Property diagram
changed (Page 1992)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Property changed
(Page 1992)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Trend property
changed (Page 1993)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Column property
changed (Page 1993)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Alarm statistics column
property changed
(Page 1993)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Statistics area column
name property
changed (Page 1994)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property
status bar element
(Page 1994)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property
toolbar button
(Page 1994)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1984 System Manual, 08/2011,
Change property value
axis (Page 1995)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property value
column (Page 1995)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
X-axis property
changed (Page 1995)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Y-axis property
changed (Page 1996)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property time
axis (Page 1996)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change property time
column (Page 1996)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Outgoing (Page 1997) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Incoming (Page 1997) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
In the alarm range
(Page 1997)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
In the tolerance range
(Page 1998)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
In the warning range
(Page 1998)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Click (Page 1998) -- -- -- --
Shortcut menu
(Page 1999)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Volume (Page 1999) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change layout
(Page 1999)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change ruler
(Page 2000)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press left mouse
button (Page 2000)
-- -- -- -- --
Release left mouse
button (Page 2000)
-- -- -- -- --
Loop-in alarm
(Page 2001)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Release (Page 2001) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Move mouse
(Page 2001)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Medium opened
(Page 2002)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Medium closed
(Page 2002)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Object changed
(Page 2002)
-- -- -- -- --
Pause (Page 2003) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Acknowledge
(Page 2003)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1985
Press right mouse
button (Page 2003)
-- -- -- -- --
Release right mouse
button (Page 2004)
-- -- -- -- --
Runtime Stop
(Page 2004)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Click toolbar button
(Page 2004)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Change slider
(Page 2005)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
StepForward
(Page 2005)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
StepBack (Page 2005) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Lock changed
(Page 2006)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Status changed
(Page 2006)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Stop (Page 2006) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Switch toolbar
(Page 2007)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Press key on keyboard
(Page 2007)
-- -- -- -- --
Release key on
keyboard (Page 2007)
-- -- -- -- --
Change video format
(Page 2008)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Full screen
(Page 2008)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Exit full screen
(Page 2008)
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Replay (Page 2009) -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Controls
Introduction
The following table shows which events occur on which controls.
Technical data subject to change.
Icon Object
Screen window
User view
HTML browser
Print job/Script diagnostics
Recipe view
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1986 System Manual, 08/2011,
Icon Object
Alarm view
f(x) trend view
f(t) trend view
Table view
Value table
Media Player
Channel diagnostics
Play ended (Page 1989) -- -- -- -- -- -- -- -- -- -- --
Activate (Page 1989)
Adjust (Page 1990) -- -- -- -- -- -- -- -- -- -- -- --
Loaded (Page 1990) -- -- -- -- -- --
Execute (Page 1990) -- -- -- -- -- -- -- -- -- -- -- --
Selection changed
(Page 1990)
-- -- -- -- -- -- -- -- -- -- --
Double-click (Page 1991) -- -- -- -- -- -- -- -- -- -- -- --
Press (Page 1991) -- -- -- -- -- -- -- -- -- -- -- --
Operator input alarm property
changed (Page 1991)
-- -- -- -- -- -- -- -- -- -- --
Block property changed
(Page 1992)
-- -- -- -- -- -- -- -- -- --
Property diagram changed
(Page 1992)
-- -- -- -- -- -- -- -- -- --
Property changed (Page 1992) -- -- -- -- -- --
Trend property changed
(Page 1993)
-- -- -- -- -- -- -- -- -- --
Column property changed
(Page 1993)
-- -- -- -- -- -- -- -- --
Alarm statistics column
property changed (Page 1993)
-- -- -- -- -- -- -- -- -- -- --
Auto-Hotspot -- -- -- -- -- -- -- -- -- -- --
Change property status bar
element (Page 1994)
-- -- -- -- -- --
Change property toolbar
button (Page 1994)
-- -- -- -- -- --
Change property value axis
(Page 1995)
-- -- -- -- -- -- -- -- -- -- --
Change property value column
(Page 1995)
-- -- -- -- -- -- -- -- -- -- --
X-axis property changed
(Page 1995)
-- -- -- -- -- -- -- -- -- -- --
Y-axis property changed
(Page 1996)
-- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1987
Change property time axis
(Page 1996)
-- -- -- -- -- -- -- -- -- -- --
Change property time column
(Page 1996)
-- -- -- -- -- -- -- -- -- -- --
Outgoing (Page 1997) -- -- -- -- -- -- -- -- -- -- -- --
Incoming (Page 1997) -- -- -- -- -- -- -- -- -- -- -- --
In the alarm range
(Page 1997)
-- -- -- -- -- -- -- -- -- -- -- --
In the tolerance range
(Page 1998)
-- -- -- -- -- -- -- -- -- -- -- --
In the warning range
(Page 1998)
-- -- -- -- -- -- -- -- -- -- -- --
Click (Page 1998) -- -- -- -- -- -- -- -- -- -- -- --
Shortcut menu (Page 1999) -- -- -- -- -- -- -- -- -- -- --
Volume (Page 1999) -- -- -- -- -- -- -- -- -- -- --
Change layout (Page 1999) -- -- -- -- -- -- -- -- -- -- --
Change ruler (Page 2000) -- -- -- -- -- -- -- -- -- -- --
Press left mouse button
(Page 2000)
-- -- -- -- -- -- -- -- -- -- -- --
Release left mouse button
(Page 2000)
-- -- -- -- -- -- -- -- -- -- -- --
Loop-in alarm (Page 2001) -- -- -- -- -- -- -- -- -- -- -- --
Release (Page 2001) -- -- -- -- -- -- -- -- -- -- -- --
Move mouse (Page 2001) -- -- -- -- -- -- -- -- -- -- -- --
Medium opened (Page 2002) -- -- -- -- -- -- -- -- -- -- --
Medium closed (Page 2002) -- -- -- -- -- -- -- -- -- -- --
Object changed (Page 2002) -- -- -- -- -- -- -- -- -- --
Pause (Page 2003) -- -- -- -- -- -- -- -- -- -- --
Acknowledge (Page 2003) -- -- -- -- -- -- -- -- -- -- -- --
Press right mouse button
(Page 2003)
-- -- -- -- -- -- -- -- -- -- -- --
Release right mouse button
(Page 2004)
-- -- -- -- -- -- -- -- -- -- -- --
Runtime Stop (Page 2004) -- -- -- -- -- -- -- -- -- -- -- --
Click toolbar button
(Page 2004)
-- -- -- -- -- --
Change slider (Page 2005) -- -- -- -- -- -- -- -- -- -- --
StepForward (Page 2005) -- -- -- -- -- -- -- -- -- -- --
StepBack (Page 2005) -- -- -- -- -- -- -- -- -- -- --
Lock changed (Page 2006) -- -- -- -- -- -- -- -- -- -- -- --
Status changed (Page 2006) -- -- -- -- -- -- -- -- -- -- -- --
Stop (Page 2006) -- -- -- -- -- -- -- -- -- -- --
Switch toolbar (Page 2007) -- -- -- -- -- -- -- -- -- -- --
Press key on keyboard
(Page 2007)
-- -- -- -- -- -- -- -- -- -- -- --
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1988 System Manual, 08/2011,
Release key on keyboard
(Page 2007)
-- -- -- -- -- -- -- -- -- -- -- --
Change video format
(Page 2008)
-- -- -- -- -- -- -- -- -- -- --
Full screen (Page 2008) -- -- -- -- -- -- -- -- -- -- --
Exit full screen (Page 2008) -- -- -- -- -- -- -- -- -- -- --
Replay (Page 2009) -- -- -- -- -- -- -- -- -- -- --
See also
Statistics area column name property changed (Page 1994)
Events
Play ended
Description
Occurs when the video or audio file has been played.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1989
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.
Loaded
Description
Occurs if a display or operating object is completely loaded in Runtime.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Execute
Description
Occurs when the scheduled task has been executed.
Selection changed
Description
Occurs when the selection is changed.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1990 System Manual, 08/2011,
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.
Operator input alarm property changed
Description
Occurs when the property of an operator input alarm is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1991
Block property changed
Description
Occurs when the property of a block, e.g., alarm text block, is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Property diagram changed
Description
Occurs when the property of a trend diagram is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Property changed
Description
Occurs when a property is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1992 System Manual, 08/2011,
Trend property changed
Description
Occurs when the property of the trend is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Column property changed
Description
Occurs when the property of a column is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Alarm statistics column property changed
Description
Occurs when the property of the alarm statistics column is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1993
Statistics area column name property changed
Description
Occurs when the column name of the statistics area is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Change property status bar element
Description
Occurs when the property of a status bar element is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Change property toolbar button
Description
Occurs when the property of a toolbar button is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1994 System Manual, 08/2011,
Change property value axis
Description
Occurs when the property of the value column is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Change property value column
Description
Occurs when the property of the value column is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
X-axis property changed
Description
Occurs when the property of the X-axis is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1995
Y-axis property changed
Description
Occurs when the property of the Y-axis is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Change property time axis
Description
Occurs when the property of the time axis changes.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Change property time column
Description
Occurs when the property of the time column is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1996 System Manual, 08/2011,
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.
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 alarm range
Description
Occurs if the available storage space has reached the configured monitoring limit "alarm". You
configure this event in the display and operating object "storage space display".
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1997
In the tolerance range
Description
Occurs if the available storage space has reached the configured monitoring limit "tolerance".
You configure this event in the display and operating object "storage space display".
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
In the warning range
Description
Occurs if the available storage space has reached the configured monitoring limit "warning".
You configure this event in the display and operating object "storage space display".
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:
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.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
1998 System Manual, 08/2011,
Shortcut menu
Description
Ocurs when the shortcut menu opens.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Volume
Description
Occurs when the volume changes.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Change layout
Description
Occurs when a property is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 1999
Change ruler
Description
Occurs when a property is changed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Press left mouse button
Description
Occurs when the operator left-clicks on a display and operating object.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Release left mouse button
Description
Occurs when the user releases the left mouse button after clicking.
This event does not occur as long as the left button remains pressed.
If the operator releases the button after clicking on a button, this event will also occur even if
the mouse pointer is no longer pointing on the button.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
2000 System Manual, 08/2011,
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.
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.
Move mouse
Description
Occurs when the user moves the mouse.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2001
Medium opened
Description
Occurs when the medium is opened.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Medium closed
Description
Occurs when the medium is closed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Object changed
Description
Occurs if the user changes a property of a display and operating object in Runtime.
Note
Every action triggered by this event is logged on individually and then logged off again when
the screen is changed. This behavior puts a burden on the working memory. Use this event
only for important changes to properties, e.g., for an I/O field.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
2002 System Manual, 08/2011,
Note
The availability of the event is dependent on the HMI device and object type.
Pause
Description
Occurs when playing of the video or audio file is paused.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
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.
Press right mouse button
Description
Occurs when the user right-clicks on a display and operating object.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2003
Release right mouse button
Description
Occurs when the user releases the right mouse button after clicking.
This event does not occur as long as the right mouse button remains pressed.
If the operator releases the button after clicking on a button, this event will also occur even if
the mouse pointer is no longer pointing on the button.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
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.
Click toolbar button
Description
Occurs when the user clicks a button in the toolbar.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
2004 System Manual, 08/2011,
Change slider
Description
Occurs when the volume slider changes.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
StepForward
Description
Occurs when the video or audio file goes to the next sequence.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
StepBack
Description
Occurs when the video or audio file goes to the previous sequence.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2005
See also
Elements (Page 1983)
Lock changed
Description
Occurs when the write access for the log is changed, e.g., from locked to released.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Status changed
Description
Occurs when the status of an alarm is changed, e.g., from incoming to outgoing.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Stop
Description
Occurs when playing of the video or audio file is stopped.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
2006 System Manual, 08/2011,
Switch toolbar
Description
Occurs when the property of the time axis changes.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Press key on keyboard
Description
Occurs when the user presses a key on the keyboard.
The keys <F10> and <ALT+PRINT> are not used by the operator for process operations.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Release key on keyboard
Description
Occurs when the user releases a key on the keyboard.
The keys <F10> and <ALT+PRINT> are not used by the operator for process operations.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2007
Change video format
Description
Occurs when the video format changes.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Full screen
Description
Occurs when the full screen mode is activated.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
Exit full screen
Description
Occurs when the full screen mode is exited.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
Visualizing processes (Professional)
9.8 Working with system functions and Runtime scripting
WinCC Professional V11.0 SP1
2008 System Manual, 08/2011,
See also
Elements (Page 1983)
Replay
Description
Occurs when the video or audio file has been replayed.
Note
Please note that the availability of the event is dependent upon the HMI device and object
type.
See also
Elements (Page 1983)
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.
Visualizing processes (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2009
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:
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
Visualizing processes (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2010 System Manual, 08/2011,
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2011
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2012 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2013
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2014 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2015
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2016 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2017
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2018 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2019
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2020 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2021
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2022 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2023
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2024 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2025
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2026 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 942)
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
WLAN reception (Page 947)
Effective range signal (Page 946)
Visualizing processes (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2027
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2028 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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2029
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 944)
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 (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
2030 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 2031)
Zone ID / connection point ID (Page 2032)
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 2030)
Visualizing processes (Professional)
9.9 Mobile Wireless
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2031
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 2030)
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
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2032 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2033
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.
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.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2034 System Manual, 08/2011,
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.
9.10.3.2 Triggers
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.
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.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2035
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:
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 (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2036 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.
Tag triggers
Tag triggers
In addition to acyclic, cyclic and event triggers, WinCC offers tag triggers.
Tag triggers consist of the specification of one or more tags. A task linked to such a trigger is
only performed when the value of the tag changes. This reduces the load on the system. The
cycle in which the tag values are scanned can be set individually for each tag. Select a value
ranging from "250 ms" to once an hour for the scanned cycles. You can also define your own
user cycles.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2037
Rules for selecting the trigger
Use the tag trigger instead of the cyclic trigger for tag processing. This reduces the load on
the system.
Cyclic triggers
You have selected "10 seconds" as the cyclic trigger. The task will be executed when the
trigger occurs.
= task is executed.
Tag triggers
The task is performed only when the value of the tag changes.
= task is executed.
9.10.3.3 Task type
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.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2038 System Manual, 08/2011,
See also
Integrating local VB scripts (Page 2040)
Integrating local C scripts (Page 2042)
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 1748)
Use a script with loops, conditional statements and abort conditions to program non-sequential
and conditional procedures.
Print task
Introduction
In addition to the "Function list", WinCC Runtime Professional also includes the "Print job" task
type.
Print job
You print the report by creating a print job. When a cyclic or acyclic trigger occurs, the
Scheduler starts the printout of a report. You define the scope of printing and the time range
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2039
of the report beforehand in the "Print jobs" editor. In addition, you specify whether the report
will be printed or written into a file.
If you have selected "Print job" as the task type, an additional field will appear in the "Task"
area. Select the predefined print job for the task in the "Print job" field.
Note
Activate "Scheduled print jobs in runtime" in the start sequence of WinCC Runtime to use the
"Print job" job type.
Click on "Runtime settings > Services > Scheduled print jobs in runtime" in the editor.
Integrating local VB scripts
Introduction
In addition to the "Function list" and "Print job" task types, Professional Runtime also allows
you to integrate local VB scripts.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2040 System Manual, 08/2011,
Integrating local VB scripts
You can create and edit local scripts. You can also convert the system functions offered in the
function list in a local script and edit the code. The local VB script is stored with the task.
A trigger starts the script in Runtime. Once you have converted a function list to a VB script,
you can no longer access the function list for this task. You will have to delete the VB script to
access the function list once again.
The Scheduler allows you to start VB scripts independent of screens. The VB scripts give you
access to tags and screens in Runtime.
There is no common data area between scripts in the Scheduler and screens. Scripts in the
Scheduler and screens can be synchronized with the DataSet object or tags. The data type of
VBS variables is always VARIANT.
The local VB script is not executed simultaneously. The script last triggered is put into a queue
until it is processed.
Note
When you create a script, the "Option explicit" statement is entered automatically in the
declaration section and cannot be deleted. The statement is necessary to avoid errors from
incorrectly spelled tags without declaration.
The statement requires you to always define tags with the "Dim" statement in your code. Do
not use the "Option explicit" statement in your code, as it can lead to Runtime errors.
Requirement
Enable "Tasks in Runtime" in the startup sequence of WinCC to use the function list and local
scripts.
Click "Runtime settings > Services > Tasks in Runtime" in the editor.
Note
You cannot call C scripts in VB scripts and vice versa.
User cycles as triggers
User cycles used as triggers for your VB scripts will always be executed in Runtime with a
granularity of 250 ms."
See also
Function list (Page 2038)
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2041
Integrating local C scripts
Introduction
In addition to the "Function list" and "Print job" task types, Runtime Professional also allows
you to integrate local C scripts.
Integrating local C scripts
You can create and edit local scripts. You can also convert the system functions offered in the
function list in a local C script and edit the code. The local C script is stored with the task.
A trigger starts the script in Runtime. Once you convert a function list to a C-script, you can no
longer access the function list for this task. You will have to delete the C script to access the
function list once again.
A trigger starts the local C script in Runtime.
The local C script is not executed simultaneously. The script last triggered is put into a queue
until it is processed.
Requirement
Enable "Tasks in Runtime" in the startup sequence of WinCC to use the function list and local
scripts.
Click "Runtime settings > Services > Tasks in Runtime" in the editor.
Note
You cannot call C scripts in VB scripts and vice versa.
User cycles as triggers
User cycles used as triggers for your C scripts will always be executed in Runtime with a
granularity of 250 ms."
See also
Function list (Page 2038)
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2042 System Manual, 08/2011,
9.10.4 Planning tasks
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 (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2043
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 task that starts the daily printout of a report.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2044 System Manual, 08/2011,
Requirements
You have created an HMI device with Runtime Professional.
The "Daily alarm report" print task has been created.
The "Scheduler" work area is open.
Procedure
1. Click "Add..." in the table of the task area.
2. Select "Print task" under "Type."
3. Enter "Daily alarm report printout" as the "Name."
4. Select "Daily" as the "Trigger."
5. In the Inspector window "Properties >Properties > General > at" enter the time "18:00".
6. Select the "Daily alarm report" print task in the "Task" area.
7. Open the "Runtime settings > Services" editor.
8. Enable "Start sequence of WinCC Runtime > Planned print jobs in Runtime".
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2045
Result
The report "Daily alarm report" will be printed every day 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 (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2046 System Manual, 08/2011,
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 (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2047
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 for Runtime Professional
9.10.5.1 Example: Activate the start screen daily
Introduction
You plan a task that activates the start screen daily with a logon dialog before the shift begins.
Requirements
A "start screen" has been created.
The "Scheduler" work area is open.
Procedure
1. Click "Add..." in the "Task" table.
2. Enter "Activate start screen" as the "Name".
3. Select "Function list" as the "Type".
4. Select "Daily" as the "Trigger."
5. In the Inspector window "Properties >Properties > General > at" enter the time "05:30".
6. In the Inspector window, open "Properties > Events".
7. Select the system function "ActivateScreen" from the "Screens" group in the function list.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2048 System Manual, 08/2011,
8. Enter "Start screen" as the "Screen name".
9. Open the "Runtime settings > Services" editor.
10.Activate "Scheduled tasks in Runtime".
Result
The "Start screen" is activated daily at 5:30 a.m.
9.10.5.2 Example: Printing a report once
Task
You plan a task that prints out a report once at the end of the year.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2049
Requirement
The "Annual overview" print task is created.
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Annual summary" as the "Name".
3. Select "Print task" as the "Type".
4. Select "Once" as the "Trigger."
5. Select "31.12.2010" in the "Properties > Properties > General > on" field of the Inspector
window.
6. Enter the time "22:00" in the "at" field.
7. Select the "Annual overview" print task in the "Task" area.
8. Open the "Runtime settings > Services" editor.
9. Enable "Start sequence of WinCC Runtime > Scheduled print jobs in Runtime".
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2050 System Manual, 08/2011,
Result
The "Annual overview" print job will be started on December 31, 2008 at 10:00 p.m.
9.10.5.3 Example: Reading the current user name
Introduction
You plan a task that writes the current user into a text field.
Requirements
A "Screen_1" screen has been created.
A "Textfield_1" text field has been created in the "Screen_1" screen.
The "Scheduler" work area is open.
Procedure
1. Click "Add..." in the table of the task area.
2. Enter "Reading the user name" as the "Name".
3. Select "Tag trigger" as the "Trigger".
4. Click "Properties > Properties > General > Add trigger" in the Inspector window.
5. Select the "@CurrentUser" system variable.
6. Select "1 min" as the "Cycle".
7. In the Inspector window, open "Properties > Events".
8. Click in the "Function list" area.
9. Enter the following VB script:
Sub Action ()
Dim user
user = HMIRuntime.Tags("@CurrentUser").Read
HMIRuntime.Screens("Screen_1").ScreenItems("Textfield_1").Text = user
End Sub
1. Open the "Runtime settings > Services" editor.
2. Activate "Scheduled tasks in Runtime".
Result
When the tag value changes, the current user is written into the "Textfield_1" text field.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2051
9.10.5.4 Example: Increment a tag
Introduction
You schedule a task that increments the value of a tag by one every hour.
Requirements
You have created an HMI device with Runtime Professional.
The "Scheduler" work area is open.
The "Tag1" tag has been created.
Procedure
1. Click "Add..." in the table of the task area.
2. Select "Function list" as the "Type."
3. Enter "Count up tag" as the "Name."
4. Select "1 hour" as the "Trigger".
5. In the Inspector window, under "Properties > Properties > General > Starting time > at
minute" enter the value "35:00".
6. In the Inspector window, open "Properties > Events".
7. Click in the "Function list" area.
8. Enter the following program code in the entry field:
Sub Action ()
Dim objTag1
Dim lngValue
Set objTag1 = HMIRuntime.Tags("Tag1")
lngValue = objTag1.Read
objTag1.Write lngValue + 1
End Sub
1. Open the "Runtime settings > Services" editor.
2. Select "Scheduled tasks in Runtime".
Result
The tag is incremented cyclically.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2052 System Manual, 08/2011,
9.10.6 Examples for Runtime Advanced and Panels
9.10.6.1 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 (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2053
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.6.2 Example: Weekly printout of a report
Introduction
You plan a task that starts the weekly printout of a report.
Requirements
A "Weekly report" report has been created.
The "Scheduler" work area is open.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2054 System Manual, 08/2011,
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 "Trigger."
4. Select "Properties > Properties > General > on day" "Friday" in the Inspector window.
5. Enter the time "18:00" in the "at" field.
6. In the Inspector window, select "Properties > Events".
7. Select the "Print/PrintReport" system function in the function list.
8. Select "Weekly report" report.
Result
The weekly print task starts on Friday at 18:00.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2055
9.10.6.3 Example: Changing the starting point of a task 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.
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.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2056 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2057
Example: 3. Configuring archiving 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.
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".
Visualizing processes (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
2058 System Manual, 08/2011,
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".
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 (Professional)
9.10 Planning tasks
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2059
9.11 Using global functions
9.11.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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2060 System Manual, 08/2011,
See also
HMI device wizard basics (Page 2061)
Importing and exporting project data (Page 2062)
General information about cross references (Page 2098)
Languages in WinCC (Page 2102)
Basics (Page 2130)
9.11.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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2061
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 2060)
9.11.3 Importing and exporting project data
9.11.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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2062 System Manual, 08/2011,
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.
See also
HMI device wizard basics (Page 2060)
9.11.3.2 Importing and exporting recipe data records
Exporting recipe data records
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2063
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
Importing recipe data records (Page 2065)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2064 System Manual, 08/2011,
Importing recipe data records
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2065
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.
See also
Exporting recipe data records (Page 2063)
Exporting recipe data records
Introduction
WinCC features an export function for exporting data records from recipes.
Requirements
The WinCC project for export is open.
Recipes have been created in a project.
The "Recipes" editor is open.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2066 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 displayed under "Recipe name".
3. Under "File name", specify the file in which the recipe data is to be stored.
4. Under "Content selection", specify if all or only selected data records are to be exported.
5. 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.
Importing recipe data records
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2067
Requirements
A CSV file containing at least one recipe has been created.
The WinCC project for 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 displayed under "Recipe name".
3. Select the file you want to import under "File name".
4. Under "Strategy", specify if existing data records should be overwritten by records of the
same name.
5. Click "Import."
The import will start.
Result
The data records are created in the selected recipe. Existing data records may be overwritten
by records with the same name from the CSV file depending on the setting for "Strategy".
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2068 System Manual, 08/2011,
Format of data from recipe data records
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:
"ID";<Name, recipe element 1>;< Name, recipe
element 2>;"LastUser";"LastAccess[UTC]"<Line break>
<Recipe data record number 1>;<Recipe data record 1 value 1>;<Recipe
data record 1 value 2>;"<Last user 1>";<Date and time 1><Line break>
<Recipe data record number 2>;<Recipe data record 2 value 1>;<Recipe
data record 2 value 2>;"<Last user 2>";<Date and time 2><Line break>
ID of the language
The recipe always has the first line, which is the header and describes the column headings.
Only the names of the recipe elements are added dynamically.
Each additional line represents one recipe data record with its recipe element values and
change information.
9.11.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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2069
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.
See also
Format of the analog alarm data (Page 2073)
Format of the discrete alarm data (Page 2076)
Format of the analog alarm data (Page 2078)
Format of the discrete alarm data (Page 2082)
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2070 System Manual, 08/2011,
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.
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
Format of the analog alarm data (Page 2073)
Format of the discrete alarm data (Page 2076)
Format of the analog alarm data (Page 2078)
Format of the discrete alarm data (Page 2082)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2071
Importing alarms
Introduction
Alarms are identified by their alarm name. An existing alarm will be overwritten with the data
from the xlsx file if the alarm name already exists in the project. A new alarm is created if the
alarm does not yet exist.
The alarm numbers must be unique in the project. If an alarm number is assigned more than
once by import, the alarm is imported and the alarm number marked as invalid.
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.
Note
There are no option settings for alarm import.
Result
The corresponding alarms including alarm texts are created in WinCC on the basis of the import
data. Messages 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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2072 System Manual, 08/2011,
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.
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:
Example of the worksheet "Analog alarms"
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2073
Table 9-19 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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2074 System Manual, 08/2011,
Example of the worksheet "Limits"
Table 9-20 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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2075
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 2069)
Importing alarms (Page 2070)
Format of the discrete alarm data (Page 2076)
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:
Example of the worksheet "Discrete alarms"
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2076 System Manual, 08/2011,
Table 9-21 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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2077
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 2069)
Importing alarms (Page 2070)
Format of the analog alarm data (Page 2073)
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 two worksheets:
Analog alarms(Analog alarms)
Limits (Limits)
Each alarm is assigned a separate line in the import file. The import file with the analog alarms
must be formatted as follows:
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2078 System Manual, 08/2011,
Example of the worksheet "Analog alarms"
Table 9-22 Meaning of the entries
List entry Meaning
ID Shows the number of the analog alarm. The alarm number must be unique in the
project.
Name Shows the name of the analog alarm. The name is used to reference an alarm.
Alarms with identical names are overwritten during import. An alarm without an
existing name is created.
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:
Parameter: <ref id = 0; type = AlarmAnalogParameter; Parameter = Limit;
DisplayType = Decimal; Length = 1; Precision = 0; Alignment = Right; ZeroPadding
= False;>
System parameters: <ref id = 0; type = CommonSystemParameter;
SystemParameter = UserName;>
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2079
List entry Meaning
Class The alarm class of an alarm determines whether or not the alarm has to 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 along with these alarms of the same group
in a single operation.
Priority Indicates alarm priority. You can sort the alarms in the alarm view by priority.
Range: 0 -16
CPU number Specifies the CPU number. This option is only activated if you have enabled the
"CPU/PLC number" alarm text block in the "Alarm blocks > System blocks" tab in
the "HMI alarms" editor.
PLC number Shows the PLC number. This option is only activated if you have enabled the "CPU/
PLC number" alarm text block in the "Alarm blocks > System blocks" tab in the
"HMI alarms" editor.
Trigger tag Specifies the tag monitored for limit value violation.
Verzgerung 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.
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.
Single acknowledgment Specifies whether each individual alarm must be acknowledged.
True = Alarms must be acknowledged individually.
Status tag Shows the tag which saves the Incoming and Outgoing alarm statuses and the
Acknowledgement request saved.
Status bit Specifies the number of the bit that is set and acknowledges the alarm.
Alarm annonciation Indicates whether an alarm is being suppressed.
True = suppressed alarm.
Display suppresion mask Indicates the display suppression method.
Additonal Text Shows the additional alarm text.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2080 System Manual, 08/2011,
Example of the worksheet "Limits"
Table 9-23 Meaning of the entries
List entry Meaning
Alarm ID The alarm number is used to reference an alarm. The alarm
number is unique. The alarm number allows alarms to be
assigned limits.
Name Shows the name of the analog alarm.
Limit mode Indicates the method used for monitoring the limit value.
Grenzen
Limit type
Specifies the limit that will be monitored. Both a tag and a
constant can be used as limit value.
Limit value Indicates the tag or constant monitored for limit violation.
Suppression Indicates whether an alarm is being suppressed.
True = suppressed alarm.
Deadband 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 interpreted as
absolute.
1 = The value specified for "Hysteresis" is a percentage value
of the limit value.
Deadband mode Specifies a constant as 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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2081
See also
Exporting alarms (Page 2069)
Importing alarms (Page 2070)
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 worksheet "Discrete alarms" (discrete alarms).
Each alarm is assigned a separate line in the import file. Structure of the import file containing
the discrete alarms:
Example of the worksheet "Discrete alarms"
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2082 System Manual, 08/2011,
Table 9-24 Meaning of the entries
List entry Meaning
ID Shows the number of the discrete alarm. The alarm number is unique.
Name Shows the name of the discrete alarm. The name is used to reference an alarm. Alarms
with identical names are overwritten during import. An alarm without an existing name
is created.
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:
Parameter: <ref id = 0; type = AlarmDiscreteParameter; Parameter = Parameter 1; Tag
= HMI_Variable_1; DisplayType = Decimal; Length = 5; Precision = 0; Alignment =
Right; ZeroPadding = False;>
System parameters: <ref id = 0; type = CommonSystemParameter; System Parameter
= UserName;>
Class The alarm class of an alarm determines whether or not the alarm has to 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 along with these alarms of the same group in a single
operation.
Priority Indicates alarm priority. You can sort the alarms in the alarm view by priority. Range:
0 -16
CPU number Specifies the CPU number. This option is only activated if you have enabled the "CPU/
PLC number" alarm text block in the "Alarm blocks > System blocks" tab in the "HMI
alarms" editor.
PLC number Shows the PLC number. This option is only activated if you have enabled the "CPU/
PLC number" alarm text block in the "Alarm blocks > System blocks" tab in the "HMI
alarms" editor.
Trigger tag Specifies the tag containing the bit that triggers the alarm.
Trigger bit Specifies the number of the bit that triggers the alarm.
Trigger mode Indicates the method used for monitoring the limit value.
Alarm parameter Indicates tag assigned to a parameter block to issue process values in alarm texts.
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.
Single acknowledgment Specifies whether each individual alarm must be acknowledged.
True = Alarms must be acknowledged individually.
Status tag Shows the tag which saves the Incoming and Outgoing alarm statuses and the
Acknowledgement request saved.
Status bit Specifies the number of the bit that is set and acknowledges the alarm.
Alarm annonciation Indicates whether an alarm is being suppressed.
True = suppressed alarm.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2083
List entry Meaning
Display suppresion mask Indicates the display suppression method.
Additonal Text Shows the additional alarm text.
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 2069)
Importing alarms (Page 2070)
9.11.3.4 Importing and exporting tags
Exporting tags
Introduction
WinCC has an export function for tags.
Requirements
The WinCC project for the export is open.
Tags have been created in the project.
The "HMI tags" editor is open.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2084 System Manual, 08/2011,
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.
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.
The WinCC project for the import is open.
The "HMI tags" editor is open.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2085
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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2086 System Manual, 08/2011,
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-25 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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2087
List entry Meaning
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2088 System Manual, 08/2011,
Example of the worksheet "Multiplexing"
Table 9-26 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.
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 (tags)
SubstituteValueUsage (substitute value)
Each tag is on a separate line in the import file. The import file with the tag data must have the
following format:
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2089
Example of the worksheet "HMI Tags"
Table 9-27 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 Specifies which PLC tag is linked to the HMI tag.
Connection Indicates the name of the connection.
Date type Specifies the data type of the PLC 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.
HMI Data type Specifies the data type of the HMI 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 in bytes. 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.
Start Value Specifies the start value of a tag.
Substitute Value Indicates the substitute value. The substitute value is used when a process value
with errors is read.
ID tag The update ID updates the value of a tag with the aid of a function or a PLC job
within a device. The update ID must be unique.
High High Limit type Indicates whether the limit value "High high" is monitored by a constant 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 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 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 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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2090 System Manual, 08/2011,
List entry Meaning
End value HMI Specifies the end value of the HMI tag.
Start value HMI Specifies the start value of the HMI tag.
Example of the worksheet "SubstituteValueUsage"
Table 9-28 Meaning of the entries
List entry Meaning
Parent Specifies the tag for which a substitute value has been defined. The tag must be
available in the "HMI-Tags" worksheet.
Substitute Value Usage Indicates the substitute value. The substitute value can be used in the following
situations:
As start value
After communication error
High High limit value
Low Low limit 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.
9.11.3.5 Importing and exporting text lists
Exporting text lists
Introduction
WinCC has an export function for text lists.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2091
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
Importing text lists (Page 2092)
Format of text list data (Page 2093)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2092 System Manual, 08/2011,
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.
See also
Exporting text lists (Page 2091)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2093
Example of the worksheet "TextList"
Table 9-29 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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2094 System Manual, 08/2011,
Table 9-30 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;>
See also
Exporting text lists (Page 2091)
9.11.3.6 Importing and exporting project texts
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2095
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.
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2096 System Manual, 08/2011,
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2097
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.
9.11.4 Using cross-references
9.11.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.
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.
See also
HMI device wizard basics (Page 2060)
9.11.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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2098 System Manual, 08/2011,
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.
9.11.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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2099
Column Content/meaning
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.
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.11.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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2100 System Manual, 08/2011,
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:
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2101
9.11.5 Managing languages
9.11.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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2102 System Manual, 08/2011,
See also
Language settings in the operating system (Page 2103)
Operating system settings for Asian languages (Page 2104)
Selecting the user interface language (Page 2105)
"Graphics" editor (Page 2116)
Languages in Runtime (Page 2120)
Example: Configuring a button for language switching (Page 2127)
HMI device wizard basics (Page 2060)
9.11.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 2102)
Operating system settings for Asian languages (Page 2104)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2103
9.11.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".
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 2102)
Language settings in the operating system (Page 2103)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2104 System Manual, 08/2011,
9.11.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".
Result
WinCC will use the selected language as user interface language.
See also
Enable project languages (Page 2105)
Selecting the reference language and editing language (Page 2106)
Languages in WinCC (Page 2102)
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2105
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 2105)
Selecting the reference language and editing language (Page 2106)
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2106 System Manual, 08/2011,
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.
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 2105)
Enable project languages (Page 2105)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2107
9.11.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.
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 2109)
Translating texts directly (Page 2110)
Translating texts using reference texts (Page 2112)
Exporting project texts (Page 2113)
Importing project texts (Page 2115)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2108 System Manual, 08/2011,
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
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2109
See also
Working with multiple languages (Page 2108)
Translating texts directly (Page 2110)
Translating texts using reference texts (Page 2112)
Exporting project texts (Page 2113)
Importing project texts (Page 2115)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2110 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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2111
See also
Working with multiple languages (Page 2108)
Exporting project texts (Page 2113)
Project text basics (Page 2109)
Importing project texts (Page 2115)
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 2108)
Exporting project texts (Page 2113)
Project text basics (Page 2109)
Importing project texts (Page 2115)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2112 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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2113
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2114 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 2108)
Translating texts using reference texts (Page 2112)
Translating texts directly (Page 2110)
Project text basics (Page 2109)
Importing project texts (Page 2115)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2115
See also
Exporting project texts (Page 2113)
Working with multiple languages (Page 2108)
Project text basics (Page 2109)
Translating texts directly (Page 2110)
Translating texts using reference texts (Page 2112)
9.11.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 2118)
Storing graphics in the graphics library (Basic, Advanced, Professional) (Page 2117)
Languages in WinCC (Page 2102)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2116 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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2117
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 2116)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2118 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 2116)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2119
9.11.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 2120)
Enabling the runtime language (Page 2121)
Setting the runtime language order for language switching (Page 2123)
Setting the default font for a runtime language (Page 2125)
Selecting the log language (Page 2126)
Languages in WinCC (Page 2102)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2120 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 2120)
Selecting the log language (Page 2126)
Enabling the runtime language (Page 2121)
Setting the runtime language order for language switching (Page 2123)
Setting the default font for a runtime language (Page 2125)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2121
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2122 System Manual, 08/2011,
See also
Languages in Runtime (Page 2120)
Selecting the log language (Page 2126)
Setting the runtime language order for language switching (Page 2123)
Methods for language switching (Page 2120)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2123
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 2120)
Selecting the log language (Page 2126)
Enabling the runtime language (Page 2121)
Setting the default font for a runtime language (Page 2125)
Methods for language switching (Page 2120)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2124 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 2120)
Selecting the log language (Page 2126)
Setting the runtime language order for language switching (Page 2123)
Methods for language switching (Page 2120)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2125
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 2120)
Setting the default font for a runtime language (Page 2125)
Setting the runtime language order for language switching (Page 2123)
Methods for language switching (Page 2120)
Enabling the runtime language (Page 2121)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2126 System Manual, 08/2011,
9.11.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 2127)
Example: Configuring a button for language switching for each runtime language
(Page 2128)
Languages in WinCC (Page 2102)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2127
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 2127)
Example: Configuring a button for language switching for each runtime language
(Page 2128)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2128 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 2127)
Example: Configuring a button in multiple languages (Page 2127)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2129
9.11.6 Replacing devices
9.11.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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2130 System Manual, 08/2011,
See also
Device-specific functions (Page 2131)
Example: Replacing devices (Page 2142)
Basics (Page 2144)
HMI device wizard basics (Page 2060)
Engineering system (Page 2380)
Basic Panel (Page 2382)
Panel (Page 2385)
Mobile Panel (Page 2389)
Multi Panel (Page 2393)
Comfort Panel (Page 2397)
WinCC Runtime Advanced (Page 2400)
9.11.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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2131
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
Basics (Page 2130)
Key assignment when replacing devices (Page 2132)
Key assignment when replacing devices (Page 2134)
Screen adjustment options (Page 2136)
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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2132 System Manual, 08/2011,
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
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2133
See also
Key assignment when replacing devices (Page 2134)
Device-specific functions (Page 2131)
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2134 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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2135
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 2132)
Device-specific functions (Page 2131)
9.11.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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2136 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2137
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.
See also
Specifying the position of screen objects (Page 2139)
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2138 System Manual, 08/2011,
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.
"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 2139)
Specifying the position of screen objects
Introduction
There are various ways to adjust the position of screen objects to the new device.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2139
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.
See also
Screen adjustment options (Page 2136)
Fit objects to contents (Page 2138)
9.11.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 2141)
Example: Replacing devices (Page 2142)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2140 System Manual, 08/2011,
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.
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 2142)
Example: Procedures overview (Page 2140)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2141
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.
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2142 System Manual, 08/2011,
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.
See also
Example: Procedures overview (Page 2140)
Basics on migration (WinCC flexible) (Page 92)
Basics (Page 2130)
Example: Adjusting screens (Page 2141)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2143
9.11.7 Copying between devices and editors
9.11.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:
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2144 System Manual, 08/2011,
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.
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.
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.
Unsupported objects and functionalities
Introduction
When an object is copied, all its properties and settings are transferred to the target HMI device.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2145
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.
9.11.7.2 Copying and pasting
Simple and extended pasting
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2146 System Manual, 08/2011,
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.
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
Linked objects copied automatically (Page 2147)
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
Simple and extended pasting (Page 2146)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2147
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
Tag Alarm
Logging tag
Cycle
Log Logging tag
Logging tag Log type
Recipe element Text list
Scheduler Triggers
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".
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2148 System Manual, 08/2011,
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".
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".
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 2136)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2149
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.
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.
Differences between Runtime Advanced and Panels and Runtime Professional
Overview
The following table shows the availability of the various functions in Runtime Advanced and
Panels and Runtime Professional.
Function in WinCC Runtime Advanced and Panels Runtime Professional
Logs Yes
Data log
Alarm log
Yes
Data log
Compressed log
Alarm log
Scheduler Yes Yes
User administration Yes Yes
Screens Yes Yes
Settings Yes Yes
Global elements Yes No
Alarms Yes
Alarm indicator
Alarm window
Alarm view
Yes
Alarm view with more functions than in
Runtime Advanced and Panels
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2150 System Manual, 08/2011,
Function in WinCC Runtime Advanced and Panels Runtime Professional
Menus and toolbars No Yes
Reports Yes
Printout using the "PrintReport" system
function
Yes
Printout using print job and scheduler
Recipes Yes User archives from WinCC V6.2
Scripts Yes
VBS
Yes
VBS
C
Structures Yes Yes
Text and graphics lists Yes Yes
Tags Yes Yes
Connections Yes
Different communication drivers
Yes
Different communication drivers
Templates Yes No
Cycles Yes Yes
9.11.7.3 Copying and pasting between Runtime Advanced and Panels and Runtime Professional
Basics
Introduction
You can copy and paste project data such as screens, objects and tags between devices in
different runtimes.
Properties and settings
Objects that are supported in both Runtimes can have different properties and settings. During
copying and pasting these differences are implemented as follows:
Properties not supported by the target HMI device are not displayed.
Default settings are specified for properties that are only supported by the target HMI device.
Settings which are not supported by the target HMI device are replaced by default settings.
If you copy an object back to the source HMI device without manually changing the settings
in the target HMI device, all properties and settings originally set in the source HMI device will
be reactivated.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2151
Unsupported events and animations
When you paste an object into a different Runtime, the following cases are possible:
The target HMI device does not support events or animations for the object copied.
Events or animations configured for the copied object are not displayed in the target HMI
device.
Events or animations for the object copied are only supported by the target HMI device.
Certain events and animations are not supported by the target HMI device for the object
copied.
Events or animations that were configured for the copied object and are not supported by
the target HMI device are not displayed on the target HMI device.
Certain events and animations for the object copied are only supported by the target HMI
device.
All events and animations originally set will be reactivated if you copy the same object back to
the source HMI device.
System functions
Supported system functions
The following system functions are supported in Runtime Advanced and Panels as well as
Runtime Professional:
ActivateScreen
IncreaseTag
InvertBit
InvertBitInTag
InverseLinearScaling
LinearScaling
ResetBit
ResetBitInTag
SetBit
SetBitInTag
SetTag
StopRuntime
DecreaseTag
ShowLogonDialog
Additional system functions are supported in Runtime Advanced and Panels.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2152 System Manual, 08/2011,
Limitations during copying
Differences between the Runtimes
Some functions are supported exclusively in one Runtime. Some functionalities are supported
in both Runtimes, but have different concepts. You cannot copy and paste These functions
between the Runtimes.
Functionalities only supported by Runtime Advanced and Panels
Templates
Global elements
You cannot copy these functions to Runtime Professional.
Functionalities only supported in Runtime Professional
Menus and toolbars
C scripts
You cannot copy these functions to Runtime Advanced and Panels.
Functions with different concepts
Configuration
Recipes
These functions cannot be copied between the Runtimes.
Objects in screens
Introduction
When you copy an object from a screen and paste it into another screen, the object is inserted
at the same position in the screen.
Text and graphics lists
When you copy a symbolic I/O field with a text list or a graphic I/O field with a graphics list and
paste it into another runtime, the text list or graphics list will be copied to the target HMI device.
Copying objects from reports
You can copy objects that are supported in the screen from a report into a screen. Unsupported
settings are replaced by supported settings. When you copy a copied object back into a report,
the changed settings remain active.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2153
Recipe view and alarm view
The "Recipe view" and "Alarm view" objects have such different concepts that you cannot copy
and paste these objects between the two Runtimes.
See also
Screen objects (Page 2154)
Objects (Page 2170)
Screen objects
Supported objects
The following table shows which objects in screens are supported in which Runtime:
Object Runtime Advanced and Panels Runtime Professional
Line Yes Yes
Polyline Yes Yes
Polygon Yes Yes
Ellipse Yes Yes
Circle Yes Yes
Ellipse segment No Yes
Circle segment No Yes
Ellipse arc No Yes
Circular arc No Yes
Rectangle Yes Yes
Connector No Yes
Text field Yes Yes
Pipe No Yes
Double T-piece No Yes
T piece No Yes
Pipe bends No Yes
I/O field Yes Yes
Symbolic I/O field Yes Yes
Date/time field Yes No
Button Yes Yes
Round button No Yes
Switch Yes No
Graphic view Yes Yes
Graphic I/O field Yes Yes
Bar Yes Yes
Status/Force Yes No
Clock Yes Yes
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2154 System Manual, 08/2011,
Object Runtime Advanced and Panels Runtime Professional
Gauge Yes Yes
Slider Yes Yes
Symbol library Yes Yes
User view Yes Yes
HTML browser Yes Yes
Sm@rtClient view Yes No
Check box No Yes
Option buttons No Yes
Scroll bar No Yes
Screen window No Yes
Disk space view No Yes
Channel diagnostics No Yes
Application window No Yes
Recipe view Yes Yes
Alarm view Yes Yes
Trend view Yes No
f(t) trend view No Yes
f(x) trend view No Yes
Table view No Yes
Alarm view Yes Yes
Recipe view Yes Yes
Charge condition Yes No
Effective range name Yes No
Effective range name (RFID) Yes No
Effective range signal Yes No
Zone name Yes No
Zone signal Yes No
Connections
Differences between Runtime Advanced and Panels and Runtime Professional
Communication drivers
Please refer to the communications manual for information about the communication drivers
possible in the Runtimes. Runtime Advanced and Panels and Runtime Professional support
different communication drivers. There is no common communication driver for both runtimes.
Area pointer
The area pointers are not supported in Runtime Professional.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2155
Copying connections
Introduction
You can copy a connection in the "Connections" editor and paste it in the "Connections" editor
of another Runtime.
Integrated connections
Integrated connections are created under "Devices & networks" in the network view. An
integrated connection is displayed in the "Connections" editor. However, you cannot edit the
integrated connection in the "Connections" editor. Any integrated connection you copy and
paste from the "Connections" editor to another Runtime will become invalid in the target HMI
device as it lacks a communication partner. You can only edit the copied integrated connection
in the network view of the target device.
Copying variables
Introduction
You can copy a tag in the "Tags" editor and paste it in the "Tags" editor of another Runtime.
Unsupported data types
If you copy a tag with a data type that is not supported in the other Runtime, then the data type
will become invalid.
Logging tags
If you have linked the tag to a logging tag, this logging tag will be copied to the target HMI
device together with the tag. A logging tag has to be assigned to a data log. A new log will be
created if there is no corresponding data log in the target HMI device.
Alarms
Any analog or discrete alarms you have configured for a tag will be copied to the target HMI
device together with the tag.
System tags
System tags are supported in Runtime Professional only.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2156 System Manual, 08/2011,
See also
Tag data types and properties (Page 2157)
Logging tags (Page 2166)
Discrete alarms (Page 2161)
Analog alarms (Page 2162)
Tag data types and properties
Data types
The following table shows which data types are supported in which Runtime.
Data type Runtime Advanced and Panels Runtime Professional
Boolean Yes Yes
Byte (Signed Byte) Yes Yes
UByte (Unsigned Byte) Yes Yes
Short (Signed Int) Yes Yes
UShort (Unsigned Int) Yes Yes
Long (Signed Long) Yes Yes
ULong (Unsigned Long) Yes Yes
Float Yes Yes
Double Yes Yes
String Yes Yes
UString (Unicode String) No Yes
Raw (Raw Data Type) No Yes
Ref (Text Reference) No Yes
Date Time Yes No
Properties
The following properties are supported in Runtime Advanced and Panels as well as Runtime
Professional:
Address
Content (comment)
Connection
Control variable
Data type
Length
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2157
Limit values:
Upper error
Generate analog alarm for upper error
Upper warning
Generate analog alarm for upper warning
Low
Generate analog alarm for lower warning
Lower error
Generate analog alarm for lower error
Linear scaling
Name
HMI device end value
HMI device start value
PLC end value
PLC start value
Start value
Structures
Structural elements
Introduction
You can copy a structural element in the "Structures" editor and paste it in the "Structures"
editor of another Runtime.
Unsupported data types
If you copy a structural element with a data type that is not supported in the other Runtime,
the data type becomes invalid in the "Structure" editor.
See also
Structure data types and properties (Page 2159)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2158 System Manual, 08/2011,
Structure types
Introduction
You can copy a structure type from the "Structures" folder and paste it into the "Structures"
folder of another Runtime.
Unsupported controller types
Since no controller type is supported in both Runtimes, the controller type will be invalid in the
target HMI device.
Device family
The device family is adapted to the target HMI device when copied. If you copy a structure
type from Runtime Advanced and Panels to Runtime Professional, for example, the "SmartCE"
entry automatically becomes "SCADA."
Internal and external data types
In Runtime Advanced und Panels, a structure type can contain either exclusively internal data
types or exclusively external ones. In Runtime Professional, both internal and external data
types can be contained in one structure type.
If you copy a structure type that contains internal and external data types from Runtime
Professional to Runtime Advanced und Panels, all internal data types become invalid. Since
no communication peer is supported in both Runtimes, all external data types become invalid
as well.
Structure data types and properties
Data types
The following table shows which data types are supported in which Runtime.
Data type Runtime Advanced and Panels Runtime Professional
Boolean Yes Yes
Byte (Signed Byte) Yes Yes
UByte (Unsigned Byte) Yes Yes
Short (Signed Int) Yes Yes
UShort (Unsigned Int) Yes Yes
Long (Signed Long) Yes Yes
ULong (Unsigned Long) Yes Yes
Float Yes Yes
Double Yes Yes
String Yes Yes
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2159
Data type Runtime Advanced and Panels Runtime Professional
UString (Unicode String) No Yes
Raw (Raw Data Type) No Yes
Ref (Text Reference) No Yes
Date Time Yes No
Properties
The following properties are supported in Runtime Advanced and Panels as well as Runtime
Professional:
Structure types:
Comment: Contents
Name
Type of controller
Device family
Structural elements:
Comment: Contents
Data type
Length
Linear scaling
Name
HMI device end value
HMI device start value
PLC end value
PLC start value
Error upper limit
Error lower limit
Start value
Bit offset
Offset
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2160 System Manual, 08/2011,
Alarms
Differences between Runtime Advanced and Panels and Runtime Professional
Supported objects in the screen
You can configure the following objects for screen alarm display in Runtime Advanced and
Panels:
Alarm view
Alarm window
Alarm indicator
In Runtime Professional, you can only configure an alarm view.
The concepts of the alarm view in the Runtimes are so different that it is not possible to copy
an alarm view between the Runtimes.
Alarm text blocks
Alarm blocks are supported in Runtime Professional only.
Discrete alarms
Introduction
You can copy a discrete alarm in the "Alarms" editor in the "Discrete alarms" tab and paste it
to another Runtime. Pasting a tag with configured discrete alarms to the "Tags" editor will
automatically also paste the corresponding discrete alarms to the "Alarms" editor.
Supported properties
The following properties are supported in Runtime Advanced and Panels as well as Runtime
Professional:
ID
Alarm class
Alarm group
Acknowledgment: Tag
Acknowledgment: Bit
Tooltip
Trigger: Tag
Trigger: Bit
Event text
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2161
Alarm number
Alarm numbers which do not yet exist in the target HMI device are transferred unchanged
when copied. If the alarm number already exists, the next free number is assigned
automatically as the alarm number for the discrete alarm.
Tooltip
Copying a tooltip with more than 255 characters to Runtime Professional will make the entire
tooltip invalid.
Event text
The event text is displayed in the following dialog boxes of the Inspector window:
Runtime Panels and Advanced:
"Properties > Properties > General > Settings > Event text"
Runtime Professional:
"Properties > Properties > Texts > Settings > Event text"
The event texts are copied into the corresponding dialog boxes with all the format data.
Event texts will become invalid:
if you copy an event text with more than 254 characters to Runtime Advanced and Panels.
if you copy an event text with a dynamic parameter to Runtime Panels and Advanced.
if you copy an event text with a text list from Runtime Panels and Advanced to Runtime
Professional.
Analog alarms
Introduction
You can copy an analog alarm in the "Alarms" editor in the "Analog alarms" tab and paste it
to another Runtime. Pasting a tag with configured analog alarms to the "Tags" editor will
automatically also paste the corresponding analog alarms to the "Alarms" editor.
Supported properties
The following properties are supported in Runtime Advanced and Panels as well as Runtime
Professional:
Alarm number "ID"
Event text
Alarm class
Alarm group
Tooltip
Trigger: Tag
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2162 System Manual, 08/2011,
Delay
Limit value
Trigger mode
Synchronize limit value
Hysteresis mode
Hysteresis
Hysteresis as a percentage
Alarm number "ID"
Alarm numbers which do not yet exist in the target HMI device are transferred unchanged
when copied. If the alarm number already exists, the next free number is assigned
automatically as the alarm number for the analog alarm.
Event text
The event text is displayed in the following dialog boxes of the Inspector window:
Runtime Advanced and Panels:
"Properties > Properties > General > Settings > Event text"
Runtime Professional:
"Properties > Properties > Texts > Settings > Event text"
The event texts are copied into the corresponding dialog boxes with all the format data.
Event texts will become invalid:
if you copy an event text with more than 254 characters to Runtime Advanced and Panels.
if you copy an event text with a dynamic parameter to Runtime Panels and Advanced.
if you copy an event text with a text list from Runtime Panels and Advanced to Runtime
Professional.
Tooltip
Copying a tooltip with more than 255 characters to Runtime Professional will make the entire
tooltip invalid.
Delay
If you copy a delay with the "Minute" or "Hour" unit from Runtime Professional to Runtime
Advanced and Panels, the setting becomes invalid.
See also
Copying variables (Page 2156)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2163
Controller alarms and system alarms
Controller alarms
Since controller alarms are configured in the controller, it is not possible to copy controller
alarms.
System alarms
Because system alarms are dependent on the HMI device, it is not possible to copy system
alarms.
Alarm classes
Introduction
You can copy an alarm class in the "Alarms" editor in the "Alarm classes" tab and paste it to
another Runtime.
Predefined alarm classes
You cannot copy and paste predefined alarm classes.
Log
In Runtime Advanced and Panels, you configure an archive in which the alarm is stored. In
Runtime Professional, you specify whether the alarm is logged for each alarm of an alarm
class.
During the copying process the logging specifications are implemented as follows:
Copying from Runtime Advanced and Panels to Runtime Professional:
If a log has been created in Runtime Advanced and Panels, "Log" is activated in Runtime
Professional.
If no log has been created in Runtime Advanced and Panels, "Log" is deactivated in
Runtime Professional.
Copying from Runtime Professional to Runtime Advanced and Panels:
If "Log" is activated in Runtime Professional, you need to specify a log in Runtime Advanced
and Panels.
If "Log" is deactivated in Runtime Professional, the entry <No log> is specified in Runtime
Advanced and Panels.
Flashing
The settings for the flash behavior are not copied.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2164 System Manual, 08/2011,
Alarm groups
Copying and pasting
You can copy an alarm group in the "Alarms" editor in the "Alarm groups" tab and paste it to
another Runtime.
Alarm groups from alarm classes
Alarm groups from alarm classes are only supported in Runtime Professional and cannot be
copied and pasted to Runtime Advanced and Panels.
Hierarchy
Hierarchies of alarm groups are only supported in Runtime Professional. When copied
between the Runtimes the hierarchy order is implemented as follows:
Copying from Runtime Advanced and Panels to Runtime Professional
If you copy an alarm group into the "Alarm groups" tab of the "Alarms" editor, the alarm
group is inserted regardless of any existing alarm groups.
If you copy an alarm group into a line containing an existing alarm group, the alarm group
is inserted as an alarm group that is subordinate in the hierarchy.
Copying from Runtime Professional to Runtime Advanced and Panels
Hierarchies cannot be shown in Runtime Advanced and Panels. Alarm groups from all
hierarchy levels are inserted independently of each other.
ID of the alarm group
Alarm numbers which do not yet exist in the target HMI device are transferred unchanged
when copied.
Logs
Differences between Runtime Advanced and Panels and Runtime Professional
Logs
Data logs are supported in both Runtimes. You can copy and paste alarm logs and compressed
logs between the runtimes.
Properties
The following properties are supported in Runtime Advanced and Panels as well as Runtime
Professional:
Data logs
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2165
Name
Comment
Storage location
Logging tags
Name
Process variable
Triggers
Logging cycle
High limit
Low limit
Comment
Events
You cannot copy configured events between Runtime Advanced and Panels and Runtime
Professional.
Data logs
Copying and pasting
You can copy a data log in the "Historical Data" editor in the "Data log" tab and paste it to
another Runtime. All logging tags contained in the data log are included automatically.
Logging tags
Introduction
You can copy a logging tag in the "Historical Data" editor in the "Data log" tab and paste it in
another Runtime.
In addition, you can copy a logging tag in the "Tags" editor of Runtime Professional and paste
it into the "Historical Data" editor in Runtime Advanced and Panels. To copy a logging tag in
Runtime Professional, open the "Tags" editor and select the "Alarms & Logs" tab in the upper
work area. Copy the desired logging tag in the lower work area of the "Data logs" tab.
Tags used in the logging tags
Any logging tag you have linked to a tag will be automatically also copied if the tag is copied
to the target HMI device. A new log will be created if there is no corresponding data log in the
target HMI device. There may be performance problems if too much of this additional data is
copied.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2166 System Manual, 08/2011,
Multiple logging of tags
When copying from Runtime Professional to Runtime Advanced and Panels, the process tags
of a logging tag become invalid in the following situations:
The tag has been logged more than once in Runtime Professional.
Several logging tags are linked to the same process tag.
Triggers
If you paste a logging tag with a cycle, the cycle will be included in the target HMI device.
In Runtime Professional, configure the log cycle of logging tags in the form "factor x cycle", for
example, twice an hour. The "Factor" property is not supported in Runtime Advanced and
Panels. The Factor property is therefore set to the default of "1" when copying from Runtime
Advanced and Panels to Runtime Professional. When copying from Runtime Professional to
Runtime Advanced and Panels, only the cycle can be seen in Runtime Advanced and Panels;
the factor is not taken into consideration. If you copy a cycle of "3 x 1h" from Runtime
Professional to Runtime Advanced and Panels, for example, this is set in Runtime Advanced
and Panels as "1h".
Copying logging tags from the "Tags" editor
When you copy a logging tag from the "Tags" editor in Runtime Professional into the "Historical
Data" editor in Runtime Advanced and Panels, the "Process tag" property is linked to an
existing tag with the same name. If there is no tag with the same name, the "Process tag"
property becomes invalid. The "Data log" property is linked to the selected data log.
If you copy a logging tag from the "Tags" editor in Runtime Professional to the "Tags" editor
of another HMI device, the "Data log" property will not be transferred.
Copying logging tags from the "Historical Data" editor
When you copy a logging tag from the "Historical Data" editor in Runtime Advanced and Panels
into the "Tags" editor in Runtime Professional, the "Data log" property will not be transferred.
When you copy a logging tag from the "Historical Data" editor into the "Logs" editor of another
HMI device, the "Process tag" property is linked to an existing tag with the same name. If there
is no tag with the same name, the "Process tag" property becomes invalid. The "Data log"
property is linked to the selected data log.
Logging tags used in compressed logging tags
When you copy a logging tag used in a compressed logging tag in Runtime Professional to
Runtime Advanced and Panels, the settings for the compressed logging tag are also copied
in the background. There may be performance problems if too many of these unnecessary
settings are copied to Runtime Advanced and Panels.
See also
Copying variables (Page 2156)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2167
Copying VB scripts
Object types, properties and methods in VB script
The objects, object types, properties and methods supported in Runtime Advanced and Panels
and Runtime Professional are listed in the VBS reference.
Pasting
You can copy VB scripts
using the shortcut menu or by drag & drop from the project tree
from the code of an open VB script to another open VB script.
Objects called in VB script
You copy a VB script. Objects and their properties which do not exist in or are not supported
by the target HMI device are called in the VB script. The syntax check reports an error. Correct
the invalid object references.
Variables called up in a VB script
The syntax check will report errors if tags are called in the copied VB script that do not exist
in the target HMI device or only exist with a different data type. Replace the invalid tags with
tags that exist in the target HMI device.
If you are planning to copy scripts into different Runtimes, use the same variables in the
Runtimes.
Copying recipes between Runtime Advanced and Panels and Runtime Professional
Recipe and recipe element
The recipe elements and recipe data records will also be copied if a recipe is copied.
NOTICE
Inconsistent data
Properties not supported by the HMI device, for example data type, will be formally copied
but will appear with an error flag.
Check the properties and reassign those flagged.
You can drag-and-drop a recipe element into the first empty line of the "Recipes Element"
editor of another HMI device. The recipe element is inserted into the other recipe. If the recipe
does not have the "Tags" communication type, the associated tag will be copied but it is
assigned an error flag.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2168 System Manual, 08/2011,
Points to note when copying from WinCC Runtime Advanced and Panels to WinCC Runtime
Professional
The properties below are preset as follows and may subsequently be edited:
"Tags" communication type
"Limited" size type
Number of data records
The storage location of the recipe is changed to "Database".
With a recipe element, the link will be copied but not the linked tag. You need to copy the tag
separately or create a new tag with the same name. The same applies to the text list.
NOTICE
Inconsistent data
Array tags are not supported in WinCC Runtime Professional. After copying the recipe, create
as many recipe elements and tags as there are array elements in the linked array tag. Link
the new recipe elements to the tags. Copy the values of the source recipe data records to
the target recipe data records.
Points to note when copying from WinCC Runtime Professional to WinCC Runtime Advanced and
Panels
The following properties will be changed but cannot be edited:
"Tags" communication type
"Limited" size type
Number of data records per HMI device
"File" storage location with default path
Recipe data record and recipe collection
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.
Features specific to WinCC Runtime Professional
You can drag-and-drop a recipe collection into the first empty line of the "Recipe Views" editor
of another device. The recipe collection will be copied but not the linked recipe elements and
their recipes.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2169
Copying cycles
Introduction
You can copy cycle in the "Cycles" editor and paste it in the "Cycles" editor of another Runtime.
Referenced cycles are also copied whenever tags, logging tags or tasks are copied. The cycles
are then displayed in the "Cycles" editor.
Supported properties
The date and time of the last change are updated during pasting.
Properties
The "Starting point" property is only supported in Runtime Professional.
Cycle units
Runtime Professional and Runtime Advanced and Panels support different cycle units.
Reports
Objects
Introduction
When you copy an object from a report and paste it into another report, the object is inserted
at the same position in the report.
Supported properties
The concepts of the "Recipe display" and "Alarm view" objects differ so greatly that they cannot
be copied and pasted between the various Runtimes.
Text and graphics lists
Text and graphics lists are automatically copied along with symbolic and graphic I/O fields and
are then displayed in the "Text and graphics lists" editor.
Copying objects from screens
You can copy objects supported in the report from a screen to a report. Unsupported settings
are replaced by supported settings. When you copy a copied object back into a screen, the
changed settings remain active.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2170 System Manual, 08/2011,
See also
Objects in reports (Page 2171)
Objects in screens (Page 2153)
Copying a report
Introduction
You can copy a report from the "Reports" folder and paste it into another "Reports" folder.
Watermarks
Watermarks are only supported in Runtime Professional. When you copy a report from
Runtime Professional to Runtime Advanced and Panels, the areas for the watermarks will no
longer be shown.
Print jobs
The print jobs in the "Reports" folder are only supported in Runtime Professional and cannot
be copied and pasted between Runtimes.
Objects in reports
Supported objects
The following table shows which objects are supported in which Runtime:
Basic object Runtime Advanced and Panels Runtime Professional
Line Yes Yes
Polyline Yes Yes
Ellipse Yes Yes
Circle Yes Yes
Ellipse segment No Yes
Circle segment No Yes
Elliptical arc No Yes
Circular arc No Yes
Rectangle Yes Yes
Polygon Yes Yes
Text field Yes Yes
I/O field Yes Yes
Symbolic I/O field Yes Yes
Date/time field Yes No
Graphic I/O field Yes Yes
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2171
Basic object Runtime Advanced and Panels Runtime Professional
Alarm view No Yes
Recipe view No Yes
Table view No Yes
f(t) trend view No Yes
f(x) trend view No Yes
Page number Yes Yes
Report name No Yes
Project name No Yes
Hardcopy No Yes
ODBC database field No Yes
ODBC database table No Yes
Alarm sequence report No Yes
CSV provider tables No Yes
CSV provider trends No Yes
Alarm report Yes No
Recipe report Yes No
Control data No Yes
Control hard copy No Yes
Control screen No Yes
Text and graphics lists
Differences between Runtime Advanced and Panels and Runtime Professional
Ranges in text lists
When specifying a range the following settings are supported in both Runtimes:
Individual value
Range
The following settings are supported in Runtime Professional:
To (<=)
From (>=)
Copying text lists and graphic lists
Introduction
You can copy a text or graphics list in the "Text and graphics lists" editor and paste it to the
same editor in another runtime. Text and graphics lists are also automatically copied along
with symbolic and graphic I/O fields and displayed in the "Text and graphics lists" editor.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2172 System Manual, 08/2011,
List entries
When a text or graphics list is copied, the corresponding list entries are included in copying.
You can also copy and paste the list entries individually.
User administration
Differences between Runtime Advanced and Panels and Runtime Professional
Users
Properties for dynamic logon and web client administration are only supported in Runtime
Professional.
User groups
The "DisplayName" and "Number" properties are only supported in Runtime Advanced and
Panels.
Properties for web client administration are only supported in Runtime Professional.
Copying users, user groups and authorizations
Copying and pasting
You can copy users, user groups and authorizations in the "User administration" editor.
When you copy a user, the corresponding user group is not copied.
When you copy a user group, the corresponding authorizations are not copied.
Default entries and system authorizations
The following users, user groups and authorizations are predefined. They cannot be deleted
and may only be edited to a limited extent:
predefined user "Administrator"
predefined groups "Administrator" and "Operators"
predefined authorizations, such as "Operate" and "Enable remote control"
You can copy the predefined entries and paste them into another Runtime. The entries copied
are pasted as user-defined entries and can then be edited.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2173
Scheduler
Copying scheduled tasks
Introduction
You can copy a scheduled task in the "Scheduler" editor and paste it to the "Scheduler" editor
of another device.
Task type
The "Print job" task type is supported in Runtime Professional only. Types that are not
supported in both Runtimes become invalid after they have been pasted.
See also
System functions (Page 2152)
Scheduler events (Page 2174)
Scheduler events
Events
The following table shows which events are supported in which Runtime:
Event Runtime Advanced and Panels Runtime Professional
Screen change Yes No
User change Yes No
Alarm buffer overflow Yes No
Runtime stop Yes Yes
When a dialog is opened Yes No
When a dialog is closed Yes No
Disabled Yes Yes
Once Yes Yes
250 milliseconds No Yes
500 milliseconds No Yes
1 second No Yes
2 seconds No Yes
5 seconds No Yes
10 seconds No Yes
1 minute Yes Yes
5 minutes No Yes
10 minutes No Yes
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2174 System Manual, 08/2011,
Event Runtime Advanced and Panels Runtime Professional
1 hour Yes Yes
Once daily Yes Yes
Once weekly Yes Yes
Once monthly Yes Yes
Once yearly Yes Yes
Tag triggers No Yes
9.11.8 Configuring system diagnostics
9.11.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 2176)
Enabling system diagnostics in the PLC (Page 2178)
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2175
9.11.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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2176 System Manual, 08/2011,
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2177
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 2175)
9.11.8.3 System diagnostics
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2178 System Manual, 08/2011,
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2179
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.
See also
System diagnostics basics (Page 2175)
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.
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2180 System Manual, 08/2011,
A screen is open.
A system diagnostics window has been created in the global screen.
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".
Visualizing processes (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2181
Result
The status diagnostics indicator has been added to the project and connected with the system
diagnostics view.
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2182 System Manual, 08/2011,
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2183
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
2184 System Manual, 08/2011,
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 (Professional)
9.11 Using global functions
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2185
9.12 Compiling and loading
9.12.1 Compiling, downloading and simulating projects
9.12.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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2186 System Manual, 08/2011,
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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2187
9.12.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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2188 System Manual, 08/2011,
9.12.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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2189
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 2210)
Generating a "Pack&Go" file (Page 2191)
Starting Runtime Advanced and Panels (Page 2197)
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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2190 System Manual, 08/2011,
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
Starting Runtime on the configuration PC (Page 2197)
Starting Runtime Advanced and Panels (Page 2197)
Starting Runtime Professional (Page 2221)
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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2191
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.
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.
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".
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2192 System Manual, 08/2011,
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.
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:
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2193
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2194 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2195
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2196 System Manual, 08/2011,
9.12.1.4 Starting Runtime
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.
Result
Runtime is started and the project is displayed on the configuration PC.
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".
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2197
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.
Result
Runtime is started on the HMI device.
See also
Starting and stopping the debugger (Page 1793)
9.12.1.5 Simulating projects
Simulation
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:
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2198 System Manual, 08/2011,
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
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2199
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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2200 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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2201
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.
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2202 System Manual, 08/2011,
Column Description
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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2203
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.
Working with the debugger
Debugging scripts
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:
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".
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2204 System Manual, 08/2011,
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.
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.
See also
Debugging (Page 1786)
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2205
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.
9.12.2 Compiling, downloading and simulating projects
9.12.2.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
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2206 System Manual, 08/2011,
The figure below illustrates the link between WinCC projects and Runtime projects using the
example of the "Compile and load" process:
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:
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2207
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.
See also
Generating a "Pack&Go" file (Page 2191)
Starting Runtime Advanced and Panels (Page 2197)
9.12.2.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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2208 System Manual, 08/2011,
Result
The configuration data of all selected HMI devices is compiled. Any errors that occur during
compilation are shown in the Inspector window.
9.12.2.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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2209
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.
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
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.
If the HMI device supports PROFINET, the name of the HMI device registered in the project
navigation is used as the device name for the PROFINET communication. The name is written
during download to the HMI device. If a device name for the PROFINET communication has
already been entered in the HMI device, it will be overwritten.
Please note the following when downloading a project to an HMI device:
You can download a project from the configuration PC to the HMI device if no project is
open or in Runtime on the HMI device.
If a project is open on the HMI device, you can only completely reload this particular project
from the configuration PC to the HMI device. Close the project open on the HMI device to
download a different project to the HMI device.
Example: The project "Mixing" is open on the HMI device but not in Runtime. If you change
the project, download the changes to the HMI device with "Software (all)". Close the project
"Mixing" on the HMI device to download the project "Bottling" to the HMI device, for example.
You can load certain changes to the configuration data without stopping Runtime (delta
loading) if a project is in Runtime on the HMI device. You will be notified if a change means
delta loading is no longer possible. If delta loading is no longer possible, you will only be
able to download the project to the HMI device using "Load (completely)". Runtime is
disabled, which may result in plant downtime.
You will have to exit Runtime and close the project on the HMI device to download another
project to the HMI device.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2210 System Manual, 08/2011,
Requirement
You have created an HMI device in the project.
The HMI device is connected to the configuration PC.
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.
3. If the "Extended loading" dialog opens:
Select the "destination path" for the compiled project on the HMI device.
The Windows user group "SIMATIC HMI" must have full access to this destination path.
Full access is usually set during installation of WinCC Runtime for the "WinCC Projects"
file. The location of this folder in the file system depends on the operating system of 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
Activating and deactivating projects on the WinCC server (Page 2537)
Overview of online delta transfers (Page 2217)
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2211
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2212 System Manual, 08/2011,
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.
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2213
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:
Auto-Hotspot
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2214 System Manual, 08/2011,
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 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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2215
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 (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2216 System Manual, 08/2011,
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.
Online delta transfer for Runtime Professional
Overview of online delta transfers
Online delta loading
WinCC lets you edit a project on the configuration PC while the same project is active in
Runtime. You can in most cases load the configuration changes to the HMI devices using
"Online delta loading" if you change the project on the configuration PC. Online delta loading
requires less time compared to the transfer of the entire project.
The "Load preview" dialog opens for online delta loading. In this dialog you specify whether
user administration or logs, which have been changed on the HMI device in the meantime, are
overwritten or retained during online delta loading.
NOTICE
Changes to the project made in the meantime on the HMI device, for example in the user
management or in the logs, are lost during the online delta loading.
Complete transfer
Fundamental changes to configuration data may prevent the online delta transfer. In this case,
a message informs you of the failure of the online delta loading after you initiated the transfer.
You then have to reload the entire project to the HMI device. You must explicitly confirm this
Runtime restart on the HMI device in the "Load" dialog. You can cancel loading at this point.
The following will happen if you start complete loading while the project on the configuration
PC is in Runtime on the HMI device:
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2217
Runtime is stopped
The entire project is downloaded to the HMI device
Runtime is restarted
Note that starting and stopping of Runtime can result in plant downtime.
Application scenarios
You will have to adapt your configuration in various different phases of your project, for
example, commissioning, operation and maintenance. You can then transfer these changes
to the HMI device online without having to exit Runtime.
Cases in which online delta loading is used include:
Continuous automation tasks:
All changes should be made online from a central configuration PC. This saves you having
to make changes to the configuration locally. You can also add, change and delete runtime
Runtime objects such as tags, alarms and logs without having to exit Runtime.
Testing changes in a protected environment:
You can perform the planned changes offline on the configuration PC before these are
downloaded to the HMI device. Project engineers can simulate the changes in a protected
environment before activating the delta data in the process. This allows you to identify and
clear configuration errors before they can cause any problems in the process or lead to a
plant shutdown.
See also
Starting Runtime on the configuration PC (Page 2197)
Use and limitations of online delta loading
Introduction
The online delta loading capability is lost in some configurations.
Files and elements
The table below shows for which actions the online delta transfer capability is retained and for
which actions it is not retained:
Element Create Delete Edit Remarks
Project name/properties of the
project
- - No -
HMI device Yes No No -
Properties of the HMI device - - No Edit:
Changes are only activated in Runtime by
deactivating the project and restarting
Runtime.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2218 System Manual, 08/2011,
Element Create Delete Edit Remarks
User cycle
(project properties)
No No No -
Connections
("HMI Tags" editor)
No No No -
Parameter of a connection
("HMI Tags" editor)
No No No -
Alarms - - - See the "Online configuration for alarms"
table below
Menus and toolbars No No No -
Online configuration for alarms
Element Attribute Create Delete Edit Remarks
- Alarm number
Alarm group
- - No -
- Alarm class Yes No Yes Inactive alarms are updated
immediately if you change the
alarm class without changing
mandatory acknowledgment.
If the mandatory
acknowledgment of a
currently active alarm and of
an unacknowledged alarm is
changed, the system
acknowledges the active
alarm.
An active alarm that is
changed to an alarm without
"deactivated" state will be
deactivated.
User-defined alarm group - Yes No Yes -
Limit values for analog
alarms
- No No No -
Alarm classes - Yes No Yes Edit:
Valid for most attributes.
Exceptions are listed
individually:
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2219
9.12.2.4 Starting Runtime
Starting Runtime on the configuration PC
Introduction
You can start your project in Runtime on the configuration PC while you are performing
configuration in WinCC. The following restrictions apply to online configuration:
The project cannot be compiled in the background while Runtime is running on the
configuration PC.
The delta data of the project is compiled automatically when you load the project to an HMI
device after having closed Runtime. You can also start compilation manually.
During startup of the project in Runtime, the project settings made in the "Runtime settings"
of the HMI device are activated.
If Runtime is running on the configuration PC, most changes are applied after compilation.
Certain changes require a restart of Runtime for their activation.
Changes to the screen that is currently open become visible after a screen change.
With some changes, the option to compile configuration changes to the active Runtime
is lost. The message that this option has been lost is only displayed when the project is
compiled.
Requirement
A project is open on the configuration PC.
Runtime is installed on the configuration PC.
Procedure
To start runtime on the configuration PC, follow these steps:
1. Select the desired HMI device with Runtime Professional in the project tree.
2. Select the "Online > Start Runtime" menu command.
3. To transfer configuration changes to the the active Runtime, select the "Compile >
Software" command from the shortcut menu of the HMI device.
Result
Runtime is started and the updated project displayed on the configuration PC.
See also
Use and limitations of online delta loading (Page 2218)
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2220 System Manual, 08/2011,
Starting Runtime Professional
Introduction
Runtime in started on a configuration PC with installed WinCC Runtime via the WinCC menu
bar. If only WinCC Runtime is installed on an HMI device, load the project to the HMI device.
Use the "WinCC StartTool" for starting the project.
Requirements
"WinCC Runtime" is installed on the HMI device.
Note
A least 100 MB free memory must be available on the storage medium before the Runtime
of a project can be started.
Starting Runtime at an Engineering Station
1. Open the desired project in WinCC.
2. Select the "Start Runtime" command from the "Online" menu.
Result
The project is compiled and activated. During activation, all Runtime services that you selected
in the Runtime settings of the HMI devices are started.
See also
Activating and deactivating projects on the WinCC server (Page 2537)
9.12.2.5 Simulating projects
Simulation
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:
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2221
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
Runtime Professional simulation
Introduction
Simulating Runtime Professional allows you to test the project with process link directly on the
configuration PC. You can also test the tags using the tag simulator.
Function
Both process values and alarms are saved to a simulation log. The data generated is deleted
from this log when you exit simulation mode.
The Runtime database is restored to the original state it had prior to simulation. Any changes
to project data made during Runtime will be lost. You use the tag simulator to simulate the
assignment of various values to the tags in your project.
Project logging and backup operations are continued during simulation.
WARNING
Possible damage to the plant
If you have changed tag values during the simulation with a PLC connection, unforeseen
plant states can result in irreparable damage to the plant. Therefore, limit manual value
manipulation to a minimum and select the test values carefully.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2222 System Manual, 08/2011,
Limitations
Client-server operation is not possible during simulation.
Simulating a project
Requirement
The project is open in the configuration PC.
Note
The tag values of faulty connections to the process cannot be simulated.
Procedure
Proceed as follows to simulate a project:
1. Disconnect the connection to the controller or switch the controller off if you do not want to
test the function of the entire process.
2. Select the menu command "Online > Simulate Runtime > With tag simulator".
Runtime starts and the simulator opens with all the configured tags.
3. Select the "New tag" command in the "Edit" menu to add a tag to the tag simulator.
4. Select the tag from the WinCC tag management.
5. In the tag simulator, select the required tag on the "Tags" tab to supply a tag with simulated
values.
6. Configure the simulation mode on the "Properties" tab:
Select the simulation mode.
Enter values for the simulation.
Click "Active" to include the tag in the simulation.
WARNING
Make sure once again that the configuration computer cannot pass any changed tags
to the PLC in the active process. If you have not switched the PLC off, the simulated
tag values will be passed to the PLC and the runtime process.
7. Click the "Start simulation" button on the "Properties" tab.
8. Observe the effect the simulation has on your project in Runtime.
9. Click on the "Stop simulation" button to stop the simulation.
10.To save the settings for the simulation, select the menu command "File > Save" and enter
a corresponding name.
The file is automatically given the *.sim extension.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2223
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 to be simulated must remain
unchanged in the project, otherwise the saved simulation data will no longer match your 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
You can start and stop the simulation for each individual tag to enable a bumpless transition
from the offline configuration to online configuration. Enable the "Active" check box in the
"Properties" tab for this purpose.
When a tag is enabled, the simulation values are calculated and transferred to the tag simulator.
Deleting a tag
To delete a tag from the tag simulator, follow these steps:
1. Select the tag name.
2. Select the menu command "Edit > Delete".
The tag is removed from the table.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2224 System Manual, 08/2011,
Result
Project simulation is started. Instead of the configured start screen, the simulation window the
screen you selected in the project navigation.
Working with the tag simulator
Simulation modes
The simulator has six different simulation modes. The configured tags are supplied with nearly
realistic values during the simulation depending on the simulation mode.
Simulation mode Description
Sinusoidal Changes the value of the tag to form a sinusoidal curve. The value is visualized
as a periodic, non-linear function.
Settings:
Amplitude
Offset (zero point for value range)
Period of oscillation
Oscillation For simulating jumps in a setpoint.
Settings:
Overshoot
Setpoint
Period of oscillation
Damping
Random Provides randomly generated values. The tag value is changed by means of a
random function.
Settings:
Minimum value
Maximum value
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.
Settings:
Start value
End value
Decrement Decreases 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.
Settings:
Start value
End value
Slider Sets a fixed value.
Settings:
Minimum
Maximum
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2225
Working with the debugger
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:
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".
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2226 System Manual, 08/2011,
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.
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.
9.12.3 Servicing the HMI device
9.12.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)
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2227
9.12.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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2228 System Manual, 08/2011,
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.
See also
Backing up and restoring data of the HMI device (Page 2229)
9.12.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
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2229
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.
See also
Backup of HMI data (Page 2228)
9.12.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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2230 System Manual, 08/2011,
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.
"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 2232)
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2231
9.12.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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2232 System Manual, 08/2011,
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
Updating the operating system (Page 2230)
Transferring license keys (Page 2233)
Managing licenses (Page 2234)
Overview for loading of projects (Page 2189)
Backing up and restoring data of the HMI device (Page 2229)
9.12.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 2234)
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2233
9.12.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".
5. Configure the "connection parameters" associated with the selected connection.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2234 System Manual, 08/2011,
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.
See also
Transferring license keys (Page 2233)
9.12.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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2235
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.
9.12.4 Reference
9.12.4.1 Error messages during loading 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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2236 System Manual, 08/2011,
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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2237
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.12.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.
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.
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
2238 System Manual, 08/2011,
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.
See also
Loading a project (Page 2190)
9.12.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".
Visualizing processes (Professional)
9.12 Compiling and loading
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2239
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 2190)
9.13 Operating in Runtime
9.13.1 Basics
9.13.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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2240 System Manual, 08/2011,
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-4 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.
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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2241
9.13.1.2 Behavior of the Runtime Advanced and Panels system
System functions and user-defined functions
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.
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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2242 System Manual, 08/2011,
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:
Early detection of danger / fault states
Increase of productivity
Enhancement of product quality
Optimization of maintenance cycles
Documentation of processes
Quality assurance
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2243
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
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".
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2244 System Manual, 08/2011,
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.
9.13.1.3 System characteristics of Runtime Professional
Reports
Overview
The protocol system in WinCC does not detect Runtime in the real sense of the meaning.
Reports and print jobs can be configured and executed at any time. Only print jobs which
represent log or process data are dependent on Runtime.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2245
Sequence
The protocol system is automatically started on every client during the startup routine. The
server operates as a protocol server, the clients as protocol clients. The clients log on to the
server during startup. The server provides current information about available print jobs and
their status to the clients. After having started a print, the client requests the corresponding
data from the server database. The print job is started locally. The protocol server receives
the current data concerning the print job status from the client and transfers the information to
the other clients.
Output
You have the following options for outputting a report in Runtime:
Using the "Print" button for the following objects:
f(x) trend view
f(t) trend view
Table view
Alarm view
Recipe view
Application window
The operator can initiate printing of a report selected in the application window in Runtime.
All queued print jobs are displayed in the application window.
Button
The operator can start printing the report using a configured button which is logically linked
to a corresponding script.
Alarms
Behavior
If alarms are displayed on a client, the clients will request the data from the alarm server. The
message server receives the configured data from the database.
Archive data and message lists can be displayed on every client. The data to be displayed
always comes from the message server. When new messages are received, the messages
are archived in the message server.
When an alarm is acknowledged at an HMI device, the acknowledgement is transferred to the
message server. The server enters the change of status in the archive and distributes the
notification to all participating clients. The same process applies to the locking of messages.
If a message server is not available in Runtime, the corresponding message appears in the
message window instead of the messages. When the server becomes available again,
messages are displayed in the message window again.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2246 System Manual, 08/2011,
Data logs
Behavior
If the data logging system is activated on an HMI device, the tag logging in Runtime operates
on the server as data log server and on the clients as data log client. Only the archive server
accesses the database and compiles and archives the process data. The clients receive
archive data from the archive server.
The log data is visualized in tabular or graphic format on all clients running tag logging in
Runtime. The data to be displayed always comes from the archive server. All operations on
the client are transmitted to the server and the result of the processing is transferred back to
the client.
Screens
Behavior
After a client has called a screen in Runtime, the "Graphic object in Runtime" function initially
searches for locally stored screens. If no screen with the corresponding name is found locally,
a search is made in the project folder on the server. A corresponding message is output if the
screen is unavailable.
If a screen selection requires data exchange with a different editor (alarms, custom C
functions), this exchange is always local. A picture can be opened and processed by several
operating stations in Runtime.
9.13.2 Commissioning projects
9.13.2.1 Commissioning projects for Runtime Advanced and Panels
Settings for Runtime Advanced and Panels
Settings in the Runtime software (Advanced)
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
full-screen mode, the project is zoomed to the full screen. There will be no window and operator
control elements for this view.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2247
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
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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2248 System Manual, 08/2011,
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 (Advanced)
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.
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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2249
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.
Starting Runtime on the Engineering Station
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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2250 System Manual, 08/2011,
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.
Result
Runtime is started and the project is displayed on the configuration PC.
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
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2251
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.
Result
Runtime is started on the HMI device.
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".
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2252 System Manual, 08/2011,
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.
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".
Backup and restoring projects
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
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2253
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.
Closing a project
Introduction
You define the steps in closing Runtime in the user program:
Procedure
Exit Runtime as follows:
1. When Runtime is running in window mode, you can close it by clicking the icon .
2. When Runtime is running in full-screen mode, you can close it by means of the program
switching function and the Task Manager.
3. When Runtime is running in full-screen mode and program switching is disabled for the
project, the closing sequence of Runtime must be configured separately. Actuate the
relevant button to close Runtime.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2254 System Manual, 08/2011,
9.13.2.2 Commissioning projects for Runtime Professional
Access rights within the operating system
Defining Access Rights in the Operating System
Introduction
Certain folders can be released for network access when working with WinCC. For security
reasons you should restrict access to these folders to specific users.
Access rights specified in WinCC
After its installation was completed, WinCC automatically sets up the following local groups in
the Windows users and groups management:
"SIMATIC HMI". These members may create local projects, and may process, start, and
access these projects remotely. The user who installs WinCC and the local administrator
are included in this group by default. Additional users must be defined by the administrator.
For additional information, refer to "Assigning users to the "SIMATIC HMI" user group".
"SIMATIC HMI CS". These members may configure only but may not make any changes
to runtime components directly. By default, this group is empty and reserved for later use.
"SIMATIC HMI Viewer". These members have read access only to configuration and
runtime data. This group is preferably used for Web publishing services accounts, e.g., IIS
(Internet Information Services) for operation of WinCC Web Navigator.
The "InstallationDirectory/WinCC/aplib" folder named "SCRIPTFCT" is released after
installation for the "SIMATIC HMI" user group. This folder contains central libraries for project
script functions.
Users of the "SIMATIC HMI" and "SIMATIC HMI CS" user group are granted access rights to
the project folder when you recreate a project. Following a manual copy, the administrator or
main user may have to open the project once to set the local authorizations properly. The
settings of the Auto-Hotspot released WinCC folders will not be changed afterwards. You may
manually change settings, if necessary.
Note
Configurators and users of runtime components must be registered not only in a "SIMATIC
HMI" group but also in a user group of the operating system. Users of the "SIMATIC HMI"
group are only granted access to the projects but not the operating system. In order to create
a project, the configurator must be at least the main user and a member of the "SIMATIC
HMI" group.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2255
Including users in the "SIMATIC HMI" user group
Introduction
Include those local users in the "SIMATIC HMI" group whose login permits access to WinCC.
You must first create local users to do so. Users of a domain may be directly included in the
user group "SIMATIC HMI".
Procedure
You add users to the "SIMATIC HMI" user group as follows:
1. Open the workstation administration under Windows.
2. Select the entry "Local Users and Groups > Users" in the navigation window .
All local users are displayed in the data window.
3. Open the "New User" dialog via the shortcut menu.
Create a user account with the same login for each user who has to access WinCC.
4. Select the entry "Local Users and Groups > Groups" in the navigation window".
All groups are displayed in the data window.
Select the "SIMATIC HMI" group.
5. Using the pop-up menu, open the "Add Member" dialog and include those users as
members of the "SIMATIC HMI" user group.
Result
The user has been added to the "SIMATIC HMI" user group. These changes become effective
after system restart.
Including domain-global user group in the "SIMATIC HMI" user group
Introduction
You can set up an additional domain-global user group for operation within a domain as
member of the "SIMATIC HMI" user group.
Requirement
The domain administrator creates a domain-global user group.
Within the domain, the domain administrator includes those users in the domain whose
login permits access to WinCC.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2256 System Manual, 08/2011,
Procedure
Set up the access rights of your operating system as follows:
1. Open the workstation administration under Windows.
2. In the navigation window, select the "Local Users and Groups > Users" entry. The data
window displays all local users.
3. In the pop-up menu, select the "New User" dialog. Create an user account with the same
login for the domain-global user group.
4. In the navigation window, select the "Local Users and Groups > Groups" entry. The data
window displays all groups. Select the group "SIMATIC HMI".
5. Using the pop-up menu, open the "Add Member" dialog and include domain-global user
group as members of the "SIMATIC HMI" user group.
Result
Access rights have been adapted. These changes become effective after system restart.
Sharing an existing project for access by the "SIMATIC HMI" user group
Introduction
Start by deleting the currently shared access to the project directory if the "SIMATIC HMI" user
group is to have access to an existing project. The project is then shared on opening.
Procedure
You grant the "SIMATIC HMI" user group access to the project as follows:
1. Open the workstation administration under Windows.
2. In the navigation window, select the entry "Shared Folders > Shares". The data window
displays all shared directories.
3. Select the respective project directory and remove the enable through the "Cancel Share"
pop-up menu.
4. If you now open the project in WinCC, the project directory is automatically shared by the
"SIMATIC HMI" user group and all members of the user group have access to the project
directory.
Note
Do not change the share name of the directory shared by WinCC.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2257
Adapting security policies in Windows
Introduction
Before you install WinCC, you must check the operating system settings. The system must
permit installation of unsigned drivers and files.
Procedure
You adapt the Windows security policies as follows:
1. In the Control Panel, open "Administrative Tools".
2. Double-click "Local Security Policy".
3. In the left pane, click "Local Policies".
4. In the right pane, double-click "Security Options".
5. Check the settings of the security policies below:
Windows 2000:
"Unsigned driver installation behavior" and "Unsigned files installation behavior (except
drivers)"
Windows XP / Windows Server 2003:
"Devices: Unsigned driver installation behavior"
For the policies, select either "Accept without warning" or "Warn, but permit installation".
Settings for Runtime Professional
Setting up the start sequence
Introduction
When you activate a project, additional program modules will be loaded to execute Runtime.
Select "Start sequence of WinCC Runtime" to specify the applications that will be started on
activation of a project. "Graphics in Runtime" is always started and is enabled by default.
Start only the applications required in Runtime to obtain a high performance level.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2258 System Manual, 08/2011,
Procedure
Set up the startup list as follows:
1. Open the "Runtime settings > Services" editor.
2. Enable the display of the online help in Runtime by activating "Enable help in Runtime".
3. Select the applications to load at the start of Runtime in the "Start sequence of WinCC
Runtime" area.
4. You can load additional tasks or applications at the start of Runtime by clicking in the table
row at "Additional tasks/application".
5. Enter a name for the additional task or application. Specify the working directory.
6. The project folder is used as working directory if you select the check box in the "Project
directory" column.
7. If you clear the check box in the "Project directory" column, use the "Find" button to specify
the folder in the "Working directory" column.
8. Specify any necessary parameters.
9. Specify the startup size of the task or application window in the "Window style" column,
e.g. minimized, maximized or standard size.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2259
Setting the language and fonts
Introduction
Define the language and corresponding fonts for Runtime activation. Define the order by which
languages are changed.
Requirement
The "Runtime Settings > Language & Font style" editor is open.
Procedure
Set the Runtime language as follows:
1. Select "Runtime language for single-language objects:" to set the substitute text language
for graphic objects.
2. Select the required languages.
The project is started in the language assigned the lowest number at the initial start of
Runtime on an HMI device.
3. Define the font for the Runtime language in the "Standard font" column.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2260 System Manual, 08/2011,
Activating the on-screen keyboard
Introduction
The on-screen keyboard is always displayed in Runtime after the operator has selected an
input field. The on-screen keyboard is automatically hidden again after input was completed.
Requirement
The "Runtime settings" editor is open.
Procedure
Proceed as follows to activate the on-screen keyboard:
1. Activate "Runtime settings > General > Use screen keyboard".
Enabling the zoom functions
Introduction
Zooming in Runtime is supported by three techniques:
Declutter
The layers and their embedded objects can be shown and hidden.
For additional information, refer to "Dynamic visualization of an object".
Extended Zooming
The Runtime view of the process screen can be enlarged or reduced using the scroll wheel
of the mouse. Hold the <CTRL> key down while turning the mouse wheel. If you turn the
mouse wheel away from the palm of your hand, you increase the zoom factor.
Panning
You can move a cutout of a screen within the document if this screen is assigned a specific
zoom factor that activates the scroll bars. A navigation crosshair appears upon clicking on
the mouse wheel. Moving the mouse pointer scrolls in the desired direction. The distance
between mouse pointer and navigation crosshair determines the scrolling speed. A second
click cancels panning.
Requirement
A driver for a Logitech mouse or Microsoft Intellimouse
The mouse wheel must be set to "Autoscroll" mode.
The "Runtime settings" editor is open.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2261
Enabling the zoom function
1. Click on "Screens".
2. Deactivate "Declutter" and "Extended zoom".
The functions are disabled if you activate "Declutter" and "Extended zoom".
Configuring Extended Zooming Picture-Specific
The "Extended Zoom" function can be enabled/disabled for specific screens. Make the
corresponding setting in the Inspector window of a screen under "Properties > Properties >
Miscellaneous".
Note
"Declutter" is now supported by the following objects:
"Slider"
"Clock"
"Gauge"
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2262 System Manual, 08/2011,
Defining hotkeys in the project
Introduction
You can define various hotkeys to operate the project. The hotkeys can be used as an
alternative to the mouse.
Windows keys
Define the key shortcuts to be supported in Runtime in the "Windows keys" dialog.
Action keys
"Logon" opens a window for user logon in Runtime.
"Logoff" opens a window for user logoff in Runtime.
"Hardcopy" opens a dialog for printing the screen in Runtime.
Requirement
The "Runtime settings" editor is open.
Procedure
Set up the hotkeys as follows:
1. Click on "Runtime settings > Keyboard".
2. Activate your hotkeys in the "Windows keys" dialog.
3. Select the action in the "Action keys" dialog.
4. Click the button in the selection list. The hotkeys dialog opens.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2263
5. Define your hotkeys.
6. Click the button to close the dialog.
Configuring hotkeys for operating and screen navigation
Introduction
Screens can also be operated if mouse control is not available. Define corresponding hotkeys
for the required operating functions. The operator calls the specific function by operating the
hotkey.
The most important hotkeys for operation without mouse in Runtime are defined in the
"Runtime Settings > Keyboard" editor.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2264 System Manual, 08/2011,
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2265
Procedure
Set up the operator hotkeys as follows:
1. Click in the input field of the selected function.
2. Click the button in the selection list. The hotkeys dialog opens.
3. Define your hotkeys.
4. Click the button to close the dialog.
You can also define single-key or a softkey <F1> - <F12> input instead of a hotkey.
Note
The function key F12 may not be configured as a systemwide hotkey.
Window control keys
These hotkey changes are activated after system restart.
Changing windows
This hotkey is used to navigate between multiple picture windows, which are configured in a
main picture. Whenever the hotkey is pressed, the next picture window will be activated for an
operation.
Note
The <DEL> and <HOME> keys cannot be used as hotkeys.
Screen navigation keys
The "Forward" and "Back" buttons of most Internet browsers allow the navigation between
Internet pages most recently called. A similar technique can be implemented in WinCC to
navigate between individual process pictures.
Configure corresponding hotkeys in the "Screen selection" dialog to facilitate screen navigation
in Runtime. Screens are logged to a temporary list after they were called. You can page through
this list using the "Forwards" and "Backwards" functions, for example, to recall the last five
screens. The valid maximum number of entries in this list is set in the field "Screen selection
memory." If this number is exceeded, the oldest entry is replaced after a new screen was called.
Note
The list logs up to 30 screen calls if the default is set for "Screen selection memory." As a
rule, it is not reasonable to substantially increase this value, since the switchover can only
be done in single steps. You can achieve more efficient screen navigation using picture
modules.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2266 System Manual, 08/2011,
Configuring cursor control
Introduction
You can configure object navigation without mouse using defined cursor control functions in
screens with tabular layout of the objects.
Define the cursor control hotkeys and the cursor characteristic in the "Runtime Settings >
Keyboard" editor.
Procedure
Set up the operator hotkeys as follows:
1. Click in the input field of the selected function.
2. Click the button in the selection list. The hotkeys dialog opens.
3. Define your hotkeys.
4. Click the button to close the dialog.
You can also define single-key or a softkey <F1> - <F12> input instead of a hotkey.
Activating 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.
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.
The time master can be a computer or an external clock, such as a SICLOCK. This master
transmits the time signal to the other components. Only one time master can be the active
clock in the network.
To prevent the failure of time synchronization, two components can be configured as the time
master. The redundant time master is a time slave as long as the active time master is
transmitting the time message frames.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2267
The time slaves receive the time signal transmitted by the time master via the bus and thus
synchronizes its time of day.
Time synchronization in Runtime
The time synchronization of the computer is entered in the start sequence of the computer for
the following events:
Running the OS project editor
After configuration of the time synchronization
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2268 System Manual, 08/2011,
Activating time synchronization
Proceed as follows to activate time synchronization:
1. Select the "Properties" command from the shortcut menu in the project navigation of
Runtime and then select "Time synchronization > General".
2. Under "Synchronization", activate "Activate time synchronization".
3. Under "Time settings", select the time source, for example, "No external time source".
4. Specify how often the time message frame should be transmitted by the time master.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2269
Synchronization via the terminal bus
Proceed as follows to synchronize the time via the terminal bus:
1. Select the "Properties" command from the shortcut menu in the project navigation of
Runtime and then select "Time synchronization > Terminal bus".
2. Under "Synchronization", activate the "Activate" check box.
3. If you also want to synchronize redundant components, activate the "Synchronize
redundant partners" check box.
4. Under "Server 1", select the server from which the HMI device should receive the time
message frame as the time slave.
5. Click "OK" or configure the synchronization via the system bus.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2270 System Manual, 08/2011,
Synchronization via the system bus
Proceed as follows to synchronize the time via the system bus:
1. Select the "Properties" command from the shortcut menu in the project navigation of
Runtime and then select "Time synchronization > System bus".
2. Under "Synchronization", activate the "Activate" check box.
3. Activate the "Show symbolic names of access points" check box. Note: If you configure
time synchronization from another computer, the installed access points are unknown. The
symbolic names are shown, however, and assigned to the physical names of the access
points when Runtime starts.
4. Under "Access point 1", select an access point and assign it a role as master or slave.
5. You also select a second access point under the following conditions:
If you want to use a redundant device.
If you want to synchronize two system buses via a "bridge".
If you want to synchronize two system buses as the master.
6. Also assign this access point a role as master or slave. The combination of these roles
defines the response as shown in the table below.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2271
Access point 1 Access point 2 Response
Slave Slave The device always functions as a time slave.
Master Master The device functions as a cooperative master at both access
points.
Master Slave The devices functions at access point 1 as the master and
transmits time message frames; at access point 2 the device
synchronizes with the time signals received there.
Slave Master The device functions at access point 2 as the master and
transmits time message frames; at access point 1, the device
synchronizes with the time signals received there.
Set time base
Setting the time base for the time of day
To set the time display on the HMI device, proceed as follows:
1. Select the "Properties > Time settings" command from the shortcut menu in the project
navigation.
2. Select one of the following options under "Time basis for time display in Runtime":
Time zone of server (migrated projects)
Local time
Coordinated Universal Time
3. Select one of the following options for the display format of the date and time:
"Configure individual components": If you want to display the date in the configured
format.
"Use ISO8610 format on all components": If you want to display the date in ISO8610
format on all components.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2272 System Manual, 08/2011,
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 (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2273
Starting Runtime on the Engineering Station
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.
Result
Runtime is started and the project is displayed on the configuration PC.
Starting Runtime Professional
Introduction
Runtime in started on a configuration PC with installed WinCC Runtime via the WinCC menu
bar. If only WinCC Runtime is installed on an HMI device, load the project to the HMI device.
Use the "WinCC StartTool" for starting the project.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2274 System Manual, 08/2011,
Requirements
"WinCC Runtime" is installed on the HMI device.
Note
A least 100 MB free memory must be available on the storage medium before the Runtime
of a project can be started.
Starting Runtime at an Engineering Station
1. Open the desired project in WinCC.
2. Select the "Start Runtime" command from the "Online" menu.
Result
The project is compiled and activated. During activation, all Runtime services that you selected
in the Runtime settings of the HMI devices are started.
Testing a project
Introduction
The following options of test WinCC projects are available:
Testing projects on the configuration computer.
Simulator
The Simulator is used to simulate 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".
Procedure
The following steps show the basic procedures for simulating a project offline without PLC
connection.
1. Start by creating a project as it is going to be run later with an interconnected PLC.
2. Save the project.
3. Select the HMI device in the project navigator.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2275
4. 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 "*.sim" contains all your settings for the simulation of tags and flags.
5. 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 "*.sim".
Closing a project
Introduction
You define the steps in closing Runtime in the user program:
Procedure
Exit Runtime as follows:
1. When Runtime is running in window mode, you can close it by clicking the icon .
2. When Runtime is running in full-screen mode, you can close it by means of the program
switching function and the Task Manager.
3. When Runtime is running in full-screen mode and program switching is disabled for the
project, the closing sequence of Runtime must be configured separately. Actuate the
relevant button to close Runtime.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2276 System Manual, 08/2011,
9.13.3 Operating projects
9.13.3.1 Basics
Overview
Operation options
The hardware determines how you can operate the HMI device:
Touch screen
The operating elements shown in the dialogs are touch-sensitive. Touch objects are
basically operated in the same way as mechanical keys. You activate operating elements
by touching them with your finger. To double-click them, touch an operating element twice
in succession.
HMI device keyboard
The operating elements shown in the screens are selected and operated using the keys of
the HMI device.
External keyboard
External mouse
Operation feedback from operating elements
The HMI device provides optical feedback as soon as it detects that an operating element has
been selected. The operating element receives the focus and is selected. This selection is
independent of any communication with the PLC. Therefore this selection does not indicate
whether the relevant action is actually executed or not.
The configuration engineer can also configure the selection of an operating element so that it
deviates from the standard.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2277
Optical feedback from operating elements
The type of optical feedback depends on the operating element:
Buttons
The HMI device outputs different views of the "Pressed" and "Unpressed" states, provided
the configuration engineer has configured a 3D effect:
"Pressed" state:
"Unpressed" state:
The configuration engineer determines the appearance of a selected field, for example, line
width and color for the focus.
Invisible buttons
By default, invisible buttons are not displayed as pressed when they are touched. No optical
operation feedback is provided in this case.
The configuration engineer may, however, configure invisible buttons so that their outline
appears as lines when touched. This outline remains visible until you select another
operating element.
I/O fields
When you select an I/O field, the content of the I/O field is displayed against a colored
background. With touch operation, a screen keyboard is displayed for the entering of values.
Direct keys
Introduction
Direct keys on the HMI device are used to set bits in the I/O area of a SIMATIC S7.
Direct keys enable operations with short reaction times that are, for example, a jog mode
requirement.
NOTICE
Direct keys are still active when the HMI device is in "offline" mode.
NOTICE
If you operate a function key with direct key functionality in a running project, the direct key
function is always executed, independent of the current screen contents.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2278 System Manual, 08/2011,
Note
You can only use direct keys when there is a connection via PROFIBUS DP or PROFINET IO.
Direct keys result in additional basic load on the HMI device.
Direct keys
The following objects can be configured as a direct key:
Buttons
Function keys
You can also define image numbers in the case of HMI devices with touch operation. In this
way, the project engineer can configure the direct keys on an image-specific basis.
For additional information on configuring direct keys, refer to "WinCC Communication."
Touch operation
Overview
Screen keyboard
When you touch an operating element requiring entry on the HMI device touch screen, a screen
keyboard appears. The screen keyboard is displayed in the following cases:
An I/O field is selected for input.
A password must be entered for accessing a password-protected function.
The screen keyboard is automatically hidden again when input is complete.
Based on the configuration of the operating element, the system displays different screen
keyboards for entering numerical or alphanumerical values.
Note
The screen keyboard display is independent of the configured project language.
General procedure
The operating elements of a screen are operated by touching the touch screen.
Proceed as follows:
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2279
1. Touch the desired operating element within the screen.
2. Depending on the operating element, perform further actions. Detailed descriptions can be
found under the respective operating element.
Examples:
I/O field: Enter numerical, alphanumeric or symbolic values in the I/O field.
Symbolic I/O field: Select an entry from the drop down list box.
Slider control: Move the slider control.
Procedure for input fields
Values are entered in the project input fields. Based on your configuration, the values are
saved to tags and transferred, for example, to the PLC.
Proceed as follows:
1. Touch the desired input field within the screen.
The screen keyboard opens.
Depending on your configuration, you can enter values in the input field in the following
manner:
Numerical values, for example decimal numbers, hexadecimal numbers, binary values
Alphanumerical values, for example digits and letters
Date/time
2. Enter the value.
3. Confirm your entry with or discard your entry using the button .
Entering and editing numerical values
Numerical screen keyboard
When you touch an operating element for numerical input on the HMI device touch screen,
the numerical screen keyboard appears. This is the case, for example, for an input field. The
screen keyboard is automatically hidden again when input is complete.
Figure 9-5 Numerical screen keyboard
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2280 System Manual, 08/2011,
Note
Opened screen keyboard
When the screen keyboard is open, PLC job 51, "Select Screen", has no effect.
Display formats for numerical values
You can enter values of the following format type in numerical input fields:
Decimal
Hexadecimal
Binary
Limit test of numerical values
Tags can be assigned limits. The current limits are indicated in the numerical screen keyboard.
If you enter a value that lies outside of this limit, it will not be accepted, for example, 80 with a
limit value of 78. In this case the HMI device will deliver a system event, if an alarm window is
configured. The original value is displayed again.
Decimal places for numerical values
The configuration engineer can define the number of decimal places for a numerical input field.
The number of decimal places is checked when you enter a value in this type of I/O field.
Decimal places in excess of the limit are ignored.
Empty decimal places are filled with "0".
Procedure
Numerical and hexadecimal values can be entered character-by-character via the buttons on
the numerical screen keyboard.
Proceed as follows:
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2281
1. Touch the desired operating element within the screen.
The numerical screen keyboard opens. The existing value is displayed in the screen
keyboard and is selected.
2. Enter the value.
You can only operate keys that are required for entering values. The keys with letters cannot
be used, for example, for entering a decimal value. Which keys can be operated can be
seen from the appearance of the keys.
You have the following options to enter a value:
The selected value is deleted when you enter the first character. Completely reenter the
value.
Use the and keys to move the cursor within the current value. You can
now edit the characters of the current value or add characters.
Use the key to delete the next character to the left of the cursor. If the value is
selected, use this key to delete the selected part of the value.
Change the sign of the value using the key.
Use the key to display the tooltip of the I/O field.
This key is only enabled if a tooltip was configured for the input object or for the current
screen.
3. Use the key to confirm your entry or cancel it with . Either action closes
the screen keyboard.
Result
You have changed the numerical value or entered a new one.
Entering and editing alphanumerical values
Alphanumerical screen keyboard
When you touch an operating element for numerical input on the HMI device touch screen,
the alphanumerical screen keyboard appears. This is the case, for example, for an input field.
The screen keyboard is automatically hidden again when input is complete.
Figure 9-6 Alphanumerical screen keyboard, normal level
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2282 System Manual, 08/2011,
Note
Opened screen keyboard
When the screen keyboard is open, PLC job 51, "Select Screen", has no effect.
Language change
Language change in the project has no influence on the alphanumerical screen keyboard.
The entry of Cyrillic or Asian characters is therefore not possible.
Keyboard levels
The alphanumerical screen keyboard has various levels.
Normal level
Shift level
The key labels change when you change levels with the key.
Procedure
Alphanumerical values can be entered character-by-character via the buttons on the
alphanumerical screen keyboard.
Proceed as follows:
1. Touch the desired operating element within the screen.
The alphanumerical screen keyboard opens. The existing value is displayed in the screen
keyboard and is selected.
2. Enter the value.
You have the following options to enter a value:
The selected value is deleted when you enter the first character. Completely reenter the
value.
Use the and keys to move the cursor within the current value. You can
now edit the characters of the current value or add characters.
Use the key to delete the next character to the left of the cursor. If the value is
selected, use this key to delete the selected part of the value.
Use the key to toggle between keyboard levels of the screen keyboard. On
switchover, the key assignment of the screen keyboard changes.
Use the key to display the tooltip of the I/O field.
This key is only enabled if a tooltip was configured for the input object or for the current
screen.
3. Use the key to confirm your entry or cancel it with . Either action closes
the screen keyboard.
Result
You have changed the alphanumeric value or entered a new one.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2283
Display tooltip
Purpose
The configuration engineer uses tooltips to provide additional information and operating
instructions. The configuration engineer can configure tooltips for screens and operating
elements.
The tooltip of an I/O field may, for example, contain information about the value to be entered.
Figure 9-7 Tooltip for an I/O field, example
Opening tooltips for operating elements
1. Touch the required operating element.
The screen keyboard opens. The representation of the key indicates whether a
tooltip was configured for the operating element or for the current screen.
2. Touch the key of the on-screen keyboard.
The tooltip for the operating element is displayed. If there is no tooltip for the selected screen
object, the tooltip for the current screen is displayed if it has been configured.
You can scroll through the contents of long tooltips using the and buttons.
Note
Switching between displayed tooltips
The configuration engineer can configure a tooltip for an I/O field and the associated
screen. You can switch between two tooltips by touching the tooltip window.
3. Close the displayed tooltip by pressing .
Alternative procedure
Depending on your configuration, tooltips can also be called via a configured operating
element.
Additional information on this topic may be available in your plant documentation.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2284 System Manual, 08/2011,
Key operation
Control keys
Introduction
The following tables list the control keys available to operate the project. For detailed
information, refer to the description of the individual operating elements.
Note
The availability of system keys is determined by the HMI device used.
Selecting operating elements
Key Function Description
+
Tabulator Selects the next or previous operating element
based on the configured tab sequence.
Cursor keys Selects the next operating element on the left, right,
above or below the current screen object.
Navigates in the operating element.
Operating operating elements
Key Function Description
+
+
+
+
Positioning cursor Positions the cursor within an operating element, for
example, in an I/O field.
Scrolling back Scrolls the list back by one page.
+ Scroll to start Scrolls to the start page of a list.
Scrolling up Scrolls the list up by one page.
+ Scroll to end Scrolls to the end of a list.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2285
Key Function Description
ENTER key Controls buttons.
Applies and ends an entry.
Opens a selection list.
Toggles between character mode and standard
mode within an input field.
A single character is selected in character mode.
In this mode, you can scroll within the character
set using the cursor keys.
Cancel Deletes the input characters of a value and
restores the original value.
Closes the active dialog.
Delete characters Deletes the next character to the right of the current
cursor position.
Delete characters Deletes the character to the left of the current cursor
position.
+ Open selection list Opens a selection list.
+ Accept value Accepts the value selected in the selection list
without closing the list.
Enter hotkey
Key Function Purpose
Toggle (numbers/letters) Toggles the assignment from numbers to letters.
No LED is lit:
The number assignment is enabled. Pressing
the key once switches to letter assignment.
An LED is lit:
The left or right letter assignment is enabled.
Each time the key is pressed, the system toggles
between the left letter assignment, the right letter
assignment and the number assignment.
Shift
(upper/lower case)
Use in hotkeys, for example, for switching to
uppercase letters.
Toggle to additional keyboard
layout
Some of the keys contain a blue special character
on their bottom left corner, for example, the "%"
character. To input these characters, press the
relevant key in combination with the special
character key shown on the left.
General control function Used in hotkeys, for example, for navigating trend
views.
General control function Used in hotkeys, for example, for the "Status/Force"
screen object.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2286 System Manual, 08/2011,
Acknowledge alarms
Key Function Purpose
Acknowledge Acknowledges the currently displayed error alarm
or all alarms of an alarm group (group
acknowledgment).
The LED is lit as long as an unacknowledged alarm
is active.
Displaying infotext
Key Function Description
Display tooltip Opens the configured tooltip for the selected object,
for example, alarm or I/O field. The LED is lit if a
tooltip is available for the selected object.
Function keys
Function keys
Function key assignment is defined during configuration. The configuration engineer can
assign function keys globally and locally.
Function keys with global function assignment
A globally assigned function key always triggers the same action on the HMI device or in the
PLC irrespective of the screen displayed. Such an action could be, for example, the activation
of a screen or the closure of an alarm window.
Function keys with local function assignment
A function key with local function assignment is screen-specific and is therefore only effective
within the active screen.
The function assigned locally to a function key can vary from screen to screen.
The function key of a screen can be assigned one function only, either a global or local one.
The local assignment function takes priority over the global setting.
The configuration engineer can assign function keys in such a way that you can operate
operating elements with function keys, for example, the alarm view, trend view, recipe view or
status / force.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2287
General procedures
Introduction
The control keys and function keys of the HMI device are available for key operation.
General procedure
The operating elements of a screen are operated using the control keys of the HMI device.
Proceed as follows:
1. Continue pressing the key or the cursor keys until the required operating element is
selected in the screen.
2. Depending on the operating element, perform further actions. Detailed descriptions can be
found under the respective operating element.
Examples:
I/O field: Enter numerical, alphanumeric or symbolic values in the I/O field.
Slider control: Move the slider control.
3. Confirm the your entry with or cancel it with .
Entering and editing numerical values
Display formats for numerical values
You can enter values of the following format type in numerical input fields:
Decimal
Hexadecimal
Binary
Limit test of numerical values
Tags can be assigned limits. If you enter a value that lies outside of this limit, it will not be
accepted, for example, 80 with a limit value of 78. In this case the HMI device will deliver a
system event, if an alarm window is configured. The original value is displayed again.
Procedure
Numerical and hexadecimal values can be entered in character mode using the system keys.
Proceed as follows:
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2288 System Manual, 08/2011,
1. Select the input field within the screen using the key.
The existing value is selected in the input field.
2. Enter the value using the numerical keypad.
You have the following options to enter a value:
The existing value is deleted when you enter the first character. Completely reenter the
value.
Press and a cursor key simultaneously. This step cancels the field content selection.
Move the cursor in the existing value. You can now edit the characters of the current
value or add characters.
The key deletes the next character to the right of the cursor. Use the key to
delete the next character to the left of the cursor.
To enter the hexadecimal characters "A" to "F", switch the numerical keypad to alphabet
mode using the key.
The lit LED of the key indicates that a tooltip is available for the selected object or
the active screen.
Use the key to view the tooltip for the operating element or active screen.
3. Confirm your entry with the key.
Result
You have changed the numerical value or entered a new one.
Entering and editing alphanumerical values
Procedure
Alphanumerical values can be entered in character mode using the system keys.
Proceed as follows:
1. Select the input field within the screen using the key.
The existing value is selected in the input field.
2. Enter the value using the system keys.
You have the following options to enter a value:
The existing value is deleted when you enter the first character. Completely reenter the
value.
Press and a cursor key simultaneously. This step cancels the field content selection.
Move the cursor in the existing value. You can now edit the characters of the current
value or add characters.
The key deletes the next character to the right of the cursor. Use the key to
delete the next character to the left of the cursor.
Switch the numerical keypad to alphabet mode using the key to enter letters.
The lit LED of the key indicates that a tooltip is available for the selected object or
the active screen.
Use the key to view the tooltip for the operating element or active screen.
3. Confirm your entry with the key.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2289
Result
You have changed the alphanumeric value or entered a new one.
Enter characters using the alphanumeric keyboard
Using the same keys of the alphanumeric keyboard you can enter up to six different characters.
The entry result depends on the combination of the keys pressed.
The values "5", "M", "m", "N", "n" and "%" are entered using the same key of the keyboard.
Use the keys , and to select the key mode.
The following table shows the entry options using the key .
Key Key Key Result
No LED is lit. Not relevant Not pressed 5
Left LED is illuminated. Not pressed Not pressed m
Left LED is illuminated. Pressed Not pressed M
Right LED is illuminated. Not pressed Not pressed n
Right LED is illuminated. Pressed Not pressed N
Not relevant Not relevant Pressed %
Display tooltip
Use
The configuration engineer uses tooltips to provide additional information and operating
instructions. The configuration engineer can configure tooltips for screens and operating
elements.
The tooltip of an I/O field may, for example, contain information about the value to be entered.
Figure 9-8 Tooltip for an I/O field, example
The lit LED of the key indicates that a tooltip was configured for the selected screen object
or for the active screen.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2290 System Manual, 08/2011,
Procedure
Proceed as follows:
1. Press the key.
The tooltip for the selected screen object is displayed. If there is no tooltip for the selected
screen object, the tooltip for the current screen is displayed if it has been configured.
You can scroll the contents of longer tooltips using the cursor keys and .
Note
Switching between displayed infotext
The configuration engineer can configure a tooltip for an I/O field and the associated
screen. You can switch between two tooltips by pressing the key.
2. Close the tooltip by pressing the key.
Alternative procedure
Depending on your configuration, tooltips can also be opened with a function key or via an
existing operating element.
Additional information on this topic may be available in your plant documentation.
Mouse and keyboard operation
Operation with the keyboard
The navigation options listed in the table can be used for keyboard operations in a screen.
Navigation PC SIMATIC Panel PC
Next field right/left <Shift+Right> / <Shift+Left> <Right> / <Left>
Next field up/down <Shift+Down> / <Shift+Up> <Down> / <Up>
To the right/left in the field <Right> / <Left> <Shift+Right> / <Shift+Left>
The other keys have identical functions on the PC and the SIMATIC Panel PC:
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2291
Key Function
<Enter> Applies a value (e.g. in unmarked input fields) or opens a
selection list.
If the I/O field is marked (highlighted in color),
WinCC Runtime will switch to the special editing mode. Only
one character at any time is marked in the field.
Use the cursor keys <Up>/<Down> to scroll through a
character table.
Use the cursor keys Right/Left to move the cursor to the next
or previous entry position.
Press <Enter> or <Esc> to exit from the entry mode. The
characters entered up to this point will be either applied or
discarded.
<Esc> Interrupts the input.
<Tab> Selects the next available screen object in the configured tab
sequence.
<Shift+Tab> Selects the previously available screen object in the
configured tab sequence.
<F1> -... <F12>,
<Shift+F1>, ..., <Shift+F12>
On the PC: Triggers a function, e.g. screen selection.
<F1>, ... or <S1>, ... or <K1>, ... On the SIMATIC Panel PC: triggers a global or local function.
CAUTION
If you press a function key after a screen change, the associated function in the new screen
may be triggered before the new screen is fully displayed.
Controlling Windows with the keyboard
You may also use the keyboard to control the operating system of your HMI device. See your
Windows manual for detailed information. The most important key combinations for SIMATIC
Panel PCs are listed in the following table.
Navigation HMI device
Open start menu <Ctrl+Esc>
Show the shortcut menu of the selected element <Shift+F10>
Select all <Ctrl+A>
Display properties of the selected element <Ctrl+Enter>
Explorer:
Change folder <F4>
Change display areas <F6>
Enable menu bar <F10>
Dialogs:
Go to next field <Tab>
Back to previous field <Shift+Tab>
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2292 System Manual, 08/2011,
Navigation HMI device
Open next tab <Ctrl+Tab>
Open previous tab <Ctrl+Shift+Tab>
Operation with the mouse
A lightning symbol attached to the mouse pointer indicates that the screen object, for example
a switch, may be operated with the mouse.
Note
If a screen object is covered by another, e.g. a button from a rectangle with a transparent fill,
it is not possible to operate with the mouse in runtime.
The screen object can be operated with the keyboard.
9.13.3.2 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 (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2293
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.13.3.3 Project security
Overview
Design of the security system
The configuration engineer can protect the operation of a project by implementing a security
system.
The security system is based on authorizations, user groups and users.
If you use an operator control with access protection, the HMI device first requests that you
log on. A logon screen is displayed in which you enter your user name and password. After
logging on, you can operate the operator controls for which you have the necessary
authorizations.
The logon dialog can be set up by the configuration engineer via an individual operator control.
In the same way, the configuration engineer can set up an operator control to log off. After
logging off, objects assigned access protection can no longer be operated; to do so, log on
again.
User groups and authorizations
Project-specific user groups are created by the configuration engineer. The "Administrators"
and "Users" groups are included in all projects by default. User groups are assigned
authorizations. Authorization required for an operation is specifically defined for each individual
object and function in the project.
Users and passwords
Each user is assigned to exactly one user group.
The following people are allowed to create users and assign them passwords:
The configuration engineer during configuration
The administrator on the HMI device
A user with user administration authorization on the HMI device
Irrespective of the user group, each user is allowed to change his own password.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2294 System Manual, 08/2011,
Logoff times
A logoff time is specified in the system for each user. If the time between any two user actions,
such as entering a value or changing screens, exceeds this logoff time, the user is automatically
logged off. The user must then log on again to continue to operate objects assigned access
protection.
Backup and restore
The user data is encrypted and saved on the HMI device to protect it from loss due to power
failure.
The users, passwords, group assignments and logoff times set up on the HMI device can be
backed up and restored. This prevents you having to enter all of the data again on another
HMI device.
NOTICE
The currently valid user data is overwritten in the following cases:
Depending on settings for a new download of the project.
Upon restore of a backed-up project
Upon import of the user administration via an operator control. The newly downloaded or
restored user data and passwords take effect immediately.
Displaying users
User view
Use
The user view is used by the administrator to manage user accounts, group assignments and
user passwords.
Users can change their passwords and logoff times.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2295
Layout
The user view contains four columns for the user, password, group and logoff time. The
passwords are encrypted by means of asterisks.
All users on the HMI device are displayed in the User view to the administrator or to a user
with administrator authorizations.
When user administration authorization is lacking, only the personal user entry is displayed.
Operation
Depending on the configuration you can:
Manage users, e.g. create, delete.
Change existing user data.
Export or import user data.
Note
On an HMI device the number is limited to 100 users and one PLC user. This restriction
does not apply to PCs. On a PC, the maximum number of users is restricted by the physical
memory.
Runtime behavior
The user view on the HMI devices OP 73, OP 77A and TP 177A also displays the "PLC User"
with administrator privileges who is logged on in Runtime.
Changing existing user data
The following options are available for the changes that can be made:
The administrator or a user with user administration authorization can change the data for
all users on the HMI device system in the user view.
User name
Group assignment
Password
Logoff times
A user without user administration authorization can only change their own user data:
Password
Logoff time
Note
If you enter the value "0" in the logoff time, user is not logged off automatically.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2296 System Manual, 08/2011,
Export or import user data
A user view contains all users, passwords, group assignments and logoff times set up on the
HMI device. To not have to enter all data again on another HMI device, you can export the
user view and then import it to another device. But you can only do this if this function has
been configured.
Note
Do not export the password list immediately after changing it. Exit the "User view" object after
making changes and wait until the changes have been written to the internal Flash memory
before performing the export.
NOTICE
The currently valid user data are overwritten during an import. The imported user data and
passwords are valid immediately.
Simple user view
Use
On HMI devices with a small display, the simple user view is used to display users on the HMI
device.
Note
The "Simple user view" object cannot be operated dynamically with a script.
Layout
The appearance depends on the authorizations.
All users on the HMI device are displayed in the User view to the administrator or to a user
with administrator authorizations.
When user administration authorization is lacking, only the personal user entry is displayed.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2297
Operation
Depending on the configuration you can:
Manage users, e.g. create, delete.
Change existing user data.
Export or import user data.
Note
On an HMI device the number is limited to 100 users and one PLC user. This restriction
does not apply to PCs. On a PC, the maximum number of users is restricted by the physical
memory.
User login
Touch and key operation
Logon dialog
Use the logon dialog to log on to the security system of the HMI device. Enter your user name
and password in the logon dialog.
The logon dialog opens in the following cases:
You use an operator control with access protection.
You press an operator control that was configured for displaying the logon dialog.
You enable the "<ENTER>" entry in the simple user view.
You enable a blank entry in the extended user view.
The logon dialog will be automatically displayed when the project is started, depending on
the configuration.
Requirement
The logon dialog is open.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2298 System Manual, 08/2011,
Procedure for touch operation
Proceed as follows:
1. Enter the user name and password.
Touch the corresponding input field. The alphanumerical screen keyboard is displayed.
2. Select "OK" to confirm logon.
Procedure for key operation
Proceed as follows:
1. Select the "User" input field within the logon dialog by pressing the key.
2. Enter the user name using the system keys.
Switch the numerical keypad to alphabet mode using the key to enter letters.
3. Use the key to select the "Password" input field.
4. Enter the password using the system keys.
5. Confirm your entries with "OK".
Note
The user name is not case sensitive.
The password is case sensitive.
Result
After successful logon to the security system, you can execute functions on the HMI device
which are access protected and for which you have authorization.
An alarm is output if an incorrect password has been entered and if an alarm view was
configured.
Mouse and keyboard operation
Requirement
The logon dialog is open.
Procedure for mouse operation
Proceed as follows:
1. Click in the input field. The alphanumerical on-screen keyboard is displayed.
2. Enter the user name and the password.
3. Click "OK" in the logon dialog.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2299
Procedure for keyboard operation
Proceed as follows:
1. Press the <Tab> key until the "Users" input field is selected.
2. Enter the user name and the password.
3. Confirm your entries with "ENTER."
Note
The user name is not case-sensitive.
The password is case-sensitive.
Result
After successful logon to the security system, you can execute functions on the HMI device
which are access protected and for which you have authorization.
An alarm is output if an incorrect password has been entered and if an alarm view was
configured.
User logoff
Requirement
You have logged into the security system of the HMI device.
Procedure
You have the following options for logging off:
You press an operator control that was configured for logoff.
You will be logged off automatically if you are not operating the project and if the logoff time
has been exceeded.
You will also be automatically logged off if you enter an incorrect password.
Result
You are no longer logged into the project. In order to use an operator control with access
protection, you first have to log on again.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2300 System Manual, 08/2011,
Creating users
Key operation
Requirement
The user view is open.
You are either authorized for user administration or you are an administrator.
A user group has been created.
NOTICE
Runtime users must be assigned to a user group. The user group is set up in the
Engineering System. The user group name is language-specific.
NOTICE
The following characters cannot be used in passwords:
Blanks
Special characters * ? . % / \ ' "
Creating users in the simple user view
Proceed as follows:
1. Select the user view using the key
TAB
or using the cursor keys.
2. Select the entry "<New user>" in the user view with the cursor keys and confirm with
ENTER
.
The following dialog opens:
3. Enter the desired user name using the system keys.
4. Select the next text box with the
TAB
key and enter a password using the system keys.
5. Confirm your entries with "OK."
The following dialog opens:
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2301
6. Select the "Group" selection box with
TAB
.
7. Assign the user to a group.
Select
ENTER
to open the drop down list box. The drop down list box opens.
Select the required entry using or .
Confirm your entry by pressing the key
ENTER
.
8. Select the text box "Logoff time" with
TAB
.
9. Enter the desired logoff time using the system keys.
Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic logoff."
10.Confirm your entries with "OK."
Creating users in the advanced user view
Proceed as follows:
1. Select the user view with the
TAB
key via the configured tab order.
2. Select a blank line with the or keys.
3. Select the desired field in the blank line of the user view with the or keys.
4. Confirm your entry by pressing the key
ENTER
.
5. Enter the desired user data:
Enter the data using the system keyboard. To enter letters, switch the numerical keypad
to letter assignment using the key
A-Z
.
Assign the user to one of the groups from the drop down list box. Open the drop down
list box with the
ENTER
key and select the desired entry with the or keys.
Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic
logoff."
6. Confirm your entry by pressing the key
ENTER
.
Result
The new user is created.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2302 System Manual, 08/2011,
Touch operation
Requirement
The user view is open.
You are either authorized for user administration or you are an administrator.
A user group has been created.
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.
NOTICE
The following characters cannot be used in passwords:
Blanks
Special characters * ? . % / \ ' "
Creating users in the simple user view
Proceed as follows:
1. Click the "<New user>" entry in the user view. A dialog opens.
2. Enter the desired user name and password.
Touch the corresponding text box. The alphanumerical on-screen keyboard is displayed.
3. Click on the text box of the group. A dialog opens.
4. Assign the user to a group. Select and to scroll the selection list.
5. Touch the required entry in the drop down list box.
The selected entry is accepted as input.
6. Touch the text box "Logoff time". The on-screen keyboard is displayed.
7. Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic logoff."
8. Confirm your entries with "OK."
Result
The new user is created.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2303
Operation with the mouse
Requirement
The user view is open.
You are either authorized for user administration or you are an administrator.
A user group has been created.
NOTICE
Runtime users must be assigned to a user group. The user group is set up in the
Engineering System. The user group name is language-specific.
NOTICE
The following characters cannot be used in passwords:
Blanks
Special characters * ? . % / \ ' "
Creating users in the simple user view
Proceed as follows:
1. Click the "<New User>" entry in the user view.
The following dialog opens:
2. Enter the desired user name and password.
Click in the corresponding input field. The alphanumerical on-screen keyboard is displayed.
3. Click "OK".
The following dialog opens:
4. Assign the user to a group.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2304 System Manual, 08/2011,
5. Click the required entry in the selection list.
The selected entry is accepted as input.
6. Click in the "Logoff time" input field. The on-screen keyboard is displayed.
7. Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic logoff."
8. Confirm your entries with "OK."
Creating users in the advanced user view
Proceed as follows:
1. Double-click the desired field in the blank line of the user view.
The corresponding on-screen keyboard is displayed.
2. Enter the respective user data in the field:
Assign the user to one of the groups from the drop down list box.
Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic
logoff."
Result
The new user is created.
Operation with the keyboard
Requirement
The user view is open.
You are either authorized for user administration or you are an administrator.
A user group has been created.
NOTICE
Runtime users must be assigned to a user group. The user group is set up in the
Engineering System. The user group name is language-specific.
NOTICE
The following characters cannot be used in passwords:
Blanks
Special characters * ? . % / \ ' "
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2305
Creating users in the simple user view
Proceed as follows:
1. Press the <TAB> key until the user view is selected.
2. Select the "<New user>" entry in the user view using the cursor keys and confirm it
with <ENTER>.
The following dialog opens:
3. Enter the user name.
4. Press the <Tab> key to move to the next input field and enter a password.
5. Confirm your entries with <ENTER>.
The following dialog opens:
6. Select the "Group" selection list using the <TAB> key.
7. Assign the user to a group.
Press <ENTER> to open the selection list. The drop down list box opens.
Select the entry. Use the <Home>,<End>,<Up> and <Down> keys accordingly.
Confirm the selection with <ENTER>.
8. Change to the "Logoff time" input field using the <TAB> key.
9. Enter the desired logoff time.
Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic logoff."
10.Confirm your entries with <ENTER>.
Creating users in the advanced user view
Proceed as follows:
1. Press the <TAB> key until the user view is selected.
2. Select an empty line in the user view using the cursor keys.
3. Select the desired field in the empty line of the user view. Use the <Up> and <Down> keys
accordingly.
4. Confirm the selection with <ENTER>.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2306 System Manual, 08/2011,
5. Enter the desired user data:
Enter the user name and the password.
Assign the user to one of the groups from the drop down list box. Open the selection
list by pressing <ENTER> and then select the entry using the <Up> and <Down> cursor
keys.
Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic
logoff."
6. Confirm your entries with <ENTER>.
Result
The new user is created.
Changing user data
Touch operation
Requirement
The user view is open.
Your authorization level determines the data you can change:
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2307
You are an administrator or a user with user administration authorization. In these cases
you are allowed to change the data for all the users on the HMI device in the user view:
User name
Group assignment
Password
Logoff time
You are a user without user management authorization. In this case you are only allowed
to change your personal user data:
Password
Logoff time, if configured
Note
You can only change the logoff time and password for the "Admin" user.
You can only change the logoff time for the "PLC_User". This user is used for logging
on via the PLC.
NOTICE
Changes in the user view are effective immediately in Runtime. Changes in Runtime
are not updated in the Engineering System.
When the user management is downloaded to the HMI device, all changes in the user
view are overwritten.
Changing user data in the simple user view
Proceed as follows:
1. In the user view, touch the user whose user data you want to change.
2. When entering the data, use exactly the same procedure as for creating a user.
Changing user data in the advanced user view
Proceed as follows:
1. In the user view, touch the user whose user data you want to change.
2. When entering the data, use exactly the same procedure as for creating a user.
Result
User data have been changed.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2308 System Manual, 08/2011,
Key operation
Requirement
The user view is open.
Your authorization level determines the data you can edit:
You are an administrator or a user with user administration authorization. In these cases
you are allowed to change the data for all the users on the HMI device in the user view:
User name
Group assignment
Password
Logoff time
You are a user without user administration authorization. In this case you are only allowed
to change your personal user data:
Password
Logoff time, if configured
Note
You can only change the logoff time and password for the "Admin" user.
You can only change the logoff time for the "PLC_User". This user is used for logging
on via the PLC.
NOTICE
Changes in the user view are effective immediately in Runtime. Changes in Runtime
are not updated in the Engineering System.
When the user management is downloaded to the HMI device, all changes in the user
view are overwritten.
Changing user data in the simple user view
Proceed as follows:
1. Confirm your entry by pressing the key
TAB
.
2. In the user view, use the cursor keys to select the user whose user data you want to change.
Confirm your entry by pressing the key
ENTER
.
3. When entering the data, use exactly the same procedure as for creating a user.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2309
Changing user data in the advanced user view
Proceed as follows:
1. Confirm your entry by pressing the key
TAB
.
2. Use the cursor keys to select the field in which you want to change data. Confirm your entry
by pressing the key
ENTER
.
3. When entering the data, use exactly the same procedure as for creating a user.
Result
User data have been changed.
Mouse and keyboard operation
Requirement
The user view is open.
You are either authorized for user administration or you are an administrator.
A user group has been created.
NOTICE
Runtime users must be assigned to a user group. The user group is set up in the
Engineering System. The user group name is language-specific.
NOTICE
The following characters cannot be used in passwords:
Blanks
Special characters * ? . % / \ ' "
Procedure for mouse operation
Proceed as follows:
1. Double-click on an empty line in the "User" column of the user view.
2. Click in the User name field. Die
3. Enter the desired user name and password.
4. Click in the corresponding input field. The alphanumerical on-screen keyboard is displayed.
5. Confirm your entries with "OK".
6. Assign the user to a group.
7. Click in the "Logoff time" input field. The screen keyboard is shown.
8. Enter a logoff time between 0 and 60 minutes. The value 0 stands for "no automatic logoff."
9. Confirm your entries with "OK".
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2310 System Manual, 08/2011,
Procedure for keyboard operation
Proceed as follows:
1. Press the <TAB> key until the user view is selected.
2. Select an empty line in the "User" column. Use the <Home>,<End>,<Up> and <Down>
keys for this purpose.
3. Enter the desired user name and password.
4. Confirm your entries with <ENTER>.
5. Assign the user to a group. Use the <Home>,<End>,<Up> and <Down> keys for this
purpose.
6. Make an entry in the "Logoff time" input field. Enter a logoff time between 0 and 60 minutes.
The value 0 stands for "no automatic logoff."
7. Confirm your entries with <ENTER>.
See also
Touch operation (Page 2307)
Deleting a user
Touch and key operation
Requirement
You have opened a screen that contains the user view.
You must be logged on with administrator rights or be authorized for user management to
delete users.
NOTICE
Changes in the user view are effective immediately in Runtime. Changes in Runtime are
not updated in the Engineering System.
When the user management is downloaded to the HMI device, all changes in the user
view are overwritten.
Procedure for touch operation
Proceed as follows:
1. Touch the user to be deleted in the user view.
2. Delete the user name.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2311
Procedure for key operation
Proceed as follows:
1. Select the user view using the key or the cursor keys.
2. Select the user in the user view by means of cursor keys.
3. Press to delete the user.
Result
The user has been deleted and may no longer log onto the project.
Mouse and keyboard operation
Requirement
The user view is open.
You are either authorized for user administration or you are an administrator.
NOTICE
Changes in the user view are effective immediately in Runtime. Changes in Runtime are
not updated in the Engineering System.
When the user management is downloaded to the HMI device, all changes in the user
view are overwritten.
Procedure for mouse operation
Proceed as follows:
1. Click the user to be deleted in the user view.
2. Delete the user name.
Procedure for keyboard operation
Proceed as follows:
1. Select the user view using the <TAB> key or the cursor keys.
2. Select the user in the user view by means of cursor keys.
3. Press <DEL> to delete the user.
Result
The user has been deleted and may no longer log onto the project.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2312 System Manual, 08/2011,
9.13.3.4 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
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.
Visualizing processes (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2313
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 (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
2314 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 (Professional)
9.13 Operating in Runtime
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2315
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
Operating recipes in Runtime Advanced and Panels
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:
Header
Current user
Link to logoff
Navigation control
Icon to hide the header
Interface language selection field
Tabs depending on the currently displayed contents
Contents
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2629
Switching the user interface language
1. Choose the desired language from the selection field in the header.
The GUI language is changed.
Hide and show the header
1. To hide the header line, click the symbol .
This provides more room for displaying the content.
2. To show the header line again, click the symbol .
Logoff
1. To log off from the DataMonitor server, click the "Log off" link.
2. Close Internet Explorer.
When you close Internet Explorer, the used license will be released immediately.
9.15.5.3 Working with WinCCViewerRT
Setting up WinCCViewerRT
Requirement
On the server PC
The DataMonitor Server is installed.
A license key is installed.
The WinCC project is in Runtime.
The WinCC screens are configured for Web access and published.
On the client PC
DataMonitor Client is installed.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2630 System Manual, 08/2011,
Procedure
Set up WinCCViewerRT as follows:
1. In the Start menu, select "Start > All Programs > Siemens Automation > Option and Tools
> HMI Tools" > WinCCViewerRT".
2. Enter the logon data in the "General" tab:
Server address: http://<server name>, or http://<IP address>
User name and password:
3. In the "Parameters" tab, specify the Runtime language and whether to disable keystrokes
that the operator uses to change to other programs.
4. Define the WinCC Runtime Professional properties in the "Graphics Runtime" tab:
Start screen
Configuration file for screen navigation
Window attributes
Illegal user actions
5. Define additional user actions in the "Runtime" tab.
Automatic logout
Enable screen keyboard.
Use <Ctrl+Alt+Del> to switch to the Task Manager and to the operating system. This
setting is only valid for the on-screen keyboard.
Open the "WinCCRTViewer" dialog by means of keystroke.
You can change the default keystroke <Ctrl+Alt+P>.
6. Close the dialog with "OK".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2631
Result
The WinCCViewerRT is configured. When the dialog is closed, the connection to the
DataMonitor server is established. The settings are saved to the configuration file
"WinCCViewerRT.xml". The settings in the configuration file are used at the next start of
WinCCViewerRT.
The configuration file is stored in the "Documents and Settings\User\Application Data\Siemens
\Automation\Portal V11\WebNavigator\Client" folder. This allows different configurations to be
used, depending on the logged on user. WinCCViewerRT applies the interface language from
WinCC.
Renaming or removing WinCCViewerRT.xml
When you rename or remove the file WinCCViewerRT.xml, the configuration dialog of
WinCCViewerRT is opened during the start. Reconfigure WinCCViewerRT, or select a different
configuration file.
Display screens
Requirements
A license key is installed on the DataMonitor Server.
The WinCC project on the DataMonitor Server is in Runtime.
The WinCC screens are configured for Web access and published.
A WinCC user with authorization no. 1002 "DataMonitor - Monitor only" is created.
Procedure
To view screens, proceed as follows:
1. In the Start menu, select "Start > All Programs > Siemens Automation > Option and Tools
> HMI Tools" > WinCCViewerRT".
2. Log on to the WebNavigator server:
If the user and password are configured in "WinCCViewerRT", no logon dialog displayed.
If no user and password was configured in "WinCCViewerRT", the logon dialog
displayed. Enter the user name and the password of the WinCC user. Click "OK."
3. Press the <Ctrl+Alt+P> keystroke to change the user. The "WinCCViewerRT" dialog opens.
Enter the user name and password on the General" tab.
You can also select the xml file that contains this data.
Result
The Web Viewer connects to the activated WinCC project. The screens of the WinCC project
are displayed.
The cursor is a "View Only Cursor" and indicates that process-related operations are not
allowed.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2632 System Manual, 08/2011,
Certain operations are still possible, such as opening the properties dialog of an online trend
control.
If necessary, you can use your own cursor as a "View Only Cursor". For more information,
refer to "Configuring runtime settings (DataMonitor) (Page 2615)".
9.15.5.4 Working with the WebCenter
Administration
User Groups and Directories
Overview
WebCenter pages and reports are stored in directories on the DataMonitor Server.
Its standard complement of directories is as follows:
"Public"
"Private"
Every user has a "Private" directory. Only the respective user has access rights to this
directory.
More information on setting up directories can be found in chapter "Creating Directories
(Page 2635) ".
Windows User Groups
The user groups "DM_ADMIN" and "DM_USER" are created during the installation of the
DataMonitor Server. You can create more user groups. More information on setting up user
groups and users can be found in chapter "Assigning Access Rights (Page 2636) ".
To access the DataMonitor, you can assign all members of a user group with the same access
rights to the directory of the DataMonitor server.
The following access authorization is possible:
Read
"Change"
"Create"
A user, as a member of a user group, only has access to a directory if the respective user
group has access rights to that directory. This permits user group-specific access. More
information on assigning access authorization can be found in chapter "Defining users in
Windows (Page 2625) ".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2633
The following screen shows the basic user administration for the WebCenter.
Windows User Administration
DataMonitor Adminstration
Windows user groups
are assigned
different access rights to
DataMonitor directories
The installation routine
of DataMonitor creates
Windows user groups
lndividual
user groups
lndividual
access of
Windows user groups
to
WebCenter pages
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2634 System Manual, 08/2011,
Creating Directories
Introduction
You store WebCenter pages in directories. The following directories exist as defaults:
"Public"
"Private"
Every Windows user has their own "Private" directory.
Requirements
The logged-in user is a member of the Windows user group "DM_ADMIN".
The DataMonitor start page is open.
Procedure
1. Click in the start page "Webcenter >Administration".
2. Click the "Directory administration" tab.
3. Enter the name "mypart" in the "New directory" field.
4. Click the "Create" button.
Result
You have created the directory "mypart". The user administration is opened automatically.
Specify the access rights for the folder. You can also exit the page and configure the access
rights at a later time.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2635
Assigning Access Rights
Introduction
In the WebCenter, directories are created in which, for example, the WebCenter pages are
stored. You can assign different access rights for the individual directories to Windows user
groups.
The following access authorization is possible:
Read
"Change"
"Create"
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2636 System Manual, 08/2011,
Requirement
The logged-in user is a member of the Windows user group "DM_ADMIN".
Procedure
1. Click in the start page "Webcenter> Administration".
2. Click the "User administration" tab.
3. Select the desired directory from the "Current Directory".
All existing Windows user groups are listed.
4. Activate the access rights in the line of the desired Windows user group.
5. Click "Save".
Result
The access rights have been configured for the desired directory.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2637
Establish a connection to the winCC data
Create connection and set up language
Introduction
A connection is configured for access to the data in the "Webcenter". A connection is set up
for each data source, e.g. WinCC server. The connection is required for example for the
function "Trends and Alarms" and the WebCenter page.
Requirement
The logged-in user is a member of the Windows user group "DM_ADMIN".
Procedure
1. Click in the start page "Webcenter> Administration".
2. Click the "Connection administration" tab.
3. Choose the language that corresponds with the linguistic region of the server or log to be
linked in "Linguistic region".
If you do not select the language that corresponds with the respective linguistic region,
characters may be displayed incorrectly on the page.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2638 System Manual, 08/2011,
4. Select "New connection".
After the new installation, no selection is possible in the "Connection" field, as no
connections have been configured yet.
5. Enter a name in the field "Connection name", e.g. "WinCC1_ Runtime".
Any name can be selected. However, it should contain a reference to the selected
connection type. Do not use spaces and special characters in the connection name.
6. Enter the name of the PC whose data you would like to access in the "Computer name"
field. As an alternative, select the name of the PC using the "Find" button.
7. Enter the desired database in the "Database" field. Alternatively, select the database using
the "Find" button.
8. Choose the desired option in the "Connection type" area.
"Swapped WinCC Log"
Further steps are required to access data from logs. For additional information, refer to
"Connecting and Disconnecting Swapped Logs (Page 2639)".
"WinCC Runtime"
The Runtime database of the selected WinCC project is entered in the "Database" field.
CAS
CAS is not available in this version.
WinCC Runtime + all segments
"CC_ExternalBrowsing" is entered in the "Database" field.
9. Activate "Automatic adaption of RT database". When a segment is changed, the name of
the database is adjusted in the connection administration.
10.Click the "Create" button.
Result
The connection to the data source is created and can be selected in "Connections".
Connecting and Disconnecting Swapped Logs
Configuring a directory
Introduction
To access data from swapped WinCC logs (log backup file), these logs must be connected to
an SQL server again.
You can connect all or individual log backup files of a directory to the SQL server.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2639
Requirements
Write protection of the log backup file has been removed
Archive backup files are write protected. Create a backup copy of the file before connecting
and remove the write protection of the copied log backup file.
The log backup files are available on the local drive.
The directories in which the log backup files are set for sharing.
The directory must be set for sharing in the Windows Explorer before you start the
DataMonitor Server.
If you set the directories for sharing later, restart the DataMonitor Server.
The user group "SIMATIC HMI VIEWER" must have "full access" to the directories.
The logged-in user is a member of the Windows user group "DM_ADMIN".
Windows Server 2003 / 2008: "Network service" has been added to the "Print operators"
group.
Windows XP / Windows 7: "Network service" has been added to the "Power user" group.
Procedure
Proceed as follows to create a symbolic directory:
1. Click in the start page "Webcenter> Administration".
2. Click the "Archive administration" tab.
3. Enter a unique symbolic name name in the "Symbolic Name" field.
The name should only contain the characters permitted in the SQL syntax. You use the
symbolic name for access via the DataMonitor client.
4. In "Directory", select the directory in which the log backups are located.
You can only select directories that have been set for sharing.
5. To connect all existing log backups of the directory, select "Automatically connect all logs
in this directory".
To connect all individual log backup files of the directory, clear "Automatically connect all
logs in this directory".
6. Click "Add".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2640 System Manual, 08/2011,
Result
You have created the symbolic directory "Test". If you have cleared "Automatically connect all
logs in this directory", define the log backups to be connected on the page "Connect/disconnect
logs (Page 2641)".
To disconnect logs, clear the desired logs on the page "Connect/disconnect logs"
Note
Connected logs on changeable media
Before changing the media in the drive you need to disconnect the logs on this medium. After
changing the medium, check whether the logs are connected on the new medium.
Deleting a symbolic directory
To remove a directory containing logs from the list of symbolic names, disconnect all logs
contained in the list. The status of the logs can be seen on the page "Connect/disconnect logs".
Connecting and Disconnecting Logs
Requirement
Write protection of the log backup has been removed
Log backups are write protected. Create a backup copy of the log before connecting and
remove the write protection of the copied archive.
The logged-in user is a member of the Windows user group "DM_ADMIN".
You have configured the symbolic directory "Test" (Page 2639).
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2641
Procedure
To connect or disconnect individual log backups, proceed as follows:
1. Click in the start page "Webcenter> Administration".
2. Click the "Connect/disconnect logs" tab.
3. Select the directory "Test" in "Symbolic directories". Existing logs are displayed in a list.
The "Info" column provides information about the status.
Green: Connected
Red: Disconnected
4. To restrict the display, click "Filter".
5. Enter the desired time period and click "Refresh display".
6. To connect a single archive, select the desired log in the "List of existing logs". Click "Save".
The status "Green" indicates that the log is connected.
7. To disconnect a single archive, clear the desired log in the "List of existing logs". Click
"Save". The status "Red" indicates that the log is disconnected.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2642 System Manual, 08/2011,
Alternative procedure
Archive backups can be connected in the following ways:
VB function using the "Restore" method. For detailed information, refer to "Restore".
Automatic Connection: If you copy the log backups to the "CommonArchiving" folder, the
logs are connected to the project in Runtime.
Using Archive Connector (Page 2643).
Result
Logs are connected. If you connect signed logs, which have been changed after the swap, an
alarm is output.
Connecting Logs using WinCC Archive Connector
Introduction
With the Archive Connector, already swapped out WinCC logs can be reconnected to an SQL
Server.
Requirements
Write protection of the log backup file has been removed
Archive backup files are write protected. Create a backup copy of the file before connecting
and remove the write protection of the copied log backup file.
The log backup files are available on the local drive.
The directories in which the log backup files are set for sharing.
The user group "SIMATIC HMI VIEWER" must have "full access" to the directories.
The logged-in user is a member of the Windows user group "DM_ADMIN".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2643
Procedure
To connect log backup files, proceed as follows:
1. Start the "Archive Connector".
2. Click "Add" in the "Configuration" tab. The "New Directory" dialog is opened.
3. Navigate to the directory in which the log backup files are stored.
4. Enter a symbolic name for the directory. Click "OK." The directory is displayed on the
"Configuration" tab.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2644 System Manual, 08/2011,
5. Click the "Connect/Disconnect Logs" tab. All the logs in the selected directory are listed in
the "Connect/Disconnect Logs" tab.
6. Select the desired log and click "Connect".
Result
A connection has been created and the desired log backup files are connected to the SQL
server.
The connection status of each log is displayed on the "Connect/Disconnect Logs tab". "From"
and "To" columns contain the archiving period denoted in the local time zone.
The "Type"column contains the details for log type.
"A" Alarm logs
"TF" Fast data log
"TS" Slow data log
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2645
Creating static process screens for the Web Center
Introduction
In the screen management, specify the screens that you need for the Web element "Static
process screens".
The DataMonitor Server generates copies of the screens at configurable cyclic intervals and
provides these to the DataMonitor Client and the form of static process screens.
Requirements
The logged-in user is a member of the Windows user group "DM_ADMIN".
The WinCC screens are configured for Web access and published. For more information,
refer to "Configuring WinCC screens for Web access (Page 2612)".
The DataMonitor start page is open.
The "Screen management" tab is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2646 System Manual, 08/2011,
Creating static process screens for the Web Center
1. Select the screens.
To select all screens, activate the check box in the column header.
To select individual screens screens, activate the check box leading the relevant screen.
2. To display only part of the screen, define the following:
X position: Start positions in x direction in pixels
Y position: Start positions in y direction in pixels
Width: Width of screen in pixels
Height: Height of screen in pixels
3. To output the time at which the static process screen screen was created by the
DataMonitor Server, activate "Stamp".
The date time are shown in the static process screen.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2647
4. To change the update cycle, enter the desired value in "Update time interval".
Select this cycle as large as possible. A cycle that is too small leads to performance
problems.
5. Click "Save".
Result
The DataMonitor Server generates the static process screens from the selected screens. The
static process screens can be configured in the Web part "Static process screens".
Removing static process screens
To remove static process screens, select the check box at the relevant entry in the "Delete
graphic object" column. Click "Save" to remove the static process screen or copy. The deleted
static process screens can no longer be configured in the Web part "Static process screens".
Finding screen names or limiting the view
Use a filter to find screen names, or to limit the view to specific screen names.
At the "Filter" entry, click to show the filter above the table. Enter the search term in the
text field and then click <Enter>.
To hide the filter, click .
Create a layout template for WebCenter pages
Introduction
You require a layout template to create a WebCenter page. Many prefabricated layouts have
been installed during the installation. Additionally, you can create your own Layout Templates.
Requirements
The logged-in user is a member of the Windows user group "DM_ADMIN".
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2648 System Manual, 08/2011,
Procedure
Proceed as follows to create your own layout template:
1. Click "WebCenter > Configuration" in the start page.
2. Click the "Create layout" tab.
3. Define the number of columns and rows.
4. Enter the name "mylayout_23" in the "Name of the layout file" field. Click "Next."
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2649
5. If required, group the table fields. For this, click the appropriate arrow symbol, such as
"Arrow up", in the desired field, for example line 3 / column 1.
The modified view will be displayed.
To restore the original table form, click "Reset configuration".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2650 System Manual, 08/2011,
6. Click "Next."
7. You define the order of the Web parts in the table fields.
If necessary, select the corresponding symbol in a table field to place the web parts vertically
or horizontally.
8. Click "Save".
Result
The layout template "mylayout_23" is created. You can use the layout template as a template
for creating a WebCenter page.
Create a WebCenter page
Introduction
Requirements
The directory "myPart" is set up.
The logged-in user is a member of the Windows user group "DM_Admin" or "DM_USER".
The Windows user groups have the "Change" or "Create" access rights to the directory.
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2651
Procedure
1. Click "WebCenter > Configuration" in the start page.
2. Click the "Create Page" tab.
3. Click the desired layout template. The file name is displayed in the "Layout file" field.
4. Enter a name in the "WebCenter page" field, for example "My_Webcenter".
5. Click the directory in which the WebCenter page is stored. The selected directory is
displayed in the field "Save WebCenter page as".
6. Click "Save".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2652 System Manual, 08/2011,
Result
The WebCenter page has been created and saved.
Insert Web parts into the WebCenter page
Introduction
You combine Web parts to create the contents of the WebCenter pages.
Requirements
The directory "myPart" is set up.
The WebCenter page "My_Webcenter" is stored in the directory.
The logged-in user is a member of the Windows user group "DM_Admin" or "DM_USER".
The Windows user groups have the "Change" or "Create" access rights to the directory.
The DataMonitor start page is open.
Procedure
Proceed as follows to insert Web parts in the WebCenter page:
1. Click "WebCenter > Pages" in the start page.
2. Click the "myPart" tab.
3. Click the "My_Webcenter" entry.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2653
4. To add Web parts, click the symbol on the right side.
The available Web parts are listed.
If you have exported web parts that have already been configured, they are listed under
"Imported web parts". If necessary, insert these web parts into your WebCenter page.
5. Select "Trend (Timestamp)".
6. Select the entry "WPZ_01_01" and click "Add".
7. Select "Alarm hit list".
If you insert several Web parts in a spreadsheet field, they are arranged horizontally or
vertically. Specify this arrangement when creating the layout template.
8. Select the entry "WPZ_02_01" and click "Add".
9. Click "Close."
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2654 System Manual, 08/2011,
Result
Web parts to display data have been inserted into the WebCenter page "My_Webcenter". The
current summary of the WebCenter page is displayed.
Configure Web parts within WebCenter pages
Requirement
The logged-in user is a member of the Windows user group "DM_Admin" or "DM_USER".
The Windows user groups have the "Change" or "Create" access rights to the directory.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2655
The WebCenter page "My_Webcenter" is open.
The WinCC project is in Runtime.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2656 System Manual, 08/2011,
Procedure
To configure Web parts within WebCenter pages, proceed as follows:
1. Click the icon in the desired Web part. The configuration dialog opens.
2. Configure the web part.
Displaying process values in a table (Page 2660)
Displaying process values in a diagram (Page 2661)
Displaying messages in the alarm table (Page 2663)
Displaying the hit list of messages (Page 2667)
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2657
Displaying statistics function for process values (Page 2668)
3. To change the position of the web part, move the web part to the desired position with the
mouse.
More Operational Capabilities
The following operating options are available:
Delete Web part
Minimize Web part
Maximize Web part
Export Web part
Export configuration of the Web part as an XML file
Deleting WebCenter Pages and Layout Templates
Requirement
Deleting layout templates
The user is a member of the Windows user group "DM_ADMIN".
The DataMonitor start page is open.
Deleting a WebCenter page
The logged-in user must have "Create" access rights for the directory in which the page to
be deleted is stored.
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2658 System Manual, 08/2011,
Deleting layout templates
1. Click "WebCenter > Configuration" in the start page.
2. Click the "Delete layout" tab.
3. Delete the selected files.
To delete several layout files, select the "Selection" check box for the files to be deleted.
Click "Delete."
To delete all the layout files, click "Select All". Click "Delete."
To delete individual layout files, click the respective "Delete" button in the "Action"
column.
Result
The selected layout file is deleted. Note that this also applies to the layout files included in your
package.
Existing WebCenter pages which use this layout template are retained. You cannot use this
layout to create new WebCenter pages.
Deleting a WebCenter page
1. Click "WebCenter > Configuration" in the start page.
2. Click the "Delete page" tab.
3. Activate the respective check box to mark the pages to be deleted.
4. Click "Delete".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2659
9.15.5.5 Working with Trends and Alarms
Displaying process values in a table
Requirements
A connection to the WinCC data is established (Page 2638)
The DataMonitor start page is open.
Procedure
Proceed as follows to display process values in a table:
1. Click "Trends & Alarms " in the start page. Click the "Process value table" tab. The Web
part "Process Value Table" is displayed.
2. Click . The configuration dialog of the Web part opens.
3. Change the title in the "Header" field. Enter a brief tip in the field "Tooltip".
4. Select the desired connection in the "Connection" field. The logging tags available via this
connection will be displayed. You can limit the number of tags using the "Archive selection"
and "Tag filter" fields.
5. Click "Add" for the desired logging tags.
6. Define the time range in the "Time period" area.
With relative times, enter a negative value in the respective field. To obtain additional
information on the time specification, click the symbol.
To check the set time range in the column "Preview time frame", click "Preview".
7. Define the number of decimal places in the "Displaying decimal places" section.
8. In the "Table size" area, define the size of the display window. For example, enter a height
of "200" and a width of "400".
If the value "0" is entered into both fields, the size is determined automatically. The size is
oriented on spatial requirements of the Web part.
9. The available WebCenter pages are displayed in the "Links to WebCenter Pages" area. To
assign the Web part to one or more WebCenter pages, click the symbol.
10.Confirm your entries.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2660 System Manual, 08/2011,
Result
The values of the logging tags are output in the process value table.
Use the arrow keys to skip backward and forward with multi-page tables. You can export the
displayed table in CSV format using the icon. Click the symbol to change your settings.
Displaying process values in a diagram
Requirements
A connection to the WinCC data is established (Page 2638)
The DataMonitor start page is open.
Procedure
Proceed as follows to display process values in a trend view:
1. Click "Trends & Alarms " in the start page. Click the "Trend (process values)" tab. The Web
part "Trend (process values)" is displayed.
2. Click . The configuration dialog of the Web part opens.
3. Change the title in the "Header" field. Enter a brief tip in the field "Tooltip".
4. Select the desired connection in the "Connection" field. The logging tags available via this
connection will be displayed. You can limit the number of tags using the "Archive selection"
and "Tag filter" fields.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2661
5. Click "Add" for the desired logging tags, e.g. "TREND_1", "TREND_2", "TREND_3. The
logging tags are listed in the "Current selection" area.
6. Define the following for the individual logging tags in the "Current selection" area:
color of time and value axis
form of the trend display
7. In the section "Value axis editor", you can select the automatic scaling for the different value
axes or you can assign a minimum and a maximum value to each axis.
8. Define the time range in the "Time period" area.
With relative times, enter a negative value in the respective field. To obtain additional
information on the time specification, click the symbol. To check the set time range in
the column "Preview time frame", click "Preview".
9. In the section "Diagram settings", define the size of the display window. If the value "0" is
entered into both fields, the size is determined automatically. The size is oriented on spatial
requirements of the Web part.
10.To display the legend, select "Show legend".
11.The available WebCenter pages are displayed in the "Links to WebCenter Pages" area. To
assign the Web part to one or more WebCenter pages, click the symbol.
12.Confirm your entries.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2662 System Manual, 08/2011,
Result
The selected process values are displayed as trends in a diagram.
The legend shows the assignment of the colors to the logging tags. Skip forward or back by
the selected time frame in the absolute time using the and buttons.
Enlarge the display and you can zoom into the diagram area to the left and right of the center
line using the "Zoom left" and "Zoom right" buttons. The button is used to restore
the original view.
Export the table displayed in CSV format using the icon.
Click the symbol to change your settings.
Displaying messages in the alarm table
Requirements
A connection to the WinCC data is established (Page 2638)
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2663
Procedure
To display alarms in the alarm table, proceed as follows:
1. Click "Trends & Alarms " in the start page. Click the "Alarm table" tab. The Web part "Alarm
Table" is displayed.
Click . The configuration dialog of the Web part opens.
2. Change the title in the "Header" field. Enter a brief tip in the field "Tooltip".
3. Select the connection in the "Connection" field.
4. Select the corresponding WinCC server in the "Selection of WinCC Servers" area.
You need this setting to be able to select a connection to a swapped out archive that
contains log files from several WinCC servers.
5. Define the time range in the "Time period" area. With relative times, enter a negative value
in the respective field. To obtain additional information on the time specification, click the
symbol. To check the set time range in the column "Preview time frame", click "Preview".
6. In the section "Language of the alarm texts", select the language in which the alarms are
displayed.
7. In the section "Filter selection", limit the expected search results by means of filter conditions
in SQL syntax. To obtain additional information on the filter conditions, click the symbol.
8. Define the following for displaying the data:
Sorting order: To obtain additional information on sorting, click the symbol.
Visible columns: To display all the columns, click "Select All". For further information,
refer to "Alarm Log Column Names (Page 2665)".
Number of decimal places
9. In the "Table size" area, define the size of the display window.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2664 System Manual, 08/2011,
10.The available WebCenter pages are displayed in the "Links to WebCenter Pages" area. To
assign the Web part to one or more WebCenter pages, click the symbol.
11.Confirm your entries.
Result
Use the arrow keys to skip backward and forward with multi-page tables. You can export the
displayed table in CSV format using the icon. Click the symbol to change your settings.
Alarm Log Column Names
Introduction
You can select the alarm log columns while displaying alarms in "Trends and Alarms".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2665
Overview of column names
Position Name Type Comments
1 MsgNo Integer 4 Bytes Alarm number
2 State Small Integer 2 Bytes Alarm Log Status
3 DateTime DateTime 8 Bytes Time stamp of alarm (Date/time without milliseconds)
4 Ms Small Integer 2 Bytes Time stamp of alarm (milliseconds)
5 Instance VarChar (255) Instance Name of the Alarm Log
6 Flags1 Integer 4 Bytes (only for internal use)
7 PValueUsed Integer 4 Bytes Process Values used
8 to 17 PValue1 to PValue10 Real 8 Bytes Numerical Process Value 1 to 10
18 to 27 PText1 to PText10 VarChar (255) Process Value Text 1 to 10
28 Computer name VarChar (255) Computer Name
29 Application VarChar (255) Application Name
30 Comment VarChar (255) Comments
31 UserName VarChar (255) User Name
32 Counter Integer 4 Bytes Running Alarm Message Counter
33 TimeDiff Integer 4 Bytes Time difference to "Incoming" status
34 ClassName VarChar (255) Alarm class name
35 Type name VarChar (255) Alarm type name
36 Class Small Integer 2 Bytes Alarm class ID
37 Type Small Integer 2 Bytes Message type ID
38 to 47 Text1 to Text10 VarChar (255) Alarm Text 1 to 10
48 AG_NR Small Integer 2 Bytes Number of the PLC
49 CPU_NR Small Integer 2 Bytes Number of the CPU
50 CrComeFore Integer 4 Bytes Foreground Color for the "Incoming" Status
51 CrComeBack Integer 4 Bytes Background Color for the "Incoming" Status
52 CrGoFore Integer 4 Bytes Foreground Color for the "Outgoing" Status
53 CrGoBack Integer 4 Bytes Background Color for the "Outgoing" Status
54 CrAckFore Integer 4 Bytes Foreground Color for the "Acknowledged" Status
55 CrAckBack Integer 4 Bytes Background Color for the "Acknowledged" Status
56 LocaIID Integer 4 Bytes Location of the Alarm
57 Priority Integer 4 Bytes Priority
58 AP_type Integer 4 Bytes Loop-in alarm
59 AP_name VarChar (255) Loop-in-Alarm Function Name
60 AP_PAR VarChar (255) Loop-in-Alarm Screen
61 InfoText VarChar (255) Info text
62 TxtCame VarChar (255) Incoming text
63 TxtWent VarChar (255) Outgoing text
64 TxtCameNWent VarChar (255) Text came in and went out
65 TxtAck VarChar (255) Text acknowledged
66 AlarmTag Integer 4 Bytes Alarm tag
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2666 System Manual, 08/2011,
Position Name Type Comments
67 AckType Small Integer 2 Bytes Acknowledgment Type
68 Params Integer 4 Bytes Parameter
See also
Displaying messages in the alarm table (Page 2663)
Displaying the hit list of messages
Requirements
A connection to the WinCC data is established (Page 2638)
The DataMonitor start page is open.
Procedure
To display alarms in a hit list, proceed as follows:
1. Click "Trends & Alarms " in the start page. Click the "Alarm hit list " tab. The web part "Hit
list of the alarms" is displayed.
Click . The configuration dialog of the Web part opens.
2. Change the title in the "Header" field. Enter a brief tip in the field "Tooltip".
3. Select the desired connection in the "Connection" field:
4. Define the time range in the "Time period" area. With relative times, enter a negative value
in the respective field. To obtain additional information on the time specification, click the
symbol. To check the set time range in the column "Preview time frame", click "Preview".
5. In the section "Language of the alarm texts", select the language in which the alarms are
displayed.
6. Select the corresponding WinCC server in the "Selection of the WinCC Server" area.
You need this setting to be able to select a connection to a swapped out archive that
contains log files from several WinCC servers.
7. In the section "Filter selection", limit the expected search results by means of filter conditions
in SQL syntax. To obtain additional information on the filter conditions, click the symbol.
8. Define the following for displaying the data:
Sorting order: To obtain additional information on sorting, click the symbol.
Visible columns: To display all the columns, click "Select All".
Number of decimal places
9. In the "Table size" area, define the size of the display window. If the value "0" is entered
into both fields, the size is determined automatically. The size is oriented on spatial
requirements of the table.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2667
10.The available WebCenter pages are displayed in the "Links to WebCenter Pages" area. To
assign the Web part to one or more WebCenter pages, click the symbol.
11.Confirm your entries.
Result
The analysis values for the alarms are displayed in a hit list:
The table contains configured data and statistical values, e.g. InfoText, frequency of the alarm.
Explanations for the columns are displayed as a tool tip when the mouse is moved over the
respective column header. Use the arrow keys to skip backward and forward with multi-page
tables.
With the icon , the displayed analysis values of the alarms can be exported in CSV format.
Click the symbol to change your settings.
Note
The display of alarms in the hit list may take some time and may place a strong load on the
CPU. A note is displayed in "Trends and Alarms" if the data volume is too high. You may then
confirm the alarm and continue without any changes, or you may cancel the process to modify
the filter criteria and thus reduce the expected amount of data.
Displaying statistics function for process values
Requirements
A connection to the WinCC data is established (Page 2638)
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2668 System Manual, 08/2011,
Procedure
Proceed as follows to display statistics functions for process values:
1. Click "Trends & Alarms " in the start page. Click the "Statistics functions for process values"
tab. The Web part "Statistics functions for process values" is displayed.
2. Click . The configuration dialog of the Web part opens.
3. Change the title in the "Header" field. Enter a brief tip in the field "Tooltip".
4. Select the desired connection in the "Connection" field. The logging tags available via this
connection will be displayed. You can limit the number of tags using the "Archive selection"
and "Tag filter" fields.
5. Click "Add" for the desired logging tags.
6. Define the time range in the "Time period" area.
With relative times, enter a negative value in the respective field. To obtain additional
information on the time specification, click the symbol.
To check the set time range in the column "Preview time frame", click "Preview".
7. Define the following for displaying the data:
Number of decimal places
Aggregate selection: Define the analysis function for the process values.
8. In the "Table size" area, define the size of the display window. For example, enter a height
of "200" and a width of "400". If the value "0" is entered into both fields, the size is determined
automatically. The size is oriented on spatial requirements of the table.
9. The available WebCenter pages are displayed in the "Links to WebCenter Pages" area. To
assign the Web part to one or more WebCenter pages, click the symbol.
10.Confirm your entries.
Result
Statistics functions for the selected process values were executed and output in the table.
The log name and tag name are displayed as a tool tip when the mouse is moved over the
respective column header.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2669
You can export the displayed table in CSV format using the icon. Click the symbol to
change your settings.
9.15.5.6 Working with Excel Workbooks
Configuring an Excel workbook
Importing data from a WinCC project
Introduction
You need the WinCC configuration data to configure Excel workbooks.
Import this data from a local WinCC project when configuring the workbook using the Excel
Workbook Wizard .
Requirements
Server PC
Office 2003 SP3, or Office 2007 is installed
The Excel add-In "Excel Workbook" is installed.
DataMonitor Server is installed.
The WinCC project is in Runtime.
A user is created in WinCC.
On the configuration PC
Office 2003 SP3, or Office 2007 is installed
The Excel add-In "Excel Workbook Wizard" is installed.
Procedure
To import data from a WinCC project, proceed as follows on the configuration PC:
1. Open an empty Excel workbook. Select the "Excel Workbook Wizard..." command in the
"DataMonitor" menu.
2. Activate the option "Establish connection with WinCC server".
3. The "WinCC Server" field is shown. Enter the name of the server PC and then click
"Connect". The log in dialog is displayed.
4. Enter the name and password of a WinCC user.
5. Click "Next >". The "Add / delete tags" dialog opens.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2670 System Manual, 08/2011,
Result
The Excel workbook is configured. Create the view of process data.
Importing data from an xml file
Introduction
You can create the Excel workbook on a PC if, for example, Excel is not installed on the server
PC. Create the corresponding xml file on the DataMonitor Server.
Requirement
Server PC
DataMonitor Server is installed.
The WinCC project is in Runtime.
A user is created in WinCC.
On the configuration PC
Office 2003 SP3, or Office 2007 is installed
The Excel add-in "Excel Workbook Wizard" is installed.
Creating an XML file on the server PC
1. In the Start menu select the command "Start > All Programs > Siemens Automation > Option
and Tools > HMI Tools" > WinCC DataMonitor Configurator Export".
The function creates an XML file and stores it in subdirectory "Web Navigator\Reports" of
the current project. The file name is automatically generated using the format
"<projectname>.XML".
2. If no Excel installation exists on the server PC, transfer the XML file to another PC on which
MS Excel and the Excel Workbook Wizard are installed.
Configuring data access using an XML file
1. Open an empty Excel workbook. Select the "Excel Workbook Wizard..." command in the
"DataMonitor" menu.
2. Activate the option "Load configuration data from file". Click "Next >".
3. Navigate to the required XML file.
4. Click "Next >". The "Add / delete tags" dialog opens.
Result
The Excel workbook is configured. Create the view of process data. Transfer the Excel
workbook to the client PC. The DataMonitor Client displays the process data of the server PC.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2671
Configuring the display of tag values
Requirements
The dialog "Add / delete tags" is open.
Procedure
Proceed as follows to display tag values in Excel:
1. Check the option for the insert sequence of tag groups in the "Add tags" area.
2. In the "Tag tree" area, click the directory icon. The object list opens.
3. Select the desired tag in the object list and drag the tag to a field of the Excel table.
4. Close the object list. The tag will be displayed in the window "Tag list".
5. In the "Tag list" window, select the tag and the "Server settings" command from the shortcut
menu.
6. In the "Server settings" dialog, enter the name and password of a WinCC user. Activate
"Activate automatic login". Confirm your entries.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2672 System Manual, 08/2011,
7. In the window "Tag list", select the tag and select the menu command "Properties" from
the shortcut menu. The dialog "Tag properties" will be opened.
8. Define the properties for the view in the table, e.g. the arrangement of headers, time stamps,
and quality code.
9. To apply the set update cycle to all tags, select "Save as default".
Settings in the areas "Display in sheet" and "Additional Data" are not valid for all tags.
10.Confirm your entries. Click the "Next >" button in the dialog "Add tag". The dialog "Add/
delete logging tags (Page 2674)" is opened.
Result
The display of tag values in an Excel sheet is configured.
In the Excel workbook, each table cell is assigned a short text and a comment which was
configured for displaying a tag value.
With tag values, the short text "OV" stands for online tags.
In the comments, the source of the displayed values is shown in the format
"WDWx_<number>_<tagname>".
The value for x means:
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2673
O = Online value
Note
After deleting/moving cells filled with configuration data or deleting/inserting new lines/
columns in the Excel worksheet, the Excel Workbook Wizard must be executed again.
The configuration data is checked and automatically adapted as a result. Confirm the data
displayed simply by using the "Next >" button. Save the workbook and close Excel.
Configuring the display of logging tags
Requirement
The dialog "Add / delete logging tags" is open.
Procedure
Proceed as follows to display logging tags in Excel:
1. In the "Tag tree" area, click the directory icon. The object list opens.
2. Select the desired logging tag in the object list and drag the logging tag into a field of the
Excel table.
3. Close the object list. The logging tag will be displayed in the window "Tag list".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2674 System Manual, 08/2011,
4. In the window "Tag list", select the logging tag and select the menu command "Properties"
from the shortcut menu. The dialog "Archive tag properties" will be opened.
5. Define properties for display in the table, e.g. the insert sequence, data resolution, display
time window.
6. To save the settings, select "Save as default". The settings in the "Additional data" area
are not saved.
Note
If you use the option "Number of data" for Data resolution > User-defined resolution", enter
an even value in the input box. Even values ensure proper trend display.
7. Confirm your entries. Click the "Next >" button in the dialog "Add logging tag". The dialog
"Add/remove alarms (Page 2676)" will open.
Result
The display of logging tag values in an Excel sheet is configured.
In the Excel workbook, each table cell is assigned a short text and a comment which was
configured for displaying a tag value.
With tag values, the short text "AV" stands for logging tags.
In the comments, the source of the displayed values is shown in the format
"WDWx_<number>_<tagname>".
The value for x means:
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2675
A = Archive value
Note
After deleting/moving cells filled with configuration data or deleting/inserting new lines/
columns in the Excel worksheet, the Excel Workbook Wizard must be executed again.
The configuration data is checked and automatically adapted as a result. Confirm the data
displayed simply by using the "Next >" button. Save the workbook and close Excel.
See also
Configuring the display of tag values (Page 2672)
Configuring the display of alarms
Requirement
The dialog "Add / Delete Alarms" is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2676 System Manual, 08/2011,
Procedure
Proceed as follows to display alarms in Excel:
1. Select the required cell in the Excel table. Click "Add alarm".
2. In the "Add alarm" area, click the directory icon. The dialog "Alarm - properties" will be
opened.
3. Define the properties for the display of alarms in the Excel table, such as headings and
insertion sequence of attributes.
4. Enter a filter condition in the "Filter string" field or use the selection dialog to define specific
alarms to be displayed, for example.
5. Use the "Maximum number of alarms" option to limit the number of most recent alarms
displayed. You can display maximum 1,000 alarms.
6. Activate the desired attributes in the list. For additional information, refer to "Alarm
Attributes (Page 2681)".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2677
7. To save the setting, select "Save as default".
8. Confirm your entries. Click the "Next >" button in the dialog "Add logging tag": The
"Description" dialog box will open.
Result
The display of alarms in an Excel sheet is configured.
In the Excel workbook, each table cell is assigned a short text and a comment which was
configured for displaying an alarm.
With alarms, the short text "AL" and the comment are shown in the format
"WDWL_<nummer>_<feldbezeichnung>".
Note
After deleting/moving cells filled with configuration data or deleting/inserting new lines/
columns in the Excel worksheet, the Excel Workbook Wizard must be executed again. The
configuration data is checked and automatically adapted as a result. Confirm the data
displayed simply by using the "Next >" button. Save the workbook and close Excel.
See also
Configuring the display of logging tags (Page 2674)
Publishing an Excel workbook
Requirement
The display of tag values, logging tags and alarms is configured.
The "Description" dialog box is open.
Procedure
To access Excel workbooks on the DataMonitor Server, proceed as follows:
1. Click "Publish". The Excel workbook is made available for download on the DataMonitor
Server.
2. Use the "Template" button to provide the Excel Workbook for the function "Published
Reports".
3. Exit the Excel Workbook Wizard
4. Save the workbook and close Excel.
Alternative procedure
You publish the Excel template on the DataMonitor client. For additional information, refer to
"Preparing an Excel Workbook as a Template (Page 2683)".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2678 System Manual, 08/2011,
Result
The Excel workbook is made available on the DataMonitor Server. If required, the Excel
workbook is downloaded on the DataMonitor clients or opened directly in Internet Explorer.
Displaying process data in an Excel Workbook online
Requirements
The Excel workbook with the configuration of the process value display must be available
on the PC.
One of the following Excel versions is necessary for online display in the Excel Workbook:
Office 2003 SP3
Office 2007
WinCC Runtime Professional is installed
DataMonitor Server is installed.
The WinCC project is in Runtime.
The DataMonitor start page is open.
The user "DM_Demo" has been created (Page 2616).
Procedure
1. Click "WebCenter > Configuration" in the start page.
2. Click the "Report tools" tab.
The Excel workbooks that were published in the Excel Workbook Wizard, are shown in an
overview.
3. Select a workbook.
4. Click the Excel workbook symbol in the "Open / Save" column.
5. Click "Open >" in the next dialog. The Excel workbook opens.
6. Select the "Excel Workbook" command in the "DataMonitor" menu.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2679
7. The name of one of the servers, whose tags are configured in the Excel table, is displayed
in the "WinCC Server" field.
The following options are available for the server name:
Access via domain
In case of accesses from outside the network domain, the domain is indicated along
with the server name.
The DataMonitor start page is the standard Web page.
Only the server name is entered in the "WinCC Server" field.
The DataMonitor start page is in the virtual directory:
The name of the virtual folder needs to be specified after the server name, e.g. "/
webnavigator".
8. Activate the "All servers" check box when the tags from several servers are configured in
an Excel sheet. The tag values of all the servers are updated in the online display.
Note
To establish connections to all the servers, select "All servers" before pressing the
"Connect" button to establish the connection.
9. Activate the connection to the WinCC project via the button "Connect". After a successful
connection, the log-in dialog will be opened. Enter the user name "DM_Demo" and the
respective password. When several servers are used, the logon dialogs of the servers
concerned open one after the other.
If no connection is established, a corresponding message is displayed. Clicking on the
dialog will display further information about the error (if available).
Note
The Excel Workbook dialog must not be closed as long as the logon dialog for connection
establishment to the server persists.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2680 System Manual, 08/2011,
10.The connection status will be displayed in the dialog. Click the buttons "Read tags", "Read
logging tags" and "Read alarms" buttons to update the respective values or displays.
If necessary, select the check box "Read cyclically" to update the tag values in cycles.
11.Close the dialog "Excel Workbook" after ending your calculations in Excel.
12.Save the results in the workbook and close Excel.
Result
The values of an online tag, a logging tag as well as a message window are displayed in the
Excel table.
Alarm Attributes
Introduction
While displaying messages in Excel Workbook you can select the attributes to be displayed
in the Excel sheet in the Excel Workbook Wizard .
Overview
Position Attribute Type Comments
1 Alarm class name VarChar (255)
2 Alarm type name VarChar (255)
3 Foreground color Integer 4 Bytes
4 Background color Integer 4 Bytes
5 Flashing color Integer 4 Bytes
6 to 15 Alarm Text 1 to 10 VarChar (255)
16 to 25 Process value 1 to 10 Real 8 Bytes Numerical Process Value 1 to 10
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2681
Position Attribute Type Comments
26 State VarChar (255) Status text
27 Info text VarChar (255)
28 Alarm class ID Integer 4 Bytes
29 Message type ID Integer 4 Bytes
30 AS Number Small Integer 2 Bytes
31 CPU Number Small Integer 2 Bytes
32 Duration Integer 4 Bytes Time difference to "Incoming" status
33 Alarm counter Integer 4 Bytes Consecutive alarm counter
34 Acknowledgment Status VarChar (255) Text of the acknowledgement status
35 Priority Integer 4 Bytes
36 Application Application with which the comment was created.
37 Computer VarChar (255) Computer on which the comment was created.
38 Users VarChar (255) User who created the comment.
39 Comments VarChar (255)
See also
Configuring the display of alarms (Page 2676)
VBA Functions of the Excel Workbook
Excel workbooks: VBA functions of the Excel workbook
The following functions are available to you in an Excel workbook if you have generated an
instance of the Excel workbook object using the
"Application.COMAddIns.Item("ExcelWorkbook.Connect").Object".
ShowDialog(0): Opens the "Excel Workbook" dialog with a normal size.
ShowDialog(1): Opens the "Excel Workbook" dialog with a minimized size.
ShowDialog(2): Opens the "Excel Workbook" dialog hidden.
CloseDialog: Closes the "Excel Workbook" dialog.
GetServerID(server name): Gets the ID of the WinCC server with a specified name, for
example: "http://Local_PC".
Connect(ServerID): Connects the specified WinCC server to the Excel workbooks. You can
get the "ServerID" using the "GetServerID(server name)" function. The "Excel Workbook"
dialog must be opened before establishing a connection.
ConnectAll: Connects all WinCC servers to Excel workbooks. The "Excel Workbook" dialog
must be opened before establishing a connection.
Disconnect(ServerID): Disconnects the Excel workbook from the specified WinCC server.
DisconnectAll: Disconnects the Excel workbook from all WinCC servers.
ReadTags(ServerID): Reads the tags from WinCC server with "ServerID". The connection
must be established before tags can be read.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2682 System Manual, 08/2011,
ReadArchives(ServerID): Reads the logs from WinCC server with "ServerID". The
connection must be established before logs can be read.
ReadAlarms(ServerID): Reads the alarms from WinCC server with "ServerID". The
connection must be established before alarms can be read.
As soon as a connection is established or closed, the event "ServerConnected(ServerID)" or
"ServerDisconnected(ServerID)" is output by the "ExcelWorkbook.Connect" object. These
events can be integrated, for example, using "WithEvents" (VB standard).
9.15.5.7 Working with reports
Preparing an Excel Workbook as a Template
Requirement
The Excel workbook is created.
The start page of the DataMonitor is open.
Procedure
Proceed as follows to prepare Excel workbooks as a template:
1. Click "Reports" in the start page.
2. Click the "Upload templates" tag.
3. Select a directory, in which the template will be stored in the "Target directory" field.
Only the directories, for which the user that is logged in has "Create" access rights, can be
selected.
4. Click the "Browse" button in the "Selected template" field. Navigate to the required Excel
workbook.
5. Click the "Upload" button.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2683
Result
The template is prepared for the function "Published Reports".
See also
Publishing an Excel workbook (Page 2678)
Configuring an Excel workbook (Page 2670)
Making an Excel workbook available as a report tool
Requirement
The Excel workbook is created.
The start page of the DataMonitor is open.
Procedure
Proceed as follows to prepare Excel workbooks as a report tool:
1. Click "Reports" in the start page.
2. Click the "Upload templates" tag.
3. Click the "Browse" button in the "Excel Workbook" field. Navigate to the required Excel
workbook
4. Click the "Upload" button.
Result
The Excel workbook is ready in the "Report tools" section.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2684 System Manual, 08/2011,
Making Settings for Reports
Introduction
Different settings are required for using the function "Reports" from DataMonitor.
Requirements
PDF Reader is installed.
The WinCC project is selected on the DataMonitor server.
The WinCC project is selected in "Scheduled print jobs in Runtime".
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2685
Procedure
To configure the reports settings, proceed as follows:
1. Click "Reports " in the start page. Click the "Settings" tab.
The "Settings" page is displayed.
2. Check the entries in the section "General project settings".
To enable output to a PDF file, select "Activate API print".
3. Enter the data for sending mail in the "Mail" area:
Server
Outgoing mail server (SMTP)
User name
Name for the sender
Password
Sender
Email account, through which you send your Email
4. Click the disk icon in the section "General project settings" to save your settings.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2686 System Manual, 08/2011,
5. In the "Circular buffer" area, you can define how many reports can be stored for the selected
target directory. The field has a pre-assigned value of 20.
6. Click the disk icon in this section to save your settings.
Result
The settings for "Reports" have now been made.
Displaying a report with an Excel Workbook
Requirements
PDF Reader is installed.
The WinCC project is selected on the DataMonitor server.
The WinCC project is selected in "Scheduled print jobs in runtime".
The DataMonitor start page is open.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2687
Procedure
Proceed as follows to create a report with Excel workbooks:
1. Click "Reports" in the start page. Click the "Excel Workbooks" tab.
The "Excel Workbooks" page is displayed.
The icons in front of the lists "List of time-controlled Excel Workbooks" and "List of event-
controlled Excel Workbooks" are cleared and show that currently, no reports are triggered.
2. Select the desired Excel workbooks, e.g. "My_workbook_1.xls" in the "Existing Excel
Workbooks" field.
This field only shows Excel Workbooks that meet the following conditions:
Workbooks that are published as templates in the Excel Workbook Wizard
Workbooks in directories for which the current user has the "Read" access right.
3. Select the directory, in which the reports will be stored in the "Target directory" field.
Only the directories, for which the user that is logged in has "Create" access rights, can be
selected.
4. Enter an e-mail address in the field "E-mail recipient". The report is e-mailed to this address.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2688 System Manual, 08/2011,
5. To configure time-controlled triggering, define the following in the "Time-controlled Excel
Workbooks" area.
Date:
Enter the date in the field or define the date using the calendar. To open the calendar,
click the "calendar" symbol.
Time
Define the triggering time.
Repetition
Define the repetition rate, e.g. "Once" or "Weekly".
6. Click the "Add" button in the "Time-controlled Excel Workbooks" area. The report is
displayed in the "List of time-controlled Excel workbooks".
7. To create the report immediately, click the symbol .
8. To configure event-controlled triggering, define the following in the "Event-controlled Excel
Workbooks" area.
Selected WinCC tag
Click . The object list opens. Select the desired tag from the object list.
Define the event control
Define the triggering event, e.g. change of the tag value.
If you selected "Low limit", "High limit", or "Both limits" for event control, you need
corresponding limit values.
9. Click the "Add" button in the "Event-controlled Excel Workbooks" area. The report is
displayed in the "List of event-controlled Excel workbooks"
Result
A time-controlled or event-controlled report has been triggered with an Excel workbook.
The report is displayed in one of the lists "List of time-controlled Excel workbooks" and "List
of event-controlled Excel workbooks". The report can be changed or deleted in the list.
Note
An event-controlled print job will not be initiated if the time, in which the tag changes, is less
than one minute.
Note that frequent initiation of the event-controlled print job OR simultaneous initiation of
several print jobs over an extended period will lead to heavy load on memory space and
resources, e.g. frequent signal changes of a tag.
Creating a report with a print job
Requirements
PDF Reader is installed.
The WinCC project is selected on the DataMonitor Server.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2689
The WinCC project is selected in "Scheduled print jobs in runtime".
The DataMonitor start page is open.
Procedure
1. Click "Reports" in the start page. Click the "Print jobs" tab.
The "Print Jobs Configuration" page is displayed.
The icons in front of the lists "List of time-controlled print jobs" and "List of event-controlled
print jobs" are cleared. The icons indicate that no reports are currently triggered.
2. Select the desired print job, such as "Report OnlineTableControl-CP" in the "Existing print
jobs" field.
You can create the report immediately via the icon.
3. In "Target directory: ", select the directory in which the reports are created.
Only the directories, for which the user that is logged in has "Create" access rights, can be
selected.
4. Enter an e-mail address in the field "E-mail recipient". The report is e-mailed to this address.
5. To configure time-controlled triggering, define the following in the "Time-controlled print
jobs" area.
Date:
Enter the date in the field or define the date using the calendar. To open the calendar,
click the "calendar" symbol.
Time
Define the triggering time.
Repetition
Define the repetition rate, e.g. "Once" or "Weekly".
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
2690 System Manual, 08/2011,
6. Click the "Add" button in the "Time-controlled print jobs" area. The report is displayed in
the "List of time-controlled print jobs".
7. To configure event-controlled triggering, define the following in the "Event-controlled print
jobs" area.
Selected WinCC tag
Click the icon. The object list opens. Select the desired tag from the object list.
Define the event control
Define the triggering event, when the tag value is changed, for example
Low limit and high limit
If you selected "Only low limit", "Only high limit" or "Both limits" for event control, limits
are required.
8. Click the "Add" button in the "Time-controlled print jobs" area. The report is displayed in
the "List of event-controlled print jobs".
Result
A time-controlled or event-controlled report with print job in PDF format has been created.
Depending on the type, the report is displayed in one the "List of time-controlled print jobs" or
"List of event-controlled print jobs". The report can be changed or deleted in the list.
Note
An event-controlled print job will not be initiated if the time, in which the tag changes, is less
than one minute.
Please consider that a frequent triggering of the event-controlled print job over a long time
period will use a lot of memory and resources, such as the frequent signal change of a tag.
Visualizing processes (Professional)
9.15 Options
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2691
9.16 Interfaces
9.16.1 OPC
9.16.1.1 OPC for Runtime Advanced
Basics
OPC
Introduction
OPC refers to standardized manufacturer-specific software interfaces for data exchange in
automation engineering.
The OPC interfaces provide a standardized environment in which devices and applications
from various manufacturers can be linked.
OPC is based on the Windows technology COM (Component Object Model) and DCOM
(Distributed Component Object Model).
OPC UA (Unified Architecture) is the technology succeeding OPC. OPC UA is platform-
independent and can use different reports as a communication medium.
Principle of operation
In WinCC, you can configure HMI devices as OPC servers or OPC clients. The particular HMI
device determines which OPC servers and OPC clients are available.
OPC Specifications
OPC specifies interfaces to gain access to the following objects in WinCC:
Process values (OPC Data Access 1.0, 2.05a)
Process values (DataAccess ClientFacet (OPC UA)
Process values (OPC XML-Data Access 1.01)
You can find additional information about the individual OPC specifications in the Internet at
the website of OPC Foundation:.
www.opcfoundation.org (www.opcfoundation.org)
See also
Supported OPC UA services of the OPC UA client (Page 2704)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2692 System Manual, 08/2011,
Compatibility
Support of the mentioned specifications is checked regularly by the "Compliance Test Tool"
(CTT) of the OPC Foundation. Interoperability with OPC products of other manufacturers is
ensured through the participation in "OPC Interoperability Workshops".
The test results submitted are published on the website of the OPC Foundation. The results
can be called up from there using the search term "OPC Self-Certified Products".
Using OPC in WinCC
Configuration option
HMI devices configured with WinCC feature an OPC interface for data communication between
automation devices or automation systems using the OPC communication driver.
You can use an HMI device as an OPC server and/or as an OPC client. As an OPC client, the
HMI device can be connected to a maximum of eight OPC servers.
The software ensures up to eight client HTTP connections for an OPC XML DA server on a
Multi Panel. For the exchange of data via an XML connection, some OPC XML DA clients
create several HTTP connections to the OPC XML DA server.
HMI device Data exchange over Operating system OPC server OPC client
PC, Panel PC (with
WinCC Runtime
Advanced)
DCOM or
OPC UA binary (TCP/
IP)
Windows XP / 7 OPC DA server OPC DA client
OPC UA Client
MP 277, MP 377
Mobile Panel 277
SOAP Windows CE OPC XML DA Server -
Comfort Panel SOAP or
OPC UA binary (TCP/
IP)
Windows CE OPC XML DA Server OPC UA Client
*: The OPC UA client exchanges data via TCP/IP.
A communication via DCOM is only possible between HMI devices of the "PC" or the
"Panel PC" type. In order for a control room PC to display the process values of Windows CE
HMI devices in the plant, for example, install "OPC-XML-Gateway" on the control room PC
using the WinCC Runtime Advanced Setup. The "OPC-XML-Gateway" supports the
communication within the SIMATIC HMI devices family between an OPC DA client and an
OPC XML DA server.
The area pointer is supported by any OPC connection.
OPC server accessibility
The following table lists the available OPC servers and how you can access them:
OPC server OPC server name
OPC DA server OPC.SimaticHMI.MhiRTm (ProgID)
OPC XML DA Server http://<xxx>/soap/OpcXml (URL)
1
<xxx>: IP address or DNS name of the HMI device
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2693
OPC server OPC server name
OPC DA server OPC.Siemens.XML (ProgID) for accessing the OPC XML DA server via
the OPC XML gateway from an OPC DA client
1
: For the access of an external OPC DA XML client.
HMI device as OPC client
To use an HMI device as an OPC client, create an "OPC" connection in the WinCC project.
The OPC client accesses the tags of the OPC server over this connection. You need a separate
connection for each OPC server.
The following exception applies here:
If you want to connect your OPC DA client to multiple panels, you only need one OPC
connection to the OPC XML gateway in your project. The multiplexing of the connection to
multiple OPC XML connections to individual panels takes place in the OPC XML62 gateway.
You configure the connections to the panels using he OPC XML Manager.
The following figure shows the use of an HMI device as a central operator control and
monitoring device:
Ethernet TCP/lP
Profibus
SlMATlC S7-400
SlMATlC S7-300
WinCC flexible
WinCC flexible
WinCC flexible
Third-party PLCs
OPC DA-Server
OPC DA-Client
OPC DA-Client
OPC XML-Server
OPC Server
HMI device as OPC server
An HMI device as OPC server makes the data available to other applications. The applications
can run on the same HMI device or on HMI devices in the connected network environment.
The following schematic diagram shows the use of MS Excel as an OPC client that displays
process values of the OPC server:
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2694 System Manual, 08/2011,
Ethernet TCP/lP
MS Excel WinCC flexible
OPC DA Server OPC DA Client
See also
Configuring an HMI device as OPC DA server (Page 2695)
Creating a connection to a WinCC OPC DA server (Page 2697)
OPC XML Gateway (Page 2700)
Configuring an OPC server
Configuring an HMI device as OPC DA server
Introduction
Which OPC server is used depends on the HMI device:
For HMI devices with Windows XP / 7, the OPC DA server is used.
For HMI devices with Windows CE, the OPC XML DA server is used
The following figure shows the two methods of accessing an OPC server:
XML
DCOM
MP 270B
MP 277
MP 370
"OPCXML Manager
OPC-Gateway
OPC DA Client OPC DA Server
OPC XML Server
Panel PC
Standard PC
Panel PC
Standard PC
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2695
Procedure
To configure an HMI device as an OPC server, proceed as follows:
1. Open the "Runtime settings" of the HMI device in the project tree.
2. Select the "Operate as OPC server" option in the "Runtime settings" under "Services >
Write/read tags".
3. Save the project.
4. Download the project to the HMI device.
5. Start runtime on the HMI device.
Result
The OPC server is accessible. If an OPC client connects to the OPC server, the OPC server
on the HMI device is started.
See also
Using OPC in WinCC (Page 2693)
Creating a connection to a WinCC OPC DA server (Page 2697)
Configuring DCOM user permissions in Windows
Introduction
The OPC DA client and OPC DA server are DCOM applications, whose security settings must
be set in compliance with the DCOM security mechanisms:
The OPC client needs launch/activation rights and access rights for the OPC DA server.
The OPC DA server only needs access rights for the OPC DA client
The following must be known on the PCs of the OPC DA server and the OPC DA client
respectively:
The user account for which the OPC DA client is executed
Requirement
You have administrator rights.
Procedure
The procedure for configuring DCOM user rights is described in the document (http://
www.opcfoundation.org/DownloadFile.aspx?CM=3&RI=326&CN=KEY&CI=282&CU=14) of
the OPC-Foundation.
For additional information on granting user rights, refer to the documentation for Windows XP,
Windows Vista, or Windows 7.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2696 System Manual, 08/2011,
Configuring an OPC client
Creating a connection to a WinCC OPC DA server
Introduction
For an HMI device to access the OPC server data of another HMI device, you need to create
a connection to this OPC server in the WinCC project. Depending on the target HMI device
used, either an OPC DA server or an OPC XML DA server is employed.
The following figure shows the two methods for accessing the OPC servers of the HMI devices:
XML
DCOM
MP 270B
MP 277
MP 370
"OPCXML Manager
OPC-Gateway
OPC DA Client OPC DA Server
OPC XML Server
Panel PC
Standard PC
Panel PC
Standard PC
If a connection to one or more OPC XML DA servers is created using an OPC XML gateway,
also enter the OPC XML DA servers in the "OPC XML Manager".
Requirement
An HMI device is configured as an OPC server.
The project on the HMI device is in runtime.
For connections to a OPC XML DA server: "OPC-XML-Gateway" is installed on the
configuration PC and the HMI device with the OPC client.
Procedure
To create a connection to an OPC server of an HMI device, follow these steps:
1. Open the "Connections" editor on the configuration PC in the WinCC project of the OPC
client.
2. Create a new connection and enter a meaningful name.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2697
3. Select the entry "OPC" as the "Communication driver".
4. Enter the communication partner under "Parameters > OPC server" in the work area:
If the connection communicates directly with the OPC server or with the OPC server on
a PC-based HMI device, select the "OPC.SimaticHMI.CoRtHmiRTm" item from the list.
If the connection communicates directly with the OPC server of a Windows CE HMI
device, select "OPC.Siemens.XML" from the list.
If the OPC server is installed on a remote computer, enter the computer's IP address
or name under "Remote computer name".
Result
The OPC connection is configured. To access the data on the WinCC OPC DA server, create
tags.
See also
Using OPC in WinCC (Page 2693)
Configuring an HMI device as OPC DA server (Page 2695)
OPC XML Gateway (Page 2700)
Configuring an OPC XML Manager (Page 2701)
Creating a connection to an OPC UA server
Introduction
The OPC UA client can access process data in the hierarchical name space of an OPC UA
server.
For the OPC UA client to access the process values of an OPC UA server, the OPC UA server
and the OPC UA client authorize each other by exchanging certificates. In addition, you can
encode the data transfer.
The OPC UA client usually classifies each certificate of an OPC UA server as a "trustworthy".
How an OPC UA server responds to a connection request of the OPC UA client depends on
the configuration of the OPC UA server.
In order to establish communication to an OPC UA server, inform yourself from the OPC UA
server operator about the following:
URL of the OPC UA server
Security settings
Required certificates
Requirement
URL and security settings of the OPC UA server are known.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2698 System Manual, 08/2011,
Procedure
To create a connection to an OPC UA server, proceed as follows:
1. Open the "Connections" editor on the HMI device.
2. Create a new connection and enter a meaningful name.
3. Select the entry "OPC UA" as the "Communication driver".
4. In the work area, under "Parameters", configure the "OPC server":
Specify the "Discovery URL" of the OPC UA server or select the OPC UA server from
the list.
Select the "Security policy"
Select the "Message security mode"
Result
The OPC UA connection is configured. You create tags to access data from the OPC UA
server.
See also
Supported OPC UA services of the OPC UA client (Page 2704)
Accessing process values of an OPC server
Requirement
The OPC server to be addressed is ready-to-operate and in the "running" status
A connection to the OPC-Server is created
Procedure
To access process values of an OPC-Server via the OPC connection, follow these steps:
1. On the configuration PC in the project navigation, open the "HMI tags" editor under the HMI
device that you use as an OPC client.
2. Create a tag with the same data type as the tag on the OPC server.
3. Select the OPC connection for "Connection".
4. Enter the "Address", or select the desired tag on the OPC server via the object list.
Result
If you launch Runtime on the HMI device, the process value from the OPC server will be written
to the tag on the HMI device via the OPC connection.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2699
See also
Permitted data types (OPC) (Page 2702)
Access to tags with OPC (Page 2703)
OPC XML Gateway
Usage
The OPC DA client uses the "OPC XML Gateway" so that the OPC DA client can communicate
with the OPC XML DA server. The "OPC XML Gateway" compiles the data in the respective
"language" of the corresponding standard. The "OPC XML Gateway" communicates
exclusively with the OPC XML DA server which runs on an SIMATIC HMI device.
Installation
To install "OPC XML Gateway", activate the "OPC XML Gateway" entry during installation of
WinCC runtime advanced in the component selection. To install "OPC XML Gateway"
afterwards, re-execute the setup of WinCC Runtime Advanced.
Proxy setting for the OPC XML Gateway
The configuration settings for the OPC XML Gateway can be found in the "SOPCSRVR.ini"
file in the section "[Configuration]". The OPC XML Gateway is configured by default on the PC
as the HMI device, so that a proxy server configured in the Internet settings of Internet Explorer
is ignored:
NOPROXY=1
If this entry is set to "0", the OPC XML Gateway uses a configured proxy server for HTTP
connections.
You can find the "SOPCSRVR.ini" file in the folder "C:\Program Files\\Siemens\Automation
\WinCC RT Advanced".
Note
When data is requested from an HMI device that cannot be accessed over the configured
proxy server, the OPC XML Gateway uses a direct connection after a Timeout. The direct
connection is set up again on every request for data and slows down OPC communication
significantly.
See also
Configuring an OPC XML Manager (Page 2701)
Using OPC in WinCC (Page 2693)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2700 System Manual, 08/2011,
Configuring an OPC XML Manager
Introduction
The OPC XML DA server, to which the OPC DA client has access, is administered in the "OPC
XML Manager". The OPC XML Manager can be found in the Windows Start menu under
"SIMATIC > OPC-XML-Gateway > OPC XML Manager".
To enter an OPC server, you need the following information:
Server prefix
Any string that is used in the name of the OPC tag. Use an abbreviation of the server, for
example. You can find the characters permitted for tag names in the reference.
Name or IP address of the OPC XML DA server
Requirement
"OPC XML Manager" is open.
Procedure
To configure the OPC XML Manager, proceed as follows:
1. To enter a new OPC XML DA server, click on the button "Add".
The "Add/Edit Webservice" dialog is opened.
2. Enter the server prefix and the name or IP address of the OPC XML DA server.
3. Close the two dialogs with "OK".
Result
The OPC XML DA server is entered. The OPC DA client can now access the data of the OPC
XML DA server via the "OPC XML Gateway".
Editing or removing an OPC server
To edit or delete a configured OPC XML DA server, select the required OPC XML DA server.
Then click either "Edit" or "Remove" .
See also
OPC XML Gateway (Page 2700)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2701
Reference
Permitted data types (OPC)
Permitted data types
The following table lists the data types supported by the WinCC OPC servers:
OPC data type WinCC data type
VT_BOOL BOOL
VT_I1 CHAR
VT_UI1 BYTE
VT_I2 SHORT
VT_UI2 WORD
VT_UI4 DWORD
VT_I4 LONG
VT_R4 FLOAT
VT_R8 DOUBLE
VT_DATE DATE
VT_BSTR STRING
The following table lists the ranges of values of the OPC data types:
OPC data type Range of values
VT_BOOL 0 or -1
VT_I1 -128 to 127
VT_UI1 0 to 255
VT_I2 -32768 to 32767
VT_UI2 0 to 65535
VT_I4 -2147483648 to 2147483647
VT_UI4 0 to 4294967295
VT_R4 3.402823466 e-38 through 3.402823466 e+38
VT_R8 1.7976931486231e-308 to 1.7976931486231e+308
VT_Date 1 January 100 to 31 December 9999
Special features in communication with the OPC-DA server
The array tag in the OPC-DA server belonging to the area pointer must be of the data type
SHORT (VT_I2).
Special features in communication with the OPC-XML server
Array tags are not supported by OPC-XML servers.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2702 System Manual, 08/2011,
Access to tags with OPC
Introduction
When accessing tags with OPC, note the following when configuring tags:
Permitted characters in tag names
Permitted cycle times (OPC XML)
Special features of the data type "STRING" (OPC XML)
Special features of the data type "Date/Time" (OPC XML)
The OPC XML DA server is tested and enabled for eight connections, each with 2 groups and
consisting of 35 tags.
Permitted characters in tag names
Only use the following characters in tag names:
Letters from "a" to "z" (no umlauts)
Numbers from "0" to "9"
Special characters: "-" and "_"
Permitted cycle times (OPC XML)
OPC XML connections are designed for the exchange of small volumes of data:
For this reason use cycle times that are greater than one second
In general, only request a small number of tags; a maximum of 30 per screen
Special features of the data type "STRING" (OPC XML)
Only valid ASCII values from 0x20hex to 0x7Fhex are supported in the data type "STRING".
Special features of the data type "Date/Time" (OPC XML)
Values of the data type "Date/Time" are always expected as UTC (Universal Time
Coordinated) by the OPC-Gateway. If a tag of the type "Date/Time" is read by the OPC client,
the returned value is a time in UTC. If a value is written to the tag, the value is treated as UTC.
The time including the time zone and daylight saving time are shown as "local time" on an HMI
device.
Example:
The time zone GMT+1 and daylight saving time is set on the HMI device.
OPC DA client (UTC time): 01.01.2005 16:00
Display on the HMI device (OPC server): 01.01.2005 18:00
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2703
Supported OPC UA services of the OPC UA client
OPC UA Services support
The OPC UA client supports the following OPC UA services:
SecurityPolicy - Basic128Rsa15
SecurityPolicy - Basic256
SecurityPolicy - None
DataAccess ClientFacet
You can additional information about OPC UA services in the "OPC UA Part 3 - Address Space
Model 1.01 Specification" document under "5.6".
Explanation of the security settings
The following table lists the security settings supported by the OPC UA client:
SecurityPolicy Message Security Mode
None
1
None
Basic128Rsa15
2
None
4
Sign
5
SignAndEncrypt
6
Basic256
3
None Sign SignAndEncrypt
1: The certificate exchange is disabled. Every OPC UA client can log on to the WinCC OPC UA server. This setting can be
disabled on each OPC UA server.
2: Certificate exchange with depth of encryption of 128 bit.
3: Certificate exchange with depth of encryption of 256 bit.
4: The data packages are exchanged after certificate check unsecured between client and server.
5: The data packages are signed with the certificates, but not encoded
6: The data packages are signed with the certificates and encoded
NOTICE
Unsecured communication between client and server possible
Use the "none" setting only for test and diagnostics purposes.
For a secure communication between client and server, use in operating mode at least the
following settings:
SecurityPolicy: Basic128Rsa15
Message Security Mode: Sign
See also
Creating a connection to an OPC UA server (Page 2698)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2704 System Manual, 08/2011,
9.16.1.2 OPC for Runtime Professional
Basics
OPC
OPC refers to standardized manufacturer-specific software interfaces for data exchange in
automation engineering.
The OPC interfaces provide a standardized environment in which devices and applications
from various manufacturers can be linked.
OPC is based on the Windows technology COM (Component Object Model) and DCOM
(Distributed Component Object Model).
In addition, OPC XML DA offers a further software interface that is based on the Internet
standards XML, SOAP, and HTTP.
OPC UA (Unified Architecture) is the technology succeeding OPC. OPC UA is platform-
independent and can use different reports as a communication medium.
See also
Using OPC in WinCC (Page 2706)
OPC Specifications (Page 2705)
Compatibility (Page 2706)
OPC Specifications
OPC specifies interfaces to gain access to the following objects in WinCC:
Process values (OPC Data Access 2.05a, 3.0; OPC XML Data Access 1.01; OPC UA 1.01)
Log process values (OPC Historical Data Access 1.20; OPC UA 1.01)
Logged alarms (OPC Historical Alarms and Events v0.92)
Alarms (OPC Alarms and Events 1.10)
For detailed information about the individual OPC specifications, refer to the website of OPC
Foundation.
*: Draft from Siemens, which is available on the OPC Foundation website.
See also
Using OPC in WinCC (Page 2706)
OPC Foundation (www.opcfoundation.org)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2705
Compatibility
Support of the mentioned specifications is checked regularly by the "Compliance Test Tool"
(CTT) of the OPC Foundation. Interoperability with OPC products of other manufacturers is
ensured through the participation in "OPC Interoperability Workshops".
The test results submitted are published on the website of the OPC Foundation. The results
can be called up from there using the search term "OPC Self-Certified Products".
See also
OPC (Page 2705)
Licensing
Licensing
For the operation of one of the supported WinCC OPC servers, the following license must be
installed:
WinCC Basic System
Using OPC in WinCC
Introduction
On a HMI device with "WinCC Runtime Professional" there are server for the following OPC
interfaces available:
OPC Data Access / OPC XML Data Access: Access to the data management of WinCC
OPC Historical Data Access: Access to the WinCC log system
OPC Alarms&Events: Access to the WinCC alarm system
OPC Unified Architecture: Access to the data management and the WinCC log system
In addition, there is by default in WinCC an OPC channel that can access the corresponding
OPC data access server as client via OPC DA or OPC XML DA.
All WinCC OPC servers are certified by the OPC Foundation.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2706 System Manual, 08/2011,
OPC communication concept of WinCC
The following screen shows the OPC communication concept of WinCC:
External system
For example, a different automation system,
Control of a third provider or a control system
WinCC OPC DA channel
OPC DA server
user-defined
OPC DA client
Process values (tags)
Archived process values (logging tags)
Alarms
W
i
n
C
C
R
u
n
t
i
m
e
P
r
o
f
e
s
s
i
o
n
a
l
W
i
n
C
C
O
P
C
s
e
r
v
e
r
customer-specific
OPC HDA client
customer-specific
OPC-A&E-Client
customer-specific
OPC UA client
OPC XML DA service
Ethernet/TCP/lP
WinCC OPC DA
WinCC OPC XML DA WinCC OPC A&E WinCC OPC HDA
WinCC OPC UA
See also
Licensing (Page 2706)
Functionality of the WinCC OPC DA Server (Page 2709)
Functionality of WinCC OPC XML DA server (Page 2709)
Functionality of the WinCC OPC HDA server (Page 2711)
Functionality of the WinCC OPC A&E server (Page 2720)
Principle of operation the WinCC OPC UA Server (Page 2738)
Creating a connection to an OPC server (Page 2747)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2707
Configuration
Basic settings for OPC
Introduction
For the following WinCC OPC servers, you configure the basic settings on the configuration
PC for OPC in the HMI device runtime settings:
OPC HDA
OPC A&E
OPC UA
Basic settings for OPC
For HMI devices with Runtime Professional, you define the following in the runtime settings:
OPC settings
You configure the following in this category:
Exception rules for the validation of writing access to log data
Security concept of the WinCC OPC UA server
Alarms
In this category you configure the mapping of the WinCC alarm system for the alarm
behavior of the following WinCC OPC servers:
OPC A&E
See also
Configure WinCC OPC HDA Server (Page 2719)
Configure WinCC OPC A&E server (Page 2731)
Configure WinCC OPC UA Server (Page 2746)
WinCC OPC server
Accessibility of WinCC OPC servers
Client-specific OPC clients data from the WinCC data management are available for the
WinCC OPC servers, for example, process values or alarms.
In order to access a WinCC OPC server, you must activate the related WinCC project on the
HMI device.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2708 System Manual, 08/2011,
WinCC OPC DA Server
Functionality of the WinCC OPC DA Server
Principle of operation
The WinCC OPC DA server enables any OPC DA client to access process values from the
data management of WinCC.
Supported specifications
The WinCC OPC A&E Server supports OPC Data Access 2.05a and 3.0.
ProgID of the WinCC OPC DA servers
You access the WinCC OPC DA server via the following ProgID:
"OPCServer.WinCC_SCADA".
Quality codes
The "Quality Code" delivers information on the status and quality of the process values. For
more information, refer to the "OPC Data Access 3.0" specification.
See also
Using OPC in WinCC (Page 2706)
Accessibility of WinCC OPC servers (Page 2708)
Licensing (Page 2706)
WinCC OPC XML DA server
Functionality of WinCC OPC XML DA server
Principle of operation
WinCC's OPC XML DA Server is implemented as a web service of Microsoft Internet
Information Server (IIS). The OPC XML DA client accesses the OPC XML DA server via an
internet protocol to which process values from the data management of WinCC are available.
Supported specifications
The WinCC OPC XML DA Server supports the specification OPC XML Data Access 1.01.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2709
"OPC XML Data Access" is a standard that supports communication over the Internet by
means of platform-independent protocol (SOAP/XML). The data access via OPC XML Data
Access has an OPC Data Access leaning on the scope of operation.
URL of the WinCC OPC XML DA servers
You access the WinCC OPC XML DA server via the following URL: "http://<xxx>/WinCC-OPC-
XML/DAWebservice.asmx"
<xxx>: IP address or DNS name of the OPC XML DA server
Note
If automatic detection of settings is enabled on a PC for the internet options under
Connections > LAN Settings", access to OPC XML DA through the web service will be slowed
considerably.
Quality codes
The "Quality Code" delivers information on the status and quality of the process values. For
more information, refer to the "OPC XML Data Access1.01" specification.
Special features of tags of "String" type
If you use tags of "string" type that logically stand for floating point values, there can be
problems when OPC clients want to write and read.
Description
An OPC client writes to a string tag and does not enter the new value in the form of a string
but as float, double or decimal.
Problem
The comma that indicated the decimal value (in German) can be lost. This will result in a wrong
value. This behavior also occurs when string tags are read if the value being read is requested
in float, double, or decimal format.
Remedy
Only use the respective floating point tags for the floating point values. Get string tags only in
string format.
See also
Using OPC in WinCC (Page 2706)
Accessibility of WinCC OPC servers (Page 2708)
Installing WinCC OPC XML DA Server (Page 2711)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2710 System Manual, 08/2011,
Installing WinCC OPC XML DA Server
Introduction
To install the OPC XML DA server automatically in the framework of the WinCC setups, the
following settings on the HMI device must be fulfilled:
Internet Information Service (IIS) is installed
Microsoft .NET-Framework 2.0 is installed
If the requirements are not fulfilled, you must install the OPC XML DA server separately after
you have installed the IIS and .Net-Framework 2.0. To avoid problems during installation, follow
in any case the steps described below.
Procedure
To configure the OPC XML DA server on the HMI device, proceed as follows:
1. Install the "Microsoft Internet Information Service (IIS)".
2. Install the "Microsoft .NET-Framework 2.0".
3. Install the WinCC OPC XML DA Server via the WinCC setup.
4. Test the installation on the OPC server:
Launch Internet Explorer on the PC running as the WinCC OPC XML Server.
On the address bar enter the URL "http://localhost/WinCC-OPC-XML/
DAWebservice.asmx".
If a page with the supported operations is displayed in Internet Explorer, the installation
was successful.
See also
Functionality of WinCC OPC XML DA server (Page 2709)
WinCC OPC HDA Server
Functionality of the WinCC OPC HDA server
Principle of operation
The WinCC OPC HDA server enables any OPC HDA client to access process values from the
data management of the WinCC log system.
Supported specifications
The WinCC OPC HDA Server supports the OPC Historical Data Access 1.20 specification.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2711
ProgID of the WinCC OPC HDA server
You access the WinCC OPC HDA server via the following ProgID:
"OPCServerHDA.WinCC_SCADA".
Quality codes
The "Quality Code" delivers information on the status and quality of the raw data. For more
information, refer to the "OPC Historical Data Access 1.20" specification.
Documentation contents
The WinCC OPC HDA Server documentation contains the following information:
An overview of the data structure
An overview of supported attributes, aggregates, and functions
For more information about the OPC HDA Server, refer to the "OPC Historical Data Access
1.20" specification.
See also
Using OPC in WinCC (Page 2706)
Accessibility of WinCC OPC servers (Page 2708)
Overview of the supported attributes (Page 2716)
Overview of the supported assemblies (Page 2717)
Overview of the supported interfaces and functions (Page 2718)
Configure WinCC OPC HDA Server (Page 2719)
Supported Write-Accesses
Introduction
By default, any OPC HDA client can change process values in a data log. The tag log validates
the data and inserts them to their corresponding time stamp.
If you frequently change a lot of process values, you can use the configuration dialog on the
conifguration PC to deactivate the validation of the process values during writing to the data
log. You speed up the large writing of process values in this way. The OPC HDA client must
sort the data themselves chronologically, otherwise the data is not accepted.
Note
Deactivate writing access
You can completely deactivate the writing via the WinCC OPC HDA server from log data via
the (user-defined) WinCC setup.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2712 System Manual, 08/2011,
Write Accesses
An OPC HDA client does not have generally writing access to the following data logs.
Compressed logs
Data logs in main memory
Swapped logs
The following table shows the supported writing accesses for a process value log on the hard
disk of a HMI device:
Action Writing in process value log allowed?
Adding process values later Yes
1)
Adding process values in Runtime Yes
2)
Inserting future process values No
Replace process values (Replace) Yes
Deleting process values Yes
1)
1: If the time period is contained in the circular log.
2: The process value is added in the data buffer currently valid for the process value log.
See also
Storing Process Values (Page 1140)
Swapping Out Process Values (Page 1142)
Special features of the OPC HDA server in WinCC for acyclic logging (Page 2714)
Configure WinCC OPC HDA Server (Page 2719)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2713
Special features of the OPC HDA server in WinCC for acyclic logging
Introduction
In WinCC. tags are logged cyclically or acyclically. The WinCC OPC HDA Server works
differently depending on the logging method for tags:
For all cyclically logged values, the OPC HDA Server operates in conformity to the HDA
specification of the OPC foundation. The OPC aggregates are linearly interpolated.
Acyclically logged tags are not included in the HDA specification of the OPC Foundation.
The OPC aggregates are interpolated incrementally. If a tag value has not changed for a
long period of time, no data are available during this time due to the interpolation.
To obtain valid data in spite of this, take note of the following particularities:
NOTICE
The OPC HDA Server is not OPC-compliant for acyclically logged tags. The OPC
Foundation's HDA specification does not cover acyclically logged tags and therefore does
not support log servers for acyclically logged tags. The supported aggregates are
calculated in conformity to the OPC HDA specification. No non-explicitly called functions
are supported.
Configuration of acyclically logged tags
When configuring acyclically logged tags, enable the "Log after segment change" option. This
enters the most recent valid value in the the new log when a segment changes.
Supported aggregates of the WinCC OPC HDA Server for acyclically logged tags
The OPC HDA Server supports the following aggregates:
OPCHDA_MINIMUM
OPCHDA_MAXIMUM
OPCHDA_AVERAGE
OPCHDA_END
OPCHDA_INTERPOLATIVE
OPCHDA_TIMEAVERAGE
OPCHDA_TOTAL
OPCHDA_DURATIONGOOD
OPCHDA_PERCENTGOOD
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2714 System Manual, 08/2011,
Supported functions of the WinCC OPC HDA Server for acyclically logged tags
ReadRaw only with "Boundings". To find the last value actually saved in an area where
value changes are not logged, always use "Boundings" when executing "ReadRaw" on a
tag.
ReadProcessed
DeleteRaw
DeleteAtTime
Insert
InsertReplace
Replace
Calculating the aggregates for acyclically logged tags
The calculation of the aggregates is based on an extended data record of raw data. The
extended data record contains not only actually stored values, but also virtual data points for
calculation. The WinCC OPC HDA Server prepares the raw data received according to the
requirements of "ReadProcessed". The virtual data points needed for the calculation are
formed from the bordering real data points. The following significant points are generated for
virtual data points:
Value for "StartTime"
Value for "EndTime"
Value for interval limits
Example
The values for "00:59:00", "01:02:00" and "01:03:00" are stored for an acyclical logging tag.
An OPC HDA Client uses "ReadProcessed" to request an aggregate with the following
parameters:
StartTime = 01:00:00
EndTime = 01:04:00
Interval = 00:02:00
Note
When generating virtual values at limits ("EndTime"/"Interval"), the time frame used for
the calculation is always 1 s less than the time stamp at the limit.
For the sake of clarity, a delta of 1 second is used in the following table. The OPC server uses
the following raw data to calculate the aggregate:
Number Time stamp Real stored values Generated virtual values
1 00:59:00 1.00
2 01:00:00 1.00
3 01:01:59 1.00
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2715
Number Time stamp Real stored values Generated virtual values
4 01:02:00 2.00
5 01:02:59 2.00
6 01:03:00 3.00
7 01:03:59 3.00
The following figure elucidates the example:
1 2
2
3
3
Real values
Virtual values
Interval start
Interval end
Value change
See also
Supported Write-Accesses (Page 2712)
Overview of the supported attributes (Page 2716)
Overview of the supported assemblies (Page 2717)
Overview of the supported interfaces and functions (Page 2718)
Overview of the supported attributes
The following table contains the attributes supported by the WinCC OPC HDA Server. For
more information, refer to the "OPC Historical Data Access 1.20" specification.
Attributes
Attribute Attribute ID Description
ItemID OPCHDA_ITEMID Indicates the WinCC logging tag to be accessed.
Item Datatype OPCHDA_DATA_TYPE Indicates the data type of the WinCC logging tag.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2716 System Manual, 08/2011,
Attribute Attribute ID Description
Description OPCHDA_DESCRIPTIO
N
Returns a description of the WinCC logging tag. You
define the description in the "HMI Tags" editor.
Engineering
Units
OPCHDA_ENG_UNITS Sets the display of measurement units. You define the
display in the "HMI Tags" editor.
See also
Functionality of the WinCC OPC HDA server (Page 2711)
Special features of the OPC HDA server in WinCC for acyclic logging (Page 2714)
Overview of the supported assemblies
The following table lists the aggregates supported by the WinCC OPC HDA Server. For more
information, refer to the "OPC Historical Data Access 1.20" specification.
Assemblies
Assembly Description
OPCHDA_COUNT Detects the raw data count for the specified time interval.
OPCHDA_START Detects the initial value of the raw data at the beginning of
the start time interval.
OPCHDA_END Detects the end value of the raw data at the end time interval.
OPCHDA_AVERAGE Detects the raw data mean value for the specified time
interval.
OPCHDA_TIMEAVERAGE Detects the time-weighted raw data mean value for the
specified time interval.
OPCHDA_TOTAL Returns the sum total value for the specified time interval.
OPCHDA_STDEV Detects the raw data standard deviation for the specified time
interval.
OPCHDA_MINIMUMACTUALTIME Returns the minimum value of the raw data time stamp for
the specified time interval.
OPCHDA_MINIMUM Detects the raw data minimum value for the specified time
interval.
OPCHDA_MAXIMUMACTUALTIME Detects the maximum value and the raw data time stamp for
the specified time interval.
OPCHDA_MAXIMUM Detects the raw data maximum value for the specified time
interval.
OPCHDA_DELTA Detects the difference between the first and the last value of
the raw data for the specified time interval.
OPCHDA_REGSLOPE Detects the slope of the regression line of the raw data for
the specified time interval.
OPCHDA_REGCONST Detects the regression line value of the raw data at the
starting point.
OPCHDA_REGDEV Detects the slope of the regression line of the raw data for
the specified time interval.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2717
Assembly Description
OPCHDA_VARIANCE Detects the raw data variance for the specified time interval.
OPCHDA_RANGE Detects the difference between OPCHDA_MAXIMUM and
OPCHDA_MINIMUM of the raw data for the specified time
interval.
OPCHDA_DURATIONGOOD Detects the period of time in which the quality of the raw data
was good. The period is indicated in seconds.
OPCHDA_DURATIONBAD Detects the period of time in which the quality of the raw data
was bad. The period is indicated in seconds.
OPCHDA_PERCENTGOOD Detects the percentage of the raw data of good quality.
OPCHDA_PERCENTBAD Detects the percentage of the raw data of bad quality.
OPCHDA_WORSTQUALITY Detects the raw data worst quality for the specified time
interval.
See also
Functionality of the WinCC OPC HDA server (Page 2711)
Special features of the OPC HDA server in WinCC for acyclic logging (Page 2714)
Overview of the supported interfaces and functions
The WinCC OPC HDA Server supports the following interfaces:
IOPCHDA_Server
IOPCHDA_SyncRead (no "ReadModified" method)
IOPCHDA_SyncUpdate
IOPCHDA_AsyncRead (no "ReadModified" method)
IOPCHDA_AsyncUpdate
IOPCCommon
For more information about the interfaces, refer to the "OPC Historical Data Access 1.20"
specification.
See also
Functionality of the WinCC OPC HDA server (Page 2711)
Special features of the OPC HDA server in WinCC for acyclic logging (Page 2714)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2718 System Manual, 08/2011,
Configure WinCC OPC HDA Server
Introduction
On the configuration PC, define in the configuration settings for the WinCC OPC HDA server
whether specific users or OPC HDA clients may change process values in the data logs without
validation.
NOTICE
The configuration settings apply for the WinCC OPC HDA server as well as for the OPC UA
server.
Note
Deactivated writing access
If the writing access of OPC HDA clients was deactivated on the data logs in (user-defined)
WinCC setup, these settings are ignored.
Procedure
To configure WinCC OPC HDA server, proceed as follows:
1. Open the "Runtime settings" of the HMI device in the project tree.
2. Define under "OPC settings" which users or OPC clients may change process values in
the data logs without validation:
To fully disable validation, select "Disable validation of the data during write access for
selected OPC clients".
To deactivate the validation for single users or OPC clients, double-click "Insert" in the
corresponding table. Enter the name of the user or the OPC client.
To re-select the validation for a single user or OPC client, clear the option in front of the
respective user or OPC client.
See also
Functionality of the WinCC OPC HDA server (Page 2711)
Basic settings for OPC (Page 2708)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2719
WinCC OPC A&E server
Functionality of the WinCC OPC A&E server
Principle of operation
The WinCC OPC A&E server enables the access to alarms of the WinCC alarm system. The
OPC A&E Client is kept informed of status changes for WinCC alarms via Subscriptions. To
avoid displaying all alarms and attributes on the OPC A&E client, configure in the Subscription
filter.
Supported specifications
OPC Alarm & Events is a specification for the transmission of alarms and events. The WinCC
OPC A&E Server supports the OPC Alarms&Events 1.10 specification.
In addition, the WinCC OPC A&E Server also supports access to historical alarms in
accordance with the Siemens draft "OPC Historical Alarms and Events v0.92".
ProgID of the WinCC OPC A&E server
You access the WinCC OPC A&E server via the following ProgID:
"OPCServerAE.WinCC_SCADA".
Quality codes
The "Quality Code" delivers information on the status and quality of an alarm. For more
information, refer to the "OPC Alarms&Events 1.10" specification.
OPC A&E Server mapping rules
To map the WinCC alarm system on OPC Alarms&Events, the WinCC OPC A&E server
supports three mapping rules "Mode 1" to "Mode 3".
"Mode 1" and "Mode 2" are supported because of compatibility reasons to WinCC OPC A&E
server version 3.52 and earlier. "Mode 1" and "Mode 2" do not have a restricted scope of
operation.
"Mode 3" widens the restricted scope of operation of "Mode 1" and "Mode 2".
Documentation contents
The WinCC OPC A&E Server documentation contains the following information:
A mapping of the alarm system on OPC A&E
An overview of supported attributes
For more information, refer to the "OPC Alarm&Events 1.10" specification.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2720 System Manual, 08/2011,
See also
Using OPC in WinCC (Page 2706)
Accessibility of WinCC OPC servers (Page 2708)
OPC A&E Server mapping rules (Page 2721)
Mapping rule "Mode 1": (Page 2727)
Mapping rules "Mode 2": (Page 2727)
Mapping rules "Mode 3": (Page 2728)
Restrictions for Mode 1 and Mode 2 (Page 2728)
Access to logged events (Page 2733)
OPC A&E Server mapping rules
General rules
OPC A&E Server mapping rules
During the configuration of the WinCC message system, settings are made to determine which
process events generate a message. This message is shown as an alarm in OPC A&E.
The following table shows the most important parameters of the alarm and how the WinCC
alarm system prepares the information:
OPC WinCC message system Type of event
Source Source where the alarm was issued. The source has the
format "<server prefix>::@LOCALMACHINE::".
S, C
Time Time of the event. Issues a time stamp in UTC (Universal
Time Coordinated).
S, C
EventType Type of event. The WinCC OPC A&E Server supports
"Simple Events" and "Condition Related Events".
S, C
Severity Priority of the alarm from WinCC S, C
EventCategory Category of the alarms. For more information on this topic,
refer to "Displaying Message Classes and Types".
S, C
Message Alarm text for the corresponding alarm number. S, C
ConditionName Specified text that is delivered to the alarm additionally.
Which text is returned, depends on the configured display
rules:
"Mode 1" and "Mode 2": Alarm number.
"Mode 3": Alarm method, for example "Analog alarm".
C
SubConditionName Corresponds "ConditionName", because WinCC
supports no Multi-State Conditions.
C
ChangeMask Changed status of the alarm. For more information, refer
to "Acknowledgment Theory".
C
NewState Status of the alarm. For more information, refer to
"Acknowledgment Theory".
C
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2721
OPC WinCC message system Type of event
ConditionQuality Returns the quality of the message. For more information,
refer to "Quality Codes".
C
AckRequired Indicates whether the message requires
acknowledgment.
C
ActiveTime Returns the time stamp for received messages. C
EventAttribute Lists the attributes required for the respective message.
For more information, refer to "Attributes of the WinCC
Message System".
C
Quality Returns the quality code of the message. C
Cookie Returns the cookie from the OPC A&E Server. C
ActorID Returns the logged user. C
S = "Simple Event"
C = "Condition Related Event"
See also
Acknowledgement theory (Page 2723)
Quality Codes for OPC A&E (Page 2725)
Attributes (Page 2725)
Priorities (Page 2730)
Alarm classes and alarm methods (Page 2729)
Alarm Logging in WinCC (Page 1235)
Alarm components and properties (Page 1258)
OPC A&E types of event (Page 2722)
OPC A&E types of event
Introduction
The WinCC OPC A&E Server supports "Condition Related Events" and "Simple Events".
Condition Related Events
"Condition Related Events" are alarms triggered by a condition. such as the limit violation of
a tag, which is then output as an alarm on the HMI device. A "Condition Related Event"contains
additionally the "Alarm" attribute.
By default, each alarm as "Condition Related Event" is sent to the OPC A&A client.
Simple Events
As "Simple Events" all other alarms are treated, which cannot be assigned to the "Condition
Related Event" type of event.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2722 System Manual, 08/2011,
In order for an alarm to be treated as a "Simple Event", the following prerequisites must be
met when the alarm class is configured:
"Acknowledgment Came In" is not activated.
"Alarm without outgoing state" is activated.
Note
Note the following while using redundant systems:
"Simple Events" that are connected to internal tags are sent twice during tag comparison.
The first alarm is triggered by master, the second by the standby server.
See also
Acknowledgement theory (Page 2723)
OPC A&E Server mapping rules (Page 2721)
Mapping rule "Mode 1": (Page 2727)
Mapping rules "Mode 2": (Page 2727)
Mapping rules "Mode 3": (Page 2728)
Acknowledgement theory
Introduction
For WinCC, the acknowledgment philosophy is how a message is displayed and processed
from "came in" to "went out". On the WinCC OPC A&E Server, this alarm status is managed
in the "ChangeMask" and "NewState" parameters.
ChangeMask
The "ChangeMask" parameter keeps track of where the alarm status changed.
Parameter values:
OPC_CHANGE_ACTIVE_STATE
OPC_CHANGE_ENABLE_STATE
OPC_CHANGE_ACK_STATE
NewState
The "NewState" parameter indicates the alarm status after a change.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2723
Parameter values:
OPC_CONDITION_ACTIVE
OPC_CONDITION_ENABLED
OPC_CONDITION_ACKED
Overview
The following table shows how WinCC alarm statuses are mapped to the "NewState" and
"ChangeState" OPC parameters:
WinCC NewState ChangeState
Received message OPC_CONDITION_ACTIVE
OPC_CONDITION_ENABLED
OPC_CHANGE_ACTIVE_STAT
E
Sent message with receipt OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACTIVE_STAT
E
Sent alarm without
acknowledgment
OPC_CONDITION_ENABLED OPC_CHANGE_ACTIVE_STAT
E
Acknowledged messages
(message pending)
OPC_CONDITION_ACTIVE
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Acknowledged messages
(message no longer pending)
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Locked message - OPC_CHANGE_ENABLED_STA
TE
Unlocked message OPC_CONDITION_ENABLED OPC_CHANGE_ENABLED_STA
TE
Received, acknowledged
message
OPC_CONDITION_ACTIVE
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACTIVE_STAT
E
Received, sent message with
receipt
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Incoming, sent alarm without
acknowledgment
OPC_CONDITION_ENABLED OPC_CHANGE_ACK_STATE
Message acknowledged by the
system (message pending)
OPC_CONDITION_ACTIVE
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Message acknowledged by the
system (message no longer
pending)
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Emergency-acknowledged
message (message pending)
OPC_CONDITION_ACTIVE
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Emergency-acknowledged
message (message no longer
pending)
OPC_CONDITION_ACKED
OPC_CONDITION_ENABLED
OPC_CHANGE_ACK_STATE
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2724 System Manual, 08/2011,
See also
OPC A&E types of event (Page 2722)
Quality Codes for OPC A&E
The "Quality Code" is required to evaluate the status and quality of an alarm.
Quality codes
OPC A&E's quality codes are presented in the following table:
Code Quality Status
0xC0 OPC_GOOD OK
0x40 OPC_UNCERTAIN Discrepancies, resulting from delayed
acknowledgment, for example
0x00 OPC_BAD Connection to source is interrupted
Attributes
The following table lists the OPC attributes of the WinCC message system. You can configure
the attributes in the "Alarms" editor. Some attributes are intended for internal use in WinCC
only and are therefore not relevant to an OPC A&E Client. These attributes are not listed.
OPC attribute WinCC message system Data type
CLASSNAME Returns the alarm class name. VT_BSTR
TYPENAME Returns the alarm method type name. VT_BSTR
FORECOLOR Returns the text color for received, sent and acknowledged alarms. VT_I4
BACKCOLOR Returns the background color for received, sent and acknowledged
alarms.
VT_I4
FLASHCOLOR Returns the flashing color. VT_I4
FLAGS Indicates whether the message requires acknowledgment. VT_I4
TEXT01 Returns the content of UserTextBlock01. VT_BSTR
TEXT02 Returns the content of UserTextBlock02. VT_BSTR
TEXT03 Returns the content of UserTextBlock03. VT_BSTR
TEXT04 Returns the content of UserTextBlock04. VT_BSTR
TEXT05 Returns the content of UserTextBlock05. VT_BSTR
TEXT06 Returns the content of UserTextBlock06. VT_BSTR
TEXT07 Returns the content of UserTextBlock07. VT_BSTR
TEXT08 Returns the content of UserTextBlock08 VT_BSTR
TEXT09 Returns the content of UserTextBlock09 VT_BSTR
TEXT10 Returns the content of UserTextBlock10 VT_BSTR
PROCESSVALUE01 Returns the content of ProcessValueBlock01 VT_VARIANT
PROCESSVALUE02 Returns the content of ProcessValueBlock02 VT_VARIANT
PROCESSVALUE03 Returns the content of ProcessValueBlock03 VT_VARIANT
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2725
OPC attribute WinCC message system Data type
PROCESSVALUE04 Returns the content of ProcessValueBlock04 VT_VARIANT
PROCESSVALUE05 Returns the content of ProcessValueBlock05 VT_VARIANT
PROCESSVALUE06 Returns the content of ProcessValueBlock06 VT_VARIANT
PROCESSVALUE07 Returns the content of ProcessValueBlock07 VT_VARIANT
PROCESSVALUE08 Returns the content of ProcessValueBlock08 VT_VARIANT
PROCESSVALUE09 Returns the content of ProcessValueBlock09 VT_VARIANT
PROCESSVALUE10 Returns the content of ProcessValueBlock10 VT_VARIANT
STATETEXT Returns the status alarm VT_BSTR
INFOTEXT Returns the information text for the alarm VT_BSTR
LOOPINALARM Indicates if loop-in alarm has been configured. VT_I4
CLASSID Returns the alarm class ID VT_I4
TYPEID Returns the message type ID VT_I4
MODIFYSTATE Returns the value of the status tag of the alarm VT_I4
AGNR Returns the number of the automation system that generated the
alarm
VT_I2
CPUNR Returns the number of the CPU that generated the alarm VT_I2
DURATION Indicates the period of time between alarm received, sent and
acknowledged
VT_I4
COUNTER Returns the number of alarms after the start of Runtime VT_I4
QUITSTATETEXT Indicates whether the alarm has been acknowledged VT_BSTR
QUITCOUNT Returns the number of active, unacknowledged alarms VT_I4
PARAMETER Outputs the message parameter. (Image of the message
configuration)
VT_BSTR
BLOCKINFO Returns the current content of the alarm block VT_BSTR
ALARMCOUNT Outputs the number of alarms pending VT_I4
LOCKCOUNT Returns the number of locked alarms VT_I4
PRIORITY Indicates the configured priority of the alarm VT_I4
APPLICATION Returns the application which triggered the alarm VT_BSTR
COMPUTER Returns the name of the computer which processed the alarm VT_BSTR
USER Returns the name of the user who processed the alarm VT_BSTR
COMMENT Returns the alarm comment VT_BSTR
HIDDEN-COUNT* Number of locked alarms VT_I4
OS-HIDDEN* Indicates whether the alarm is locked VT_BOOL
OS_EVENTID* Indicates the WinCC alarm number VT_I4
BIG_COUNTER* Alarm counter VT_CY
UNIQUE EVENT ID* corresponds to the "BIG_COUNTER" VT_CY
*: Are supported only by "Mode 3".
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2726 System Manual, 08/2011,
See also
Alarm classes and alarm methods (Page 2729)
Mapping rule "Mode 1": (Page 2727)
Mapping rules "Mode 2": (Page 2727)
Mapping rules "Mode 3": (Page 2728)
Mapping rule "Mode 1":
"Mode 1" displays the whole WinCC alarm system under a "OPC Source" with the name
"localhost::" The "TEXT01" WinCC attribute is written in the OPC alarm text.
The WinCC alarm number is displayed on the "Condition" of the WinCC OPC A&E server.
"Mode 1" supports the "Simple Events" and "Condition Related Events" types of event. Events
can be filtered according to the "Event Type", "Category" and "Severity" criteria.
See also
Restrictions for Mode 1 and Mode 2 (Page 2728)
Attributes (Page 2725)
OPC A&E types of event (Page 2722)
Configure WinCC OPC A&E server (Page 2731)
Alarm classes and alarm methods (Page 2729)
Priorities (Page 2730)
Mapping rules "Mode 2":
"Mode 2" is implemented as of version 3.5.2. of the WinCC OPC A&E server. The WinCC
alarm number is displayed on the "Condition" of the WinCC OPC A&E server.
The text attribute of the WinCC alarm ("TEXT01" to "TEXT10") you have configured, is written
in the OPC alarm text of "OPC Source".
"Mode 2" supports the "Simple Events" and "Condition Related Events" types of event. Events
can be filtered according to the "Event Type", "Category" and "Severity" criteria.
See also
Restrictions for Mode 1 and Mode 2 (Page 2728)
Attributes (Page 2725)
OPC A&E types of event (Page 2722)
Configure WinCC OPC A&E server (Page 2731)
Alarm classes and alarm methods (Page 2729)
Priorities (Page 2730)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2727
Mapping rules "Mode 3":
"Mode 3" is implemented as of version 3.6 of the WinCC OPC A&E server. "Mode 3" supports
the hierarchical mapping of user-defined alarms. The hierarchy of "OPC Areas" is set by the
user-defined alarm groups.
With "Mode 3" you query the address space of the WinCC OPC A&E server according to
"Areas" and "Sources".
"Mode 3" supports the "Simple Events" and "Condition Related Events" types of event. Events
can be additionally filtered according to the "Area" and "Source" criteria. "Mode 3" supports
the "System Message" OPC category.
See also
Attributes (Page 2725)
OPC A&E types of event (Page 2722)
Configure WinCC OPC A&E server (Page 2731)
Priorities (Page 2730)
Restrictions for Mode 1 and Mode 2
Notes on mapping rules "Mode 1" and "Mode 2":
The mapping rules for "Mode 1" and "Mode 2" contain significant restrictions. The mapping
rules for "Mode 1" and "Mode 2" are therefore only because of compatibility reasons supported
by the previous version and are not developed further.
Note
In order to ensure compatibility with the previous version, the WinCC OPC A&E server cannot
use multiplexer.
The restrictions are solved in the mapping rule "Mode 3".
Some of the restrictions of the mapping rules "Mode 1" and "Mode 2" are listed below:
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2728 System Manual, 08/2011,
The WinCC alarm attributes are passed on via the OPC interface.
The IDs value range of WinCC alarm attributes is defined by the OPC specification by
"Property sets":
ID Set 1 contains the "OPC-specific Properties". Range: 1 99
ID Set 2 contains the "Recommended Properties". Value range 100 to 199
IDs 300399 are especially reserved for OPC A&E
IDs 400 to 4999 are reserved by OPC.
ID Set 3 contains the "Vendor-specific Properties". Range: 5000 and higher
The IDs of the WinCC attributes must have values from 5000 and higher.
Mode 1 and Mode 2 pass on the IDs of the WinCC alarm attributes via the OPC interface.
These IDs are in the range of 0 to 61.
If an OPC client, for example, requires the attribute with the IDs 2 ("Item Value") and 3
("Item Quality") from the WinCC OPC A&E server, the OPC client receives instead the
corresponding WinCC alarm atrocities. In this case the attributes are "ForeColor" and
"BackColor".
Restrictions for transfer of WinCC alarm numbers
Alarm numbers are only transferred as text in the "Condition" when "Condition Related
Events". When "Simple Events", the alarm numbers are completely lost.
Some WinCC attributes are not supported, for example "UNIQUE_EVENT_ID"
You can use the "UNIQUE_EVENT_ID" attribute for alarm synchronization of redundant
server couples. During switching between redundant servers, the following could happen:
Alarms can be double- transferred
Alarms can be lost
You can find an overview of all attributes supported by the different modes at "Attributes
(Page 2725)".
See also
Mapping rule "Mode 1": (Page 2727)
Mapping rules "Mode 2": (Page 2727)
Alarm classes and alarm methods
Introduction
The WinCC message system informs the user of disturbances and operating conditions in the
process. A WinCC alarm always belongs to a specific alarm class and alarm method that is
related to the "Event Category".
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2729
Event Category
Note
"Event Category" depends on the set mapping rules
The characteristics of the mapping rules "Mode 1" and "Mode 2" are described below:
An "Event Category" is displayed on the WinCC OPC A&E Server for every combination of an
alarm class and alarm method.
An "Event Category" is determined by a "CategoryID" and a descriptive "Category Description".
The "CategoryID" consists of the WinCC-internal ID of an alarm class and alarm method. The
"Category Description" comes from the names of the alarm class and alarm method.
The names of the alarm classes and alarm methods can be ascertained explicitly via the alarm
attributes "CLASSNAME" and "TYPENAME".
See also
Mapping rules "Mode 2": (Page 2727)
Mapping rule "Mode 1": (Page 2727)
Priorities
Introduction
The priority of WinCC alarms is displayed by the WinCC OPC A&E server on the "Severity"
attribute.
You can configure up to 17 priority levels in WinCC. The "Severity" OPC attribute has a value
range from "1" to "1000":
1: Lowest priority
1000: Highest priority
Depending on the number of the configured WinCC priority levels, the value in the "Severity"
attribute is automatically retrieved by linear scaling.
Exception: For the mapping rules "Mode 1", the priority levels configured in WinCC are
displayed directly on the "Severity" attribute.
Example
If you do not change the default settings in the configuration settings of the WinCC OPC A&E
server, the 17 priority levels are going to be displayed in the WinCC OPC A&E server as follows:
Priority level in WinCC Assigned value in the "Severity" attribute
0 1
1 64
2 127
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2730 System Manual, 08/2011,
Priority level in WinCC Assigned value in the "Severity" attribute
3 190
... ...
15 937
16 1000
See also
Mapping rule "Mode 1": (Page 2727)
Mapping rules "Mode 2": (Page 2727)
Mapping rules "Mode 3": (Page 2728)
Description of the System Blocks (Page 1414)
Configure WinCC OPC A&E server
Introduction
Define the display of the WinCC alarm system in the configuration settings of the WinCC OPC
A&E server.
The following screen shows the configuration settings in the "Runtime settings" of the HMI
device:
Requirement
Alarms are configured.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2731
Procedure
To configure WinCC OPC A&E server, proceed as follows:
1. Open the "Runtime settings" of the HMI device in the project tree.
2. Configure the server settings at "Alarms > OPC Alarms & Events":
Define the low and high limit for the display of the priority range.
To activate the WinCC alarms with the mapping rule "Mode 3" in the WinCC OPC A&E,
activate "Activated" and "OPC areas".
Use primarily this setting.
Assign to the "OPC event source" and the "OPC event alarm" respectively an alarm
quality, for example, " User text block 3".
Result
The WinCC alarms are displayed completely in the WinCC OPC A&E. If you have configured
user-defined alarms, areas and sources of the user-defined alarms are displayed in the WinCC
OPC A&E server.
Alternative procedure
You can display alternatively because of compatibility reasons the WinCC alarm also according
to the "Mode 2" and "Mode 1" mapping rules in the WinCC OPC A&E server:
1. To display the WinCC alarms with the mapping rule "Mode 2" in the WinCC OPC A&E
server, activate "Activated" and deactivate"OPC areas".
2. To display the WinCC alarms with the mapping rule "Mode 1" in the WinCC OPC A&E
server, deactivate "Activated" and "OPC areas".
See also
OPC A&E types of event (Page 2722)
Priorities (Page 2730)
Basic settings for OPC (Page 2708)
Mapping rule "Mode 1": (Page 2727)
Mapping rules "Mode 2": (Page 2727)
Mapping rules "Mode 3": (Page 2728)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2732 System Manual, 08/2011,
Accessing logged alarms
Access to logged events
Introduction
You can access the archived messages via the OPC A&E Server using an OPC client. Two
methods are supported for accessing logged alarms:
Output archived messages from a time period in the past
Output archived messages from a time period in the past without mentioning end of period.
After the output of archived messages, all other newly generated messages are
automatically sent to the OPC client.
NOTICE
After reading tagged logs, you are not allowed to use the returned "ActiveTime" of an
alarm to acknowledge the alarm or to track any transitions in the alarm. To ensure this
does not happen, the OPC A&E Client must check the "EventType" of an alarm for the
extra flag "OPC_HAE_HISTORICAL_EVENTFLAG". The "ActiveTime" is not correct on
logged alarms. You can find information on the additional flag under "Identifying archived
messages".
Polling the "Historic alarms and events" functionality
The table below lists the filters offered by the WinCC's extended OPC A&E Server, in addition
to the standard filters:
Filter Filter Values Description
OPC_HAE_FILTER_BY_TIMEFRAME 0x80000000 Corresponds to the "ReadRaw" function
for OPC Historical Data Access
OPC_HAE_FILTER_BY_STARTTIME 0x40000000 Corresponds to the "AdviseRaw"
function for OPC Historical Data Access
Source filter and historical alarm request
In order for you to be able to request logged alarms, the OPC client must support the "SetFilter"
functionality on a Subscription. The OPC server will also send logged alarms if you insert the
keyword "OPCHAEServer" into the array of the "Source Filter" in a Subscription. In addition
to this keyword, you can use other parameters to define which messages are to be read:
Method
Time period
With or without limits
The lists of sources that are assigned in the filter can include other source names besides the
"OPCHAEServer" source. In this a case, the Subscription delivers only the logged events of
the given sources. The sequence of the source names is inconsequential.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2733
After configuring the source filter, you can retrieve the selected time period from the client with
a "Refresh" call.
See also
Identifying logged alarms (Page 2737)
Syntax for accessing logged alarms using OPC (Page 2734)
Read methods for logged alarms (Page 2735)
Syntax for accessing logged alarms using OPC
Syntax
OPCHAEServer hMode=(read|advise) htStartTime=szTime
[hEndTime=szTime] [bBounds=(TRUE|FALSE)]
Parameter
hMode = [read|advise]
Required Defines how the archived messages and events are to be read.
Read
Outputs logged alarms and events of a defined period from the past (comparable to
ReadRaw for OPC Historical Data Access).
The following example shows how a filter is set to read over the past 30 minutes:
OPCHAEServer hMode=read htStartTime=NOW-30M bBounds=TRUE
Advise
Outputs archived messages and events from a definite period, When all logged alarms are
received, new alarms are sent in the same way as for an active subscription (comparable
to AdviseRaw for OPC Historical Data Accesss).
The following example shows how alarms are read from 30 minutes ago until now
(subscription must be active):
OPCHAEServer hMode=advise htStartTime=NOW-30M
Note
The following notation is supported for the parameters "htStartTime" and "htEndTime":
Relative notations such as "NOW"
Symbolic values such as "NOW", "YEAR", "MONTH"
Specification of absolute UTC data/time values according to XML notation:
2006-09-01T10:00:00.000Z
The use of symbolic notation corresponds to the syntax of OPC Historical Data Access.
htStartTime =
Required Defines the time from when the messages and events are to be read from the archive.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2734 System Manual, 08/2011,
htEndTime =
Optional Defines the time up to which the messages and events are to be read from the archive.
For "hMode = read", the default setting "NOW" is used.
bBounds = [TRUE|FALSE]
Optional Defines how messages close to the start and end time are to be handled. The function
is identical to OPC historical data access.
bBounds=FALSE:
Time stamp of the first transferred alarm >= htStartTime
Time stamp of the last transferred alarm < htEndTime
bBounds=TRUE:
Time stamp of the first transferred alarm <= htStartTime
Time stamp of the last transferred alarm >= htEndTime
The default setting is FALSE.
See also
Read methods for logged alarms (Page 2735)
Identifying logged alarms (Page 2737)
Read methods for logged alarms
Introduction
You can use one of the two read modes to read archived messages:
read
advise
"read" mode
"read" mode is used to read logged alarms from a defined period in the past. The sequence
of read messages is always read from the alarms in chronological sequence in reference to
each OS server. By setting the start and end time, you can specify whether the last message
is to be read first or last. If the start time is earlier than the end time, the last message is last
in the output.
If you want to use "read" mode, run the following functions on the subscription:
1. SetFilter
2. Refresh
A "SetFilter" during the "Refresh" will be rejected. Activating the subscription during "Refresh"
does not affect how the Refresh is carried out.
The historic events will continue to be transferred with the Refresh flag.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2735
The newly generated events are transferred according to the standard reaction of an active
subscription:
Taking into account the set filter values with the exception of "historic" source
"OPCHAEServer"
Without the Refresh flag
Enables the client to distinguish between the received events based on the Refresh flag. An
event package never contains historic and new events at the same time.
Event packets with the Refresh flag contain only historic events. These events can also be
in queue.
Event packets without the Refresh flag contain only newly generated events.
"advise" mode
"advise" mode is used to read logged alarms starting from a defined period in the past. After
reading all archived messages, new messages are sent in the same way as for an active
subscription. The archived messages are transferred in chronological sequence in reference
to each OS server: The archived messages from a start time onwards are transmitted.
Thereafter, the newly archived messages transferred.
Note that you are not permitted to define an end time for "advise".
An active subscription is used for "advise" mode. If you run the "SetFilter" function on an active
subscription, the historical alarms are transferred immediately.
If you run the "SetFilter" function on an inactive subscription, the logged alarms are sent only
after the subscription is activated. If you want to use "advise" mode with an inactive
subscription, follow these steps:
1. SetFilter.
2. Set the subscription to "Active" using "SetState".
The transmission is interrupted if you deactivate the subscription.
The transmission is ended if you set the subscription to "inactive". A "SetFilter" is rejected
when the subscription is active.
A "Refresh" on an active "historic" subscription in "advise" mode functions in the same way as
it does for a standard subscription:
All queued condition related events are transferred to packages with Refresh flag. The last
packet also contains an additional "Last Refresh" flag.
A "Refresh" call has no influence on the reading of historical alarms in "advise" mode.
See also
Syntax for accessing logged alarms using OPC (Page 2734)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2736 System Manual, 08/2011,
Identifying logged alarms
General procedure
Logged alarms are distinguished using an additional flag in EventType. This flag is ORed with
the real EventType.
Name EventType EventType (archived message)
OPC_SIMPLE_EVENT 0x01 0x81
OPC_CONDITION_EVENT 0x04 0x84
OPC_TRACKING_EVENT 0x02 0x82
OPC_HAE_HISTORICAL_EVENTFLAG 0x80
Examples
Example 1
The following source filter is used to output logged alarms and events from the past 30 minutes
in "read" mode. The oldest message for each OS server is output as the first one. The low limit
value is also sent.
OPCHAEServer hMode=read htStartTime=NOW-30M bBounds=TRUE
Example 2
The following source filter is used to output events logged on September 1, 2006, from 10:00
a.m. to 12:00 p.m. in "read" mode. The newest message for each OS server is output as the
first one. The limits for this time period are also sent.
OPCHAEServer hMode=read htStartTime=2006-09-01T12:00:00.000Z
htEndTime=2006-09-01T10:00:00.000Z bBounds=TRUE
Example 3
The following source filter is used to output logged alarms and events from the past 30 minutes
in "advise" mode. After reading the archived messages, newly generated messages are sent
in the same way as for an active subscription.
OPCHAEServer hmode=advise htStartTime=NOW-30M
See also
Access to logged events (Page 2733)
Syntax for accessing logged alarms using OPC (Page 2734)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2737
WinCC OPC UA Server
Principle of operation the WinCC OPC UA Server
Principle of operation
The WinCC OPC UA Server provides the following values:
Process values
Values from tag logs
The WinCC OPC UA server is installed as Windows service and started automatically. The
WinCC OPC UA server supports only the "UA-TCP UA-SC UA Binary" communication profile.
The used port number is adjustable.
Supported specifications
OPC Unified Architecture is a specification for the transmission of process values and log data,
as well as alarms and events. The WinCC OPC A&E Server supports the transfer of process
values and log data. With this constraint, the WinCC OPC UA Server conforms to OPC UA
specification 1.01.
URL of the WinCC OPC UA server
You access the WinCC OPC UA server via the following URL: "opc.tcp://[NodeName]:[Port]/
OpcUaServerWinCC".
[NodeName]: placeholder for the computer name. Is set automatically.
[Port]: Port number. The default is "4861".
Discovery Server
The "Discovery Server" is available by the OPC foundation. The "Discovery Server" is by
default installed on the HMI device as Windows service. On the "Discovery Server" via OPC
UA server UA clients information is available that is registered on the "Discovery Server".
The WinCC OPC UA server registers for Runtime-Start, depending on the configuration, on
no, one or all available "Discovery Servers" If you end the Runtime, the WinCC OPC UA server
is automatically logged off from the "Discovery Server".
Supported languages in the WinCC address area
The WinCC OPC A&E Server supports the WinCC address area in the following languages:
German
English
French
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2738 System Manual, 08/2011,
Italian
Spanish
See also
Using OPC in WinCC (Page 2706)
Accessibility of WinCC OPC servers (Page 2708)
Security concept of OPC UA (Page 2739)
OPC UA Services support (Page 2741)
Name area of the WinCC OPC UA server (Page 2742)
OPC UA Data Access (Page 2744)
OPC UA Log Access (Page 2744)
Configure WinCC OPC HDA Server (Page 2719)
Security concept of OPC UA
Introduction
The WinCC OPC UA server uses the TCP/IP protocol for data exchange. For authorization
between WinCC OPC UA server and OPC UA client certificates are exchanged. In addition,
you can encode the data transfer.
Security concept
The WinCC OPC UA server and each OPC UA client authorize themselves mutually by
exchanging certificates.
By default, the WinCC OPC UA server creates during installation a self signed instance
certificate. You can alternatively replace this instance certificate with a project-specific instance
certificate.
Note
Private key and own certificates
If you have an own certification center, you can create your own certificates and make them
available for all communication partners. In this case, delete the instance certificate created
by WinCC OPC UA server.
The instance certificate is stored in the certificate memory. Depending on the configuration of
the WinCC OPC UA server, one of the following certificate memory is used:
Certificate memory of the WinCC OPC UA server
Certificate memory of the operating system in "UA Applications" folder
In order for the WinCC OPC UA server and an OPC UA client to communicate with each other,
the certificates must be known to each other:
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2739
You use the common certificate of the operating system
Or:
You copy the certificates in the certificate memory of the participating communication
partners:
WinCC OPC UA Server
OPC UA Client
Discovery server (optional)
Security settings
The following table lists the security settings supported by the WinCC OPC UA server:
SecurityPolicy Message Security Mode
None
1
None
Basic128Rsa15
2
None
4
Sign
5
SignAndEncrypt
6
Basic256
3
None Sign SignAndEncrypt
1: The certificate exchange is switched off. Every OPC UA client can log on to the WinCC OPC UA server.
2: Certificate exchange with depth of encryption of 128 bit.
3: Certificate exchange with depth of encryption of 256 bit.
4: The data packages are exchanged after certificate check unsecured between client and server.
5: The data packages are signed with the certificates, but not encoded
6: The data packages are signed with the certificates and encoded
NOTICE
Unsecured communication between client and server possible
Use the "none" setting only for test and diagnostics purposes.
For a secure communication between client and server, use in operating mode at least the
following settings:
SecurityPolicy: Basic128Rsa15
Message Security Mode: Sign
You can deactivate the application of SecurityPolicy "none" in the configuration settings of
the WinCC OPC UA server.
User identification
For user account identification of an OPC UA client, the WinCC OPC UA server supports the
methods "Anonymous" and "User name / Password". Each user account must be known in
the user administration of the operating system of the WinCC OPC UA server.
The user identification is only used for setting up a communication session. Different access
rights are not supported.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2740 System Manual, 08/2011,
You can deactivate the support of anonymous users in the configuration settings of the WinCC
OPC UA server.
See also
Configure WinCC OPC UA Server (Page 2746)
Principle of operation the WinCC OPC UA Server (Page 2738)
OPC UA Services support
Introduction
The WinCC OPC A&E Server supports the following described functionality.
OPC UA Service Sets
The following table shows the supported OPC UA Service Sets:
OPC UA Service Sets Services Comment
Discovery Service All -
Secure Channel
Service
Session Service
All -
View Service Browse
BrowseNext
RegisterNodes
UnregisterNodes
Detect the displayed WinCC data: Process values
and log process values
Attribute Service Read
Write
only WinCC tags
only WinCC tags
HistoryRead
HistoryUpdate*
only logging tags
only logging tags
Subscription Service All only "Value" attribute of WinCC tags
MonitoredItem Service All only "Value" attribute of WinCC tags
*: With restrictions, see "Supported Write-Accesses (Page 2712)"
OPC UA profile and Conformance Units
Note
The OPC UA profiles for "Historical Access" are not yet released, that is why they are not
listed in the following:
The WinCC OPC A&E Server supports the following OPC UA profiles without restrictions:
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2741
6.5.17 SecurityPolicy - Basic128Rsa15
6.5.18 SecurityPolicy - Basic256
6.5.19 SecurityPolicy - None
6.5.21 Base Server Behaviour Facet
6.5.22 Standard DataChange Subscription Server Facet
6.5.28 Enhanced DataChange Subscription Server Facet
6.5.39 UA-TCP UA-SC UA Binary
The WinCC OPC A&E Server supports the following OPC UA profiles shown in the following
table, however with restrictions:
Profile "Group" Not supported "Conformance
Unit"
6.5.25 Core Server Facet Attribute Services Attribute Write Index
6.5.26 DataAccess ServerFacet Data Access Data Access Analog
Data Access Multistate
Data Access PercentDeadBand
Data Access Semantic Changes
Data Access Two State
6.5.35 Standard UA Server Attribute Services Attribute Write StatusCode &
TimeStamp
See also
Principle of operation the WinCC OPC UA Server (Page 2738)
Name area of the WinCC OPC UA server
Introduction
The WinCC OPC UA server provides OPC UA clients with an hierarchical name area to display
the following Runtime data:
Process values (WinCC tags and WinCC tag groups)
Data log inclusive logging tags
The name area of the WinCC OPC UA server is attached in the "Objects" default folder.
The following screen shows the name area of the WinCC OPC UA server of an active WinCC
project on the local PC ("@LOCALMACHINE::"):
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2742 System Manual, 08/2011,
1
2
3
Start node of the specific name area of WinCC.
Display of the WinCC tags; the structure corresponds to the structure of the tags in WinCC.
Display of the data log
Display of the WinCC tags
Tag groups, communication drivers and connections are displayed by OPC UA objects of the
"FolderType" type. Each of these folders has references of the "Organizes" type to the
subordinate objects and tags.
Internal and external WinCC tags are displayed by OPC UA tags of the "DataItemType" type.
If a WinCC tag is additionally logged, the displayed OPC UA tag has additionally a reference
of the "HasHistoricalConfiguration" type for a log configuration. The "Historizing" and
"AccessLevel" attributes are respectively set.
The following table shows the most important attributes of the OPC UA tags that represent a
WinCC tag. You can find the complete list of attributes in the "OPC UA Part 3 - Address Space
Model 1.01 Specification" document under "5.6":
Attribute Description Comment
NodeId Unique designation of the WinCC tag
BrowseName WinCC tag name
DisplayName WinCC tag name
Value Tag value and status
DataType OPC UA data type that corresponds to the
WinCC tag type, for example:
Int32; signed 32 bit value
UInt32; unsigned 32 bit value
-
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2743
Attribute Description Comment
AccessLevel "CurrentRead" / "CurrentWrite"
"HistoryRead" / "HistoryWrite"
correspondingly to the WinCC
tag configuration
ValueRank Always "Scalar" -
Display of the logging tags
Process values and compressed logs are displayed by OPC UA objects of the "FolderType"
type. Each of these folders has references of the "Organizes" type to the related logging tags.
Logging tags from process value or compressed logs are displayed by OPC UA tags of the
"BaseDateVariableType" type. A logging tag always has a reference of the
"HasHistoricalConfiguration" type for a log configuration.
The following table shows the most important attributes of the OPC UA tags that represent a
WinCC logging tag. You can find the complete list of attributes in the "OPC UA Part 3 - Address
Space Model 1.01 Specification" document under "5.6":
Attribute Description Comment
NodeId Unique designation of a logging tag
BrowseName Name of the logging tag
DisplayName Name of the logging tag
Description Node description
Value Not available For a logging tag, this attribute
cannot be read nor changed.
DataType OPC UA data type that corresponds to the
WinCC tag type, for example:
Double; 64-bit floating point number
UInt32; unsigned 32 bit value
-
AccessLevel "HistoryRead" / "HistoryWrite" -
ValueRank Always "Scalar" -
OPC UA Data Access
Internal and external WinCC tags are displayed by OPC UA tags of the "DataItemType" type.
Other DataAccess tag types as "AnalogItem" or "DiscreteType" are not supported.
The WinCC OPC A&E Server supports the reading access on the OPC UA tag attributes as
"DataType" or "AccessLevel". Writing access and subscriptions are only supported for the
"Value" attribute.
OPC UA Log Access
Introduction
"OPC Historical Access" enables the access to logs and includes the "Historical Data" and
"Alarms & Events" services. The WinCC OPC UA server supports only the "Historical Data"
service.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2744 System Manual, 08/2011,
The WinCC OPC UA Server offers the OPC clients access to the raw data of tag logs via
"Services".
HistoryRead (READRAW)
HistoryUpdate (INSERTDATA, REPLACEDATA, UPDATEDATA, DELETE_RAW)
You can read and limitedly write with an OPC UA client the values of logging tags in the tag
logs. Depending on the configuration of the tag log, the logging tag can contain either raw or
already processed process values.
Characteristics of logging tags
According to the OPC "OPC UA Part 11 - Historical Access 1.00 Specification" document, the
tags to be logged must have a precise reference to a tag configuration
("HistoricalConfiguration"). A process tag can be contained in WinCC and also in several data
logs. In this case the process tag is linked to one of the corresponding logging tags.
Attribute / Properties of log configurations
The following table shows the Properties of an OPC UA tag configuration of the
"HistoricalConfigurationType" type: In the "Description" attribute, the logging tag comment
configured in WinCC is displayed. You can find the complete list of attributes in the "OPC UA
Part 11 - Historical Access 1.00 Specification" document under "4.7.1.4":
Property Description / Value Comment
Definition WinCC process tag name For a process value log
Stepped True -
The following optional Properties are not supported:
MaxTimeInterval
MinTimeInterval
ExceptionDeviation
ExceptionDeviationFormat
Limitations for Service "HistoryUpdate"
You can use the Service "HistoryUpdate" only on process value logs.
The following table lists the functions supported by the WinCC OPC UA server: Which functions
are supported depends on the configuration of the WinCC OPC UA server as well as the
process value log configuration. You will find additional information in the "OPC UA Part 11 -
Historical Access 1.00 Specification" document under "5.5":
Service Function Description
HistoryUpdate INSERTDATA Insert new log values
REPLACEDATA Replace existing log values
UPDATEDATA Replace of insert log values
DELETE_RAW Delete log values
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2745
See also
OPC UA Services support (Page 2741)
Name area of the WinCC OPC UA server (Page 2742)
Supported Write-Accesses (Page 2712)
Configure WinCC OPC HDA Server (Page 2719)
Configure WinCC OPC UA Server
Introduction
Define the following in the configuration settings of the WinCC OPC UA server:
OPC HDA Server settings
Port number (Default: "4861)"
Security settings
Requirement
A project with an HMI device is open.
Procedure
To configure WinCC OPC UA server, proceed as follows:
1. Open the "Runtime settings" of the HMI device in the project tree.
2. If necessary, configure the writing access validation at "OPC settings > OPC HDA settings".
NOTICE
The "OPC HDA configuration" settings apply for the WinCC OPC HDA server as well as
for the OPC UA server.
3. Configure the server settings at "OPC settings > OPC Unified Architecture Server
configuration":
Change the "Port number", if required
Activate at least a "SecurityPolicy" and the respective "Message security mode".
NOTICE
Unsecured communication between client and server possible
Use the "none" setting only for test and diagnostics purposes.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2746 System Manual, 08/2011,
Result
The WinCC OPC UA Server is configured. If you activate the project on the HMI device, the
WinCC OPC UA server is accessible.
See also
Security concept of OPC UA (Page 2739)
OPC UA Log Access (Page 2744)
Supported Write-Accesses (Page 2712)
Basic settings for OPC (Page 2708)
WinCC OPC connection
Creating a connection to an OPC server
Introduction
If to an OPC DA server an external control is available, you can access its process values from
WinCC with the help of the WinCC OPC connection. You configure for this in the engineering
system an OPC connection to the desired OPC server. You configure afterwards WinCC tags
for the process values of the OPC server.
Requirement
The OPC server to be addressed is ready-to-operate and in the "running" status
The OPC server and the HMI device with WinCC Runtime Professional are located in a
network
Procedure
To create a connection to an OPC server, follow these steps:
1. On the HMI device, open the "Connections" editor.
2. Create a new connection and enter a meaningful name.
3. Choose "OPC" as the "Communication driver".
4. In the work area under "Parameters > OPC settings", enter the communication peer.
Select the "Type of OPC server".
Select the OPC server based on the OPC server type you chose, or enter the IP address
or name of the remote computer.
Result
The OPC connection is configured. To access data from the OPC server, you create tags.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2747
See also
Accessing process values of an OPC server (Page 2748)
Using OPC in WinCC (Page 2706)
Accessing process values of an OPC server
Requirement
The OPC server to be addressed is ready-to-operate and in the "running" status
A connection to the OPC-Server is created
Procedure
To access process values of an OPC-Server via the OPC connection, follow these steps:
1. On the configuration PC in the project navigation, open the "HMI tags" editor under the HMI
device that you use as an OPC client.
2. Create a tag with the same data type as the tag on the OPC server.
3. Select the OPC connection for "Connection".
4. Enter the "Address", or select the desired tag on the OPC server via the object list.
Result
If you launch Runtime on the HMI device, the process value from the OPC server will be written
to the tag on the HMI device via the OPC connection.
See also
Creating a connection to an OPC server (Page 2747)
Commissioning OPC
Configuring DCOM user permissions in Windows
Introduction
The OPC DA client and OPC DA server are DCOM applications, whose security settings must
be set in compliance with the DCOM security mechanisms:
The OPC DA client needs launch/activation rights and access rights for the OPC DA server.
The OPC DA server only needs access rights for the OPC DA client.
The following must be known on the PCs of the OPC DA server and the OPC DA client
respectively:
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2748 System Manual, 08/2011,
The user account for which the OPC DA client is executed
The "Simatic HMI" user group
The "Simatic HMI" user group is already created on an HMI device during installation. The
security settings of WinCC OPC DA server and the WinCC OPC channel are also
preconfigured during installation.
In order to create an additional user for the operation of the OPC DA client, add the user as a
member to the "Simatic HMI" user group.
Requirement
You have administrator rights.
Setting up a user account on PCs with an external OPC DA server or external client
On PCs without a WinCC installation, you configure the access rights manually.
1. Open Windows user administration.
2. Create the "SIMATIC HMI" user group.
3. Under "DCOM > My Computer > COM Security > Access Permissions > Edit Default" enter
the permissions "Local Access" and "Remote Access".
4. Assign the user accounts for this user group.
For additional information on granting user rights, refer to the documentation for
Windows XP / Vista / 7.
Adjusting Windows firewall settings
Introduction
After installation of WinCC, the Windows firewall settings of the WinCC OPC servers are
correctly configured.
If OPC clients access OPC servers in different subnets, you must adapt the configuration of
the permitted network areas to the OPC servers.
9.16.2 Customer controls
9.16.2.1 Overview
Introduction
Use customer controls to create and standardize complex, frequently used display objects.
Visual Studio 2005/2008 Professional .NET is used to create these.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2749
You can, for example, place several motors of a similar type in a plant. In a customer control,
you can summarize motor data such as operating mode, setpoint, actual value, rotational
speed, operational status, frequency.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2750 System Manual, 08/2011,
Hz
Frequency
Value
Setpoint
Process value
Manual Auto
Mode
1/minute
Speed
M
Operating mode
Off
On
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2751
When the customer control is finished, you can integrate it an unlimited number of times into
WinCC screens, as well as in other applications.
Central changes to the customer control are automatically adopted at all usage locations. In
this way, you can later expand a customer control with additional functionality. The changes
are effective on all customer controls of this type used in WinCC screens that are already
configured.
Target group of this documentation
This documentation is intended for design engineers with experience in VB.net or C#.
9.16.2.2 Interfaces
Introduction
To access the WinCC tag value, WinCC makes interfaces available for access to the WinCC
data provider. The connection to the WinCC data provider is established or disconnected using
methods. Methods are also used to read or write tag values synchronously or asynchronously.
Synchronous:
The customer control sends a request to the data provider for which a reply is expected
immediately. The customer control waits until a reply comes from the data provider.
Asynchronous:
The customer control sends a request to the data provider for which a reply is not expected
immediately. Sending the request and receiving the reply occur at separate times.
Interfaces
ITag
The ITag object supports the following methods:
Method Description
Register (Page 2764) Registers the customer control as a consumer at the data provider. The
consumer receives a cookie from the data provider. The cookie is used to
assign a request from the data provider to a consumer.
ReadTag
(Page 2764)
Reads the value of one or more tags at the same time
ReadTagAsync
(Page 2765)
Reads the tag value asynchronously
ReadTagCyclic
(Page 2766)
Cyclic reading of the tag values. The update cycle is used to determine how
often the value is updated.
RemoveCyclicTag
(Page 2766)
Removes one or more tags
Cancel (Page 2767) Cancels the cyclic reading of the tag values
WriteTag
(Page 2767)
Writes values to one or more tags synchronously
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2752 System Manual, 08/2011,
Method Description
WriteTagAsync
(Page 2768)
Writes values to one or more tags asynchronously
Unregister
(Page 2769)
Removes the consumer
ITagSink
The ITagSink object reacts to specific events using methods.
Method Description
OnCanceled
(Page 2769)
Occurs when the ITag method "Cancel" has ended.
OnDataChanged
(Page 2770)
Occurs when a tag value is changed by the following ITag methods:
ReadTagAsync
ReadTagCyclic
OnError (Page 2771) Occurs as an event of an error with the following methods:
ReadTagAsync
ReadTagCyclic
WriteTagAsync
OnDataChanged
OnWriteComplete
OnRemoved
(Page 2771)
Occurs when the ITag method "RemoveCyclicTag" has ended.
OnWriteComplete
(Page 2772)
Occurs when the ITag method "WriteTagAsync" has finished.
Requirement
The "Siemens.Runtime.ControlDev.dll" reference is set. For additional information, refer to
"Setting the reference "Siemens.Runtime.ControlDev.dll (Page 2755)".
Storage of file:
WinCC Runtime Professional: \Siemens\WinCC\bin
WinCC Runtime Advanced: ...\WinCC Runtime Advanced
Basic procedure
1. Create an ITag object to connect to the data provider.
2. The "Register" method is used to register the customer control as a consumer of the data
provider. The consumer receives a cookie from the data provider. The cookie is used to
identify the access by the consumer to the data provider.
3. When the connection is established, you can access the tag values using the methods of
the ITag object.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2753
9.16.2.3 Demo project
Demo project "CCITagTestLibrary"
The "<Installationsverzeichnis>SCADA-RT_V11\ControlDevelopment\samples
\VB90\CCITagTest" directory contains the demo project "CCITagTestLibrary". The various
methods of the iTag-Interfaces are used in this Demo project.
Use the demo project as a template for your own customer controls. This demo project includes
the interface to the data provider of WinCC.
To use the demo project, proceed as follows:
1. Copy the entire "CCITagTestLibrary" folder to a local destination directory.
2. Double-click on the "CCITagTestLibrary.vbroj" file.
See also
Creating and testing customer controls (Page 2754)
9.16.2.4 Creating and testing customer controls
Creating and testing customer controls
Introduction
This section shows the basic procedure for creating and testing a customer control in VB.net.
To follow the configuration steps, use a VB.net project that uses the provided
"CCITagTestLibrary" demo project as a template.
Requirement
Visual Studio 2005/2008 Professional .NET
WinCC RT Advanced or WinCC RT Professional
WinCC project for WinCC RT Professional or WinCC RT Advanced has been created. For
additional information, refer to "Editing a project".
Basic procedure
To create and test the "ITagUserControl" customer control, proceed as follows:
1. Check the reference "Siemens.Runtime.ControlDev.dll" (Page 2755)
2. Create a user interface (Page 2757).
3. Create the program code (Page 2758).
4. Create customer controls (Page 2759).
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2754 System Manual, 08/2011,
5. Test customer controls in Visual Studio (Page 2760).
6. Test customer controls in WinCC (Page 2762).
See also
Demo project (Page 2754)
Creating a WinCC project (Page 2760)
Check the reference "Siemens.Runtime.ControlDev.dll"
Introduction
To access the data provider of WinCC, the VB.net project is linked to the
"Siemens.Runtime.ControlDev.dll" library.
Requirement
Visual Studio 2005/2008 Professional .NET is installed.
A VB.net project is open. The VB.net project uses the demo project as a template.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2755
Procedure
Proceed as follows to verify the reference:
1. In Solution-Explorer, double-click the "CCITagTestLibrary > My Project" item.
The Project Designer opens.
2. Click on "References" in the Project Designer.
3. If the reference is not set, click on "Add...". In the "Add Reference" dialog, click "Browse".
4. In WinCC Runtime Professional, navigate to the directory "...\Siemens\WinCC\bin".
In WinCC Runtime Advanced, navigate to the directory "...\WinCC Runtime Advanced".
5. Select the entry "Siemens.Runtime.ControlDev.dll". Click "OK".
See also
Interfaces (Page 2752)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2756 System Manual, 08/2011,
Creating a user interface
Settings
For the configuration you require objects with the following settings:
Object Quantity Property Setting
GroupBox 1 Text ReadTag
Label 2 Text
Text
TagName
Value
Textbox 2 (Name) txtReadTagTagName
(Name)
ReadOnly
txtReadTagValue
True
Button 1 Text
(Name)
Read
btnReadTagStart
Requirement
A VB.net project is open. The VB.net project uses the demo project as a template.
The toolbox is displayed.
The properties window is displayed.
Procedure
To create the user interface, follow these steps:
1. In Solution-Explorer, double-click the "CCITagTestLibrary > ITagUserControl.vb" item. The
Form Designer opens.
2. Insert a GroupBox into the form from the tool window. Configure the GroupBox with the
settings described above.
3. Insert two text box objects into the form from the tool window. Configure the objects with
the settings described above.
4. Add two labels to the form. Configure the labels with the settings described above.
5. Add a button to the form. Configure the button with the settings described above.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2757
Result
The user interface for the "ITagUserControl" customer control has been created.
Creating program code
Introduction
To use customer control to access the WinCC tag values, implement the access to the ITag
interface.
Procedure
To create the program code, proceed as follows:
1. For access to the ITag interface, enter the following:
' ITag interface
Dim m_ITag As ITag ' get the Tagset Object from the container
m_ITag = Site.GetService(GetType(ITag))
' Connect to server
m_RegisterCookie = m_ITag.Register(Me)
1. Double-click the "btnReadTagStart" button in the Form Designer. The code window with
the "btnReadTagStart_click" subprocedure opens automatically.
2. Insert the following code between "Sub btnReadTagStart_Click" and "End Sub".
Private Sub btnReadTagStart_Click(ByVal sender As Object, ByVal e As EventArgs)
_Handles btnReadTagStart.Click
Try
Dim TagName As Object = "Tag_Test" ' name of the tag, e.g. coming from TextBox
Dim Values As Object = m_ITag.ReadTag(m_RegisterCookie, TagName)
Dim Value
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2758 System Manual, 08/2011,
Dim strResult
For Each Value In Values
strResult = CStr(Value) ' the result of the ReadTag could be written in a TextBox
(Ensabled = False)
Next
Catch ex As Exception
MsgBox("ReadTag:" & vbCrLf & ex.Message)
End Try
End Sub
Result
Access to the ITag interface is implemented and the code for the button "btnReadTagStart" is
created.
To access the ITag interface from Visual Studio, the ProgID of the data provider must be
transferred.
ProgID for WinCC Runtime Professional: CCITagControl.ITagControl.1
ProgID for WinCC Runtime Advanced: FwTagDataProvider.FwTagDataProvider
Example
' Create the TagServer Object
Dim oTagServer As Object = CreateObject("CCITagControl.ITagControl.
1")
' Set the Tagset Object
m_ITag = oTagServer
You can find the full program code in the demo project "CCITagTestLibrary.
Creating customer controls
Procedure
To create the customer control, proceed as follows.
1. Double-click the "My Project" entry in the project folder explorer. The Project Designer
opens.
2. Click on the "Compile" button in the Project Designer. Specify the destination directory for
the DLL file for "Build output path".
3. Save the change in the VB.net project "CCITagTestLibrary".
4. Select the "CCITagTestLibrary" entry in the project folder explorer. Select the "Build"
command in the shortcut menu.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2759
Result
The "ITagUserControl.dll" file is now located in the destination directory. The customer control
"ITagUserControl" will be displayed in the toolbox.
Testing customer controls in Visual Studio
Creating a WinCC project
Introduction
To test the "ITagUserControl" customer control, you will have to create the "TK_Test5" tag and
the "CC_ITagUserControl" screen in WinCC.
Requirement
WinCC project for WinCC RT Professional or WinCC RT Advanced has been created.
You have created and opened the "CC_ITagUserControl" screen.
The internal tag "TK_Test5" has been created.
Procedure
To create the WinCC project for the test, proceed as follows:
1. Add an I/O field in the "CC_ITagUserControl" screen. Link the I/O field to the "TK_Test5"
tag.
2. Add a slider to the screen. Link the slider to the "TK_Test5" tag.
3. Configure the "SetTag" system function at the "Change" event with the following settings:
Parameter Setting
Tag (output) TK_Test5
Value TK_Test5
Result
The "CC_ITagUserControl" screen has been created. The tag value in the I/O field will be
displayed when you use the slider in Runtime.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2760 System Manual, 08/2011,
Creating a test form
Introduction
You cannot test the "ITagUserControl" customer control in the Visual Studio Form Designer.
You need a test form to test the customer control.
Requirement
"ITagUserControl" customer control has been created.
Procedure
Proceed as follows to create a test form:
1. In Solution-Explorer " select the project folder "CCITagTestLibrary". Select "Add > New
Project..." in the shortcut menu. The "Add new project" dialog opens.
2. In the left window "Project types" under "Other languages > Visual Basic", select the entry
"Windows". In the right window "Templates" select the entry "Windows Forms Application".
3. Enter "TestCustomControl" as the "Name". Click "OK".
4. A test form opens. Insert the "ITagUserControl" control into the test form.
5. Double-click the "TestCustomControl > My Project" entry in the project folder explorer. The
Project Designer opens.
6. Click on "References" in the Project Designer. Verify that the reference to
"Siemens.Runtime.ControlDev.dll" has been set.
Storage of file:
WinCC Runtime Professional: \Siemens\WinCC\bin
WinCC Runtime Advanced: ...\WinCC Runtime Advanced
7. Save the project
Result
You have created the test form for testing the "ITagUserControl" customer control.
Testing customer controls in Visual Studio
Requirement
WinCC runtime is started.
Test form is created.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2761
Procedure
To test the customer control in Visual Studio, proceed as follows:
1. Start the test of the customer control with <F5>. The "Form1" form opens.
2. Enter "TK_Test5" in the "TagName" field. Click "Read".
Result
The tag value "TK_Test5" will be displayed in the "Value" field. Move the slider to change the
tag value in WinCC. The current tag value will be displayed in the I/O field. Click on "Read" to
update the tag value in the customer control.
An error message will appear if you enter an incorrect tag name in the "TagName" field.
Testing customer controls in WinCC
Adding customer control in WinCC
Introduction
To use customer controls in WinCC, you need to add them to the "My Controls" palette.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2762 System Manual, 08/2011,
Procedure
To add customer controls, proceed as follows:
1. Open a screen.
2. Select the "Select object" command in the shortcut menu of the "Tools" task card.
3. Click "Specific .Net Controls" in the "Select control" dialog. Navigate to the desired customer
control, for example "ITagUserControl", in the "Select assembly" field.
4. Select the "ITagUserControl" customer control.
5. Click "OK".
Result
The"ITagUserControl" customer control is displayed in the "My Controls" palette.
Testing customer controls in WinCC
Requirement
The "CC_ITagUserControl" screen has been created and opened.
Procedure
To test the "ITagUserControl" customer control, proceed as follows:
1. Add a "ITagUserControl" to the screen.
2. Start WinCC Runtime with the start screen "CC_ITagUserControl".
3. Move the slider. The new value is displayed in the I/O field.
4. Enter "TK_Test5" in the "TagName" field.
5. Click on the button "Read".
Result
The "ITagUserControl" customer control has been added. If you activate WinCC Runtime, the
tag value is displayed in the "Value" field.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2763
9.16.2.5 Reference
ITag methods
Register
Description
Registers the customer control as a consumer at the data provider. The consumer receives a
cookie from the data provider. The cookie is used to assign a request from the data provider
to a consumer.
Syntax
RegisterCookie Object.Register (CustomerControl)
Parameter
Object
Name of the ITag object
Customer Control
Name of the customer controls
Return value
RegisterCookie
Cookie to identify the consumer
ReadTag
Description
Reads the value of one or more tags at the same time.
Syntax
Values Object.ReadTag(RegisterCookie, TagNames)
Parameter
Object
Name of the ITag object
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2764 System Manual, 08/2011,
RegisterCookie
Cookie to identify the consumer
TagNames
Tag name
Return value
Values
Tag value
ReadTagAsync
Description
Reads the value of one or more tags asynchronously.
Syntax
Object.ReadTagAsync (RegisterCookie, TagNames, ClientCookies, CacheDevice)
Parameter
Object
Name of the ITag object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag name
ClientCookies
Cookie for identification of tags
CacheDevice
This parameter is only evaluated by WinCC RT Professional.
0 = The tag value is read from the process image (cache).
1 = The tag value is read directly from the AS.
See also
OnDataChanged (Page 2770)
OnError (Page 2771)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2765
ReadTagCyclic
Description
Cyclic reading of the tag values. The update cycle is used to determine how often the value is
updated.
Syntax
Object.ReadTagCyclic (RegisterCookie, TagNames, UpdateRates, ClientCookies,
ServerCookies)
Parameter
Object
Name of the ITag object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag name
UpdateRates
Update cycle of the tags. The value is entered in milliseconds.
ClientCookies
Cookie for identification of tags
Return value
ServerCookies
Cookie for identification of tags The return value is used by the ITag method
"RemoveCyclicTag (Page 2766)".
See also
OnDataChanged (Page 2770)
OnError (Page 2771)
RemoveCyclicTag
Description
Removes one or more tags.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2766 System Manual, 08/2011,
Syntax
Object.RemoveCyclicTag (RegisterCookie, ServerCookies)
Parameter
Object
Name of the ITag object.
ServerCookies
Cookie for identification of tags
See also
ReadTagCyclic (Page 2766)
OnRemoved (Page 2771)
Cancel
Description
Cancels the cyclic reading of the tag values.
Syntax
Object.Cancel (RegisterCookie)
Parameter
Object
Name of the ITag object
RegisterCookie
Cookie to identify the consumer
See also
OnCanceled (Page 2769)
WriteTag
Description
Writes values to one or more tags at the same time.
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2767
Syntax
Object.WriteTag(RegisterCookie, TagNames, Values)
Parameter
Object
Name of the ITag object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag name
Values
Values written to the tags
WriteTagAsync
Description
Writes values to one or more tags asynchronously.
Syntax
Object.WriteTagAsync(RegisterCookie, TagNames, ClientCookies, Values)
Parameter
Object
Name of the ITag object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag name
ClientCookies
Cookie for identification of tags
Values
Values written to the tags
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2768 System Manual, 08/2011,
See also
OnError (Page 2771)
Unregister
Description
Removes the consumer.
Syntax
Object.Unregister (RegisterCookie)
Parameter
Object
Name of the ITag object
RegisterCookie
Cookie to identify the consumer
ITag methods
OnCanceled
Description
Occurs when the ITag method "Cancel (Page 2767)" has ended.
Syntax
Object.OnCanceled (RegisterCookie)
Parameter
Object
Name of the ITagSink object
RegisterCookie
Cookie to identify the consumer
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2769
OnDataChanged
Description
Occurs when a tag is changed by the following ITag methods.
ReadTagAsync (Page 2765)
ReadTagCyclic (Page 2766)
Syntax
Object.OnDataChanged (RegisterCookie, TagNames, Values, Qualities, VarStates,
TimeStamps, ClientCookies)
Parameter
Object
Name of the ITagSink object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag names
Qualities
Quality code of the tags
VarStates
Tag status of the tags
TimeStamps
Time stamp
ClientCookies
Cookie for identification of tags
See also
OnError (Page 2771)
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
2770 System Manual, 08/2011,
OnError
Description
Occurs as an event of an error with the following methods:
ReadTagAsync (Page 2765)
ReadTagCyclic (Page 2766)
WriteTagAsync (Page 2768)
OnDataChanged (Page 2770)
OnWriteComplete (Page 2772)
Syntax
Object.OnError (RegisterCookie, TagNames, ClientCookies, Errors)
Object
Name of the ITagSink object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag names
ClientCookies
Cookie for identification of tags
Errors
Error code
OnRemoved
Description
Occurs when the ITag method "RemoveCyclicTag (Page 2766)" has ended.
Syntax
Object.Remove(RegisterCookie, ClientCookies)
Parameter
Object
Name of the ITagSink object
Visualizing processes (Professional)
9.16 Interfaces
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2771
RegisterCookie
Cookie to identify the consumer
ClientCookies
Cookie for identification of tags
OnWriteComplete
Description
Occurs when the ITag method"WriteTagAsync (Page 2768)" has finished.
Syntax
Object.OnWriteComplete(RegisterCookies, TagNames, ClientCookies)
Parameter
Object
Name of the ITagSink object
RegisterCookie
Cookie to identify the consumer
TagNames
Tag names
ClientCookies
Cookie for identification of tags
See also
OnError (Page 2771)
9.17 Migration to WinCC V11
9.17.1 Overview
Overview of the section "Migration to WinCC V11"
SIMATIC WinCC V11 offers a number of functional changes. Some functions differ from the
functions that you know from familiar environments such as WinCC V7 or WinCC flexible.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2772 System Manual, 08/2011,
This document provides an overview of the special functions and procedures in
SIMATIC WinCC V11.
These functions and procedures are fundamentally different from the WinCC V7 and
WinCC flexible version, or have a different name.
9.17.2 WinCC V7
9.17.2.1 Actions
Actions in WinCC V7
WinCC supports the use of actions for dynamic response of the processes in your WinCC
project. These actions are written in ANSI-C code. Action sequences are event-triggered.
Actions can be used to run the following background tasks independent of the screen:
Daily printout of a report
Tag monitoring
Calculations
How do I configure tasks in WinCC V11?
You configure tasks in WinCC V11 using the scheduler.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2773
You can use the scheduler to configure tasks to run independent of the screen in the
background. Actions are mapped to tasks of the function list type.
At each task, you configure exactly one function list which is processed line by line.
Alternatively, you configure a C or VB script. To start the task, you define a trigger.
For more detailed information, see:
Work area of the "Scheduler" editor (Page 2034)
Example: Reading the current user name (Page 2051)
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2774 System Manual, 08/2011,
9.17.2.2 User objects
User objects in WinCC V7
Objects of the object pallet can be combined to form a group or user object based on a multiple
selection. You can also insert a group or combined object into the project library.
In contrast to a group, a user object enables the individual customization of properties and
events that can be displayed and edited in the "Object properties" window. A user object can
be edited in Graphics Designer, similar to an individual object of the object pallet.
How do I configure faceplates in WinCC V11?
You use faceplates to create individually configured display and operating objects in WinCC
V11. In contrast to user objects, faceplates can be modified centrally.
WinCC V11 provides the "Faceplates" Editor within the project library for creating faceplates
and editing their properties.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2775
Faceplates are based on a type-instance model to support the centralized editing. You create
central properties for a faceplate in the types. The instances represent local places of use for
the types.
For more detailed information, see:
Basics on faceplates (Page 785)
Example: Configuring a faceplate (Page 809)
9.17.2.3 User administration
User administration in WinCC V7
The "User Administrator" editor is used to set up and manage user administration.
The user administrator enables the setup and management of access rights for WinCC
functions and WinCC users.
In the user administration, you can assign functions such as logon timeout, or log on using a
key switch / smart card to the users.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2776 System Manual, 08/2011,
The "User Administrator" editor is used for engineering and in runtime.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2777
How do I configure user administration in WinCC V11?
User administration in the engineering system
You manage users, user groups and authorizations centrally in the WinCC user
administration. You transfer users and user groups along with the project to the HMI device.
Users are always assigned to a group and therefore inherit the group authorizations.
User administration in runtime
You can employ a user view in a screen to manage users in runtime as well. You manage
users and passwords directly in the user view on the HMI device.
For more detailed information, see:
Form of the user administration (Page 1685)
Complex user view (Page 1714)
9.17.2.4 Direct connection
Direct connections in WinCC V7
A direct connection is used to respond to events. Whenever this event occurs in runtime, the
value of a source element is applied to a target element.
Example of the "Mouse click" event:
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2778 System Manual, 08/2011,
The fill pattern of the "Rectangle1" object is synchronized with the fill pattern of the "Circle1"
object.
A screen change is executed.
How do I configure system functions in WinCC V11?
In WinCC V11, direct connections are mapped to system functions.
You use system functions in a function list or in a user-defined function. When the event occurs,
execute the configured system functions using the function list.
When configuring a function list, select the system functions from a selection list that is sorted
by categories.
For the implementation of the direct connection, specific functions are integrated, such as
"SetPropertyByProperty".
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2779
For more detailed information, see:
System functions (Page 1743)
Configuring a function list (Page 1750)
9.17.2.5 Dynamic Wizard
Dynamic Wizard in WinCC V7
The Dynamic Wizard can be used to set up the dynamic response of an object by means of
C-script actions. When a wizard runs, prepared C-script actions such as set bit / reset bit and
trigger events are defined and saved in the object properties.
You can always edit the C-script actions in the Events tab of the object properties.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2780 System Manual, 08/2011,
How do I configure system functions in WinCC V11?
You provide objects dynamic properties in WinCC V11, for example, using system functions.
You use system functions in a function list, or in a user-defined function. When the event
occurs, execute the configured system functions using the function list.
When configuring a function list, select the system functions from a selection list that is sorted
by categories.
For more detailed information, see:
System functions (Page 1743)
Configuring a function list (Page 1750)
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2781
9.17.2.6 Dynamics dialog
Dynamic dialog in WinCC V7
The Dynamic dialog is used to configure dynamic object properties. In the Dynamic dialog,
you formulate an expression by using tags, functions and arithmetic operators.
The value of the expression, the status, as well as the quality code of the tags used in the
expression are used to generate the value of the object property in runtime.
The Dynamic dialog is used, for example, for the following purposes:
Mapping the range of values of a tag to colors.
Monitoring of individual tag bits and mapping the bit value to colors or texts.
Monitoring of a Boolean tag and mapping the tag value to colors or texts.
Monitoring the status of a tag.
Monitoring the quality code of a tag.
How do I configure animations in WinCC V11?
Dynamic object properties can be realized, for example, using animations that you configure
in the object properties list, "Properties > Animations".
These animations dynamically change the background color of an object, for example.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2782 System Manual, 08/2011,
The function "Animate property" is of particular help to you when configuring dynamic
properties for the dynamic dialog.
Simple animations are also possible via a tag connection at display and operating objects.
For more detailed information, see:
Basics on dynamization in the property list (Page 756)
Configuring a new animation (Page 735)
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2783
9.17.2.7 Working efficiently
Mass data processing in WinCC V7
The WinCC Configuration Tool is an Excel add-in. The tool enables the simple configuration
of mass data, such as tags.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2784 System Manual, 08/2011,
How do I work efficiently in WinCC V11?
WinCC enables efficient processing of process data in table editors. WinCC provides the
following corresponding functions:
Importing and exporting project data
Multiple selection
Global changes to a property
You export or import the following project data:
Recipe data records
Alarms
Tags
Text lists
Project texts for translations
Exporting and importing reduces the workload.
Instead of creating new data records, use the data you have already created in previous
projects.
For more detailed information, see:
Importing and exporting project data (Page 2062)
9.17.2.8 Structures and structure tags
Structure tags in WinCC V7
Structures are used to enable grouping of a larger number of tags and tag types that form a
logical unit.
In WinCC V7, you also create structures which you can address by their names at the tag.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2785
How do I configure user data types in WinCC V11?
In WinCC V11, user data types enable you to group a number of different tags that form a
logical unit.
You create user data types as a type and use instances of this type in the project.
User data types are project-specific data and are available for all HMI devices of the project.
You create user data types and user data type elements in the project library. User data types
must be enabled before they can be used in the project.
The configured properties of a user data type are used in the instances of the user data type.
If needed, you can change individual properties directly at the point of use, for example, at a
tag. Changes to a property at the tag do not affect the user data type created.
For more detailed information, see:
Basics on user data types (Page 1023)
Basics on user data types (Page 1023)
See also
Creating the user data type (Page 1025)
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2786 System Manual, 08/2011,
9.17.3 WinCC flexible
9.17.3.1 Libraries
Libraries in WinCC flexible
Libraries are a collection of pre-configured screen objects. They expand the number of
available screen objects and increase engineering efficiency, because library objects are
always available for reuse; there is no need to reconfigure them.
WinCC flexible enables you to create two library types:
Project library
Global library
A library can contain all the WinCC flexible objects, such as screens, tags, graphic objects, or
alarms.
How do I configure libraries in WinCC V11?
In WinCC V11, you also configure the "Project library" and the "Global library".
You can no longer store any system functions in libraries, as was the case in WinCC flexible.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2787
Both the "Project library" and the "Global library" contain the two folders, "Copy templates" and
"Types". You can create or use the library objects as a copy template, or as a type.
Copy templates
Use copy templates to create independent copies of the library object.
Types
Create instances of objects of the "Types" folder and use the instances in your project. The
instances are bound to their respective type. Changes to an instance also change all other
instances. Types are marked by a green triangle in the "Libraries" task card.
Managing the library objects
You can only copy and move library objects within the same library.
For more detailed information, see:
Libraries in WinCC
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2788 System Manual, 08/2011,
9.17.3.2 Screens and templates
Screens and templates in WinCC flexible
In WinCC flexible, you create screens that an operator can use to control and monitor machines
and plants. When you create your screens, the object templates provided support you in
visualizing your plant, displaying processes and defining process values.
The project has a template for every HMI device. You can centrally configure the function keys
and objects for your project in these templates.
Every screen based on this template will contain the function keys and objects that you
configured in the template. Changes to an object or of a function key assignment in the template
are applied to the object in all the screens, which are based on this template.
How do I configure screens and templates in WinCC V11?
In WinCC V11, you also configure "Templates" and a "Global screen" along with the "Screens".
You determine functions and objects in the template which then apply to all screens based on
this template. You can create multiple templates in WinCC.
In the "Global screen", define the elements which are independent of the template used for all
screens of an HMI device. The "Alarm window" and "Alarm indicator" objects are available for
use as global objects. For HMI devices with function keys, configure the function keys in the
"Global Screen" editor.
For Comfort Panels, you also have the possibility of configuring a "System diagnostics view"
in the global screen.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2789
Excluding the controls, the screens are displayed in runtime in the following order:
Screen
System
Global screen
Screen
Template
Layer
Layer
Layer
31 0
31 0
31 0
For more detailed information, see:
Screen basics
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2790 System Manual, 08/2011,
9.17.3.3 Scripts in faceplates
Scripts in faceplates in WinCC flexible
You configure a script in the "Scripts" tab of the "Faceplate configuration" dialog. These scripts
are only available within the faceplate.
Interconnect the script directly to the events of the objects contained in the faceplate, for
example, with the "Click" event of a button. If you use the faceplate in a screen, a faceplate
instance is generated.
How do I configure scripts in faceplates in WinCC V11?
In the configuration area of the "Faceplates" editor, you create scripts that you only use within
a faceplate type.
In contrast to WinCC flexible, WinCC V11 allows you to configure several scripts for a faceplate.
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2791
For more detailed information, see:
Example: Creating a script in the faceplate type
9.17.3.4 Synchronization of recipes
How do I configure the synchronization of recipes in WinCC V11?
You configure the synchronization of recipes in the "Recipes" editor in WinCC V11. A few terms
have changed in WinCC V11 compared to WinCC flexible.
Synchronization for Panels and RT Advanced
To synchronize recipe tags that are configured in I/O fields with the recipe view, activate
"Direct synchronization".
Disable "Direct transfer of individually modified values" to specify that the recipe tags are
automatically transferred to the controller when you edit the I/O fields.
Activate "Coordinated data transfer" to monitor the transfer of recipe data in runtime using
area pointers.
For more detailed information, see:
Synchronization of recipe data records with the PLC
Visualizing processes (Professional)
9.17 Migration to WinCC V11
WinCC Professional V11.0 SP1
2792 System Manual, 08/2011,
Using online and diagnostics functions
10
10.1 General information about online mode
Online mode
In online mode, there is an online connection between your programming device / PC and one
or more devices.
An online connection between the programming device/PC and the device is required, for
example, for the following tasks:
Testing user programs
Displaying and changing the operating mode of the CPU
Displaying and setting the date and time of day of the CPU
Displaying module information
Comparing blocks
Hardware diagnostics
Before you can establish an online connection, the programming device/PC and the device
must be physically or remotely connected. As an alternative, some devices support a
simulation mode. In this case, a connection to the device is simulated via the PLCSIM virtual
interface.
After establishing a connection, you can use the Online and Diagnostics view or the "Online
tools" task card to access the data on the device. The current online status of a device is
indicated by an icon to the right of the device in the project tree. You will find the meaning of
the individual status icons in the relevant tooltip.
Note
Some online functions depend on the range of the installed software or whether a project is
open.
Standby or hibernation of the programming device / PC
If the programming device / PC is changed to the standby or hibernation mode when there is
an online connection, all online connections are terminated. When the programming device /
PC wakes up from hibernation, the online connections are not automatically re-established.
Note that suddenly terminating an online connection can lead to loss of data or a connected
device may interrupt program execution.
WinCC Professional V11.0 SP1
System Manual, 08/2011, 2793
Performing an LED flash test
In many online dialogs you can perform an LED flash test, if the device connected online
supports this feature. When you click on the "LED flashing" button, an LED flashes at the
currently selected station. This feature is useful, for example, when you are not sure which
device in the hardware configuration corresponds to the station currently selected in the
software.
Read any additional information and learn about the possible limitations to the LED flash test
in the respective device documentation.
See also
View in online mode (Page 2795)
Using online and diagnostics functions
10.1 General information about online mode
WinCC Professional V11.0 SP1
2794 System Manual, 08/2011,
10.2 View in online mode
Online displays
After the online connection has been established successfully, the user interface changes.
The following figure shows a device connected online and the corresponding user interface:
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 Professional V11.0 SP1
System Manual, 08/2011, 2795
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 2793)
Basics of project data comparison (Page 210)
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.
Using online and diagnostics functions
10.3 Online access
WinCC Professional V11.0 SP1
2796 System Manual, 08/2011,